How I work · 01
Understand the work first.
I start with how the work actually flows, not with a framework.
the boring questions save the most money
Rajat, software architect and developer
I design and build the software a business runs on.
Most businesses run on parts that don’t talk to each other. I take them apart until I understand them, then put them back together until they feel right: one system your team can run, and keep changing.
Move across the pieces to find the viewDrag sideways to find the view
Aligned · scroll on ↓
- 01 · The partsMost businesses run on parts that don’t talk to each other. Orders arrive by email. Stock lives in a spreadsheet. Only a developer can update the site. A login for every tool. Reports built by hand. The same data typed in four places.
- 02 · Take apartI take them apart until I understand them. every system has a view where it makes sense
- 03 · ComposeThen I put them back together until they feel right. One system your team can run, and keep changing.Orders tracked end to end. Live stock, one source. A site your team edits. One login, the right access. Reports that build themselves. Data entered once.
How I work · 02
Build the whole thing.
Database to screen, by one person who knows why each part exists.
fewer handoffs, fewer surprises
How I work · 03
Leave it runnable.
Your team can change it after I hand it over, and the notes say why.
the best compliment is not needing me
In numbers
- Years building software
- 10+
- Platforms shipped since 2025
- 4
- Largest team led
- 6
- Hours to a first reply
- 24–48
What I build · 1 of 2
Portals and platforms
Customer, partner and staff portals on one codebase, each person seeing only what they should.
Internal tools
Back-office apps and small ERPs that replace the spreadsheet and the email thread.
Real-time data
Pipelines and live dashboards that update as things happen, not at the end of the day.
What I build · 2 of 2
Sites you run yourself
Fast websites with a content system your team actually uses, so the site stays current.
AI where it helps
Assistants that do real work inside your tools, like drafting and publishing a page when you ask.
A second look
An architect’s review of a system before a rewrite, a migration or a scale-up gets expensive.
not sure which one you need? ask me
Where to next
Site map · 4 destinations
You are here · Homestart anywhere
- 01 · ProjectsThe work, drawn4 case studies, each with its real architecture, and 8 earlier projects.Open
- 02 · BlogNotesWriting on architecture, building with AI and running large systems.Open
- 03 · AboutThe long version10+ years of experience, the skills behind it and a résumé.Open
- 04 · ContactStart a conversationTell me what’s slowing your business down. I usually reply within 24–48 hours.Write
Tell me what’s slowing your business down.
a few lines is enough to start
I usually reply within 24–48 hours
Received01
To · Rajat
—
Thanks. Your brief is on the drawing board.
I usually reply within 24–48 hours.
Start another briefYour brief did not go through.
Please go back and try sending it again.