How will people use it?
The first screen your team uses in six weeks, not the first demo in six months.
Web platforms, mobile apps, design systems and commerce, shipped as working slices: a real screen on real data every two weeks, not a prototype that never lands.
What it is
We build the surfaces people work in — web platforms, mobile apps, storefronts, and the design system underneath them. Work ships in two-week slices against real data, on your domain and behind your login, so the first thing you review is the product rather than a picture of it. The design system is delivered as owned code in your repository, not a licence you rent from us.
Who it is for
If none of these sound like your situation, this is probably the wrong arc — and we would rather tell you that than sell you a discovery.
- Your ops team runs the business in nine spreadsheets and one WhatsApp group.
- The customer-facing site converts, and the internal tool it hands off to is a PDF form.
- Checkout drops a quarter of its carts and nobody can say at which step.
- Every new page takes three weeks because there is no component library, only copies of one.
How the work is shaped
Repeatable shapes, not bespoke proposals. Each one has been run before and has a duration we hold to.
- 01Working Slice · 6 weeksOne journey end to end — screen, data, auth, deployment — live on your domain and used by a real team before the next slice starts.
- 02Design System Build · 4 weeksTokens, components and states delivered as code in your repository, every component carrying its four states and a keyboard path.
- 03Platform Build · 12–16 weeksThe full surface across roles: multi-tenant data, role-based views, admin, billing hooks, and the release pipeline that keeps shipping after we leave.
What it costs
Published, not gated. The assumptions column is the part that matters — a price without them is a guess you discover was wrong in week three.
| Band | From | What it buys | Typical duration | Assumes |
|---|---|---|---|---|
| Working Slice | ₹8,00,000 | One journey end to end — interface, data model, auth and deployment pipeline — in production use. | 6 weeks |
|
| Design System | ₹11,00,000 | Token set, 20–25 components with every state, a documentation site, and two existing pages migrated onto it. | 4–6 weeks |
|
| Platform Build | ₹26,00,000 | Multi-role platform: tenancy, roles, the working surfaces, admin, release pipeline and handover. | 12–16 weeks |
|
What sits inside it
Web platforms
Multi-tenant applications with roles, approvals and an audit trail built in from the first slice.
Mobile apps
One codebase for iOS and Android, written for the field team rather than the office.
Design systems
Tokens and components as owned code, with every state and keyboard path specified.
Commerce
Catalogue, checkout and recovery flows instrumented step by step, so a drop-off has a name.
What it has produced
Every number here comes from work on this page. Follow it to the story and check it.
- of abandoned carts recovered within eight weeks
- 23%of abandoned carts recovered within eight weeksSee the story
- to publish a property listing, from six days
- 9 hoursto publish a property listing, from six daysSee the story
- between slices, every slice in production use
- 2 weeksbetween slices, every slice in production use
- states and a keyboard path on every component we ship
- 4states and a keyboard path on every component we ship
The work behind it
The carts that used to just leave
A grocery group's online checkout was losing more baskets than it converted. Rebuilding it recovered nearly a quarter of them.
23% target recovery of abandoned baskets within eight weeks
40 staffSix days to publish a listing, down to nine hours
An estate agency stopped waiting on a photographer and a copywriter to get a property live.
9 hours design target from instruction to live listing
Is Experience what you need?
Tell us what is slow and what it is costing. If the answer is a different arc, or no arc at all, we will say so before anyone writes a proposal.
Scope the first slice