Ask anything in one sentence

One fixed price for the whole build, set when you sign off the three-day prototype and its scope list. Our usual size of build is ₹3 lakh to ₹5 lakh: an entire system, built end to end and running in production. That is a guide, not a quote.

You make a set-up payment of ₹20K-50K at sign-off, which is deducted from the price, and pay the rest once, after your acceptance test passes.

How pricing works

One thing: a set-up payment of ₹20K-50K at sign-off. It covers the AI usage and the servers your build runs on, and it is deducted from the fixed price.

Discovery and the first prototype, with two revisions, are free, and the rest of the price is due only after your acceptance test passes.

How the price works

In two parts. At sign-off, a set-up payment of ₹20K-50K, deducted from the fixed price. Then the rest, once, after your acceptance test passes.

There are no other payments along the way: no day rates, no milestone invoices, no billed meetings. Discovery and the first prototype, with two revisions, are free.

How the price works

Yes. The 30-minute call, discovery and the first prototype, with two revisions, are free. The first payment is the set-up payment at sign-off, once you have clicked through the prototype and agreed the scope list.

Only if you ask for something outside the scope list. Each change request is written down, priced as a fixed item and built only on your yes.

A bug found during your acceptance test is never a change request, and the price does not change, however long the build takes us.

Anything beyond the agreed prototype is a change request: written down, priced as a fixed item before work starts, and built only when you say yes. Small ones are often free; we say which.

Examples: a WhatsApp reminder the day before each appointment, a second user role with its own screens, an export of the monthly report to Excel.

Example change requests

Yes. The prototype fixes a first scope and its price. Later additions are change requests, each priced as a fixed item before work starts, or a new build on the same terms.

If your traffic outgrows the standard hosting, the extra hosting is passed on at cost.

More, because the price rises with complexity. The model does not change: a larger system is still one fixed price, set at prototype sign-off, with a set-up payment then and the rest paid once, after your acceptance test passes.

Yes, we can talk about it. Our usual size of build is ₹3 lakh to ₹5 lakh, and that is a guide, not a quote: your own price is fixed when you sign off your prototype.

Tell us what you need

Outside the fixed price:

• Changes you ask for beyond the scope list, each priced as a fixed item before work starts.
• Third-party fees, passed on at cost with nothing marked up: AI models (LLMs) and voice models once the system is live, SMS and WhatsApp charges, third-party licences, and hosting above the standard size if your traffic needs it.
• Moving data from an old system, where the old data is the problem: scoped during the 3-day prototype and priced separately if it is large.
• Maintenance and the production server after the first 6 months, from ₹3K a month.

The build itself, its testing, the security review and the first 6 months of hosting and support are inside the fixed price.

What the price covers

Everything from the first call to the hosting after go-live:

• Scoping and design
• A working prototype in 3 days
• Development
• Automated testing on every change
• A security review before go-live
• Deployment
• Hosting and support, free for the first 6 months
• The hand-over: the code, its tests, the documentation and the runbooks

What every build includes

A conventional build is priced by how many people work on it and for how many months, and much of that time goes on coordinating and waiting. Here, one expert directs a team of AI agents that write and test the software in parallel, so the calendar holds more building and less waiting.

The saving is not a discount. It is the cost of not paying for the waiting.

Where the saving comes from

Yes. Hosting, nightly encrypted backups, security updates and fixes for anything that stops working as agreed are free for the first 6 months.

After that, the price for maintenance and the production server starts from ₹3K a month. If your traffic grows beyond the standard set-up, the extra hosting is passed on at cost.

After go-live

No. A build is one fixed price: no day rates, no charge for each user, no milestone invoices and no billed meetings.

Discovery and the first prototype, with two revisions, are free.

Start with discovery. We work it out with you until there is a scope a prototype can be built from. It is free, and so is the first prototype, with two revisions. Once it is clear what done looks like, we set one fixed price.

If you already know what you need, you skip it and start at the prototype.

How the price works

No GST is added, and the prices are in Indian rupees (INR).

Any mode of payment is welcome. When you pay is set: a set-up payment at sign-off, and the rest once, after your acceptance test passes.

How the price works

If you want to stop, or want money back, we talk it through and come to an agreement together.

The only payment before your acceptance test is the set-up payment at sign-off; the rest of the price is not due until the test passes.

A working prototype in 3 days, and the finished system in 1 month, tested and security-checked. The price does not change, however long the build takes us.

The six steps

The price does not move. It was fixed at sign-off, and nothing more is invoiced until your acceptance test passes.

During the month you have a working link that updates every few days, so nothing is a surprise at the end.

The risk register

1. A 30-minute scoping call. Nothing due.
2. A working prototype in 3 days, with two free revisions. Nothing due.
3. Sign-off and one fixed price, with a set-up payment of ₹20K-50K that is deducted from it.
4. The production build, in 1 month, with a security review before it goes live.
5. Your acceptance test. You pay the rest once it passes.
6. Hosting and support, free for the first 6 months.

Every step in detail

A 30-minute conversation, and it is free. You describe what you need and who will use it. We say whether it is a fit and what the three-day prototype will show. If software is the wrong answer, we say so on this call.

To ask for one, email us the times that suit you at hello@aikameva.in.

Tell us what you need

A real, clickable version of your system on a link you can open: every screen your users will touch, on sample data, with the rules written beside each screen as the agreed scope list.

You click through it and tell us what to change; two revisions are free. It fixes the scope and the price, and nothing is due for it.

Every step in detail

Then it did its job three days in, not three months in. You tell us what to change and we revise it: two revisions of the first prototype are free. Then we fix the scope list, and only then is anything paid or built.

No. There is no technical brief to write. You describe what you need and who will use it, and bring the files you already have.

The three-day prototype turns that into the scope list: the rules written beside each screen. You agree the prototype and the list at sign-off, and they are the contract the price is fixed to.

You and your team test the finished system against the scope list you signed off. If it passes, you pay the rest of the fixed price. If it does not, we fix it and you test again.

We help you write the test list, and you decide what done looks like. A test only catches what it checks, so the list is worth writing with care.

We fix it and you test again. The rest of the price is not due until it passes. Bugs found in your test are ours to fix; new wishes are change requests.

Most of the work is ours. Your part is three things:

• A few hours in the first three days, on the scoping call and while you click through the prototype.
• The documents and files you already have: price lists, spreadsheets, the forms your team fills in.
• A few days at the end of the month for your acceptance test.

What we need from you

No. You describe what you need, use the three-day version, and tell us what is right and wrong about it. There is no technical brief to write and no server to buy: we design it, build it, test it, host it and look after it.

You get a working link that updates every few days, so nothing is a surprise at the end. You watch it grow and comment on the link.

Every step in detail

Whatever your business needs built. Most small companies and start-ups come to us for one of these:

• Workflow automation
• Agentic AI
• Machine learning
• Websites and web apps
• Dashboards and reports
• Data and connections

The list is not the limit. Tell us what you need, and if software is the wrong answer, we say so on the first call.

What we build, in detail

Yes. Workflow automation is the daily work in one system, instead of spreadsheets, paper and WhatsApp chats:

• Inventory and stock management
• Orders and deliveries
• Bookings and appointments
• Customer records
• Quotations and invoices
• Approvals and task tracking

We start from the files you already have: your Excel sheets, price lists and forms.

Your business on one system

AI agents that do the legwork and hand you the result to check. For example:

• Lead generation: an agent finds businesses that fit your kind of customer and lists them for you.
• Research on companies, markets and data, with a summary that shows its sources.
• Answering customers on WhatsApp from your own price list, handing over when unsure.
• Answering questions from your own documents, with the page each answer came from.
• Follow-ups and reminders for payments, renewals and appointments.
• Reading invoices, forms and emails and entering the details, ready for you to check.

What we build

Yes. It answers your customers on your own WhatsApp number, from your own price list, and books appointments only into slots that are really free. It hands over to a person when it is unsure.

Our own booking and enquiry receptionist works this way. It is in early access with a few clinics and car detailing shops.

Our work

Yes. You ask in plain words and get the answer, with the page it came from. When the answer is not in the approved material, the system says so and routes to a person rather than guessing.

It can also sit inside your own product, answering your users from your own material and showing where each answer came from.

The six areas, in detail

Yes. Forecasts and predictions from the data you already have:

• Sales and demand forecasting
• What to restock, and when
• Customers likely to leave, or to buy again
• Scoring leads by how likely each is to become a customer
• Spotting unusual transactions, such as a bill entered twice

What we build

From a company website to the first version of your product:

• Company websites
• Online catalogues and booking pages
• Customer portals, where each customer signs in and sees their own orders and documents
• Internal web tools your team opens in a browser
• A start-up's first product, with sign-in and an admin console

What we build

Yes. A working version in 3 days, on a link you can show customers and investors, and the first live release in a month: sign-in, the core workflow and the admin screens your team runs it from.

The first release is the real system, not a demo to rebuild later, and it is made to take more users and more data as you grow. It is built with open, widely used tools, so it can run on any cloud you choose, or on your own servers.

The code is yours on payment, with its tests, documentation and runbooks, ready for the developers you hire later.

Your first product

Yes. Your numbers in one place, with recommended actions: sales and stock by branch, daily and monthly reports ready on time with no copying and pasting, and one set of numbers for the head office and every branch.

The reports can be built from the Excel sheets you already fill in.

What we build

Yes. Your existing data is brought in, cleaned up and connected:

• Your Excel sheets imported, with an undo if it was the wrong file
• Duplicate records merged into one clean record
• Data moved out of an old system and checked against it
• The tools you already use, such as a POS or a payment gateway, linked to your system through their APIs
• Your own WhatsApp number connected to your system

Where the old data is the problem, we scope it during the 3-day prototype and price it separately if it is large.

What we build

Yes. A tool that has an API can be connected to your system: a POS, a payment gateway or any other tool with one. We also import your Excel sheets and connect your own WhatsApp number.

For a particular tool, tell us which one.

Data and connections

No. We build websites and web apps, not Android or iOS apps.

Questions

One of our client builds is a voice agent that makes collections calls. It calls a lender's overdue customers, talks it through as a person would, sends a payment link while they are still on the line and records any promise to pay.

It speaks English today and is shown as a live demo on sample data.

Our work

Small teams with no IT department, who need software that works and someone to keep it working: clinics, shops, service businesses, distributors and start-ups alike, wherever the work lives in spreadsheets, on paper and in WhatsApp chats.

You do not need to know anything technical.

Who we build for

We build whole systems for one fixed price. That rules out a few kinds of work:

• A fixed-price build where nobody can yet say what done looks like. That starts with discovery, which is free, until the scope is clear.
• Supplying people by the hour to join another team.
• A project where software is the wrong answer. We say so on the scoping call.

What we do not take on

Yes, we can have a look at it. Whether the existing software can be reused is decided case by case, once we have seen it.

Not marketing or branding. IT support we give only for products that are on a maintenance contract (AMC) with us.

What we build is software: workflow automation, agentic AI, machine learning, websites and web apps, dashboards and reports, and data and connections.

By default we host it for you, on a small virtual machine that we set up, run and look after, so there is nothing for you to buy or manage. For Indian clients the default is a server in India.

If your data has to stay in one region, or you want the system on your own cloud or servers, we set it up there instead.

Where it runs

Yes. The system can run in your own cloud or on your own servers; that is a normal set-up for us. The build, the tests and the security review stay the same. What changes is where the system lives and how it is reached, and the hosting line in the price changes with it, not the month.

A fully air-gapped set-up, with no connection to outside networks, is possible too. It is more work than a cloud build, and we say what it costs before you commit.

Where it runs

On a server in India by default, under the DPDP Act, India's data protection law, or wherever you require. It is not used to train any model, and it is backed up nightly.

One client's data is invisible to another, enforced by the database itself, and every build gets a security review before it goes live.

Your data

This site sets no cookies, shows no advertising and runs no analytics. What you type in this box stays on your own device, and closing the tab clears it.

There is one exception: if there is no written answer and you choose to send your question to a person, your question and the email address you give are sent to our inbox through a mail-forwarding service, FormSubmit. What you send us is used to reply to you, and for nothing else.

Privacy notice

No. Your data is not used to train any model. Where it lives is where you decide; for Indian clients the default is a server in India.

Your data

Yes. Backups are encrypted and pushed offsite every night, and the restore is rehearsed before go-live. The backup and restore procedure is part of what you receive at hand-over.

After go-live

Yes. Deletion on request is a procedure, not a negotiation.

Your data

Before every production deployment, the build goes through a security review. We review the whole repository and test the running system, with a deliberate attempt to break in, across the same eight areas every time, from how people sign in to what answers from outside.

Each finding is reproduced where it can be, fixed, and covered by a test that catches it if it ever comes back. It is inside the fixed price.

It is our own review, not an independent certified audit. If you need one, an outside tester can be brought in.

What every security review covers

The same eight areas on every build, checked in the code and against the running system:

• Authentication and sessions
• Tenant isolation: one client's data invisible to another, enforced in the database
• Authorisation on every route
• Input handling: uploads, URL ingestion, tokens and oversized bodies
• Secrets: keys separated by purpose, sealed at rest, nothing in the repository
• Public endpoints: rate limits and budgets
• Dependencies, pinned and hashed
• Deployment: headers, exposed ports, and what answers from outside

What every security review covers

Every finding is written up the same way: its severity (blocker, high, medium or low), how it was reproduced, the change that closes it, the guarding test that failed before the fix and passes after it, and what is still open, with an owner, the risk it carries and a mitigation plan.

The launch-readiness audit that follows lists every finding to closure, by date.

What the report contains

Yes, it can use your own sign-in service. Every security review checks how people sign in, and how their sessions are handled.

None yet. We are a small company, and our work speaks for us. Right now we are not in a position to take on the cost of certification; we intend to in future.

What stands today: for Indian clients the default is a server in India, under the DPDP Act, India's data protection law, and every build gets a security review before it goes live. That review is our own, not an independent certified audit; if you need one, an outside tester can be brought in.

The security review

The system runs on hosting we set up and look after, with nightly encrypted backups, security updates and fixes for anything that stops working as agreed. That is free for the first 6 months; after that, the price for maintenance and the production server starts from ₹3K a month.

New features are change requests, priced before any work starts.

After go-live

For clients on support, we are a call away. Support covers the hosting, nightly encrypted backups, security updates and fixes for anything that stops working as agreed.

Support after go-live

By default the system runs on a small virtual machine we look after. If your traffic outgrows the standard hosting, the extra hosting is passed on at cost.

Additions to the system itself are change requests, each priced as a fixed item before work starts.

Where it runs

You do, on payment. You receive the repository with its tests, the documentation, the runbooks, the build log and the backup and restore procedure, so your own developers can take over whenever you like.

The hand-over

The code we write for you is your intellectual property (IP), and it is yours on payment. Reused components keep their own licences.

The hand-over

No. The code is yours on payment, and the hand-over is the repository with its tests, the documentation, the runbooks and the restore procedure, so another team can run it. Your own developers can take over whenever you like.

The hand-over

When your acceptance test passes and you pay, the code is yours. You receive:

• The repository, with its tests and the instructions to run them
• The documentation
• The runbooks: written step-by-step procedures for running the system
• The build log, dated
• The backup and restore procedure, rehearsed

The hand-over

Aikameva Labs builds software for small companies and start-ups, end to end. One expert with a decade of domain experience directs a team of AI agents and reads every change. We are based in India.

We publish the method, not the person, because the method is what you are buying. You meet the expert on the scoping call, and their name is on your contract.

How we build

We are training more experts, and there are already people who run production work with the digital twin, a written memory of how the expert works and what has been decided.

If work stops mid-build, the rest of the price is not due. Once it is live and paid for, the repository, runbooks and restore procedure are already yours, with the instructions another team would need to run it.

The risk register

The company is new; the method and the work are not. Our own booking product went from first commit to an audited deployment in six weeks, with 1,685 automated tests passing.

And apart from the set-up payment, you pay nothing until the system passes your own acceptance test.

Measured on our own product

Seven pieces of work. We describe them rather than name them, because we do not name clients:

• A booking and enquiry receptionist on WhatsApp (our own product)
• An inventory and forecasting system for a retailer (client build, being built now)
• An investor radar built on traceable data (client build)
• A voice agent that makes collections calls (client build)
• A forecasting workbench with what-if scenarios (client build)
• An AI workbench for staff across departments (our expert's enterprise work)
• A salesperson that works over WhatsApp (client build, being built now)

Our work

Yes. Our own booking and enquiry receptionist and a collections voice agent, a client build, are shown as a demo, and for most of the other pieces of work you can ask for a walkthrough. Ask through the contact form.

For your own system, the three-day prototype does that job: a working version on a link, with nothing due for it.

Tell us what you need

Measured on our own booking and enquiry receptionist, which went from first commit to deployment in six weeks:

• 1,685 backend tests and 48 calendar tests passing on 14 Sep 2026
• 8 simultaneous bookings for one slot end with exactly 1 booking
• 12 to 75 ms to acknowledge the webhook, against Meta's 5,000 ms limit
• A go-live audit of 33 findings, all closed
• 219 commits by one author, 13 Aug to 25 Sep 2026

Measured on our own product

Aikameva Labs is based in India. The work starts with a 30-minute call, and you follow the build on a working link that updates every few days.

For Indian clients the default is a server in India; elsewhere, the system is hosted in the cloud inside the region your data has to stay in.

Where it runs

Yes, on request. The work starts with a 30-minute call, and you follow the build on a working link that updates every few days.

Write to hello@aikameva.in with a few lines on what you need, or use the contact block on the homepage. A person reads every message and replies within one working day, with whether it is a fit and what the three-day prototype would show.

For a 30-minute call, email us the times that suit you. Or ask here: if there is no written answer, leave your email address and your question goes to the same person.

The six-question fit check answers that in two minutes, with no email needed; the answer appears on the page and goes nowhere else.

Or tell us what you need on a 30-minute call. We say whether it is a fit, and if software is the wrong answer, we say that too.

The fit check

Of the sixteen risks in a project, ten move to us, two are shared and four stay with you.

You see a working prototype in 3 days before anything is agreed, the price is fixed at sign-off, and apart from the set-up payment nothing is invoiced until the system passes your own acceptance test. What stays with you: your team's time, third-party fees, messy old data, and writing the acceptance test with care.

The risk register

No, we are not hiring.

One expert plans the work. A team of AI agents builds it at the same time. The expert checks every piece before it is kept, machines test it on every change, and before it goes live we try to break in.

Then we host it, look after it, and hand you everything.

How we build

Yes. The expert reads every change the agents produce before it is kept. A finding is acted on when it is reproduced, not when it is argued, and what was removed is recorded.

One reviewer can miss things, so tests, database constraints and the security review sit behind the review.

Technical questions

No. Deployment needs a human's click. Before that, the expert reads every change, automated tests run on every change, and a security review runs before every production deployment.

The workflow

Tests are written with the code and run on every change, and agents also play your users, with the questions people actually type. Then your own acceptance test has the last word.

Our own booking product carries 1,685 backend tests. You receive the test suite in your repository and can run it yourself.

How we build

It is designed for. Deterministic paths answer first. Every answer an AI system gives carries its sources, and when the answer is not in the approved material the system says so and routes to a person rather than guessing.

Technical questions

Whichever is right for the constraint, chosen per project on measured results, not brand. We build bring-your-own-model where we can, and licence terms are checked as part of the choice, not after it.

That is about the models inside your system. For the building itself we use Claude Code, Anthropic's coding agent.

Technical questions

Our own booking and enquiry receptionist runs on FastAPI, a React console, PostgreSQL, Redis, MinIO, Keycloak, and Prometheus with Grafana, on a small virtual machine. For documents and search it uses Docling, and Infinity serving bge-m3 and bge-reranker-v2-m3.

The repository you receive runs on Linux, with its tests and the instructions to run them. For what your own build would use, send your question to a person.

The stack