Terms of service
Last updated 31 July 2026
These terms cover two separate things: using this website, and how a Miramer engagement works. They are not the contract for your project — that is the written proposal you accept. Where the two differ, the proposal wins.
1. Who you are dealing with
Miramer is an automation practice based in Salem, Tamil Nadu, India, operated by Alex. Correspondence: [email protected].
2. Using this website
- Everything here is for information. Descriptions of what we build, and of what it typically achieves, are not promises about your operation — we cannot know your operation until we have looked at it.
- The price range published on this site is indicative, given so you can decide whether a conversation is worth your time. The price for your work is the one in your proposal.
- Sending the contact form creates no contract and no obligation on either side.
- The Miramer name, logo and the writing on this site are ours. Read them, quote them with attribution, but do not republish them as your own.
3. How an engagement works
- It starts with a free operations review — about 30 minutes, no cost, no obligation, and no expectation that it leads anywhere.
- We then send a written proposal: what we will build, what it costs, how long it takes, and what we need from you. Work begins when you accept it in writing.
- Scope and price are fixed at that point. If you want something outside the scope, we quote it separately rather than absorbing it quietly and reappearing with a larger invoice. If we underestimated the work, that is ours to carry, not yours.
- Every workflow is handed over with a written runbook, so that someone other than us can understand and maintain it.
4. What we need from you
- Access to the systems being automated, and one named person who can answer questions and make decisions without a committee.
- An accurate description of the process. We build what we are shown; if the described process turns out not to be the real one, the rework is chargeable.
- Your own subscriptions and usage costs — n8n hosting, AI model usage, WhatsApp Business API, Google Workspace and the like. We tell you what these will be before work starts. They are billed to you by those providers, not marked up by us.
5. Payment
- Half on acceptance of the proposal, half on handover, unless the proposal says otherwise.
- Invoices are payable within 14 days.
- Taxes are charged where applicable and shown separately on the invoice.
- All amounts are in Indian rupees.
6. Who owns what
- The workflows, configurations, prompts and documentation built for you are yours once the engagement is paid in full. Where we build inside your own accounts, they are already yours and always were.
- We keep the right to reuse general methods, know-how and components that are not specific to you. We do not reuse your data, your process, or anything that identifies your business.
- You keep every right in your own data. We claim none of it, and we do not use it to train anything.
7. Confidentiality
What we learn about your operation stays with us. We will not name you as a client, publish your logo, or describe your process publicly without your written agreement — including in case studies on this site. The same obligation runs the other way about our methods and pricing.
8. What automation can and cannot promise
This section exists because the honest version is rarely said out loud, and it is better read before the work than after.
- Automations depend on systems we do not control — WhatsApp, Google, your ERP, AI model providers. Those change without asking us, and a change can break something that worked. That is precisely why every build is handed over documented.
- AI components produce probable outputs, not certain ones. Where we use them, we design the workflow so that a person reviews the exceptions. We do not represent that any AI output is correct without review, and you should not rely on one as if it were.
- We do not guarantee a particular saving in hours or rupees. We measure what changed and report it honestly, including when it is less than we hoped.
- If we think a process is not worth automating, we say so before you spend anything.
9. Correction after handover
For 30 days after handover we fix, at no charge, anything that does not work the way the proposal said it would. Changes you want beyond that, and repairs needed because a third-party system changed, are agreed and quoted separately.
10. Limits of liability
- Our total liability arising from an engagement is limited to the fees you have paid for that engagement.
- We are not liable for indirect or consequential loss — lost profit, lost business, or loss of data held in systems we do not operate.
- Nothing in these terms limits any liability that cannot lawfully be limited under Indian law.
11. Ending an engagement
Either of us may stop, in writing. You pay for the work completed to that point; we hand over what has been built and its documentation. Nothing is held back as leverage — a client who wants to leave should be able to.
12. Governing law
These terms and any engagement under them are governed by the laws of India, and the courts at Salem, Tamil Nadu have jurisdiction.
13. Changes to these terms
The website terms may change; the date at the top tells you when they last did. The version that governs your engagement is the one in force on the date of your proposal, and it does not change underneath you.