Prasham H Trivedi Ahmedabad · Available for one new project EN / ગુ

The engineer who takes your operations off spreadsheets — and stays with you as the business grows.

Senior engineer, 15 years including MongoDB and multi-tenant SaaS. Works solo, directly with the owner. Builds what fits — custom when it needs to be custom, Shopify or similar when that fits. Doesn't disappear after launch.

તમારી ભાષામાં, તમારી રીતે.

Start a conversation

Opens WhatsApp · usually replies same day

§ 01

Who this is for

You run an operational business that works, mostly. But one workflow is breaking — orders lost in WhatsApp threads, inspections done on paper and re-typed twice, a spreadsheet that three people edit and nobody trusts. You can name the workflow today.

You don't have a developer. You don't want a developer on payroll. You've talked to one or two agencies. The quotes were ₹8L for what felt like a template, and the project manager was thirty minutes late to the second call.

You'd rather work with someone you can WhatsApp at 9pm. Someone who'll still pick up six months after launch.

What you actually want is software that's modern, affordable, and easy to live with. Everything else — the years, the stack, the credentials — is table stakes.

§ 02 · A parable

What 'fit' actually means

SaaS is hit-or-miss against this brief. Sometimes a tool fits the way you already run. More often it asks you to bend your workflow to its idea of how a business should work — and bills you monthly for the privilege. Custom, done right, is the inverse: the software takes the shape of your work, not the other way around. Your software. Your flow.

Two things have to be true for that to hold. The numbers your business runs on must agree with each other — accuracy is the floor of the work, never a feature on top of it. And someone has to stay close to it after launch, because workflows drift, and the software has to drift with them.

Most software vendors arrive with a new peg and a different cow. I build for the cow you already have.

§ 03

Selected work

Three engagements, equal weight. No logo wall, no badges. The work is the proof.
03.1 Construction · Custom

A field workflow, fit to the team's hands

A construction company in Gujarat ran inspections on Excel — re-typed twice, with photographs scattered across WhatsApp threads. We rebuilt it as a backend the field team could feed from their phones, in the order they actually inspect things, with verifiable evidence at every step. Not a generic field-ops product — the system shaped to their rhythm, not the other way around.

Outcome Reconciliation errors prevented. Hours saved. [pending numbers]
03.2 D2C · Shopify

A D2C storefront that doesn't feel like one

An Ahmedabad-based wellness and beauty brand wanted a Shopify storefront that didn't read like Shopify. Catalog, cart, and post-purchase tuned to how the brand actually wants to talk to its customers — Shopify treated as a tool, not a template, and shaped to the brand's voice instead of the other way around.

Outcome A storefront that reads as the brand's own, not the platform's.
03.3 Internal · Method

The tools I build for myself

Parakh — an intent-driven API testing harness. VaatChitra — call transcription for Gujarati and Hindi. MCPlex — a unified AI-tool router. Sanskrit names because the family resemblance is the point. These aren't products; they're the engineering discipline that goes into client work, made visible.

Outcome What I ship for myself, I ship for you.
A note

What runs through this work is what it doesn't do. Scope doesn't drift. Communication doesn't break down. Interest doesn't fade after launch. The stack doesn't turn out to be wrong for the workload, and nobody wakes up six months in to a business that has quietly become a different one. Most software projects fail in one of those five shapes. Fit means not failing in any of them.

§ 04

How this works

We talk. Usually a call, usually in Gujarati or English-with-Gujarati-as-needed, usually 45 minutes. I ask about the workflow that is breaking. You ask whatever you want about me.

If we agree the work is real, we set a fixed scope and a fixed price. I don't bill hourly. I don't run weekly status meetings. I send proof — actual working software — every two weeks.

After we ship, the relationship doesn't end. WhatsApp stays open. If something breaks, I'm the first call, not a support ticket queue. There is no SLA on this. There is just my word.

§ 05

Why this kind of work is possible now, but wasn't five years ago

05.1

Senior engineering at consumer prices.

A senior engineer can now run the workload of a small team. The economics shifted; the rates didn't have to.

05.2

Software in the language of the business.

What used to take a translator now happens in conversation. I model your workflow in your words, not in mine.

05.3

Infrastructure that doesn't break the budget after launch.

Modern cloud (Cloudflare-native, mostly) means support and uptime stop being a separate problem.

§ 06

When you should call someone else, not me

If you have an in-house dev team or a CTO, you have what I am.

If you want weekly project-management ceremony, I'm not the shape you need.

If your business is below ₹2cr in revenue, I'll point you to someone who does this work at that scale better than I do.