Sell the work you keep turning down.
Structured content briefs are landing on agency desks across Australia, New Zealand, India and the UAE, and most get declined for the same reason: nobody has a DITA team. We are that team — behind your brand, on your paper, to your client.
Who sits where.
Full white label by default. We can be introduced as a named specialist partner instead if that helps you win — your call, on every deal.
Your client
Holds the content problem and the budget. Signs with you, is invoiced by you, and talks to your account team throughout.
Your agency
Owns the relationship, the commercials and client-facing project management. Sets the resale price. Keeps the account permanently.
TechConnect Space
Information architecture, metR conversion, QA, DITA-OT publishing and content operations. Invisible unless you decide otherwise.
Four kinds of firm this works for.
You own the content relationship already
Structured content is the upsell you can't currently staff — and it's a larger, stickier engagement than anything else on your rate card.
What changes: a new line of business with no hiring, no DITA training budget, and no tooling spend.
Your clients' estates are full of it
Sitecore, AEM, WordPress and Drupal practices sitting on product documentation that shouldn't be in a web CMS at all.
What changes: a replatforming project gains a documentation workstream you can scope and price instead of leaving on the table.
You have the strategy, not the engineering
Rule packs, DITA-OT plugin work, CI pipelines and batch QA at volume are a different discipline from content strategy and editorial.
What changes: you keep the advisory work and stop subcontracting engineering to whoever is free.
Migration is the blocker in front of your deal
A licence sale stalls the moment the prospect realises their content has to get into the system first.
What changes: a costed migration path attached to the proposal, and a faster route to go-live.
How the partnership works.
Stated plainly, because vague partner terms are how these relationships go wrong. Everything below goes into the partner agreement.
| Term | How it works |
|---|---|
| Pricing to you | A wholesale day rate or fixed project price. You set the resale price and keep the margin — we never see or set what your client pays. Indicative rates shared on the first call. |
| Deal registration | Register an opportunity and it is protected for an agreed period. We will not approach a registered client directly, during the engagement or after it. |
| Non-circumvention | Mutual and written. Your client stays your client permanently, including for follow-on content operations retainers. |
| Branding | White label by default — deliverables, documentation and templates carry your marks. Named-partner introduction available per deal, on request. |
| Client contact | None unless you invite it. When you do, we join as your specialist team member and follow your lead in the room. |
| Pre-sales support | Scoping calls, effort estimates, proposal content and technical Q&A at no charge on qualified opportunities. |
| IP and ownership | Converted content, information model, custom DITA-OT plugins and documentation transfer to your client. metR remains Metapercept's product, licensed for the engagement. |
| Confidentiality | Mutual NDA before any client content is shared. Content can be processed in a nominated region, or inside the client's own environment for sensitive libraries. |
| Exit | No exclusivity, no minimum volume, no annual commitment. Stop whenever it stops working. |
We need first references. You need a reason to go first.
We are new, and we need first references more than first margin. So the earliest engagements are priced accordingly, and the terms say so out loud rather than pretending otherwise.
What we want back is narrow and specific: permission to write up the work, and one reference call. Not exclusivity, not volume commitments, not a testimonial you didn't mean.
- Reference rate on the first engagementA materially reduced wholesale rate, in exchange for a named case study and one reference call after delivery.
- Case study written for you, not about usWe draft it, you approve it, and you may publish it under your own brand with our involvement anonymised if the client prefers.
- Priority delivery slotsFounding partners are scheduled ahead of the general queue while capacity is building.
- Rate held after the programme closesYour founding rate is honoured on subsequent engagements for an agreed period.
- Roadmap inputWhich source systems get metR rule packs built next is decided partly by what founding partners are being asked for.
- Named delivery leadA person, not a ticket queue — retained after the programme ends.
Each market buys this differently.
Same capability, different entry point. Below is how we position, what triggers a live opportunity, and what a client in each market will ask you to evidence.
Australia
Largest of the four by addressable spend. Buying is compliance-led and procurement-heavy — which is exactly why the white-label model helps: your track record carries the deal.
- Sectors: mining and resources, defence primes, medical devices, utilities, higher education
- Triggers: audit findings, CMS end-of-life, a failed accessibility review, an acquisition merging two content estates
- Partner fit: Sitecore and AEM implementation agencies, technical communication consultancies
- They'll ask for: documented process, security posture, references, fixed-price scope
New Zealand
Smaller market, shorter decision chains, low tolerance for first-engagement risk. Land small and expand — the pilot structure was built for exactly this buying behaviour.
- Sectors: agri-tech, SaaS exporters, healthcare, local government
- Triggers: a lone technical writer resigning, expansion into a second language market, a support-cost review
- Partner fit: often the same agencies serving Australia; strong word-of-mouth in a small market
- They'll ask for: a paid pilot with a defined exit, not a framework agreement
India
Home delivery market. Price-sensitive at entry, but with the largest volume of legacy PDF and the fastest-growing GCC demand of the four.
- Sectors: global capability centres, product engineering firms, automotive and industrial manufacturing, BFSI
- Triggers: a global parent mandating a documentation standard, a CCMS rollout, an AI programme blocked on content quality
- Partner fit: technical writing firms, engineering services companies, Metapercept's existing network
- They'll ask for: demonstrated throughput and cost per topic, on-site availability when required
UAE
Highest value per engagement of the four. Bilingual delivery is usually mandatory rather than optional, which favours structured content strongly — and makes the argument easy to make.
- Sectors: government and semi-government entities, aviation, oil and gas, healthcare, construction
- Triggers: an Arabic-language compliance requirement, a digital government programme, a national standards mandate
- Partner fit: local systems integrators, content and translation agencies, regional consultancies
- They'll ask for: Arabic and right-to-left publishing demonstrated live, plus data residency answers
How this works across time zones.
The questions every partner call opens with.
You're new. Why would I put you in front of my client?
Because the risk is bounded and visible. The audit is fixed-fee and the deliverable is yours regardless. The pilot measures conversion accuracy on the client's real content before anyone commits to a full run. Every stage ends in an artefact you keep. And the underlying capability comes from Metapercept, which has done this work for years — what's new is the company, not the practice. If that isn't enough for a particular client, it isn't, and we'd rather you didn't force it.
Will you go around me to my client?
No, and it's contractual rather than a promise: deal registration plus mutual non-circumvention, covering the engagement and follow-on retainers. Practically — a channel business that poaches its first accounts doesn't get a second cohort of partners, and we know it.
What do I need to know to sell this?
Enough to recognise the opportunity, not enough to scope it. If a client mentions duplicated content, translation cost, multi-channel publishing, audit trails, or an AI project stalling on content quality — that's the signal. Bring us in for the technical conversation; that's what pre-sales support is for.
Can I resell at my own margin?
Yes. You're quoted a wholesale rate and you set the client price. We don't ask what it is and we have no visibility into it.
What if the client's content doesn't convert well?
The audit tells you before you've sold anything, which protects you more than it protects us. Some libraries — inconsistent legacy PDFs, scanned documents — need more manual work than automation can remove, and occasionally a migration isn't worth doing. We'd rather say so at the audit stage than discover it halfway through delivery.
Do you only do DITA?
It's the centre of what we do, but honestly DITA earns its complexity at reuse, multi-channel and translation volume. Below that threshold a lighter structured format may serve the client better, and the audit will say so. Recommending against a sale occasionally is what makes the recommendation worth anything.
Does the client need a CCMS too?
No. DITA in a Git repository with oXygen and an automated build is a legitimate permanent setup and much cheaper. A CCMS becomes worth it at larger team sizes, heavier workflow needs or serious translation volume. We're tool-agnostic and will say which side of that line a client sits on — useful if you also resell a CCMS.
What about existing URLs and SEO?
In scope. We produce a URL mapping from old CMS paths to the new output structure plus a redirect specification, so rankings and deep links from support tickets survive the move.
Ready when you are.
Apply as a partner, or bring us a live client opportunity. Either works as a starting point.