The playbook · Our full method
PublicMost firms keep their method secret. Here is ours.
This is the exact sequence we run on every deployment — what happens each week, what we need from you, what the day-7 demo contains, how pricing works, and how you leave. No mystery, no fine print. Read it, then decide if you want an engineer on your floor.
The sequence
Eight weeks, logged in advance
Every job runs the same log. The dates change; the entries don't.
Before
The quote. One conversation. We scope the job, you get a fixed quote in writing — a deployment fee and a monthly run fee. Two numbers, before anything starts. They don't move.
Day 0
Arrive.
An engineer arrives at your premises. Not a salesperson — the person who will write the code. They take the chair, plug in, and start watching how the work actually happens.
Day 1–6
Watch. Build.
Mornings on the floor, afternoons building. The engineer follows the work, not a brief — the front desk, the billing register, the machines, the WhatsApp groups. What actually slows you down shows up here, not in a requirements document.
Day 7
Demo.
A working demo — on your data, in your process, shown to the people who'll use it. Not slides, not mockups. If it doesn't convince you, the engagement ends right there.
Week 1–3
Production.
The demo becomes a production system your team actually uses. We run it alongside your existing process until your people trust it, and we train them on the floor — not over a call.
Week 8
Prove.
The result shows up where it counts — your numbers, not a slide deck. Whatever we agreed to move on day 0, we measure it together and put it on the card.
After
Runs without us.
We build it with you, then it runs without us. Your data stays yours — exports included. No dependency, no lock-in, no retainer hostage. The run fee keeps it hosted and maintained, and you can stop any time.
END OF LOG · NEXT ENTRY: YOURS
REV 1 · ISSUED JUN 2026
Requisition
What we need from you
The whole list. If the third item makes you hesitate, that's worth knowing before day 0 — the method doesn't work without it.
REQ-1
A chair
A seat where the work happens — reception, shop floor, back office. Not a conference room. The engineer needs to see the real thing, not hear about it.
REQ-2
A power socket
We bring the laptop and everything on it. Your socket, your existing internet — a Jio hotspot is enough. Nothing to install, nothing to buy.
REQ-3
The people doing the work
Thirty minutes a day with the people who actually do the job — the receptionist, the operator, the billing clerk. Not just the owner. They know where it hurts.
Acceptance
Exactly what the day-7 demo contains
A demo you can't verify is a sales pitch. So here's the checklist — hold us to every line.
Item 1 of 5
Working software on your real data.
Your patients, your machines, your invoices — loaded and live. No sample data, no lorem ipsum.
Item 2 of 5
One core workflow, end to end.
The one that hurts most — picked with you in week one. It works from start to finish, not in fragments.
Item 3 of 5
A walkthrough on your premises.
Run by the engineer, in front of the people who'll use it. They click the buttons, not us.
Item 4 of 5
The week-3 plan, in writing.
Exactly what the production system will include, and what it won't. One page.
Item 5 of 5
The number we intend to move.
Missed appointments, machine hours, collection days — named on day 7, measured at week 8.
NOT ON THE TABLE
Slide decksMockups or 'visions'A discovery reportA sales pitch
Commercials
How pricing works
Two numbers, quoted in writing before day 0. We'd rather lose a job to an honest quote than win one with a vague estimate.
Fixed deployment fee
Covers the engineer on your floor, the build, training your team, and the week-8 measurement. One number, quoted in writing before day 0.
Monthly run fee
Keeps the system hosted, maintained and fixed — including the messaging bills. One predictable number every month. No surprises, and you can stop any time.
The exact ₹ depends on scope. A clinic’s front desk is not a five-machine shop floor. So we scope first, quote before day 0 — and the quote doesn’t move. Not at week 3, not at week 8.
YOU WILL NEVER BE BILLED FOR
- Hourly rates
- Discovery-phase invoices
- Change-request charges
- Renewal 'renegotiations'
Exit
How you leave
A method you can't exit isn't a method — it's a trap. Ours is built so that staying is a choice you make every month.
CLAUSE E-1
NO LOCK-INWalk away after the demo. You owe nothing.
If the day-7 demo doesn't show you money, say so. We pack up, shake hands and leave — and you owe nothing for the week, the demo, or the engineer's time.
CLAUSE E-2
Leaving later is just as easy.
Once live, the run fee continues only while you want the system. Stop it, and your data leaves with you in a standard export. No exit charges, no held-hostage records.
SIGNED · FWDDEPLOY, BENGALURU
YOURS · AFTER THE DEMO, NOT BEFORE
Next entry · Your floor · Open
You've read the method. The next log is yours.
A chair, a power socket, and the people doing the work. That's all day 0 costs you.