012–4 weeks
Sprint
A specific question or a launch that cannot slip.
- Fixed scope and fixed price
- One clear deliverable
- Direct access to senior leadership
Approach
Five short stages — sprint or year-long. Something real exists fast enough to prove the plan.
Working hours
IST (UTC+5:30), async in the tools your team already uses.
The five stages
01 / Week 0
Signal
Numbers, customers, competitors, and the one thing blocking growth. Most engagements change shape here.
- Discovery calls
- Data and funnel audit
- Constraint named
02 / Week 1
Frame
Position, audience, and scope on one page — clear enough to repeat to an investor.
- Positioning
- Scope and roadmap
- Success metrics
03 / Weeks 2–3
Prototype
The cheapest version that can still be judged, in front of real people while changing our minds is free.
- Working prototype
- Creative directions
- Early feedback
04 / Weeks 4–8
Ship
Build and launch with a date. Marketing and engineering move together — one team, one invoice.
- Production build
- Campaign live
- Handover docs
05 / Ongoing
Compound
Launch is the start of the data. Kill what failed, double down on what worked.
- Monthly review
- Iteration backlog
- Growth reporting
Ways to work together
026–12 weeks
Build
Taking a brand, site, app or workflow from nothing to live.
- Full discovery through launch
- Weekly demos, no status theatre
- Codebase and assets handed over
03Monthly
Partner
Founders who want a marketing and product team on tap.
- Reserved capacity each month
- Continuous shipping and reporting
- Cancel with 30 days notice
How we behave
Hold us to these
- 01
One team, no telephone game
The people you meet do the work. No account layer diluting the brief.
- 02
Strategy that ships
We only recommend what we are willing to build ourselves.
- 03
Small scope, real dates
Ship a smaller thing on the day we promised — not a bigger thing eventually.
- 04
Evidence over instinct
Instinct sets the hypothesis. Numbers decide what happens next.
- 05
You own everything
Code, accounts, assets, docs. No lock-in, no mystery logins.
- 06
Automate the boring work
If a task is repeated and unloved, it should be a workflow.
Week one is a conversation, not a contract.
We would rather say the work is not worth doing than sell a plan nobody believes in.