Skip to main content

phoenix://accelerators

Some of your batch will reach demo day with a deck.

You know which ones by week three. This page is for the person running the programme, not the founders in it.

Founders should start at the homepage instead.

> the_cohort_problem

It reads as a company failure. It lands as a programme one.

A founder who reaches demo day without a working product has had a bad quarter. A programme that puts three of them on stage has a pattern — and the people in the room, the ones you need for the next batch, are the people best equipped to notice it.

It rarely happens for the reason it looks like. It is usually not a founder who didn't try. It is a technical co-founder who left, or never existed; a non-technical founder who cannot evaluate a contractor and so keeps not hiring one; or a build budget that went into a hire who took eleven weeks to arrive and then needed direction nobody in the company could give.

None of those are fixed by more mentorship. They are fixed by someone senior building the thing, with a hard end date, inside the programme calendar.

> fits_the_calendar

Four weeks fits inside a programme. Twelve does not.

This is the whole reason the page exists. A twelve or thirteen week programme cannot absorb a three-month build — by the time it lands, demo day has happened. It can absorb a four-week one with room on both sides: time to scope properly at the start, and time to put the product in front of real users before anyone stands on a stage.

Started early enough, a company arrives at demo day with a product that has been used, and a slide about what happened when people used it. That is a different conversation from a roadmap slide, and it is the conversation your programme gets judged on.

The weeks above are an illustration, not a fixed schedule — every programme runs its own calendar and we fit into it.

Illustrative placement in a twelve-week programme: scope in the first third, build in the second, iterate on real usage in the third.

> pricing

There is no cohort rate.

Companies from your batch pay what everyone pays: Sprints start at £4k, fixed scope, fixed price, four weeks, agreed in writing on a 30-minute scoping call before any work starts.

We could offer you a discount. We would then have to recover it somewhere, and the only place to recover it is scope — which means the cohort discount gets paid for by the founders, in the form of a build that quietly does less. One honest number is worth more to you than a percentage off.

There is also no partnership to sign, no perk-page listing to negotiate, no revenue share, and no referral fee in either direction. Nothing changes hands between us and the programme. Send us a company when one needs it.

> good_fit

Send us the ones who

  • Know what question the product needs to answer, and can say it in a sentence.
  • Have a founder who can make scope decisions in hours, not committee cycles.
  • Are early enough in the programme that four weeks still leaves room to use the thing.
  • Need a working product on their own infrastructure, not a clickable prototype.

> wrong_call

Don't send us the ones who

  • Need sustained throughput across several workstreams — that is a hiring problem, not a Sprint.
  • Have a product whose smallest useful version is still six months, usually for regulatory or safety reasons.
  • Are two weeks from demo day. We will not start something we cannot finish honestly.
  • Want a prototype to photograph for a deck. Cheaper and faster elsewhere, and we will say so.

The version of this for investors, with the cost arithmetic

> phoenix://book

Book it as the programme, not as a founder.

Thirty minutes with Josh to work out which companies in your batch this actually fits — and which ones it doesn't.

30 minutes · no pitch · no partnership to sign