Question 1

What's the difference between a technology partner and a tech vendor?

Accepted Answer

Please visit the site to view this detailed answer.

Question 2

How do I know my white-label partner won't contact my clients directly?

Accepted Answer

Please visit the site to view this detailed answer.

Question 3

What should I expect from a technology partner after go-live?

Accepted Answer

Please visit the site to view this detailed answer.

Question 4

Can a small agency use white-label tech to compete with larger agencies?

Accepted Answer

Please visit the site to view this detailed answer.

Question 5

How is pricing handled?

Accepted Answer

Please visit the site to view this detailed answer.

Question 6

What if our client meets your team by accident at an event?

Accepted Answer

Every team member carries a no-mention rule for partnership engagements they touch. A slip is a documented breach of the partnership agreement on our side.

Question 7

Can we trial you on one project before signing the full partnership?

Accepted Answer

Please visit the site to view this detailed answer.

Question 8

Do you have active competitors of ours in your current engagements?

Accepted Answer

We’ll tell you on the second call, before specifics change hands. If we’re working with a direct competitor inside your protected niche and region, the partnership wouldn’t make sense for either side. The non-compete is region-and-niche-specific, written into the agreement, and negotiable on both sides.

Question 9

How does communication work day to day?

Accepted Answer

Please visit the site to view this detailed answer.

Question 10

What’s the turnaround on a typical engagement?

Accepted Answer

Scoped on the second call alongside the SOW. Most of full-build engagements move on a sprint cadence with launch windows agreed in the planning phase. Take-over engagements add a code-audit week up front. Standalone post-launch-only engagements have a codebase-learning ramp before care begins.

Question 11

Who owns the code and the IP when an engagement closes?

Accepted Answer

You do. From the first commit. Every artefact transfers to your organisation at commit time — no phased delivery, no escrow, no clauses that hold IP back. Through you, your client owns it on the terms you’ve agreed with them. The closure is operational, not a release of rights.

Question 12

What technologies and frameworks do you cover?

Accepted Answer

Frontend (React, Next.js, Vue, Angular, TypeScript). Backend (Node, Python, PHP/Laravel, .NET, Ruby on Rails). Headless CMS (Sanity, Strapi, Contentful, WordPress). Ecommerce (Shopify Plus, WooCommerce, Magento, BigCommerce). Mobile (React Native, Flutter, native iOS/Android). AI/automation (custom agents, LangChain, integrations). Full grid above.

Question 13

How are scope changes mid-build handled?

Accepted Answer

Re-quoted on a separate SOW in writing before any new work begins. Variance reports surface the same week from the lead who saw the change first, on their own message in your channel. Nothing absorbed quietly. You decide what to pass through to your client and what to absorb.

Question 14

What does a typical first call look like?

Accepted Answer

About forty-five minutes, taken personally by one of our leads. Three questions, in this order: what you're trying to build, what's already in place, and what twelve months from now looks like if the engagement worked. We listen for the gaps as much as the answers — the real shape of the work usually lives there. The first call is the work, not the setup for it.

Question 15

How do you handle scope changes mid-build?

Accepted Answer

Changes get written down before they start. We map the new work openly, including what it is, what it changes, and what it sets in motion, so you see the shape of it before anything begins. Anything that affects the original direction is surfaced to you the same week by the lead who saw it first. Nothing gets folded in quietly.

Question 16

What does this look like behind our agency brand?

Accepted Answer

We work in your tools, under your domain, with your name on every deliverable. Mutual NDA, including any specialist we'd bring on. Your client experiences continuity with your team, meaning they don't see us in the picture at all. A non-solicit clause sits in every engagement we sign. Brand alignment is the operating default, not a feature we add on top.

Question 17

What happens after the Stays Program ends?

Accepted Answer

A one-page closeout document, then your choice. A continued partnership with us, shaped around what the product actually needs. A handover to your in-house team. Or a clean pause with a check-in already on the calendar. Whatever comes next is built around the relationship and the work, not a tier on a page.

Question 18

How do you decide when to push back on a brief?

Accepted Answer

Every engagement starts with the Solve-the-Real-Problem workshop, meaning the brief is the entry point, not the destination. If the route described in the brief won't reach the outcome you want, you'll hear it from us before a single ticket gets written. Honest before comfortable. The workshop output is yours, ready to use, however the relationship moves forward.

Question 19

How does the white-label model work in practice?

Accepted Answer

Your client never sees an Orizon name, email, invoice, or face. We work on your tools — your Slack or Microsoft Teams, your project tracker, your repo organisation, your domain on every staging environment. Every commit is in your team's name format. Every document we produce reads as your agency's work. Mutual NDA, non-solicit by contract.

Question 20

Who owns the code and the IP when an engagement ends?

Accepted Answer

Your agency (and through you, your client) owns everything from the first commit. Every artefact — code, design files, architecture decision records, documentation — transfers to your repo at commit time. No phased delivery, no escrow, no clauses that hold IP back. The cleanest possible exit terms.

Question 21

What size engagement do you take on?

Accepted Answer

From the Solve-the-Real-Problem workshop as a standalone (a few days) through platform work that runs across multiple quarters. The minimum useful engagement is the workshop. The maximum is whatever the build calls for. Most engagements span two to four capabilities, lasting a few months.

Question 22

What if our engagement needs a technology not in your stack table?

Accepted Answer

Mention it on the first call. The stack lists the technologies we work with most often, not the only ones we'll touch. We add technologies as engagements call for them, not as a marketing exercise. If we can't deliver on something honestly, you hear that on the first call.

Question 23

Where are you based, and how do you work with USA clients?

Accepted Answer

Headquartered in Ahmedabad, India. The team operates on a working window that overlaps with the US business day — morning east-coast through afternoon west-coast. Live conversation is available during the working hours of the agencies and brands we work with. Asynchronous handovers everywhere else.

Question 24

What happens to the build after launch?

Accepted Answer

Every engagement includes a ninety-day post-launch programme — same channel as the build phase, same names on the messages. Stabilize, Tune, Plan. After the programme ends, ongoing maintenance is scoped to what your client's site needs. See /stays-program for the structure.

Frequently Asked Questions