DoonDzn designs and builds custom software — commerce systems, portals, internal platforms and apps. The design comes first: complete, written, and priced before you commit to a build.
AI made writing code cheap. It did not make deciding what to build any easier. That decision is the work — and we do it first, in writing, priced, and yours whether or not we build it.
§01Why builds go wrong
Software rarely fails because someone couldn't write the function. It fails earlier, in a decision nobody had enough of the picture to make.
The estimate was honest. It was made without the map.
Nobody could see the integrations underneath until the work had already started.
It was built exactly as specified.
The specification was the thing that was wrong, and it was signed before anyone could tell.
The demo was perfect. Real data was not.
It was never run against the volume, the mess or the exceptions until launch week.
It works, and now nobody can change it.
Every new requirement costs more than the last one did, and nobody can say why.
Three vendors, three opinions, one system.
Each part was delivered. No one was accountable for whether the whole thing held.
So the design is what we sell, not the keystrokes. It is written down before anything is built, it carries a fixed price and a fixed date, and it is yours to take elsewhere if you decide we are the wrong firm to build it.
§02What you receive
The design phase is fixed in scope and ends in six things you can hold. Any competent firm could build from them — which is the point.
Every screen, every state, every role — what the software is, before anyone builds it.
Tables, relationships and rules. The single decision most expensive to get wrong later.
Every system it must talk to, and what happens when one of them is down.
What ships first, what ships later, and what should not be built at all.
Both agreed at the end of design, before you commit a rupee to a build.
How it reaches production without a maintenance window or a held breath.
§02.1What you can hold us to
Terms, not adjectives — and each one is in the contract, not just on the website.
One number, agreed before the build begins.
No hourly billing, no change-order dripWorking software you can open, on your real data.
Not a demo set, not a status callSource, design files, documentation, infrastructure.
Day one, not on final paymentThe people who design it are the people who build it.
No handover to a benchPost-launch support included with every project.
And no standby retainer after it§03What we've built
We lead with this one because it sets the ceiling. A dealer portal, a consumer storefront and a configurator, all selling the same stock under different rules. Nothing we have built since has been harder — only different.
Three surfaces, three pricing models, one stock number. The difficulty is not any single surface — it is that all three write to the same inventory under different rules about who may order what, at what price, and with whose approval.
§03.1What changed for them
ConfiguratorE-Commerce · 3 months
Compatibility was checked by hand, against knowledge that lived in a few people's heads. Invalid builds reached customers as returns and refunds.
Dealer networkB2B Portal · 4 months
Three hundred dealers, every price confirmed by a person before it could be quoted, every order re-keyed into Tally at the other end.
§03.2Elsewhere
The sector changes. The method doesn’t — design the system, price it, build it, hand it over.
A multi-family office platform, with an ROI calculator validated against the firm's own models.
Patient booking wired into the clinic's existing software rather than replacing it.
A children's learning platform, built end to end.
A pump distribution and service network platform.
Storefronts and studio platforms where the brand carries the sale.
Bilingual and multi-region builds for clients abroad.
The full record is here if you want it.
§04How it runs
The design phase stands alone and is priced alone. Nothing commits you to the next step until you have seen the price and the date for it.
A written view on whether this is worth building — including the case against it.
The six deliverables above. Fixed scope, fixed price, fixed date.
Working software every two weeks, running on your real data.
The sequence below, reversible at every step.
Source, infrastructure, documentation and knowledge transfer to your team.
§04.1Going live
When it replaces something already carrying real traffic. No maintenance window, and no step that cannot be undone.
The new system reads production and writes nothing.
Nothing to roll backBoth systems write; every output compared, order by order.
Daily divergence reportEvery mismatch explained and closed. Not most of them.
You sign off at zero deltasChannel by channel, smallest first, old path still warm.
Rollback is one config changeThe old system retires on a dated plan, not by neglect.
Burn-down date agreed up front§05What it costs
Fixed price, agreed at the end of design, before you commit to a build. No hourly billing.
Commerce operations, B2B portals, configurators, internal platforms, booking and learning systems, apps — designed, built and taken live.
A Shopify Plus or Next.js storefront, a marketing site, or a single-purpose tool on a brief that is already settled.
Below ₹2.5L we are the wrong call and will say so in the first reply. We also do not sell standby maintenance — billing monthly to watch a stable system is revenue we have not earned. You own the source, the infrastructure and the documentation from day one.
§06Whether we fit
Stated here so neither of us spends half an hour finding out.
§07Questions
Turning an idea into a designed system, then building it. The specialism is the method rather than the industry: we work out what the software actually has to be — data model, screens, integrations, scope, price, date — and hand you that in writing before any build is committed to. Most of our depth is in complex commerce, which is where that method has been tested hardest.
Yes. Shipped work in financial services, healthcare, education, industrial distribution and design, alongside custom web applications, internal tools, CRM and ERP systems, and mobile apps for iOS and Android. Commerce is where we go deepest, not where we stop — a dealer network on one shared inventory is a harder problem than most, and the same method carries across.
Because the work is different. A storefront can be templated; a system that prices 300+ dealers correctly and never oversells cannot. Below ₹2.5L we'd have to cut the parts that make it reliable, so we'd rather say no. If you need a storefront or a single-purpose tool on a defined scope, that tier starts at ₹2.5L.
Yes — Shopify and Shopify Plus, WooCommerce, and custom Next.js. We recommend the platform that fits the problem. Often the honest answer is that your platform is fine and only the operational layer around it needs building.
Often yes, and it's usually cheaper than a rebuild. We audit what exists, fix what's failing, and build the missing operational layer around it rather than replacing a system that works.
Fixed price, quoted at the end of the design phase. You get complete scope, timeline and price before any build commitment. The design phase is scoped and priced on its own, so nothing obliges you to build with us afterwards. No hourly billing, no surprise line items.
Most custom systems deliver in 8–16 weeks. A defined-scope build runs 4–8 weeks. Exact weeks are fixed at the end of the design phase, before you commit to a build.
Every project includes 30 working days of post-launch support. After that we don't sell standby maintenance on a stable system — we'd be billing you to watch something that works. Ongoing engagements only where there's a real roadmap.
Absolutely. We sign NDAs before any detailed technical or business discussion. Just mention it in your first message.
Yes. We've built for clients in India, Israel, Japan, and the US. Time zones handled with async communication and weekly sync calls. All documentation in English, proposals quoted in USD for international work.
You do — 100%. Every line of code, every design file, every piece of documentation is yours from day one. No lock-in, no dependency on us. You can take it anywhere, any time.
Next.js, React, TypeScript, Node.js and PostgreSQL for most systems. Shopify Plus or WooCommerce where the platform fits. React Native, Flutter or native Swift for mobile. The stack follows the problem, not the other way round.
§08Start
You do not need a spec or a brief — working out what the thing actually is happens to be the job. A paragraph on what you want to exist, and what you are running now, is enough for a useful first call. Say the word if you would rather have an NDA in place first.