Terms of service

Miramer is the trading name of Miramer AI Technologies, an automation practice based in Salem, Tamil Nadu, India. GSTIN 33AXDPJ6338E1ZQ. Correspondence: alex@miramer.in.

• 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.

• 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.
• A proposal is valid for 30 days from its date. After that we may need to requote, because third-party costs and our own prices are reviewed periodically.
• 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.

• 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. We tell you what these will be before work starts. They are billed to you by those providers, not marked up by us.

The schedule follows the value of the work. Your proposal states which of these applies before you accept it.

• Production work does not begin until both the initial payment and the access we need are in hand.
• Prices exclude applicable taxes.
• All amounts are in Indian rupees.

• 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.

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.

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.
• If we think a process is not worth automating, we say so before you spend anything.

Automation work carries a 30-day defect warranty from acceptance. It covers defects measured against the acceptance criteria agreed in your proposal — a narrower thing than everything that might later be wanted, and better said now than when you ask.

• One structured acceptance cycle is included. Changes after that are handled as change requests, each with its own price and timeline. A new feature is not a revision, and a new integration is not a bug fix.
• The warranty does not cover new features or new requirements, new integrations or new document types, scope changes, a change made by a third-party platform, changes you make to the configuration, third-party price changes, or errors caused by data or actions on your side.
• When the warranty ends you move to a support plan or to per-incident support. There is no indefinite free support.

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.

These terms and any engagement under them are governed by the laws of India, and the courts at Salem, Tamil Nadu have jurisdiction.

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.