Behind your brand. Nowhere near your client.
A white-label tech partnership with documented terms, a published five-layer discretion framework, a fixed-cost scoping model, and a ninety-day post-launch programme included in every engagement. Sit behind your brand on a build, an audit, a take-over, or only the launch. The same standards on every route.
Why our names aren’t on this page.
We work white-label by default. Most of what Orizon ships sits behind another agency’s brand, under an NDA they signed with their client. We don’t put our names on work that isn’t ours to claim, and we don’t put them on this page either.
The full reasoning is on About →
What we build for agencies.
Twelve categories of build we ship under agency brands, each with handoff-ready code, your team’s commit conventions, and documentation that reads as your team produced it.
Handoff-ready code
Clean, modular, structured for speed.
Your team’s conventions
We adopt your git workflow & commit patterns.
Docs like your own
Pragmatic, thorough white-label docs.
Custom WordPress
Clean code, SEO-friendly structures, custom theme + plugin development, client-ready handoff.
→Webflow Website Builds
Pixel-accurate Webflow with CMS collections, animations, scalable class systems.
→Headless CMS Websites
Next.js + Sanity, Strapi, or Contentful. API-driven content platforms built for scale.
→Shopify & Shopify Plus
Theme builds, Liquid customisations, CRO, app integrations, storefront performance.
→WooCommerce Development
Custom product flows, checkout customisation, payment gateways, clean documentation.
→Custom Web Applications
Dashboards, SaaS modules, internal tools — database architecture and backend logic included.
→Mobile App Development
iOS, Android, cross-platform (React Native, Flutter). Client portals and internal tools.
→AI Agents & Automation
Custom AI agents, chatbot integrations, workflow automation, integration with legacy systems.
→API & Third-Party Integrations
CRM, ERP, payment gateways, inventory and analytics platforms. Endpoint docs included.
→SEO, AEO & GEO
Schema, internal linking, AI-answer-ready structure, location-page architecture.
→Performance & Core Web Vitals
Site speed, responsive behaviour, Lighthouse audits, before/after reports for your client.
→Accessibility Remediation
Compliance fixes that meet legal, usability, and enterprise accessibility standards.
→Maintenance & Support
Plugin and module updates, uptime monitoring, backups, security patches, and emergency fixes.
→What we build with. The tech stack.
The Orizon site runs on Next.js 14 + Sanity + Vercel. Client engagements run on whatever the build calls for. Below is the working stack across recent and current engagements.
Description
Hover any technology to read what it’s for. Tap to add it to your stack summary below.
Your Stack Summary
Select the technologies your build leans on. We’ll scope the engagement around exactly this stack on the first call — and flag anything we’d add.
Engagement model matrix. Four ways to engage.
Not every project arrives at the same point in its life. Partnerships work in four shapes.
A new build, end to end
The full four-phase engagement of Discovery, Strategy, Build, Launch & Stay, scoped as a fixed-cost SOW on the second call. Perfect for when you need a white-label team to deliver a client project.
A take-over gone sideways
Code audit first, written diagnostic next, then a plan to fix, set aside, or rebuild. For when a previous partner stalled, shipped something broken, or quietly disengaged.
Extended-team capacity
Embedded senior engineering on top of your in-house team for a specific feature, sprint, or quarter. Senior from day one, closing on the agreed date.
Standalone post-launch
Runs on a build we didn’t ship. Time to learn the codebase first, then the same operating standard as any engagement we shipped ourselves.
Not sure which one fits? That’s what the fit call is for. Bring where you are and we’ll tell you which shape makes sense — on the first call, before any commitment.
Book a fit callPricing modes. How pricing works.
No tier table. No hourly menu. The partnership uses three pricing modes depending on the shape of the engagement.
Project-scoped
Fixed cost. In writing.- ·Scoped openly on the second call
- ·Written SOW with a milestone timeline
- ·Fixed cost on the SOW — anything outside gets a new one
New builds, take-overs, and any defined deliverable.
Sprint-retained
Capacity, by the sprint.- ·Retained capacity in two-week sprints
- ·Named hours and named outputs per sprint
- ·Renewed in writing each sprint
Steady delivery rhythms and quarter-long extended-team work.
Workshop-only
A sharp read, first.- ·Solve-the-Real-Problem workshop, standalone for a flat fee
- ·Written diagnostic and scope outline as the deliverable
- ·No commitment to the build that follows
A sharp read on a brief before committing to a build.
Re-quote rules
Anything that moves the original scope gets re-quoted before work begins. Scope creep gets surfaced the same week by the lead who saw it first, on its own message in your channel — not folded into a status update.
Included by default
Mutual NDA returned promptly. Brand alignment brief on the second call. Decision-rights matrix signed before kickoff. ADRs committed to your repo. The ninety-day post-launch programme. Termination clean, no penalty.
Scoped as separate work
Net-new builds outside the SOW. Migrations to platforms not in scope. Brand or visual identity work. Paid media setup. Long-tail SEO content. Anything that isn’t engineering on the build at hand. Fixed-cost. Re-quoted before scope moves. No surprises.
From first message to first build day. How a partnership starts.
Five stages from inquiry to first build day. Stages, not days; every engagement moves at the pace its scope calls for.
Inquiry
Drop a line. Bring the brief you’re working from, the previous-partner experience that didn’t work, or the client engagement you’re trying to figure out how to staff. The first reply comes from a co-founder, not an SDR. We read what you’ve sent before we book the call.
Fit call
A focused call held by a co-founder. Three questions in order: what you’re trying to build, what’s already in place, what twelve months from now needs to be true. The mutual NDA goes out the same day. If the partnership doesn’t fit, you hear that on the call. The honesty isn’t optional.
The workshop
Solve-the-Real-Problem. The brief is the entry point, not the destination. We test it against the outcome and surface the gaps. The output is a written diagnostic and a scoped quote outline — yours to keep, however the partnership moves forward.
Agreement
Partnership agreement + brand alignment brief. Six clauses (see below). Plus a brand alignment brief — a questionnaire capturing voice, visual standards, terminology, tooling, client-facing conventions. Returned and signed before kickoff. The agreement is shorter than most NDAs.
Kickoff
Decision-rights matrix signed. Working channel agreed. Repo access provisioned by your DevOps. The first build day starts with a standup in your tools, in your team’s voice. From here, the four-phase engagement runs as documented on Process.
What your client never sees. Five layers of invisible.
Discretion broken into five operational layers. Each one holds for the full duration of the engagement.
Invisible team
Your client never sees an Orizon face, name, or email. Our public profiles don’t name the work that ships under your name.
Invisible tooling
Your Slack, your tracker, your repo organisation, your domain on every staging environment, your name in every commit author field.
Invisible billing
We invoice you. You invoice your client. The accounting trail stops at your books.
Invisible IP
Every artefact gets committed to your repo under your team’s name format. IP transfer is immediate, not phased.
Invisible exit
When an engagement closes, no leftover credentials, no orphaned admin accounts, no support inbox on our side. The relationship that began invisibly ends the same way.
Where the partnership sits. Partnership vs in-house vs offshore.
Three routes an agency takes when extra engineering capacity is needed. They’re not equivalent. Here is what changes between them.
| Dimension | In-house hire | Offshore freelancer | Orizon partnership |
|---|---|---|---|
| Senior review on every layer | Depends on the hire’s seniority — most agencies can’t justify a senior salary for occasional needs. | Almost never. Quality is variable, review process is informal. | Senior eyes on architecture, infrastructure, security, performance before code reaches your repo. |
| NDA + non-solicit | Employment contract — but protection only holds while employed. | Sometimes a one-off NDA. Non-solicit rarely enforceable. | Mutual NDA + non-solicit in every engagement, holding through the engagement and an agreed tail. |
| IP ownership | Yours from the start. | Variable. Some platforms hold IP in escrow until payment clears. | Yours from the first commit. Written into the agreement. |
| Brand alignment + voice | High, with onboarding. | Low. Hand-off is typically the limit. | Brand alignment brief signed before kickoff. Every artefact reads as your team’s work. |
| Communication channel | Your tools. | Often platform-specific; pushes out into email. | Your Slack, your tracker, your repo. We don’t run a portal you have to check. |
| Capacity flex | Hard — hiring and firing has overhead. | Easy — but quality varies project to project. | Sprint-retained or project-scoped. Scaling up or down is in writing. |
| After launch | Whatever you build internally. | Usually ends at delivery. | Structured care included by default. |
| What you’re paying for | Salary + benefits + overhead + recruitment + retention risk. | Hourly rate, with quality and IP risk built in. | Project-scoped or sprint-retained, with the partnership agreement absorbing the risk. |
Senior review on every layer
Depends on the hire’s seniority — most agencies can’t justify a senior salary for occasional needs.
Almost never. Quality is variable, review process is informal.
Senior eyes on architecture, infrastructure, security, performance before code reaches your repo.
NDA + non-solicit
Employment contract — but protection only holds while employed.
Sometimes a one-off NDA. Non-solicit rarely enforceable.
Mutual NDA + non-solicit in every engagement, holding through the engagement and an agreed tail.
IP ownership
Yours from the start.
Variable. Some platforms hold IP in escrow until payment clears.
Yours from the first commit. Written into the agreement.
Brand alignment + voice
High, with onboarding.
Low. Hand-off is typically the limit.
Brand alignment brief signed before kickoff. Every artefact reads as your team’s work.
Communication channel
Your tools.
Often platform-specific; pushes out into email.
Your Slack, your tracker, your repo. We don’t run a portal you have to check.
Capacity flex
Hard — hiring and firing has overhead.
Easy — but quality varies project to project.
Sprint-retained or project-scoped. Scaling up or down is in writing.
After launch
Whatever you build internally.
Usually ends at delivery.
Structured care included by default.
What you’re paying for
Salary + benefits + overhead + recruitment + retention risk.
Hourly rate, with quality and IP risk built in.
Project-scoped or sprint-retained, with the partnership agreement absorbing the risk.
Six clauses · The same six every time. The agreement we’d sign.
Six clauses, the same six in every partnership. Shared openly on the second call. The full agreement runs to a few pages.
01 · Mutual NDA
Both sides. Covers Orizon and any specialist for the duration of the engagement plus an agreed tail.
02 · Non-solicit
If a client of yours reaches us directly, we route them back in writing. Non-negotiable on our side; timeframe is negotiable on yours.
03 · IP assignment
Every artefact gets committed to your repo under your team’s name format. IP transfer is immediate, not phased.
04 · Decision-rights matrix
Named owners on each side for architecture, scope, sequence, and escalation. Written per engagement.
05 · Termination
Either side ends with written notice. Clean handover including credentials and any active maintenance position. No penalty.
06 · Brand alignment
Your voice, your visual standards, your terminology, your tooling. We adopt them; we don’t ask you to adapt to ours.
Lines we’ve decided not to cross. What we won’t do.
Five operating lines, written into the partnership agreement, signed before kickoff.
No direct contact
Never contact your client directly. No emails, no calls, no DMs on platforms where they could find us. The only exception is a written request from you authorising a specific interaction, with rules agreed first.
No public naming
Never name you publicly without consent. No posts on social, no client logos on a clients page, no name-drop in a sales conversation. Written go-ahead from you comes first.
No soliciting
Never solicit your client. Contractually bound. If a client of yours ever reaches Orizon directly, we route them back to you in writing the same day.
No silent specialists
Never sub-contract without naming the specialist. Specialists are introduced by name, scope, and NDA status before they touch your repo. Nobody appears in your engagement you haven’t been told about.
No niche conflict
Never compete in your protected niche. The partnership agreement names the niche and region you’ve asked for protection in. We don’t take engagements that would compete with you inside that boundary.
Questions you’re about to ask. Common questions.
The partnership conversation. Stay in touch.
Bring a brief that’s been sitting on your desk. A project the previous partner stalled on. A client engagement you’re trying to figure out how to staff. We won’t pitch you. We’ll read what you’ve sent us and tell you what we’d do with it on the first call.