We publish what most eQMS vendors make you apply to find out — the commission, the renewal treatment, the deal-registration window, and where the services revenue lands. Read it before you talk to us.
Built for regulatory, QA, and validation consultancies already billing GxP hours — not for software resellers.
Four reasons, and each one is something you can check on this page before you talk to us.
Your clients already ask which eQMS to buy — you advise that decision without being part of it, and then inherit whatever they chose and validate it anyway. As a partner you carry the platform and the validation on one account, instead of a project that ends when the report is signed. It changes the shape of your revenue too: consulting income is capped by headcount, renewal commission is not.
You keep 100% of what you charge for implementation and validation. We do not take a percentage of it, we do not pay commission on it, and we do not compete with you for that work on your own accounts. The subscription commission — 20% year one and 8% on every renewal, for as long as the customer stays — sits on top of it, paid monthly on revenue we have actually collected.
The validation pack, the delivery RACI, the commission, the registration window and the terms are all on this page, and you see the full agreement before you are asked to sign anything or introduce anyone. So is the list of what we do not have — no ISO 27001, no SOC 2, no certification programme yet. You should never learn a limitation from your own client.
Our first partner read the draft agreement closely and pushed back, and the programme changed because of it — that is what “founding partner” means here. Join a mature channel and you inherit rules written for someone else years ago. Join at this stage and the rules are still being set — while the programme is small enough that what you say about them reaches a founder directly.
The firms taking Complere to market — named, with their territory and the work they actually do.
Confianza y Calidad en la Validación de Sistemas Computarizados. A validation consultancy serving regulated manufacturers in Mexico, and the first partner to take Complere to market. They list Complere in their own navigation as Digitalización del SGC.
Pick the one that matches how your firm already makes money. Most life-sciences consultancies belong in the second. “Founding partner” is not a fourth track — it is what we call the first partner in a market, whichever track they are on.
For advisors and consultants whose clients ask what to buy, but who do not want to run a sales process, carry the contract, or take on delivery work.
For validation, CSV, and QA consultancies. You configure and validate the system for your client, and you keep every hour of that work.
For platforms whose customers overlap with ours — LIMS, ERP, MES, training and document systems that a regulated quality process has to reach.
Across the eQMS category, almost nobody publishes this. We would rather you decide whether the economics work before you spend a call finding out.
| Term | Our position |
|---|---|
| First-year commission | 20% of first-year subscription value. |
| Renewal commission | 8% of subscription value on every renewal, for as long as the customer stays. |
| Your services revenue | 100% yours. Implementation, configuration, and validation fees you charge your client are not commissionable in either direction. We do not take a cut, and we do not pay one on them. |
| Basis and timing | Paid on collected subscription revenue, monthly, after the customer's payment clears. Refunds are clawed back. |
| Deal registration | 90 days exclusive credit on a named legal entity. The clock starts when we confirm your registration in writing, and renews on documented activity. |
| Exclusivity | None, in either direction. We do not grant territories, and we do not ask you to sell only Complere. You are protected on accounts you register, not on a map. |
| Minimums | No volume target, no annual quota, no fee to join. |
Rates above are the standard programme terms. Currency, invoicing, and local price bands are confirmed in your agreement.
A fair question, and one our first partner asked before signing anything. Here is the same answer we gave them.
| What it means | What it does not mean |
|---|---|
| You were first in your market. It is per region, not per programme — there can be a founding partner in Mexico and another in India. | Not equity. No shareholding, no options, no board seat, no claim on the company. |
| Your questions change the programme. The agreement, the registration rules and this page all move when a founding partner pushes back — because there is not yet a mature channel whose rules you are joining. | Not exclusivity. We do not grant territories to anyone, founding partners included. Protection comes from deal registration. |
| You are named here — with your territory and the work you do — for as long as the partnership runs. | Not different economics. Same 20% year one and 8% renewal, same 90-day registration, same terms published on this page. Being first does not buy a better rate. |
| It sits alongside your track, not instead of it. A founding partner is still a referral, implementation or technology partner. | Not a rank. It records who was first. It does not place you above partners who join later, and it is not something later partners can be sold. |
Two lists, because this runs both ways. What we expect of a partner, and what you are entitled to expect of us — including the things we do not have yet.
| Prerequisite | Why it matters |
|---|---|
| You already bill GxP hours | Validation, CSV or CSA, Part 11 remediation, audit preparation, or ISO 13485 implementation. Our commission is deliberately modest because the real money for a good partner is in the services around the deal. A firm whose revenue depends on licence margin will not last. |
| Three or more years operating | Regulated buyers check how long their consultant has existed. So do we. |
| An existing life-sciences client base | Pharma, biotech, medical device, CDMO, or CRO. What matters is that you already hold the trust of quality leaders in a regulated market — that relationship is the hard part, and it is not something we could build for you. |
| Inspection or audit experience | At least one client taken through an FDA, EMA, or MHRA inspection, or an ISO 13485 certification audit. Your client will ask regulatory questions in the first meeting, and they should hear the answer from their consultant rather than from a vendor. |
| A validation lead on your side | Someone who owns the validation conversation with your client — so the two of us are reviewing our pack together, rather than us explaining it to you. |
| Three real opportunities — anonymised | Not a market-size estimate. Describe three situations without naming anyone: sector, rough size, country, and what is forcing each one to change. Do not send client names at this stage — many of you are contractually barred from it, and we would rather you kept that discipline. Names belong after an NDA and deal registration, if ever. |
| No undisclosed competing platform | We do not require exclusivity. We do require you to tell us if you already resell a directly competing eQMS, so we can discuss it at the start rather than discover it inside a deal. |
A partner programme this young has real gaps. Here they are, so you can weigh them now rather than discover them in front of a client. Each one is being worked; none of them is promised as done.
| Gap | Where it stands |
|---|---|
| ISO 27001 and SOC 2 | Not held. If your buyers require a current certificate at first contact, we are not the right platform to take them yet. |
| A formal partner certification | Training exists and is required — see above. What does not exist yet is certification: a written assessment, a published list of named certified consultants, and annual requalification against each release. So today you can tell a client your team is trained by us; you cannot yet show them an accreditation. We are building it and will tell you what it requires before we ask you to sit it. |
| An implementation case study | We have one partner and no jointly published project yet. Affiliation is not the same as a delivered implementation, and we will not present it as such. |
We are not a fit for generic IT resellers with no regulated practice, or for firms whose opening requirement is territory exclusivity, white-label rights, or source-code access. If any of the gaps above is a blocker for your buyers, tell us in the application — we would rather say so now than have you find out in front of a client.
Concrete things, not adjectives.
Provided on approval, so you can show a client real workflows instead of screenshots. Scope and duration are confirmed with you at approval.
The per-module validation pack, available under NDA for your client's technical due diligence. Most vendors make your client ask; you will have it before the meeting. See what it contains before you apply.
We train your team before you lead a client engagement — platform administration, configuration, the validation pack and how to use it with a client, and the delivery model above. Delivered by us, at no fee. Required for implementation partners before they lead; open to referral partners, but not needed to introduce.
You see the full partner agreement before you are asked to sign anything or introduce anyone to us. The rate, the renewal treatment and the registration window do not change between this page and that document.
We are a small team, which is the point — you get a named person who answers, not a partner portal ticket queue. If we cannot support you properly we will not sign you.
Named here, with your territory and your services, once your agreement is in place. Our first partner listed us before we listed them — that is the standard.
A one-page leave-behind carrying your name alongside ours, for conferences and client meetings. We have already built these for partners rather than promising them in principle — the first was made for our founding partner, not drawn from a template we keep on file.
And for a specific opportunity: give us about a week and we will prepare the pitch for that customer — their regulatory context, the objections they are likely to raise, and the modules that actually matter to them — instead of handing you a generic script to adapt.
Most consultancies know exactly what they would write about. Almost none get to it, because every hour spent writing is an hour not billed. So we do the writing.
Around one piece a month — a blog article or a LinkedIn post — in your market and your language. It starts however suits your week: a working session with your specialist so the argument is genuinely theirs, or — if their diary is full — we draft first from what your firm has already said publicly, and they change whatever is wrong. Either way the drafting, sourcing and fact-checking are ours.
No eQMS vendor we surveyed publishes their partner terms. These four are settled programme positions and will not change between this page and your agreement. Everything else — term length, notice periods, marks licence, and local specifics — is in the agreement itself, and we will send it before you commit to anything.
| Position | What it means for you |
|---|---|
| Non-exclusive, both directions | We will not grant a territory to anyone, including you. You are free to carry other products. Protection comes from deal registration, not from a map. |
| No cross-tenant access, ever | A partner has no access to any tenant except the one that customer has authorised them to work in — and that authorisation is the customer's to give and to withdraw, not ours. Each tenant has its own database, so there is no shared pool to leak across. Access is by named user under the customer's own role model, subject to your confidentiality terms and their data-protection agreement. This is not negotiable and it protects you as much as it protects them. |
| Validation services stay with you | The implementation and validation work you sell is yours in full. We do not compete with you for it on your own accounts, and we do not take a percentage of it. |
| 90-day deal registration | A named legal entity, confirmed in writing, protected for 90 days and renewable on documented activity. If two partners register the same account, the first written confirmation wins. |
The delivery model, published rather than negotiated per engagement. Scope shifts with the deal — this is the default we work from, and the starting point for your statement of work.
One rule shapes the whole table: the customer is Accountable on every validation row. Under EU GMP Annex 11 and GAMP 5, the regulated company owns the validated state of its computerised systems. That accountability cannot be bought from a vendor or delegated to a consultant, and we will not sign a matrix that says otherwise. What a partner and a vendor can carry is the work and the evidence.
R Responsible — does the work · A Accountable — owns the decision and signs · C Consulted — input required before sign-off · I Informed — told once done
| Activity | Customer | Partner | Complere |
|---|---|---|---|
| Platform infrastructure, hosting and availability | I | I | A R — our platform, our estate, our responsibility |
| Backup and disaster recovery of the platform | I | I | A R — we run and test it; targets are set in your contract |
| Environment provisioning and AWS region selection | A — your data-residency decision | C | R — we provision in the region you choose |
| Platform security controls and patching | I | I | A R |
| Supplier qualification of Complere | A | R — coordinates the qualification and reviews our answers | R — we complete the questionnaire, supply the evidence, and answer findings |
| User requirements (URS) | A R | C | I |
| Configuration specification | A | R | C |
| Validation plan and risk assessment | A | R | C — VMP and RA templates ship with the pack |
| Data migration — extraction, mapping and load | A | R | C |
| Migration reconciliation and its approval | A — the customer approves the reconciliation | R | I |
| IQ / OQ execution | A | R | C — protocols ship with the pack; execution is a human activity |
| PQ / UAT | A R | C | I |
| Deviations and failed test scripts | A | R | C — escalate to us where the cause looks like a product defect |
| Product defect investigation and product CAPA | I | I | A R — the defect, its root cause and the fix are ours |
| Security incident affecting the platform | A for their own response | I | A R — investigation, containment, and notifying you and the customer |
| Availability incident | I | I | A R — restoration and status communication |
| Data-integrity event in a tenant | A | R — investigate with the customer | R where platform behaviour is implicated |
| Traceability review and approval | A | R | C |
| Validation Summary Report | A | R | I |
| Go-live authorisation | A R | C | I |
| Release-impact assessment | A | C | R — we state what changed and what it touches, ahead of the release |
| Vendor regression testing of the platform | I | I | A R — our release, our regression suite |
| Customer-specific regression after a release | A | R | C |
| Change control | A R | C | I |
| Periodic review | A | R | C |
| Inspection and audit support | A R | R — front line, in the room | C — evidence, architecture answers, escalation to a founder |
| Record retention and archival | A | I | R — the platform retains records per your contracted terms |
Response and restoration targets sit alongside this table in your agreement, graded by severity — a production outage and a cosmetic defect do not carry the same clock. Where a customer has no implementation partner, the Partner column falls to Complere or to the customer, agreed in the statement of work. Nothing in this table transfers regulatory accountability away from the regulated company.
Five steps. None of them is a formality, and the qualification in the second one runs in both directions.
Nine required fields, no client names. We reply within two business days — including to the applications we decline, and we tell you why.
One conversation, both ways: your practice against the prerequisites above, and our gaps against what your buyers will require at first contact. If either side is not a fit, this is where we say so.
You receive the full partner agreement before you sign anything or introduce anyone. The rates, the registration window and the four published terms do not change between this page and that document.
Implementation partners are trained by us before leading a client engagement; referral partners can take the same training but do not need it to introduce. The sandbox tenant is provisioned on approval.
Register a named legal entity — the address and format come with your agreement. Protection runs for 90 days from our written confirmation and renews on documented activity — and from here the commission terms above apply.
We do not publish a week-count for these steps. The pace depends on your team's availability as much as ours, and we have one partner's worth of data — not enough to promise a number we would then miss. Ask on the qualification call and you will get a real one.
Read the prerequisites above first. We reply to every application, including the ones we decline, and we will tell you why.
Not seen the platform yet? Start with the platform overview or request a demo — it is easier to judge the fit once you have seen what your clients would be running.
One thing before you fill this in. The parts of this programme worth anything came from a partner telling us what was wrong with them — our first partner argued about the draft, and the terms read differently now because of it.
So if something here does not fit how your firm actually works — the tracks, the way the split is drawn, the length of the registration window — say so in the application. We would rather change it now than have you sign something shaped for somebody else. That is not a courtesy; it is how the programme has been built so far.
20% of first-year subscription value and 8% of subscription value on every renewal, for as long as the customer stays. Commission is paid on collected subscription revenue, monthly, after the customer's payment clears. Implementation and validation services you deliver are yours in full and are not commissionable in either direction.
No, in both directions. We do not grant territory exclusivity, and we do not ask you to sell Complere exclusively. Partners are protected on the deals they register, not on a map.
You register a named legal entity. The clock starts when we confirm receipt in writing, and you hold exclusive credit on that account for 90 days. The window renews on documented activity. Registration protects the account, not the region. If two partners register the same entity, the first written confirmation wins. The registration address and format come with your agreement, so there is nothing to look for after you sign.
Not today. We do not hold ISO 27001 or SOC 2 certification, and we tell partners this before they take us into a deal rather than after. What we do provide is the per-module validation pack, available for technical due diligence under NDA. If your buyers require a current certificate at first contact, tell us during the application and we will say plainly whether we are a fit yet.
Two contracts, not one. Complere contracts with the customer directly for the software subscription, and invoices it. An implementation partner contracts separately with that same customer for implementation and validation services, invoices those itself, and keeps the fees in full. Referral partners do not contract with the customer at all — they introduce, and we carry the whole relationship.
Under every track, a partner can access only the tenant that customer has authorised. Acceptance of services deliverables, professional liability for that services work, and dispute handling sit in the services contract between you and your client — not with us. Renewal commission treatment after a partnership ends is set in your agreement; ask for it before you sign.
A sandbox tenant is provided on approval so you can demonstrate real workflows rather than slides. Scope and duration are confirmed with you at approval.
Tell us in the application. We do not require exclusivity, but a partner carrying a directly competing platform creates a conflict we would rather discuss openly at the start than discover in a deal.
You select the AWS region at provisioning. Each customer tenant has its own database, so data residency is set per customer rather than per platform. Tell us where your clients need their data to sit and we will confirm the region at provisioning.
The content is yours. It publishes under your consultant's name, on your channels, and you own it outright — including if the partnership ends. We draft from your team's own arguments — in a working session, or, if their diary is full, from what your firm has already said publicly with your specialist correcting anything wrong — so the position in the piece is genuinely theirs and they can defend it in a client meeting. We do not add Complere claims to it. One rule applies everywhere: any content that discusses or recommends Complere carries a clear partnership disclosure. That is not optional and not a judgement call.
Then it does not publish. Approval is written and it is yours — there is no version of this where something goes out under your name that you have not signed off. You can also change it however you like; it is your byline, not ours.
We train, and it is required before you lead a client engagement. Training covers platform administration, configuration, the validation pack and how to use it with a client, and the delivery responsibilities in the RACI above. We deliver it, and there is no fee.
Certification is a different thing, and it does not exist yet — no written assessment, no published list of named certified consultants, no annual requalification against releases. We are building it. Until then you can tell a client your team is trained by us, but you cannot show them an accreditation, and we will not imply otherwise.
It means you were the first partner in your market, and that your experience shapes the written programme while it is still being written. It is per region, so there can be a founding partner in Mexico and another elsewhere, and it sits alongside your track rather than replacing it.
It is not equity, exclusivity, a board seat, or a better commercial deal — founding partners are on exactly the same published rates, registration window and terms as everyone else. It records who was first; it does not rank you above partners who join later.
Few, deliberately. We are a small team and a partner we cannot support is worse for both of us than a partner we never signed. If we are at capacity in your market we will say so rather than sign you and go quiet.
