How we work · The studio operating model

A small studio. Three engagements at a time. Built end-to-end.

We hold ourselves to one quality of work and to one cadence. We don’t scale by hiring or by templating — we scale by refusing engagements that don’t fit. Three structures below describe what we accept; everything else, politely, we don’t.

IThe three engagements

I1 week

Audit

One week. One question: what's leaking your customers, and how do we fix it?

We score your existing site against the Sheenhaus twelve-signs methodology, identify the specific failures that are leaking premium buyers, and deliver a written report with prioritised recommendations. Useful as a standalone diagnostic or as the first phase of a longer engagement.

What you get

·Audit report (15-25pp PDF) with the twelve signs scored
·Lighthouse + AI-visibility + structural diagnostics
·Prioritised remediation list with effort + impact estimates
·Two follow-up calls — one to walk through the report, one to scope the rebuild if you commission it

If you commission the Build engagement within 60 days, the Audit is credited against it.

II14 – 28 days

Build

The cinematic, AI-native rebuild. Hand-coded from line one.

A complete rebuild of your public website on a modern stack (Next.js, React, GLSL where it earns it, Sheenhaus's typography system). We script the work into fortnightly sprints with a fixed launch date. Two-week engagements ship a tight 5–8-page site; four-week engagements ship a larger brand surface with editorial sections, motion, and integrations.

What you get

·Full website rebuild on Next.js (or your stack, if there's a reason)
·Custom motion + 3D where it serves the brand — never gimmicks
·AI-readable structured data, schema, and content surface
·Hand-off pack: docs, design tokens, CMS guide, deployment pipeline

Fixed scope. Fixed launch date. No retainer locks in.

IIIOngoing

Operate

Workflow automation, AI integrations, ongoing surface work. A studio retainer behind your business.

After a Build (or, less commonly, on its own), we run as your remote technical team — landing the small but compounding work that keeps the surface moving and the workflows running. Capped at four hours per business day so the work stays craft, not throughput.

What you get

·Workflow automations (Zapier / Make / custom Node)
·AI-native integrations (search, content, agents, intake)
·Editorial surface work — new sections, reports, campaigns
·Monthly written readout: what shipped, what didn't, what's next

Month-to-month. Cancel any time. No exit clauses.

IIWhat a Build week looks like

One cadence. Async-first. Written down.

We work in fortnightly sprints with two live calls per week. Everything is written down: a shared Linear board, a weekly looms, a Slack channel that quiets down outside working hours. You always know what shipped, what didn’t, and why.

Day 0
Brief & scope-lock
A one-hour live call to lock the brief, the scope, and the launch date. We produce a written one-pager you sign off before any code is written. Scope is fixed; we say no to changes that don't fit, in writing.
Day 1 – 4
Architecture & systems
Information architecture, design tokens, motion direction, content surface. The plumbing for the next ten days. You see a Loom every day; you respond async.
Day 5 – 11
Build
Hand-coded section by section. Daily preview link. Two live calls (Tue, Fri) to walk through what shipped and what's blocked. AI-readable schema and content structure shipped alongside the visual layer.
Day 12 – 13
Polish & QA
Lighthouse 95+ everywhere. AI assistant compatibility tested. Real-device QA. Content review with your team.
Day 14
Launch
Go-live during your business hours, in your time zone. We sit on the line for the first 90 minutes. The hand-off pack arrives the same day.

IIITime zone

The studio is based in Delhi (IST · UTC+5:30). We hold working hours from 09:00 to 22:00 IST — which gives us overlap with the UK workday, the entire EU and Middle East workday, and US Pacific morning. Live calls are scheduled in your time zone, never ours.

London / Dubai	8+ hours overlap
New York	3–4 hours overlap, evenings IST
San Francisco	2 hours overlap, late nights IST

IVHow we communicate

·Slack channelfor the engagement — replies within four working hours, quieter outside.
·Two live calls per week— scheduled in your time zone, 30 minutes each, written agenda.
·Loom updateson days without a call — you watch on your own time, react async.
·Linear boardfor the work itself — visible to you, always.
·Written readoutat the end of every week — what shipped, what didn’t, what’s next.

VWhat we don't do

The negative space matters as much as the work.

No templates. Every site is hand-coded. We use design systems, not page builders.
No procurement battles. If your buyer needs a 30-page RFP, we’re probably the wrong studio.
No agency middlemen. You work with the same two people from brief to launch.
No hourly billing. Fixed scope, fixed launch date — every engagement.
No NDAs at first contact. We’ll sign one before we see anything sensitive, never before.
No retainers we can’t cancel. Operate is month-to-month, no exit fee.
No surprise scope changes. If you change the brief, we re-scope in writing first.

That’s the model. Want to start a conversation?

Send a brief Book a 30-minute call