For the day the spreadsheet stops being enough.
Internal dashboards, customer portals, order and booking apps, and Android apps for teams in the field. Built properly, hosted on your accounts, with the code in your GitHub.
Every growing business hits this moment. The Google Sheet that ran everything has five people editing it, a formula somebody broke in March, and a founder who can't answer "what's the status today?" without calling three people. You don't need enterprise software. You need one well-built app that does the ten things your business actually does.
What I build
- Internal dashboards. Orders, jobs, staff, payments, stock. One screen the owner can trust, with the reports the sheet never managed.
- Customer and client portals. Let customers see their orders, bookings, invoices or documents without messaging you.
- Booking, order and lead management apps. With logins, roles, history and notifications on WhatsApp or email.
- Android apps for field teams. Update a job, upload a photo, mark a delivery, from a phone with patchy signal.
- AI built in where it earns its place. Summaries, drafting, classification, search. Not sprinkled on for the sake of it.
How it's built
Modern, boring, well-supported tools: a web framework, a proper database, hosting that scales without a rewrite, and automations wired in with n8n where it makes sense. I'll name the exact stack in the scope so any developer can pick it up later. That's deliberate.
How a project runs
- A call and a look at the sheet. The current spreadsheet tells me most of what the app needs to do.
- Written scope, fixed price, and a first-version list. Apps grow. The scope says exactly what is in version one so it ships instead of drifting.
- Design and build in weekly check-ins. You see it working early, on real-looking data, and change direction while it's cheap to.
- Launch on your accounts. Domain, hosting, database and app store listing in your name.
- Handover. Code in your GitHub, a recorded walkthrough, written notes, and an agreed window for fixes.
The quickest way to scope this: a screenshot of the spreadsheet. It usually tells me whether you need an app, a better sheet, or just an automation.
Timelines and cost, honestly
An internal dashboard with logins and a few screens is usually four to eight weeks. A customer-facing app or an Android app on top of it takes longer. Cost depends on the number of screens, roles and integrations; you get a fixed figure in writing before you decide, and the monthly hosting cost alongside it.
Building for teams in Delhi NCR and across India
Most app builds start with a business in Delhi NCR — Delhi, Noida, Gurugram, Ghaziabad or Faridabad — though plenty run entirely over calls with teams elsewhere in India. Either way the process is the same: scope and price agreed in writing first, a demo link you can open while it is being built, then the code, keys, hosting and Play Store listing handed over in your name.
Questions people ask
Will I own the code?
Yes. It's in a GitHub repository under your account from day one, and every hosting and database account is in your name.
Can another developer maintain it later?
That's the whole idea. The stack is standard and named in the scope, and the handover notes are written for whoever comes next.
Do you also do the design?
Yes. The app is designed to be used by your team, not to win awards, and you see and approve the screens before they're built.
What about an iPhone app?
Ask. In many cases a well-built web app covers iPhone users, and I'll tell you if a native iOS app is actually worth the extra cost.
What if we only need a small change to our existing app?
Message me with what you have. If it's a quick fix, I'll say so and price it that way.
Do you build Android apps and web apps for small businesses in India?
Yes. Most builds are internal tools: a dashboard replacing a shared spreadsheet, a customer portal, or an Android app for a field team. Scope and price are agreed in writing first, and the code, keys and store listing stay in your name.
The other two things we build
Before you build an app
Outgrown the spreadsheet?
A screenshot of it is all I need to tell you what I'd build, in what order, and what it would cost.