Partnerships

An engineering team that stays with you.

For companies with several things to build at once. A partnership starts with a discovery and runs in two-week cycles, month after month, with the same team.

Built for

When one project is not enough

01 Platforms across several areas Sales, operations and finance on one system, built in stages and connected to what you already use.
02 AI agents with governance Agents that work with your data and your team, with permissions, logs and a person who answers for them.
03 Engineering, growth and operations together The software, the campaigns that feed it and the servers that run it, planned as one roadmap.
How it is priced

One monthly price, built from the blocks you need

After the discovery you get a written proposal with the blocks, the cycle plan and one monthly price.

Starts with Technical discovery $690 one-time One to two weeks to map your process and systems. Credited against the partnership if you go ahead. Buy the discovery →
Monthly blocks
Part-time CTOArchitecture and vendor decisions, reviews and a monthly roadmap.
From $1,490 / month
Support and evolutionMonitoring, backups and monthly hours for changes.
From $390 / month
Meta Ads at scaleSeveral brands or countries, with creative sized to your volume.
Quoted
Delivery managementA project manager running your work in two-week cycles.
Quoted
Managed infrastructureHosting, monitoring and support on our servers or yours.
Quoted
Every cycle

What you get every two weeks

01 Something usable Each cycle ends with work your team can use and review, not a progress slide.
02 A written status Progress, risks and the decisions we need from you, in a few lines.
03 Milestones you approve Owners, dates and acceptance criteria in Firespace App, closed with your sign-off.
04 One lead, same team One person answers for the partnership, and the team does not rotate.
Are you an agency? Partner terms and a standing engineering team under your brand. See partner terms →

Questions

How does a partnership start?

With a technical discovery. It ends with findings, prioritised requirements and a written proposal; its price is credited if you go ahead.

Can we change priorities along the way?

Yes, between cycles. Every two weeks we agree what comes next, and changes to scope or price are written down before they apply.

Who owns the code and the data?

You do. Repositories and databases are yours, and your data can always be exported.

Planning more than one project?

Tell us what you are building this year. We reply within one working day with how a discovery would look.