Commerce engineering
Storefronts that survive Black Friday.
ExploreH-6, Kailash Park, Basai Darapur, Bali Nagar, Delhi 110015
Clownmind is a product & commerce engineering studio. Composable storefronts, web platforms, mobile apps and the internal tooling underneath them — designed, engineered and operated by one small senior team.
Building for the web
Products shipped
Countries served
Client retention
Teams we have shipped with
We do not hand a project between departments. The people who scope the work are the people who build it, and they stay on it through launch.
Storefronts that survive Black Friday.
ExploreDecoupled front ends on your existing backend.
ExploreApplications, portals and marketing systems.
ExploreNative and cross-platform apps people keep.
ExploreResearch, interface systems and identity.
ExploreAcquisition, lifecycle and measurement.
ExploreInternal tools, integrations and data work.
ExploreMost clients arrive convinced they need a replatform. Roughly a third of them do. The framing week tells you which group you are in.
Choosing wrong costs a year. These are the four routes we take most often, and the honest reason we would pick each one.
Custom Online Store 2.0 builds, Hydrogen storefronts, Shopify Functions and the app work that starts once the defaults run out.
98
Median Lighthouse performance
Every platform engagement starts with the same question: what would have to be true for you not to replatform?
How we run migrationsThe architecture that suits a subscription brand will actively harm a wholesale business. We start from the model, not from the platform.
B2B
Trade accounts, negotiated pricing, approval chains
Company hierarchies, requisition lists, credit terms and quote-to-order flows. We build the boring machinery that lets a sales team stop taking orders over email.
D2C
Own the relationship end to end
Storefronts built for repeat purchase — subscriptions, loyalty, first-party data and a lifecycle programme that does not depend on rented audiences.
Marketplace
Many sellers, one trustworthy experience
Vendor onboarding, split payouts, commission logic and the moderation tooling that keeps quality from sliding as supply grows.
B2B2C
Sell through partners without losing the customer
White-label storefronts, partner portals and shared inventory across a network of resellers, franchisees or clinics.
Domain knowledge is mostly knowing which constraints are real. These are the industries where we have made the expensive mistakes already.
Catalogue systems, checkout rebuilds and store operations tooling for brands selling direct at volume.
Booking engines, property systems and guest apps where availability logic has to be exactly right.
Listing portals, agent workflows and valuation tooling with search that behaves under real filters.
Patient-facing products and clinical tooling built under HIPAA and GDPR from the first commit.
Learning platforms, assessment engines and institutional portals that survive term-start traffic.
Payment flows, lending journeys and reconciliation tooling with an audit trail that stands up.
Every stage produces something you own outright. Nothing is held hostage to the next invoice.
A paid week where we map the constraints, the existing systems and what success has to look like in numbers. You keep the output whether or not we continue.
A written technical plan with the trade-offs made explicit, a milestone schedule, and a fixed budget band for the first release.
Two-week increments, a preview URL from day three, and a Slack channel where your team can see the work rather than wait for a demo.
Load testing, runbooks and monitoring before go-live, then a support window while your team takes the wheel — or a retainer if you would rather we kept it.
We pick technology you can hire for and we can hand over. Novelty has to earn its place by solving a problem the conventional choice cannot.
Front end
Back end
Data
Commerce
Mobile
Platform
These are lightly edited excerpts from reference calls, published with permission.
Written by the people doing it, mostly about the decisions that turned out to matter more than expected.
11 August 20269 min
Big-bang replatforms fail for the same reason big-bang anything fails: there is no safe moment to stop. Here is the order we move things in, and why the storefront always goes first.
Ines Vogel · Principal architect
28 July 20267 min
Every team we meet has a performance target. Almost none of them have a mechanism that stops a regression from shipping. Those are very different things.
Marcus Oyelaran · Engineering lead
9 July 20266 min
Roughly one client in five takes our framing document and does the work in-house. We think that is a feature, and here is the reasoning behind it.
Sara Kilián · Managing partner
If the answer you need is not here, the fastest route is a thirty-minute call with someone who would actually work on it.
Product and commerce engineering: composable storefronts, web platforms, mobile apps, internal tooling, and the design and growth work that surrounds them. We are a build studio, not a staffing shop — although we do run embedded teams when a client already has strong technical leadership.
With a paid framing week. We map the constraints, look at the existing systems, and write a technical plan with the trade-offs made explicit. You keep that document whether or not you continue with us, and roughly one in five clients uses it to do the work in-house.
A framing week is a fixed fee. Build engagements are quoted as a band per milestone rather than a single number, because the honest answer changes as the architecture becomes clear. Most first releases land between eight and sixteen weeks of a three-to-five person team.
Completely, from the first commit. Work happens in your repository under your organisation, on your cloud accounts. There is no proprietary framework you have to keep paying us to maintain.
Delhi, Bengaluru and Mumbai, with the head office in Delhi. Every project runs with at least four hours of overlap with the client's working day, and the people you meet in the framing week are the people who build the thing.
That is most of our work. We pair with in-house teams, review their code, and deliberately hand ownership across as the engagement goes on. The end state we aim for is your team not needing us.
Thirty minutes with a principal engineer. No deck, no discovery call disguised as a sales call.