Skip to content
Simple Smooth Safe
Partners

DocGen partner programme

You keep delivery. The licence price stays public.

Last updated 21 August 2026

Simple Smooth Safe is not a body shop and not a Microsoft licence reseller. We make DocGen: PDFs from Dataverse templates (Handlebars + FetchXML), one API (sss_GenerateDocument), running in the customer's Azure subscription.

If you implement Dynamics or Power Platform, the customer already sees the numbers on simplesmoothsafe.com/docgen/. We do not give partners a different customer price.

Three routes

Pick one per deal. They do not stack.

Intro only

You introduce, we deliver. You are paid 15% of the first-year licence fee, after the customer has paid us — across however many environments the introduction closes: €1,125 on one environment, €4,500 on four. Once, on the first year. It does not stack with delivery.

Delivery

You install against our runbook. We do not charge the €5,500 first-environment deployment. You bill the project at whatever you charge for it. The customer pays us €625 per production environment per month, billed annually, at the public price.

OEM / embed

For ISVs with a vertical solution on Dataverse who today have compiled templating inside the product — Aspose.Words with LINQ, or an equivalent. You embed the engine and keep everything else: your product, your brand, your customer relationship, your price.

Wholesale, per end-customer production environment, billed annually:

EnvironmentsPer monthPer year
1–5€291.67€3,500
6–20€250€3,000
21–50€208.33€2,500
51+Talk to us

Minimum year-one commitment is 5 environments, so €17,500 — you pay for five in year one even if you deploy fewer; the 1–5 rate is what each of them costs. From year two you pay for the environments you actually run. You resell at whatever price you like. We do not control it and do not want to.

This is not a discount on the public licence. It is a different relationship: you carry delivery, tier 1 support and billing, and we do not.

You do:

We do:

Evaluate before you email. The deployment runbook, the API contract and the template documentation are public at simplesmoothsafe.com/docgen/docs/. If your evaluation starts with the docs rather than a call, start there — nothing is held back for the conversation.

Publisher prefix. The API is sss_GenerateDocument and it keeps our publisher prefix. We do not produce partner-prefixed builds. The prefix is visible in your product's schema, so your customers can see it. If that is a blocker, say so now rather than after signature.

Continuity. The OEM agreement establishes a source code escrow at signature — it is part of the agreement, not an optional extra, and the deposit covers the runbook and the build instructions, not just the code. It releases on insolvency, on death or incapacity, or after 12 months without a release. On trigger you receive an irrevocable perpetual licence to the source, for maintaining your own product — with no right to resell the engine on its own.

Versions. The engine is versioned: the container image and the managed solution release together, and you pin the image tag per end customer — an update reaches a customer environment when you deploy it, not when we publish it. The request and response contract of sss_GenerateDocument is stable; a breaking change to it carries 12 months' notice and a documented migration path. We support the current release and the one before it — older than that, the first support answer is upgrade, against the runbook. There is no fixed release cadence and we will not invent one here: releases ship when Chromium, the Dataverse API or a fix requires them.

If the OEM relationship ends. End-customer environments already deployed keep generating — licensing never blocks a document, and that holds for OEM customers too. You may renew the environments you already registered, at the then-current wholesale rate, for as long as you keep supporting them; what ends is the right to add new ones. And if the reason it ended is on our side, the escrow above triggers and you maintain your own product.

Deal registration. You register end customers by email. They stay registered for 24 months. We do not approach a registered customer directly for DocGen, DMS or PSA Hub — any product of ours — during the term plus 12 months. There is no exclusivity — territorial, vertical or any other kind. We do not grant it.

Hosting. One container per end customer, in that customer's own Azure subscription. ISV-hosted multi-tenant is a separate conversation and a separate price.

Term. Annual, paid in advance, non-refundable. Renews automatically unless either party gives 60 days' notice before the renewal date. The price is fixed for 24 months from signature.

Everything in this section, on one A4 page: download the OEM sheet as a PDF →

Build and maintain, or embed

This compares embedding DocGen against building the same thing yourself. It is not a comparison against other products.

Build and maintain Embed DocGen
Render engine (headless Chromium, fonts, containers) Yours to build, package and keep running. Included.
Aspose.Words OEM licence + annual support Licensed and renewed by you, every year. Not used. Templates are HTML, rendered by Chromium.
Template store and FetchXML runner Yours to build in Dataverse. Included.
Nesting, enrichment and correctness warnings Yours to design and test. Included.
Chromium and Dataverse API compatibility over time Ongoing work, on your roadmap. Ours.
Test suite Yours to write and maintain. Ships with the engine, run on each release.
Marginal cost per document Azure compute, plus any per-document terms in your renderer licence. Azure compute. No per-document fee from us.
Time to ship Engineering months before the first document. A deployment per environment, against the runbook.

The engineering effort shown in that table is an estimate, not a measurement. We have not built your version of it and cannot tell you what it would cost you.

Sandbox

A partner sandbox environment at no charge, for demos. Not production. OEM partners get an OEM sandbox on the same terms.

What you do not get

Pricing

All prices on this page, including the OEM wholesale table above, are in euros and exclusive of VAT. EU business customers with a valid VIES-registered VAT number are reverse-charged. Customers outside the EU are invoiced in euros with no Portuguese VAT added — confirm the treatment on your side with your own tax adviser.

LinePrice
SSS DocGen licence, one production environment, per year €7,500
First-environment deployment and onboarding — waived if a delivery partner installs against the DocGen runbook €5,500
Intro-only fee, 15% of the first-year licence on one environment €1,125

Dev and test environments are free. Extra production environments are another €625/month each. Full rate card including template changes: /docgen/.

Two things are not discounts, and we would rather say so here than be asked. Where a customer takes DocGen and DMS in the same environment, the pair is €1,000 a month because it is one deployment — same app registration, same container — so the add-on carries shared cost, not a reduced licence. And the OEM wholesale rate above is a different product relationship, not a cheaper version of the same one: the ISV carries delivery, tier 1 support and billing. The customer-facing licence price is the same for everyone.

Fit

You already have customers on Dataverse who still ship invoice or statement layouts as compiled releases (Aspose / LINQ or similar). If they are not on the Microsoft platform, skip this.

Start

To implement or introduce: email info@simplesmoothsafe.com with subject: Partner — DocGen, and say which customer environment you have in mind.

To embed: email info@simplesmoothsafe.com with subject: Partner — OEM. Say what your product is, what does its templating today, and roughly how many end-customer environments you expect in year one. We will stand up your OEM sandbox from that email — you evaluate against the real engine, not a deck.

Unipessoal — the person who replies does the work. If that concerns you, read the continuity terms under OEM / embed before writing it off: the agreement puts the source, the runbook and the build instructions into escrow at signature, precisely so the answer to "what if something happens to you" is written down before it matters.