phoenix://investors
One of your companies can't ship.
You already know which one. This page exists so you can decide, in about thirty seconds, whether we're worth an introduction — and so you can forward the URL instead of writing the explanation yourself.
Written for the person making the intro, not the founder taking it.
> the_arithmetic
What shipping actually costs out of the round.
A contract developer senior enough to make architecture decisions without supervision runs around £600 a day. Eight weeks of that is forty working days — roughly £24,000, with no fixed end date and no commitment to a shipped thing at the end of it. For reference, the UK median contract rate for a software developer was £513 a day over the six months to 16 August 2026; £600 is what the senior end costs.
A junior hire is cheaper per day and far more expensive per decision. It is a twelve-month commitment made by a company with a twelve-month runway, it carries recruitment lead time before anyone writes a line of code, and it needs a senior engineer in the room to say what to build — which is precisely what the company doesn't have, and why it can't ship.
A Sprint is fixed scope, fixed price, four weeks. Sprints start at £4k and land between £4k and £8k depending on scope, agreed in writing before any work starts. Out of a £250k pre-seed that is between 1.6% and 3.2% of the round for a working product on their own infrastructure.
That is the whole argument. If the numbers don't move you, nothing further down this page will.
£600/day is the senior end of the UK contract market. Median for a software developer contract was £513/day over the six months to 16 August 2026 — ITJobsWatch.
> what_they_get
A working product on their stack, in four weeks.
- Scope
- Agreed on a 30-minute scoping call and written down before any work starts. It does not move mid-Sprint. If the honest cut doesn't fit four weeks, they get told that on the call rather than in week three.
- Ownership
- Deployed to their infrastructure, with handover docs, and they own the code. No lock-in, no hosting hostage, no proprietary framework that only we can maintain.
- Accountability
- One senior engineer — Joshua Sandhu — leads every Sprint personally, kickoff to ship. Trusted collaborators when scope demands it, and the founder always knows who is on their project. No account manager between them and the build.
> scope_discipline
The thing you're actually underwriting.
Speed is not the risk. A developer who will not cut scope is the risk, because that is the one who burns the round — not by charging too much, but by agreeing to everything the founder asks for and delivering none of it on time.
Both published case studies name what got cut and why, because that is the part worth checking. In the retail AI build we cut multi-warehouse, full seasonal modelling, ERP write-back, and three of the four integrations the client had already paid for. We also cut the CEO's dashboard, which was the argument, and shipped a CSV export instead. In the consumer AI build we cut a fifty-brand catalogue, accounts, the web version, and the share function the founder wanted most.
None of those cuts were popular on the call. All of them were the reason the build shipped.
> do_not_introduce_us_if
When not to make the introduction.
You are staking your own credibility on this, so here is where we are the wrong call.
They need a team, not a build.
If the company already knows what to build and needs sustained throughput across several workstreams, they need to hire. A Sprint answers a question; it does not staff a roadmap.
The scope genuinely cannot be cut.
Some products are not provable in a reduced form — hard regulatory surface, safety-critical systems, anything where the smallest useful version is still six months. We will say so on the call rather than take the money.
They want a prototype for a deck.
We build working products on real infrastructure. If a clickable prototype answers the question, that is cheaper and faster elsewhere, and we will tell them so.
The founder cannot make decisions inside a week.
Four weeks only works when scope decisions land in hours rather than in committee. A founder who needs to consult three people before every call is not going to enjoy this.
> what_we_do_not_claim
What you will not find on this site.
No client outcome metrics. We do not publish what our clients raised, what they earned, or what their users did, because we do not have written clearance to. The case studies stop at what we built and hand over — which is the less impressive half of the story and the half we can stand behind.
No logo wall. Both client engagements are under NDA and both case studies are anonymised. The two organisations named on the homepage — ScienceBank and a Harvard Medical School lab at Mass General Brigham — are Josh's own company and his own consultancy, labelled as such. Neither hired Phoenix Solutions.
No availability countdown. The site used to carry a monthly slot count. It went stale, which is what slot counts do, so it is gone rather than maintained badly.
> how_an_intro_works
Forward this page. That's the whole ask.
Send the founder to globalphoenix.co.uk/book or copy Josh in directly at joshua.sandhu@globalphoenix.co.uk. The first call is thirty minutes, has no pitch in it, and ends with a straight answer about whether a Sprint fits their build.
There is no referral fee, and there will not be one. If we start paying for introductions, the introductions stop being worth anything — to you or to the founders taking them.
If you want to test us before you spend your own credibility, book the call yourself and ask about a company you know. Thirty minutes will tell you more than this page can.
> phoenix://book
Worth an introduction?
Book the call yourself and ask about a portfolio company. No pitch, no follow-up sequence.
30 minutes · no pitch · no referral fee, in either direction