The business runs on spreadsheets
Orders in one file, stock in another, approvals in a WhatsApp group. Nobody has a reliable view of anything, and month-end turns into detective work.
New 5-Day Prototype Sprint, ₹15,000 flat
I build the software your business runs on.
I'm Mohit Sehgal. For 13 years I've built custom systems for Indian companies, and most of them start the same way: five days, one working prototype, ₹15,000 flat.
- 13 years writing production software
- I review everything that ships
- Fixed scope, fixed price
Engagement
5-Day Prototype Sprint
Flat fee
₹15,000
- Day 1
See how the work actually happens today
- Day 2
Pick the one thing worth proving
- Day 3
Build the core workflow
- 4Day 4
Sort out roles, approvals and exceptions
- 5Day 5
Hand over the prototype and the numbers
By Friday you have something real to click through and put in front of your team, with a price on the full build. Then you decide.
Working with teams of 10 to 100 in
- Manufacturing
- Distribution
- Healthcare
- Education
- Professional Services
- Logistics
The starting point
You've probably hit one of these.
Almost nobody calls me because they want software. They call because someone on the payroll is spending their week on work that a computer should have handled.
Off-the-shelf software half fits
You bought a product shaped around somebody else's process. Now you're paying people to work around the gaps, the licence renews higher every year, and the fit hasn't improved.
Good ideas wait months
A customer portal. A quotation flow that doesn't need three emails. Everyone agrees it should exist. It sits there because nobody wants to sign off a big budget on a hunch.
I build the piece that's missing and automate the part that repeats. Whatever already works, I leave alone.
How most projects start
The 5-Day Prototype Sprint
Five working days to turn your idea into something you can actually use. One fee, agreed up front, and nothing that runs on past Friday.
₹15,000 flat fee · 5 working days
Most software budgets get signed off before anyone has seen a single screen. Five days is usually enough to find out whether the idea holds up, and what building it properly would really cost you.
- A working prototype on a private link you can share
- The main workflow clickable end to end
- A written scope and a fixed price for the full build
- My recommendation, including the times I say the build is a bad idea
How the week runs
- 1
Sit with the people doing the work
I map how the process runs today, including the bits nobody has written down because they live in one person's head.
- 2
Agree what to prove
We pick the single workflow that settles whether this idea is worth building, and I write down what the prototype has to demonstrate.
- 3
Build the core
The main flow, working end to end, with your real data and your terminology on screen. No placeholder text.
- 4
Handle the edges
Roles, approvals, exceptions. This is the material that usually surfaces three months into a project that was scoped badly.
- 5
Hand over
I walk you through what I built, tell you what I think is worth building next, and give you a costed plan for the full system.
Your team needs about two hours all week. One session on Monday, one review on Friday. I handle everything in between.
Solutions
Sorted by what you're trying to get done.
Find the outcome you need this quarter. Tell me about it and I'll say whether software is really the answer, or whether you'd be better off fixing the process first.
Build new products
Test the idea before it turns into a budget line. I build the smallest version that answers the question, and if the answer is good, we grow it into the real thing.
- Validate business ideas
- Prototype development
- Custom software
- Mobile apps
Sell better
Close the gap between an enquiry landing and an order being confirmed. Quotes go out the same day, and you can see where every deal actually stands.
- Quotation software
- Customer portals
- Sales automation
- CRM that fits
Automate operations
Get the repetitive work off your team's plate. Data entry, status updates, the report somebody rebuilds by hand every Monday morning.
- Internal tools
- Workflow automation
- Dashboards
- Business systems
Support customers
Routine questions get answered at 2am without anyone being awake. The ones that need a human reach your team with the background already gathered.
- Chat assistant
- Booking assistant
- Knowledge assistant
- Support workflows
Why me
Speed from the tools, judgement from 13 years.
Anyone can generate a lot of code quickly these days. The harder question is whether what came out will survive contact with your business, and that part I learned the slow way.
How I use AI
AI gets me through the routine parts of development far quicker, which is the only reason a prototype takes five days now and not five weeks. What it can't do is tell me what's worth building, how the thing will behave under real load, or where it'll quietly fall over in year two. I still read every line before it reaches you.
I read every line that ships
Nothing goes out on autopilot. When I bring in help on a bigger build, the architecture, data model and security are still mine to sign off.
Real systems, real industries
Healthcare, education, ERP, CRM, HRMS. Some of what I built years ago is still in daily use, which is the only test of this work that counts.
Fixed scope, fixed price
You know the cost and the date before I start. There's no hourly meter running and no invoice at the end that you didn't expect.
You own everything
Code, data, hosting and accounts stay in your name. Take it in-house whenever you want to.
Selected work
Systems that changed how a business runs.
Four projects from the last few years. I've described what each one replaced, because that's the part a client can actually verify.
- Years building software
- 13
- Industries I have built for
- 8
- Modules in a single platform
- 50+
- To a working prototype
- 5 days
Healthcare
Clinic and pharmacy platform
Over 50 modules covering doctors, hospitals and pharmacies. Patient records, appointments, billing and stock all sit in one system, used by clinics in several states.
Replaced separate billing, records and pharmacy software
Media operations
Custom ERP for a growing agency
Projects, resourcing, approvals and delivery tracking moved into a single system. The spreadsheet stack and the email approval threads it grew out of are both gone.
One system in place of nine spreadsheets
Sales operations
CRM integration for a US software team
Their CRM and their product database had no connection, so reps typed every lead twice. I wired the two together and put the full customer history on one screen.
Reps stopped double-entering every lead
Immigration services
Case management system
Document checklists, stage-wise ownership and status updates that go out to applicants on their own. Nobody has to chase a file to find out where it is.
Ended the daily "where is my application" calls
Industries
I probably already know how your business works.
Every industry has its own vocabulary and its own awkward exceptions. If I've worked in yours before, that's a few weeks of explaining you don't have to do.
Manufacturing
Production tracking, job cards, machine and material planning, dispatch and stock visibility.
Distribution
Order taking, pricing and schemes, dealer portals, credit limits and collection follow-up.
Healthcare
Patient records, appointments, billing, pharmacy stock and compliance-ready reporting.
Schools & education
Admissions, attendance, fee collection, timetables and parent communication.
Professional services
Client onboarding, matter and task tracking, document management, time and billing.
Logistics
Trip and fleet tracking, proof of delivery, freight billing and customer visibility.
Agencies
Project pipelines, retainer tracking, approvals, resourcing and client reporting.
Multi-location teams
One version of the truth across branches, with role-based access and consolidated reporting.
Questions
What people ask me before they start.
If your question isn't here, email me and I'll answer it. I'd much rather sort out a doubt now than have it surface halfway through a build.
What exactly do I get for ₹15,000?
A working prototype of one core workflow, on a private link you can click through and show your team. With it comes a written scope for the full system and a fixed price to build it. Sometimes my recommendation is that you shouldn't build it at all, and you get that too. Five working days, start to finish.
What does the full build cost after the sprint?
That depends on what the prototype tells us is worth building, which is the whole reason for running it first. You'll have a fixed price in writing before any further work starts. Quite often the sprint shrinks the scope people walked in with, and the build ends up costing less than they had budgeted.
Do we have to use AI?
No. I use AI where it genuinely saves your team time: answering routine customer questions, reading documents, drafting the same email for the hundredth time. Where a plain rule does the job more reliably, I use the plain rule. If AI won't improve the outcome, I'll tell you.
How much of my team's time does this take?
About two hours across the whole sprint. One working session at the start where we map your process, one review session at the end. For bigger builds I work in short cycles with a weekly check-in, so nobody on your side has to babysit the project.
Who owns the code and the data?
You do. Code, data, hosting, third-party accounts, all of it goes in your name from day one. If you want to move the work in-house or hand it to another team later, everything transfers. There is nothing to negotiate.
We already have software. Can you work with it?
Usually yes, and it's often the cheaper answer. A lot of my work is extending an ERP or CRM someone has already paid for: adding the missing pieces, connecting systems that don't talk to each other, building the reporting layer on top. Replacing software that mostly works is rarely the right call.
Do you work with businesses outside your city?
Yes, across India, remotely. Video sessions and shared documents cover most of it. On larger engagements I plan an on-site visit at the start, because some operations you really do have to walk through in person before you can build for them.
Get started
Give it five days before you give it five months.
Tell me which process is eating the most time in your week. I'll come back with what it would take to fix, and whether a sprint is the sensible way to start.
- I reply within one working day, and I write the reply myself
- You'll know what I recommend before you pay anything
- Plenty of people run one sprint and stop there. That is fine
Tell me what you're trying to fix
I'll get back to you within one working day and tell you whether I can help.