Product direction, then delivery

Your roadmap is probably fiction.

Building got cheap. Deciding didn’t. Formula Station works out what’s actually worth building — then gives you the team that ships it, from $1,500 a month.

Start with the eight questions below. We’ll tell you what the gap is costing you, in engineer-months.

Tick what’s true. Be honest, nobody’s watching.
How many engineers?

0/8

Nothing ticked yet. Have a go — the maths is more interesting than the marketing.

01 What happened

Execution got cheap. Nobody sent a memo.

For twenty years the answer to every problem was more engineers. Then the price of building collapsed — distributed teams, contract shops, and machines that write passable code at three in the morning without complaining about it.

Congratulations. You can now build almost anything.

So can everyone else, which leaves exactly one thing to compete on: knowing what’s worth building. That part didn’t get cheaper. It got harder, because you can now afford to be wrong at a speed previous generations could only dream of.

  1. What’s worth building

    The one everything else inherits

  2. What exactly to build

    Scope, shape, sequence

  3. Build it

    Design and engineering

  4. Ship it

    Release, measure, repeat

Everything after step zero inherits step zero. Almost everyone you can hire sells you steps two and three.

02 Who it’s for

The same disease at every size. Only the bill changes.

Direction set by the loudest voice rather than the clearest reasoning looks different at eight people than at three thousand. Underneath, it is the identical failure.

1–10 engineers

Startup

The founder is the product manager, and the product manager is drowning. Direction gets set by whoever spoke most recently — usually an investor, occasionally a competitor’s launch, once memorably a tweet.

What it costs you

Runway. You cannot buy the quarter back, and there aren’t many left.

11–200 engineers

Scaleup

Founder instinct stopped scaling somewhere around the second team, and nothing replaced it. You hired product managers. You did not, it turns out, install product judgement — those are separate purchases.

What it costs you

Compounding. Headcount is now outrunning judgement, and the gap widens with every offer letter.

200+ engineers

Enterprise

Prodigious output, no traceable line to anything. Roadmaps get negotiated the way treaties do, because there is no shared basis for settling them any other way.

What it costs you

Multiplication. Wrong × 300 engineers is comfortably the most expensive thing the company does.

03 Direction

First, work out what’s worth building.

Three ways in. All of them end with a decision you can defend, and a list of things to stop.

  1. Direction Sprint

    Two weeks, fixed fee

    We take your roadmap apart in front of you, with the people who actually decide things in the room. You get a defensible answer to “why this, why now” — and the genuinely useful bit, a list of things to stop.

    Good whenYou need clarity fast, or you need to end an argument that has been running since spring.

  2. Embedded product leadership

    Three to six months

    A fractional CPO, two or three days a week. We run product and we teach it, on the working theory that you would rather not need us indefinitely.

    Good whenYou have a product team and no product leadership — or leadership that is quietly underwater.

  3. Direction, then build

    Ongoing

    The sprint decides it; a Formula Station team builds it. Same people from the decision through to the release, which is the whole point — nothing is lost in the handover because there is no handover.

    Good whenThe thing needs to exist, and handing a spec to a shop and hoping is not a plan.

04 Delivery

Then the team that builds it.

Once the direction is settled, someone has to ship it — and handing the answer to a different company is where most of the value leaks out. Two ways to run it: a dedicated team on subscription, or a one-time build, scoped and quoted as a whole. Same people either way.

Rather keep the team once it ships? That’s the subscription — the same people, staying on.

Starter

$1,500/mo

You know the next thing to build and need it shipped properly. One developer who owns it end to end, with a product manager keeping it honest.

Your team

  • 1 Full-Stack Developer (full time)
  • 1 Product Manager (part time)
  • Joins your Slack and your repo
  • Weekly written progress report
  • Your Git workflow, not ours
  • Cancel anytime, 30 days notice
Choose Starter

Growth

$4,500/mo

The thing has a design surface and real users. Development and design working the same sequence, rather than handing files over a wall.

Your team

  • 2 Full-Stack Developers (full time)
  • 1 UI/UX Designer (part time)
  • 1 Product Manager (full time)
  • Daily standups
  • Sprint planning you can attend
  • Figma handoff, or Figma optional
  • Dedicated Slack channel
Choose Growth

Scale

$7,500/mo

A whole product team. Build, design, QA and product management under one roof — the arrangement that actually works, at a fraction of hiring it.

Your team

  • 3 Full-Stack Developers (full time)
  • 1 UI/UX Designer (full time)
  • 1 Product Manager (full time)
  • 1 SQA Engineer (full time)
  • CI/CD set up and maintained
  • Code review on every change
  • Dedicated product manager
  • Priority support
Choose Scale

Every plan includes a dedicated product manager and full IP assignment. Cancel anytime with 30 days notice. Not sure which tier? The diagnostic above usually settles it.

05 The difference

Strategy that never ships is a PDF with opinions.

You can hire two kinds of firm.

Strategy consultancies hand you a document and a handshake. The thinking is often genuinely excellent. It dies on contact with your sprint board.

Development shops build precisely what you point at and hold no view on whether you should. You get exactly what you asked for, which is usually the problem.

We do both, in that order, and with the same people. Direction without delivery is theatre. Delivery without direction is very expensive fidgeting. And splitting them across two companies means the answer gets re-explained to strangers before anyone writes a line of code — which is where most of it quietly goes missing.

What strategy consultancies, development shops and Formula Station each take responsibility for
ResponsibilityStrategy firmDev shopFormula Station
Decides what to buildYesNoYes
Builds itNoYesYes
Same people either side of the decisionNoNoYes
Answerable for whether it workedNoNoYes

06 Who we build with

Teams already shipping with us.

  • ArchiConnect Homes
  • Waffle Time
  • Zerofin
  • Bay Developments
  • ArchiConnect Store
  • ArchiConnect Academy
Idea to MVP in 6 weeks. With traditional hiring, we’d still be interviewing.
Jalal AhmadCEO, ArchiConnect
40% less than equivalent in-house hires — and we got better talent.
Abrar GalibFounder, Waffle Time
Not random freelancers — an integrated unit that ships quality code from day one.
RezaFounder, NexBridge

07 Who we are

A bench, not an agency.

Zerothlab started from one route through the industry — PM, then product lead, then CPO, then CTO — and one observation from it. Most product advisors have never had to ship what they recommended. Most engineering firms have never had to justify what they built. The interesting work sits in the overlap, and the overlap was empty.

So the firm is built as a bench of people who have worked both sides, and assembled per engagement.

  • Product Manager
  • Product Lead
  • CPO
  • CTO
  • Product leadership

    ex-CPOs and ex-CTOs who have owned both a roadmap and a payroll, and know which one wakes you at 4am.

    On an engagementSets direction, and is answerable for it. Sits in your exec meetings, not beside them.

  • Product management

    Senior PMs who have run discovery that killed their own favourite feature, and shipped anyway.

    On an engagementTurns direction into a sequence someone can build on Monday.

  • Product and UX design

    Designers who prototype rather than present. Research that changes the plan, not research that ratifies it.

    On an engagementMakes the thing usable before it is expensive to change.

  • Engineering

    Front, back and mobile. People who ship, as distinct from people who advise on shipping.

    On an engagementBuilds it. Also tells you honestly when the thing you asked for is a bad idea.

  • Data and analytics

    Enough rigour to tell you whether it worked, and enough spine to say when it didn’t.

    On an engagementInstruments the bet before you place it, so the answer is knowable afterwards.

Assembled, not allocated

You get the team the problem needs, not the team we happen to have spare. A two-week direction sprint is one or two senior people, not a pyramid with a partner on top.

Senior by default

Every person on an engagement has done the job at the level you are hiring for. We do not staff juniors against senior rates and call it leverage.

Small on purpose

Teams of three or four that decide and ship, rather than teams of twelve that coordinate. The overhead of a large team usually exceeds its output.

You will not meet the senior team in the pitch and a different team in the delivery. It is the same people either way — that is the entire reason we keep the bench small.

08 Questions

The ones people actually ask.

Do I have to buy the direction work to get a team?

No. If you already know what you are building and why, start with a delivery plan and skip the sprint — we will tell you so rather than sell you both. The sprint exists for the case where the answer is less settled than it feels, which is more common than anyone likes to admit.

What actually happens in a Direction Sprint?

Two weeks. We interview the people who own the decisions, go through the roadmap item by item, look at whatever data exists, and come back with a defensible sequence — plus an explicit list of things to stop doing. It ends in a working session, not a slide deck left behind.

Do you do one-off projects, or only subscriptions?

Both. A subscription gets you a standing team and continuous delivery. A custom build is one-time: we scope it in a short call, quote the whole thing, and hand it over finished — full IP, no retainer, optional support afterwards. Plenty of clients start with a custom build and move to a subscription once there is something live to look after.

How quickly can my team start?

Most teams are onboarded within 48 hours. Your dedicated team joins your Slack, accesses your repos, and attends their first standup within two business days.

Can I switch plans?

Yes. Upgrade or downgrade anytime — changes take effect at your next billing cycle. Urgent scaling can often be done within 24 hours.

What tech stacks do you cover?

All major stacks — React, Next.js, Vue, Angular, Node.js, Python, Go, Java, .NET, Flutter, Swift, Kotlin, plus AWS, GCP, and Azure.

What if a team member isn’t a good fit?

No-questions-asked replacement within 48 hours at no extra cost. Our 92% retention rate speaks to the quality of our matches.

Do I own the IP?

100%. All code, designs, and work products belong entirely to you. We have no claim to your intellectual property.

What’s the minimum commitment?

Monthly plans: cancel anytime with 30 days notice. Annual plans: two months free, billed yearly. No lock-in contracts.

How is this different from an agency?

Flat-rate dedicated teams, not hourly billing. Pre-assembled squads with daily workflows — the consistency of in-house with the flexibility of outsourcing. And an agency will build what you specify; we will tell you when the specification is the problem.

Ninety minutes. No deck.

Bring the decision you keep reopening. You’ll leave with a sharper version of the problem — and if we’re not the right people to fix it, I’ll say so inside the first twenty minutes rather than the third invoice.

If you filled in the diagnostic, your answers come with you. No forms.