For managed service providers
An AI security service you can sell on Monday.
Your clients are asking about AI. Their insurers are asking about AI. Reselling AI licenses carries no margin and you already know it — the money is in the service wrapped around them. Binary Rogue delivers that service under your brand.
How it works
You keep the relationship. We do the work.
-
You spot the trigger
A client's cyber renewal is coming up, or a security questionnaire has stalled a deal of theirs, or they have asked you what to do about ChatGPT. You already know this before anyone else does — that is the advantage the channel has and why this works.
-
You scope it with a worksheet
Employee count, identity platforms, and whether they run any AI systems of their own. Three inputs produce a price. No discovery call with us required, and no waiting on a quote to get back to your client.
-
We deliver, branded as you
Every deliverable is built white-label from the first engagement — your logo, your name, your client's name. We can work behind your team or alongside them on a call, whichever your relationship calls for. Your client does not need to know we exist.
-
You keep the margin and the renewal
You bill your client at your rate. Watch converts into recurring revenue on your agreement, not ours. We never approach your clients directly — that is in the partner agreement, not just in the conversation.
Partner pricing
What you pay, and what you have room to charge.
| Service | Your cost | Typical end-client price | Delivery |
|---|---|---|---|
| Rogue Scan Discovery and evidence |
$750 | $2,000–2,500 | 5 business days |
| Rogue Audit Discovery, adversarial testing, governance |
$3,000 | $6,000–7,500 | 2–3 weeks |
| Rogue Watch Ongoing monitoring and renewal evidence |
$350/month | $750–1,000/month | Ongoing |
Prepaid for the first two engagements, net 30 thereafter. End-client pricing is illustrative — you set your own.
The version of this that actually builds your pipeline: run a discovery pass on a prospect you are trying to win, and walk in with a list of the AI applications holding access to their tenant. It is specific, it is about them, and it is a conversation no competitor is having. Ask us about partner terms for prospect engagements — that is a different arrangement to client delivery and it is priced to be used.
What you get
Partner enablement
- A one-page sell sheet in your branding, ready to send
- A scoping worksheet — three inputs, out comes a price
- A rebrandable sample report so you can show a client what they are buying
- A 20-minute recorded walkthrough for your account managers, so they can sell it without you in the room
- A named contact — you deal with the person doing the work, not a queue
Straight answers
The things you are about to ask
Will you go around us?
No, and it is a written term of the partner agreement, not a promise on a call.
What access do you need in my client's tenant?
Read-only, least-privilege, time-boxed. Global Reader and Security Reader in Entra, or the equivalent read-only admin role with audit log access in Google Workspace. Every script we run only reads.
Is all of it strictly read-only?
On the Microsoft side, yes. On the Google side there is one honest exception, and we would rather you hear it from us: listing a user's connected applications requires admin.directory.user.security, and Google publishes no read-only version of that scope — it also permits revoking tokens. Our tooling only lists, never revokes, and we will run without the scope if your client prefers, with the coverage loss documented in the report. Anyone who tells you the Google side is entirely read-only has not looked.
Who signs the authorization letter?
Your client does, and it names exact systems and windows. We will not test anything on a verbal.
Can your team do the readout?
Either way. We can hand you the deck and stay invisible, or join as your specialist. Both are normal.
One conversation is enough to know if this fits.
Tell us roughly how many clients you support and what identity platforms they run. If the fit is not there, we will say so on the first call rather than the third.