An open-book guide to the engagement, from the first call to ninety days after launch. We're showing you the work, the timeline, the decision rights, and the answers to the questions you're about to ask. Read it the way you'd interview a co-founder you're considering hiring.
The first conversation is the start of the relationship, not a setup for it. After we speak, a small set of things land in your inbox — so you can move forward with the team behind you already in motion.
Each one is signed by the person who took the call. Nothing automated, nothing templated. The relationship is already underway.
“Four pieces, in your inbox, ready when you are.”
Orizon · sent back to you
Sent back promptly so the conversation can open up. Covers everyone on our side — the team you'll work with directly and any specialist we'd bring on.
From the person who took your call
Your ambition, your current setup, what we picked up on, and the shape we see the work taking — under their name, so you know exactly who's on it with you.
Orizon · scope
The shape of what we'd build together — the milestones, the sequence, the deliverables — written down so you can picture the engagement before it begins.
Calendar invitation
A Solve-the-Real-Problem workshop, where we map the brief against the outcome you're aiming for — and surface the gaps between the two.
Discovery & Alignment, then Strategy & Planning, then Build, then Launch & Stay. Each phase has one job — and each one closes with something you can read, share, or sign.
The first call is where the relationship starts. A co-founder takes it personally, comes prepared, and listens.
a clear picture of how we'd approach the build, and enough context to begin shaping the plan with you.
The whole engagement in one view — where the work moves through each phase, and what comes into your world along the way.
First conversations, shared context, alignment on the outcome and the ambition behind it.
Architecture, integrations, data shape, user flows, and the brand and delivery alignment underneath.
Engineering in rhythm, preview deploys on every change, ongoing check-ins under your brand.
A co-ordinated go-live, performance monitoring, and a smooth handoff to real traffic.
Real traffic meeting the build for the first time; early fixes and team training.
Analytics review, performance work, the first iteration shaped by what users actually do.
A roadmap workshop, partnership options, and a clear view of what comes next.
Not every project starts at the same point in its life. We work in four shapes — pick the one that matches where you are.
You have a client — or your own brand — that needs a custom build: a site, an app, a platform, an integration. We run the full four phases. This is what we're built for.
Someone else started it and stalled, or shipped something that doesn't do the job. We pick it up: a careful code audit first, then a written plan for what to fix, set aside, and rebuild. The audit stands on its own — take the findings and run, in any direction.
You have your own team doing the bulk of the work and need engineering capacity on top — for a feature, a sprint, a quarter. We work as part of your team, in your tools, on your standards. No long onboarding. Senior involvement from day one.
Some agencies finish their own build and want post-launch care without the build engagement. We run the Stays Program standalone — Stabilize, Tune, Plan — learning the codebase properly first, then running it exactly as we would on a build we shipped ourselves.
Not sure which one fits? That's what the fit call is for. Book it →
We've laid out the options below — tell us which ones your team runs, and we'll work in those.
If your team works somewhere we haven't listed, we'll meet you there.
We don't ask you to learn our tools to start the engagement.
For agency engagements, here's how discretion lands in practice. The NDA-first white-label model is the operating default — not a feature you have to ask for.
Mutual NDA, signed before any specifics change hands. Covers us and any sub-vendor we'd bring on for the engagement. Every member of our team is under NDA before they touch your repo.
Your Slack. Your project tracker. Your branded deliverables. Direct contact with your client only on your written request, with rules agreed first. The default is total separation — your client doesn't know we exist, and that is the design.
A non-solicit clause sits in every engagement we sign. If a client of yours comes to us directly, we route them back to you straight away, in writing. The partnership agreement template is available before any commitment is made.
We follow your decks, your terminology, your email domains. Every artefact ships under your name by default. The repo lives in your organisation, the staging environment runs on your subdomain, and the documentation reads as your team's — because operationally it is.
Engagements rarely break on quality. They break on quiet ownership — decisions taken in passing, assumptions that compound. So every decision below has a named owner on each side before the engagement starts. The names change per partnership; the structure stays the same.
If a decision is taken anywhere outside those owners — a corridor exchange, a side thread, a quick message between adjacent people — it stays in conversation until those two write it down together. That is how nothing gets lost.
08 / 10We're open about where an engagement begins and ends. Here's what every partnership includes by default, and where we'd shape a separate piece of work alongside it — agreed openly, before anything starts.
What every partnership includes — no line items to negotiate, no surprises later.
Have a question we haven't answered? Ask it on the call →
We read every message · Within a day, every time · We work in your timezone