About
A studio built around one idea: own the whole chain, or own none of it.
Phoenix Info is an engineering and growth studio of around fifty engineers, marketers and specialists. We work with companies who have outgrown the point where three separate vendors can coordinate well enough to be useful.
delivered
satisfaction
specialists
served
The origin
We started by fixing other people's handovers
A large share of our early work was inheriting systems that had been built and abandoned. Undocumented code, cloud accounts nobody had the credentials for, a marketing site the client could not edit, and a CRM full of leads that had never been followed up.
The pattern was consistent enough to be instructive. Each individual vendor had done roughly what they were asked. The failures were all in the gaps — the site team assumed the CRM team was handling lead routing, the CRM team assumed the backend team was, and nobody was.
That is why we deliberately kept engineering and marketing in the same organisation, under shared accountability, rather than specialising in one and referring out the other. It is harder to run and it is the entire reason clients consolidate onto us.
How we work
Six commitments, and what they cost us
Values pages are usually worthless because nothing on them has a downside. Each of these has one, so here they are.
We recommend against work we could bill for
If your existing system can be extended rather than rebuilt, we will say so — even though the rebuild is the larger invoice. The cost: we lose deals to firms happy to quote the rewrite.
You own everything from day one
Repositories in your organisation, cloud accounts in your name, domains at your registrar. The cost: nothing stops you leaving, so we have to keep earning it monthly.
One named engineer, one named lead
You always know who is doing the work and who to call. The cost: we cannot silently swap people to whoever is free, which constrains how fast we can take on new work.
Working software every two weeks
A staging URL you can click, not a status update. The cost: you see the unfinished parts, which is uncomfortable but catches wrong assumptions in week three rather than week twelve.
We are open about our AI use
We say where AI tooling sits in our process and where a human is accountable. The cost: some buyers would prefer to hear a flat no, and some competitors quietly imply exactly that.
We plan our own exit
Documentation and training aim at your team running things without us. The cost: some clients genuinely do leave once capable. Most bring us the next project instead.
Fit
When to call us, and when not to
A bad-fit engagement wastes your budget and our reputation. Better to be direct before the first call than three weeks into a project.
- You have a real business with real customers and the system is now the constraint
- Several connected problems — site, internal tooling, and demand
- You want to understand the trade-offs, not just approve a deck
- You can give us access to the people who actually use the system
- You are hiring for capability, not just the lowest hourly rate
- You need it live in two weeks and the scope is still moving
- The main decision criterion is the lowest quote received
- Nobody internally can commit time to reviewing progress
- You want AI added because the board asked, with no defined use
- You are seeking a vendor to blame rather than a team to work with
Next step
Tell us what is actually broken.
A 30-minute call with an engineer, not a salesperson. You will get a straight read on whether we are the right team — including if the answer is no.