Skip to content
Clownmind
Independent studio · est. 2016

We build the commerce and product software other teams quote six months for.

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.

  • Composable commerce
  • Product engineering
  • Design systems
  • Growth
Building for the web
11yrs

Building for the web

Products shipped
430+

Products shipped

Countries served
17

Countries served

Client retention
96%

Client retention

Book a 30-minute architecture call

Bring the messy version. We will tell you what we would do about it, and whether we are the right people to do it.

No sales sequence. One reply from a senior engineer, usually within a working day.

Teams we have shipped with

What we do

Seven practices, one delivery team

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.

All services

Not sure which of these you need?

Most clients arrive convinced they need a replatform. Roughly a third of them do. The framing week tells you which group you are in.

Talk it through
Platform depth

We are opinionated about platforms, and happy to argue

Choosing wrong costs a year. These are the four routes we take most often, and the honest reason we would pick each one.

Past the theme ceiling, without leaving the platform

Custom Online Store 2.0 builds, Hydrogen storefronts, Shopify Functions and the app work that starts once the defaults run out.

  • Hydrogen and Oxygen storefronts
  • Checkout extensions and Functions
  • Subscriptions, bundles and loyalty
  • Shopify Plus B2B implementation
  • Migration from Magento or WooCommerce

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 migrations
Business models

Four shapes of commerce, four very different builds

The 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.

  • Customer-group pricing
  • Quote and approval workflows
  • Purchase order and net terms
  • Rep-assisted ordering

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.

  • Subscription and replenishment
  • Loyalty and referral
  • First-party data capture
  • Lifecycle automation

Marketplace

Many sellers, one trustworthy experience

Vendor onboarding, split payouts, commission logic and the moderation tooling that keeps quality from sliding as supply grows.

  • Vendor onboarding and KYC
  • Split payments and payouts
  • Ratings and dispute handling
  • Catalogue moderation

B2B2C

Sell through partners without losing the customer

White-label storefronts, partner portals and shared inventory across a network of resellers, franchisees or clinics.

  • Multi-tenant storefronts
  • Partner portals and reporting
  • Shared inventory and fulfilment
  • Co-branded experiences
Industries

Twelve sectors where we already know the awkward parts

Domain knowledge is mostly knowing which constraints are real. These are the industries where we have made the expensive mistakes already.

Retail & Commerce

Catalogue systems, checkout rebuilds and store operations tooling for brands selling direct at volume.

Hospitality & Travel

Booking engines, property systems and guest apps where availability logic has to be exactly right.

Property & PropTech

Listing portals, agent workflows and valuation tooling with search that behaves under real filters.

Health & Clinical

Patient-facing products and clinical tooling built under HIPAA and GDPR from the first commit.

Education & Learning

Learning platforms, assessment engines and institutional portals that survive term-start traffic.

Finance & FinTech

Payment flows, lending journeys and reconciliation tooling with an audit trail that stands up.

How we work

Four steps, and you can stop after any of them

Every stage produces something you own outright. Nothing is held hostage to the next invoice.

  1. 01

    Framing week

    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.

  2. 02

    Architecture & plan

    A written technical plan with the trade-offs made explicit, a milestone schedule, and a fixed budget band for the first release.

  3. 03

    Build in the open

    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.

  4. 04

    Launch & operate

    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.

Technology

A deliberately boring stack, with a few interesting exceptions

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.

Where we apply it

Front end

Next.jsReactTypeScriptTailwindHydrogenAstro

Back end

Node.jsFastifyNestJSLaravelPythonGo

Data

PostgresRedisElasticsearchBigQueryPrismaTemporal

Commerce

Shopify PlusBigCommerceAdobe CommerceWooCommerceStripeAlgolia

Mobile

SwiftKotlinReact NativeFlutterExpoFirebase

Platform

VercelAWSCloudflareTerraformDockerGrafana
Testimonials

What clients say when we are not in the room

These are lightly edited excerpts from reference calls, published with permission.

They rebuilt our checkout in nine weeks and then spent another two arguing us out of three features we did not need. Conversion went up either way. That mix of speed and pushback is rare.
PRPriya RamanathanVP Digital · Halberd Outdoor
The framing week was worth the whole fee on its own. We came in wanting a replatform and left with a plan to fix search instead, which turned out to be the actual problem.
TFTomás FerreiraHead of Product · Meridiana Living
We had two agencies before this. Clownmind is the first one whose handover documentation our own engineers could read on a Friday and deploy from on a Monday.
DWDana WhitcombeCTO · Northlake Health
Their SEO people write code. I did not realise how much time we had wasted on audits nobody could implement until findings started shipping in the same sprint.
KAKenji AoyamaGrowth Director · Studio Ferrous
Peak week went by without a single incident. They rehearsed the load twice in September and found a caching bug that would have cost us the whole of Black Friday.
ANAyesha NkemdirimDirector of Ecommerce · Verdant Supply Co.
They told us not to build the AI feature we asked for and explained why in writing. Six months later that was clearly the right call. I trust the next recommendation more because of it.
MBMarcus BellFounder · Rowan & Fen
Journal

Notes from the middle of the work

Written by the people doing it, mostly about the decisions that turned out to matter more than expected.

Read the journal
FAQ

Questions we get asked first

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.

Want an opinion on your architecture before you commit budget?

Thirty minutes with a principal engineer. No deck, no discovery call disguised as a sales call.