Partner deck · one page, no slides
You sell the CRM. We build the part your client's old software refuses to give you.
Wholesale, white-label, and with the uncomfortable numbers printed alongside the good ones. If you have ever lost a deal to the sentence "but everything lives in Gesden", this page is the answer to it.
The deal you keep losing
It is never the marketing. It is the data.
The pitch lands. The client wants the CRM, the reminders, the review requests, the follow-up on unpaid invoices. Then the practice manager says the patients live in Gesden, or the quotes live in Presto, or the accounting lives in A3, and none of it is coming out.
At that point you have three options. Quote an integration you cannot scope and eat the overrun. Sell a CRM the client will type into twice and cancel in four months. Or walk away from a client you already won.
The fourth option
Subcontract exactly that piece.
You quote the whole project at your price. We deliver the bridge at wholesale, on a fixed fee and a fixed date, with your name on it. The client's software stays where it is, the records move, and your CRM stops being a second place to type things.
You keep the relationship, the retainer and the margin. We keep a queue of the same program showing up again, which is the whole reason wholesale is worth it to us.
What you pay, what you charge
Wholesale, and the arithmetic in the open.
You pay us
$1,997
€1,997 in Europe · per bridge
$97
€97 · per month, per client
You charge
3,500-4,500
Typical partner build price
250-300
Typical monthly, on top of your own retainer
You keep
Around 1,900 on the build and roughly 175 a month, per client, for work you do not do and cannot currently hire for one deal at a time.
Ten clients on the same program is about 1,750 a month of new recurring margin, and the tenth one costs us a fraction of the first.
Same number, your currency: dollars outside Europe, euros inside. Resale prices are what partners in this space charge for the same scope; you set yours.
How a deal runs
Five steps, and you are only in two of them.
-
01
You send us the wall
You, 10 minutes
An email with the client's sector, the program that is blocking the deal, and roughly how many records are in it. We answer within two working days with go, no-go, or 'needs a review first'.
-
02
Review, if the software is new to us
Us, 5 business days
We read the program: official API, authorised exports, database shape, licence terms. You get the report and a fixed quote. Wholesale review is 497, credited in full against the build.
-
03
Paperwork before access
Both, 1-2 days
Partner agreement between you and us. Data processing agreement between you and your client, with us named as sub-processor. Nobody reads a database on a handshake.
-
04
Build and read-back
Us, 3-4 weeks
One bridge, three automations on their real records. Then we re-read every record from the live account and compare it against what we sent, field by field. A 200 response is not proof.
-
05
Handover, then monthly
You in front, us behind
You demo it. Your name on it. From then on the monthly covers watching it and fixing it when the vendor changes something, which they will, without telling anyone.
What we commit to
- Your brand in front, ours nowhere near the client's panel or inbox.
- No direct approach to a client you introduce. In the agreement, with a term.
- Fixed fee, fixed date, and the build fee back if it does not work on real data within 30 days.
- Every write verified by reading the live record back, field by field, before we call it done.
- A data processing agreement in place before we touch anything.
What we will not do
- Touch or patch the vendor's binary. Ever, for anyone, at any price.
- Promise a connector we have not run against a real installation.
- Ship a bridge without the monthly. It is not an upsell, it is the thing that keeps it alive.
- Take a third retainer while two are running. We would miss both.
- Handle patient health records without a specific agreement signed first.
Where we actually are
Read this before you introduce us to anyone.
No bridge has shipped to a paying customer. Twenty connectors are written and every one was built against mocks. If you bring the first deal, you are bringing the first deal, and the price, the guarantee and the honesty on this page are all built around that.
What is real: a GoHighLevel CLI and MCP server with 609 endpoints across 71 command groups, running our own accounts daily; twelve MCP servers written in-house; and a hosted access platform with authentication, entitlements, billing, a job queue and a per-tenant panel, whose 123 tests were run green on 2026-09-03.
What that buys you: the second client on the same program costs us about a fifth of the first. An agency with ten dental clinics on Gesden is worth far more to us than ten unrelated one-offs, which is exactly why the wholesale price is what it is.
Partner questions
The ones that decide it.
Will you go around me to my client?
No, and it is in the partner agreement with a term and a penalty, not just as a promise on a website. Under this brand our customer is the agency. Our retail brand speaks Spanish to local businesses and is contractually kept away from any client you introduce.
Whose name is on the delivery?
Yours. We do not appear in the client's panel, in their emails, or on the call unless you invite us. If you want us on a technical call as 'your integrations team', that is fine too: your call, every time.
What if the vendor blocks the route after we deliver?
That is the risk the monthly exists to cover, and we will not pretend otherwise: the integration is not our moat, it is the vendor's, and they can close the door. If a route closes we move to the next one down the list at no extra build cost, and if all four close we stop billing the monthly rather than charge for something that no longer works.
Can I white-label the review as well?
Yes. The report ships unbranded as a template you drop your logo into, or with our name on it if you would rather it read as an independent audit. Say which before we start writing it.
How many partners are you taking?
Two builds a month total, across all partners. That is the real constraint, and it is why the first partner slots are worth having: at two a month, a partner with a queue gets scheduled first.
What do you need from me on every deal?
An introduction to the technical decision maker at the client, whoever administers the legacy software, and a signed data processing agreement. That is it. You do not do the scoping call, you do not write the spec, and you do not chase the vendor.