# The Stack Not the Certificate The most important correction to come out of the August 2026 evidence gathering, and it moves the company's centre of gravity. > [!important] Compliance isn't the comparable. The stack is. > A medium estate does not have one system problem, it has two — and it already pays for both: > > - **Compliance**, bought annually from a consultant proxy against a five-year certification cycle. > - **A plantation ERP**, bought as an annual subscription plus a one-off implementation charge. > > The ERP subscription is the larger line **by a wide margin** — a single year of it approaches the whole multi-year compliance spend. ==The money is in the ERP, not the certificate.== ## Why this reverses an earlier conclusion An earlier reading of the field notes held that Rimau was **underpriced** — that if the compliance cycle cost six figures a year, a RM800–1,500/month subscription captured a fraction of the value. That was wrong, on two counts. There is **one audit a year, not two or three**, and group-scheme membership is materially cheaper per member than standalone certification. Measured against a group-scheme compliance budget alone, RM800–1,500/month is **a multiple of the entire incumbent compliance spend** — a budget that will not carry it. > [!warning] The honest version > If Rimau prices as a compliance product, it is **too expensive**, not too cheap. The compliance line item is small, annual, and already served. ## Why the stack framing rescues the price Priced against the **combined** spend — compliance plus ERP, two vendors, two contracts, two systems that do not talk to each other — the same RM800–1,500/month is a **minority share of what the estate already pays**, for something neither incumbent delivers: one system where the operational record and the compliance evidence are the same record. That is also the cleanest statement of the product thesis: **MSPO evidence and ERP data are the same data.** Estates pay twice today because the two products were built separately. Selling the combination, at a discount to the pair, is a position neither incumbent can match without rebuilding. ## What it changes 1. **The comparable in every deck and sales conversation** shifts from *the consultant's invoice* to *the annual software and compliance bill combined*. 2. **The ERP is no longer a reluctant scope expansion** ([[Rimau/Plantation OS - The ERP Question]]) — it is where the revenue actually sits. Compliance is the entry point and the data-acquisition mechanism. 3. **The moat argument sharpens.** Not "we do the compliance job nobody covers," but "we collapse two budgets into one product, and the compliance data is what makes the operational product work." → [[Rimau/The Flywheel and Rimau Sentient]] 4. **Pricing needs rebuilding from scratch** against the combined stack, before any agentic features are priced in at all. ## The open question Whether the buyer perceives the two budgets as one. They are approved at different times, by different people, against different justifications — a certificate you must have, and software you might. Collapsing them commercially may be easier than collapsing them **psychologically**, and that is a discovery question, not a spreadsheet one. ## Related - [[Rimau MOC]] - [[Rimau/Business Model and Go-To-Market]] - [[Rimau/Plantation OS - The ERP Question]] - [[Rimau/Competition and the Impartiality Line]] - [[Rimau/Open Questions and Numbers to Reconcile]]