org.tech / Company / Partners You keep the relationship. Terms per partner

For the advisor whose client keeps asking about AI, and who cannot in good conscience recommend a tool they cannot scope.

Your client trusts you. We would like to keep it that way.

There is no partner programme here, no badge and no tier table. There is a product that solves a problem your clients keep raising, an entry offer small enough to recommend without risking your credibility, and a standing rule that we never present ourselves as your staff or take custody of your client's account. The commercial terms are agreed with you, one partner at a time.

People who already hold the trust.

AUDIENCE · WHO THIS IS FOR

Every organization is being asked about AI by its own staff, and most of them ask their existing advisor first. That advisor is usually the one person in the room with nothing to sell and something to lose, which is exactly why the question lands there.

If that is you, this page is about what you can do with the question other than deflect it.

You keep the client
Terms agreed per partner
No programme, no badge
01

Managed IT providers.

You already run their environment and they are asking you where an AI tool would put their data. The deployment lands in the client's own cloud account, so it does not cut across your estate or your support model.

02

Security and privacy advisors.

You are the reason a SaaS AI tool got stopped, and you would rather offer an alternative than be the department of no. The posture questionnaire is written for you to read before anyone is sold anything.

03

Accountants and advisers.

Your clients ask you what this should cost and whether the spend is sane. Published prices, compute billed by the provider directly to the client, and no per-seat subscription to forecast.

04

Fractional executives.

A fractional CIO, CTO or CISO is often the one expected to have a position on this. Ours is written down in enough detail that you can agree or disagree with it in public.

The question is already on your desk.

THE CASE · WHY BOTHER

Referring a supplier is a risk to a relationship you spent years building, so the case has to be better than "we pay a fee". Here is the case as we would make it to ourselves.

The conflict worth naming

If your firm resells a bundled suite copilot, this will occasionally compete with it, and that is better said here than discovered later. Our own position is that a bundled copilot is often fine for ordinary productivity and the wrong instrument for sensitive material and custom capability. Both of those can be true for the same client at the same time, and the honest conversation usually ends with them running both.

How it works, step by step.

MECHANICS · IN PRINCIPLE
  1. 01The introduction

    You introduce, and stay in the room

    You make the introduction and you are welcome on every call, including the technical ones. Nothing is presented to your client that you have not seen first, and we will not schedule around you. If you would rather run the conversation yourself with us behind you, that works too.

    Gate
    Is this client's problem actually one we solve, or are we about to waste your credibility?
    Decides: you and org.tech, before the client is approached
  2. 02The assessment

    A bounded, paid first step

    The engagement starts with the strategic assessment: their systems mapped, the posture questionnaire worked through with whoever holds the security veto, a recommended tier with every override reasoned, and a deployment plan sized to their account. They keep it either way. You get the same document, if the client agrees to share it.

    Gate
    Does governed AI earn its place here, and can the client name the owner of the outcome?
    Decides: the client's executive sponsor
  3. 03Deployment and after

    The platform lives in their account, not in ours or yours

    The deployment is built into a cloud account the client owns and is billed for directly. The service agreement for the platform is between org.tech and the end client, in every arrangement, because a platform relationship routed through a third party quietly turns into a subcontract that nobody can inspect. Your commercial arrangement with us sits alongside that, agreed in writing between us.

    Afterwards, you stay the advisor. We stay the operator. Your client can end either relationship without losing the platform, which is the same promise we make to them about us.

    Gate
    Is it clear to the client who operates the platform and who to call?
    Decides: everyone, in writing, at the start

What you can say in one sentence.

LANGUAGE · COPY THIS

Nobody refers a supplier they cannot describe. Here is the sentence, the two-sentence version and the money line, written so they can be repeated accurately by someone who is not a cloud engineer.

org.tech deploys a private AI platform into a cloud account you own, with your policies enforced in the system, and you keep the platform whether or not you keep them.The one sentence, copy it verbatim

A

The two-sentence version.

"Most private AI means the vendor holds your data privately. org.tech deploys the platform into a cloud account you own and are billed for directly, applies your privacy and security policies as controls in the system rather than as a document, and operates it for a monthly fee you can cancel while keeping everything that was deployed."

For an emailVerbatim
B

The money line.

"It starts with a $2,500 assessment they keep either way. Deployment starts at $2,500 and typically lands around $5,000 once scoped. Managed operations is $500 a month, cancellable. Compute is billed by their own cloud provider directly to them at list price, so there is nothing to mark up." All figures Canadian dollars.

For a CFOThe ladder
C

The security line.

"Designed to align with SOC 2 and ISO/IEC 27001. They provide the technical controls that support your program, and they hold no third-party attestation, which they say out loud on their own site." Say it that way. A partner who overstates our compliance position is the fastest way to lose a security reviewer.

For a reviewerThe split
D

What not to say.

Not "the AI runs inside your network", because a managed model service cannot. Not "your data never leaves the country", because residency is a real choice with a real capability cost. Not "certified". If you are unsure whether a sentence is safe, the page of things we refuse to claim is public.

Four things we will never do.

BOUNDARIES · WHAT WE WILL NOT DO
01

Take over your account.

We deploy and operate a platform in the client's own cloud account. We do not want their endpoints, their network, their identity estate or their books, and we will decline work that arrives by drifting into yours. If a client asks us to, we will tell them to ask you.

ScopeOurs stays narrow
02

Dress up as your staff.

No white-labelling of us. The platform is white-labelled to the end client, which is a different thing entirely: their brand on their dashboard. We will not appear on a call as your employee, sign an email as your firm, or let a client believe your team built what we built.

IdentityNever hidden
03

Hide who operates it.

The end client always knows that org.tech deploys and runs the platform, who the principal is, and how small the practice is. A continuity risk concealed behind a partner logo is the exact failure this company is built to avoid, and we publish our own version of that risk.

TransparencyContinuity
04

Publish a badge wall.

No partner logos, no tier names, no certification crests, and no figure on this page telling you what a referral is worth. Terms are agreed per partner, in writing, and a number printed on a web page before we have met is a number invented for marketing.

TermsPer partner
01Is there a referral fee?

Terms are agreed per partner and put in writing, and we do not publish a rate. Some arrangements are a straightforward referral, some are a resale where you hold the commercial relationship for your own scope of work. In every version, the platform service agreement is between org.tech and the end client, because that is what keeps the ownership story true for them.

02Can we operate the platform for our own clients?

Possibly, and it is a real conversation rather than a brochure answer. It needs genuine cloud engineering capability on your side, since running a deployment means reading infrastructure as code and deploying a release. Start with the demo and an assessment on one client, and we will both learn quickly whether the fit is there.

03What do you need from us?

An accurate description, an introduction to someone who can decide, and your honesty about where you think we are wrong. That last one is worth more than the first two: a partner who pushes back on a claim is doing the same work our own claim discipline does.

04Will you sell around us?

No. A client you introduce is your relationship, and we hold that as a standing rule rather than a clause that expires after twelve months. If a client you introduced approaches us directly about work in your scope, we will tell you.

⎯⎯ Book the strategic assessment ⎯⎯

Your private AI, inside your control ·

Book a call to talk about a specific client, or send them the assessment and stay in the room for all of it.