Observe
I watch the work happen before I write a requirement down.
Off-the-shelf platforms make you bend. I map the real workflow — leads, clients, approvals, reporting — build the system around it, and hand it over so your team can run it.
Who it is for
Many businesses run on a process that does not fit the software they bought. The gap gets filled with spreadsheets, a WhatsApp group and one person who remembers how it all connects. Custom operations software is worth building when that gap costs more than the build — which can happen sooner than owners expect.
Finance and service businesses — mutual fund distributors, advisers, agencies — whose real process lives in spreadsheets, WhatsApp groups and one person's memory.
Operations teams that have outgrown an off-the-shelf CRM and pay licence fees that scale with headcount for features nobody uses.
Owners who want a system their own team can run after launch, without depending on me.
Outcomes
01One system of record for leads, clients, tasks and approvals.
02Role-based access, so each person sees only what they should.
03Reports that reconcile to the numbers you already trust.
04Your data in a database you own, exportable at any time.
05A documented handover, so the code and the knowledge are yours.
Signals
Process
Typically 10 – 20 weeks. You get a working build, with a short demo, every week, and on final payment the code, the accounts and the documentation are yours. The full process
I watch the work happen before I write a requirement down.
The process as it is, the process as it should be, and the delta between them.
Module by module, in the order that removes the most manual work first, with a working demo every week.
Historic data moved, reconciled and signed off before anyone switches over; then documentation and a walkthrough with your team.
Included
Workflow and process mapping
Multi-role dashboards and permissions
Quotation, billing and inventory modules
Reporting that reconciles to the accounts
Migration from existing tools and spreadsheets
Typical stack
Next.js
TypeScript
PostgreSQL
Prisma
Role-based access
Self-hosted or cloud
Questions
Usually, yes. I start with a short audit of what you have and give you an honest answer on whether extending it or replacing part of it is cheaper over the next eighteen months. Existing data is migrated as part of the project — extraction, cleaning, reconciliation and a sign-off step before cutover.
Not always. If a standard product fits your process, I will tell you to buy it. Custom wins when the process is your competitive advantage, or when licence and workaround costs compound past the cost of the build.
Yes. Self-hosted deployment is possible, with reproducible builds and a runbook your IT team can operate. Whether it suits you depends mostly on who will maintain it afterwards.
You do, on final payment. The repository, infrastructure accounts, credentials and documentation transfer in full.
You get a working build on a real URL, with a short demo, every week. That is how a change of direction gets caught while it is still cheap.
Handover is a phase with its own deliverables: documentation and a walkthrough with your team, plus a support window agreed in the proposal. After that you can run it yourselves or retain me for changes.
Yes. The live systems on the Work page are CRM platforms for Indian mutual fund distributors, built while I was at Aina Tech Services LLP. Their public sign-in pages describe the features, and I can walk through what I built on a call.
Related notes
The other core services
Design and website work is also available.
Start here
Tell me what you are trying to achieve and I will come back with an honest view on scope, sequence and whether custom crm & erp development is really the thing you need first.