Four studios. One build.
Every project runs through the disciplines it needs and none of the ones it doesn’t. Below is the actual shape of an engagement — the method, what the first month looks like, how we price it, and the work we turn down.
- Founded
- 2019
- Team
- 24 across four studios
- Projects shipped
- 60+
- Based
- Lucknow, India · working GMT–GMT+8
- Longest engagement
- 4 years, ongoing
- Repeat client rate
- 72%
The four-layer method
The same four layers the object on the homepage is made of. Each one has to finish before the next starts, and each produces something written that both sides sign off.
- 01
Discovery
The Outer LayerWe do not write a line of code until we understand the market surface. The brief you arrive with describes a solution someone has already chosen; this phase peels it back to the need underneath, which is frequently a different problem than the one in the brief.
1–3 weeks- A written problem statement both sides sign off
- Constraint map — technical, regulatory, organisational
- Scope with an explicit list of what we are NOT doing
- 02
Design
The VisualsInterfaces drawn to be understood before they are admired. Every screen has to earn its place against the need established above, and anything that cannot be traced back to it gets cut here rather than built and cut later.
2–6 weeks- Interactive prototype of the primary flows
- Design tokens and component inventory
- Accessibility decisions made at the primitive level
- 03
Engineering
The CoreScalable architecture built to hold — Flutter on mobile, Next.js on the web, Go and Node beneath. We ship to a real environment in the first fortnight and keep it shippable every day after; a branch that has not been deployed is an estimate, not a status.
6–24 weeks- Production deployment from week two
- Test coverage on the paths that carry money or data
- Runbook and architecture decision records
- 04
Growth
The RootsWhat holds after launch. DevOps, CI/CD, observability, and the tech strategy that decides what gets built next. Most of our engagements are with clients we have already shipped something for.
Ongoing- CI/CD pipeline your team owns and can change
- Monitoring with alerts that mean something
- A quarterly technical review, for as long as it is useful
What a first month looks like
Discovery starts. We interview whoever actually uses the thing, not only whoever commissioned it, and read whatever code already exists.
First deployment to a real environment. Usually close to empty — the point is that the path from repository to production exists and your team has walked it with us.
Problem statement and constraint map delivered in writing. This is the document that decides whether the original brief survives contact.
First increment demo against agreed scope, and a costed plan for the next quarter. From here the cadence repeats every two weeks.
How we work
Measure before rewriting
The rewrite you asked for is often unnecessary, and we would rather say so in week three than bill you for eighteen months. On one engagement, profiling turned a platform rewrite into a hot-path rewrite and took a two-year project down to twenty-two weeks.
Ship to production early
First deploy inside two weeks, every time, even when the thing deployed is nearly empty. Everything difficult about shipping — access, secrets, DNS, review sign-off — surfaces on the first attempt, and you want that in week two rather than the week you planned to launch.
Strangle, never big-bang
Legacy systems come out one at a time behind an interface that does not change. Cutover weekends are a risk profile we decline; where the failure mode is serious, we shadow-read the new path against the old for weeks before anyone relies on it.
Accessibility in the primitive
Focus handling, contrast and target sizing belong in the component, not on a checklist at the end. If the library is used correctly it should not be possible to ship a 30px tap target — the accessible version is the only version available.
Hand over as we go
Your team is in the repository from week one, and the pipeline is one they can change without us. An engagement that ends with a dependency on the agency that built it has failed at something we consider part of the work.
Say no to scope we cannot do well
We do not take native games, embedded firmware, or ML research. We will tell you that in the first call and, where we can, point you at someone who does.
Ways to work with us
Discovery Sprint
2–3 weeksYou have a problem and competing opinions about the solution.
A fixed-scope, fixed-price piece of work that ends in a written problem statement, a constraint map and a costed plan. It stands alone — roughly a third of the time the recommendation is that the build is not worth doing yet, and that is a successful outcome.
Deliverable: Problem statement, technical plan, costed roadmap
Product Build
3–9 monthsThe problem is understood and something needs building.
A cross-disciplinary team working in two-week increments against a scope agreed at the start of each. Production deployment from week two, your engineers in the repository throughout, and a demo you can actually click at the end of every increment.
Deliverable: A shipped product and the pipeline that maintains it
Architecture Review
1–2 weeksSomething is slow, expensive or fragile and nobody agrees why.
We profile the system, read the code, interview the team, and produce a written assessment with findings ranked by cost to fix against value of fixing. No obligation to have us do the work — several of these have ended with a client's own team executing the plan.
Deliverable: Written assessment with prioritised findings
Embedded Team
6 months+You need capacity with judgement, not contractors with tickets.
Two to five people working inside your process, your standup and your repository. We push back on the roadmap where we think it is wrong — that is most of the value, and a client who wants ticket-takers should hire ticket-takers.
Deliverable: Sustained delivery inside your team
Selected clients
- Northwind Retail Group
- Meridian Utilities
- Atlas Telemetry
- Brightpath Health
- Kestrel Financial
- Harbourline Logistics
Start with a conversation.
Most engagements begin with a discovery sprint, and roughly a third of those end with us recommending you don’t build the thing yet. Tell us what you’re working on.
Start a project