Most builds don’t die at launch.
They die in the ninety days nobody is watching.
The ninety days where most builds prove out — or quietly fall apart. Built into every Orizon project. Behind your brand, or inside your team. Either way, we stay.
Most builds don't die at launch.
They die in the ninety days nobody is watching.
In our industry, the day a website goes live is supposed to feel like the end of something. The build team posts on LinkedIn. The shared channel goes quiet. The agency moves on to the next project.
We’ve watched what happens next more times than we’d like to admit. Real traffic finds the bugs that QA missed. The first checkout breaks for a customer using a browser nobody tested. The brand owner messages the team at eleven on a Saturday and gets a Monday-morning reply from a project manager already booked into the next kickoff.
The ninety days after launch are where most builds actually live or die. Real customers replace test users. Conversion rates settle. The people who built the thing find out whether the thing they built actually works.
So we decided to stay.
Every Orizon build comes with the Stays Program. Ninety days of structured post-launch care. Included. Never an extra invoice. Same channel as the build phase. Same names on the messages.
Ninety days. Three phases. Included.
- →Bug fixes from real traffic
- →Security patches
- →Deployment monitoring
- →Team training & handover
- →Analytics installation verified
The “we didn’t disappear” relief — the site is live and somebody is still watching it.
- →Performance audit on shipped pages
- →Real-user analytics review
- →First conversion-optimisation iteration
- →Accessibility pass
- →Content QA against live traffic
The “they’re still actively making it better” surprise — most agencies have moved on by week three.
- →Quarterly roadmap workshop
- →Named primary contact handover
- →Documentation of what comes next
The decision is yours, made with information you couldn’t have had on launch day.
By Day 90 you’ll know whether you want us to keep going. Most clients do.
Generous.
Not unlimited.
Clarity protects both sides. The Stays Program covers the ninety days after launch generously, but it isn’t a maintenance retainer in disguise.
- ✓Bug fixes on the original build scope
- ✓Performance work — image optimisation, caching, Core Web Vitals
- ✓Security patches and dependency updates
- ✓Analytics and monitoring verification
- ✓Minor copy and asset swaps (≤30 min per request)
- ✓One handover training session, recorded
- ✓The Day 60–90 roadmap workshop
- —Net-new features outside the original build scope
- —Design redirection past the brief
- —Marketing campaigns and ad creative
- —Third-party SaaS setup not in the original build
- —Multi-stakeholder strategy beyond the single roadmap session
- —Emergency development after Day 90 without an active plan
- —Anything that names a new outcome the build wasn’t scoped for
Part of the build.Not an afterthought.
The Stays Program is bundled into every Orizon project. Priced into the project quote so the team's time across the ninety days is paid for at contract signing. The program never shows up as a new line on a new invoice. It's part of what you already agreed to.
We bundle the program into one price rather than itemising it because the itemised version is what breaks the partnership. When every fix is a new ticket and every ticket is a new charge, the conversation stops being about the work and starts being about the invoice. We'd rather not have that conversation. So we built the program so we don't have to.
No Nickel-and-Diming
A unified financial structure lets us focus on solving the hardest technical problems — without the friction of administrative change orders.
The Stays Program
Ninety days of embedded post-launch care, included in every build — never a separate invoice.
Behind your brand.
Through your channel.
Most Orizon work ships under another agency’s name. Your client never sees an Orizon email, an Orizon invoice, or an Orizon face. Mutual NDA before the first call. Communication only through the channel you choose — your shared channel, your project tracker, your domain on the deliverables. The Stays Program runs the same way it runs everywhere else, but every message that reaches the client carries your branding, not ours.
Day 1 to Day 90, your client experiences continuity with your team. The same people who shipped the launch are the ones watching the analytics, patching the bugs, and writing the planning-call agenda in week twelve. From the outside, it reads as your retention play. From the inside, it’s how we built it.
It removes the post-launch support burden you’d carry unbilled — and gives your client a reason to renew with you, not to shop the next project to a competitor.
When you bring Orizon in directly, the Stays Program is a continuation, not a handoff. The team that knows your stack is the team patching the bugs and watching the analytics. They know every integration, every edge case, every business rule.
For founders who’ve worked with agencies before, that’s the part that’s usually missing. The build team gets replaced by a support team who doesn’t know the codebase. The Stays Program is how we never make you re-explain your business.
Inside your team.
Same people, kickoff through Day 90.
Day 91 —
three doors open.
The Stays Program closes formally on Day 90 with a one-page closeout document — cumulative hours, key fixes shipped, performance metrics before and after, and the agreed primary contact for the next phase. From there, the decision is yours.
Continue with us
A maintenance partnership scoped to your site. No tiers, no minimums; custom-quoted on the closeout call.
Choose this path→Hand to in-house
Hand over to an in-house team you hired during the build, with the closeout document and the named contact as the bridge.
Choose this path→Pause cleanly
Pause with a written check-in already on the calendar for sixty days out. No annual lock-in, no pressure on launch day.
Choose this path→We don’t sell tiers. Whatever comes next is shaped by what your site actually needs.
Read the full pricing approach→