Partner programme
Run WorkMonitor for other people’s teams.
Deliver it, fold it into a managed service, or put your own name on the surfaces your clients open. Every client stays its own organisation. The margin is yours.
Client organisations are provisioned through the /v1/tenants API. You will walk through your first one with us before you sign anything.
One agreement, every client separate
Provision each client from the /v1/tenants APIClient organisation
Who from your side
What the client opens
A design studio
Who from your side:Your delivery lead, scoped to that node
What the client opens:Certificates verified on your domain
A claims team
Who from your side:Two consultants, scoped to one team inside it
What the client opens:The approver widget, in your colours
A logistics operator
Who from your side:Your account manager, scoped to that node
What the client opens:A timeline embedded in your portal
Every record carries the organisation it belongs to, so a cross-client read is a foreign-key violation rather than a permission somebody can misconfigure. An illustration of the shape. Not a client list.
How the money works
Two arrangements. Only one has a published price.
Refer a customer and the terms are on this page — you could be signed up by this afternoon. Take the delivery on and the number moves with how much of the work is yours, so we agree it with you rather than print it.
You deliver
Margin comes off the licence
You own the rollout, the configuration and the client relationship. What you keep moves with volume and with how much of the delivery is yours, so it is set in your agreement rather than printed here.
- No certification to sit. Agreements set expectations on delivery quality, not on volume.
- Node-scoped roles: a consultant opens the client they are working on, and nothing beside it.
- Your brand on the client-facing surfaces, on a domain you control.
You refer
20% of what they pay, for 12 months
- of every payment
- 20%
- per referral
- 12 months
- attribution window
- 90 days
- payout minimum
- $50
No delivery obligation, no minimum volume, nothing to certify. Share a link, and every payment the customer behind it makes pays you.
See the affiliate programmeDelivery tracks
Which arrangement is yours
What separates them is who owns the client, where the money comes from, and whether you have to build anything. Most of them need nothing built at all.
| Track | What you own | How you are paid | What you build |
|---|---|---|---|
| Solution partnerYou deploy and configure it for a client, and stay the person they call. | What you own:The rollout, the configuration and the relationship. | How you are paid:Margin off the licence, agreed per agreement. | What you build:Nothing. You configure; you do not integrate. |
| Managed service providerMonitoring as one line inside a managed service you already run. | What you own:The service the client buys. This is a component of it. | How you are paid:Margin off the licence, moving with volume. | What you build:Nothing. Each client is its own organisation, and your people are scoped to it. |
| Technology partnerYour product, with verified work data inside it. | What you own:Your own product and its roadmap. | How you are paid:Not a revenue share. You are here for the surface, not the margin. | What you build:Against the v1 REST API, the typed SDK and the token-scoped widgets. |
| White-labelProof of work arrives from you rather than from a vendor nobody has heard of. | What you own:The client-facing surfaces: the verifier, the badge, the widgets. | How you are paid:Agreed with the rest of the arrangement. | What you build:A custom domain and your brand. The platform underneath stays ours. |
Rates on the solution and managed-service tracks are set in the agreement rather than published here. They move with volume, and with who does the delivery work.
What you are actually reselling
Embedded is the part with your name on it
White-label branding, a custom domain, verification widgets a client opens without an account, and scoped keys so an integration gets exactly the surface it needs. The inventory below is read straight from the product page, marks and all.
Scoped keys, never master keys: a key is minted for one integration, held to a set of scopes and an address range, and revoked without touching the others.
- Widgets & white-label
- Embeddable verification widgets
- White-label branding
- Custom domains
- Developer API & SDK
- REST API (v1)
- Typed SDK
- OpenAPI spec & docs
- Scoped API keys
- Partner webhooks (HMAC)
- OAuth2 client-credentials
- API usage metering
- Reseller & multi-tenant
- Multi-tenant / reseller provisioning
Why the marks are on this page
A capability you discover mid-rollout becomes your problem with your client.
Every capability named here is read from the product catalogue rather than retyped for a partner audience, so a line that changes on the product page changes here in the same commit. Client organisations are provisioned through the /v1/tenants API, and the diagram at the top of this page shows the boundary each one sits behind.
Straight answers
The questions we would ask in your position
Every answer here is the one you would get on a call. Open as many as you like; they stay open, so two can be held side by side.
It depends on the track. The referral track is published: 20% of what a referred customer pays, for their first 12 months, with no delivery obligation — see the affiliate programme page. Solution partners and managed service providers take margin off the licence and own the rollout. Technology partners are not a revenue share at all; they build on the API and appear in the integrations directory. Solution and MSP rates are agreed per agreement, because they move with volume and with who does the delivery work.
Yes, and it is enforced rather than configured. Every record is tied to its organisation by a composite foreign key in the schema, so a cross-client read is a constraint violation. Within an organisation, roles scope to a node in the org tree, so your consultants open the client they are working on and nothing next to it.
On the client-facing surfaces, yes. White-label branding and a custom domain are part of the Embedded product, so a verification page or an embedded widget reads as yours. The platform your consultants work in is not resold as your own software.
For the referral and solution tracks, nothing. For technology partners there is a read-only v1 REST API with scoped keys and a published OpenAPI reference, a typed SDK, and token-scoped embed widgets. Zapier covers the no-code path to 6,000+ apps.
No certification programme today, and no minimum on the referral track. Solution and MSP agreements set expectations on delivery quality rather than on volume. If a formal certification matters to your procurement, say so during the conversation rather than assuming it exists.
From here
What the next conversation needs
Your engineers, and your client’s procurement, will ask for these before anyone signs.
- EmbeddedWhite-label branding, custom domains, the verification widgets and reseller provisioning, on the same scoped-key model as the rest of the API.
- DevelopersThe quickstart, scoped keys, HMAC webhooks and the OpenAPI reference the API serves itself.
- IntegrationsThe connectors already shipped, so a client’s stack is one less thing you have to build for them.
- SecurityTenant isolation, the audit trail and the certification status, written for the review your client will run.
- EnterpriseSAML, SCIM, retention and the sign-off pack, for the clients whose procurement asks before the pilot.
- Affiliate programme20% for 12 months, published, with no delivery obligation and nothing to build.
Bring us a client you already have.
Tell us who they are, how many desks, and how much of the delivery you want to own. What comes back is the arrangement that fits and what it is worth. Not a brochure.
We will walk through provisioning your first client organisation on the call.