— SERVICES
Three ways to work with the studio.
Every engagement is written down before a rupee changes hands. Scope, phases, timeline, and a real number — not a range.
01 ENGAGEMENT MODELS
Engagement models
Product Sprint
Two weeks. One outcome. Ship a prototype, an MVP slice, or a focused feature into production.
From ₹30K
- Discovery call + scope brief
- Design + build against a written outcome
- Live staging URL by end of week 2
- Code + docs handed over
Full Build
The whole product, from brief to store. Design, engineering, deploy, handover — all under one roof.
From ₹2L
- Discovery week — brief, flows, scope kill list
- Design system + high-fi screens
- Phase-gated build with weekly demo
- Prod deploy on your infra or ours
- Runbook, docs, 2-week hyper-care
Ongoing Retainer
A dedicated slice of the studio every month — for new features, platform care, and the long tail of shipping.
From ₹40K/mo
- Reserved capacity every month
- New feature releases + iteration
- Platform care — security, perf, uptime
- Monthly report + roadmap check
02 WHAT WE BUILD
Four kinds of build, and the proof for each.
The packages above are how the work is bought. This is what the work is — and every claim here points at a live project rather than a promise.
- 01
Web platforms and product UIs
Marketing sites that load in under a second, and the logged-in product behind them — dashboards, admin panels, publishing flows, role-based access. Server-rendered where it helps ranking, client-rendered where it helps the user, and never the other way round.
More on web platforms and product uis →
Shipped: Trivarna Foundation · MC Finnzon · Acoustimart
- 02
Mobile apps, on both stores
One codebase, two stores, and a release process that does not need a specialist to run. We ship Flutter for most builds and React Native when the product already lives in a React world — including the store listings, review responses and the first few post-launch releases.
More on mobile apps, on both stores →
Shipped: Cortix · Karum Kurum
- 03
D2C storefronts and checkout
Indian e-commerce is a payments and messaging problem as much as a catalogue one. Variant-heavy products, combo offers, Razorpay checkout, WhatsApp and SMS order updates, courier and inventory sync — built so the person running the shop can change a price without calling us.
More on d2c storefronts and checkout →
Shipped: 2b2.in · BB99 · Saffron Blinds
- 04
AI features that earn their invoice
Model calls are the easy part; the cost curve and the failure modes are the work. We scope an AI feature to a measurable job, put a rupee number against it per user per month, and build the guardrails that stop a runaway bill before it starts.
More on ai features that earn their invoice →
Shipped: Cortix matchmaking · What AI actually costs
03 WHAT YOU GET
Every engagement ends the same way.
A build is only finished when someone else can run it. The full six-week timeline — discovery, design, build, polish, launch — is written out on the studio page.
The code, in your org
Your GitHub, your Cloudflare or Vercel account, your Supabase or Firebase project. We build inside your infrastructure from day one, so nothing has to be transferred at the end.
A runbook, not a README
How to deploy, how to roll back, where the secrets live, what breaks first under load, and who to call. Written while the work is fresh, not reconstructed after.
Two weeks of hyper-care
Every Full Build ships with a fortnight of same-day fixes after go-live — the window where real users find what staging never did.
A written scope, before a rupee moves
Phases, deliverables, timeline and a number — not a range. Change requests are re-quoted in writing rather than absorbed silently into the schedule.
04 FAQ
The questions that come up every kickoff call.
Can I combine engagement models?
Yes — most clients start with a Sprint or Full Build and roll into a Retainer once the product is live. That way capacity is reserved for the inevitable second wave of feature requests.
What are payment terms?
Sprints are 50% at kickoff, 50% at ship. Full Builds are milestone-based — typically 25% at contract, 25% at design sign-off, 25% at build-complete, 25% at prod deploy. Retainers are monthly upfront. All against GST invoices.
Who owns the code?
You do, from day one. Your GitHub org, your Cloudflare account, your Supabase project. We work in your infrastructure so there is nothing to “hand over” at the end — it was always yours.
What if scope changes mid-project?
Written change request, re-quote, updated timeline. Small changes are usually absorbed. Big ones get a formal amendment. We would rather pause and re-align for a day than build the wrong thing for a week.
Do you work with clients outside India?
Yes — active clients in the UAE, Oman, the USA and Australia. Invoicing in USD/AED/OMR available. Timezone overlap is easy for the Gulf; for the USA and Australia we schedule a fixed daily sync window at each end of the day.
What are you not going to do?
We don’t do marketing content, SEO copywriting, growth marketing, or paid ads. We ship the software; you drive the go-to-market. If those are what you need, we can recommend partners.