# Competition and the Impartiality Line > [!quote] The one-liner > **The incumbent is a consultant with a filing cabinet.** ## The landscape | Player | What it is | Why it does not close the gap | | --- | --- | --- | | **Consultant proxies** (Wild Asia and similar) | Human agents who inspect, prepare and apply on the estate's behalf | RM9–12.5k a year and nothing in between. The consultant leaves; the readiness leaves with them. | | **Plantation ERP** (LintraMax; the legacy Sarawak system) | Published footprint: 1M+ ha, 700+ estates, 80+ mills, 200+ companies across MY/IND/PNG, 23 years. Cloud platform spanning estate ops, mill weighbridge-to-lab, a field app, mapping, analytics and attendance. Annual subscription plus a one-off implementation charge — **the larger of the two budgets an estate carries** | Manual-heavy, often half-used — estates run pen-and-paper *in parallel*, so the workflow is fragmented rather than unified. **No compliance intelligence, no AI.** ==And it needs cell signal.== | | **Government rails** (e-MSPO; an MPC platform of some form) | The regulator's system of record | Collects filings. Does not keep an estate ready. | | **Paper and spreadsheets** | The real incumbent | Everything above. | | **Refineries and majors** (Wilmar, IOI, Musim Mas, Sinar Mas) | In-house sustainability teams | Will *copy* ideas rather than buy. Do not pitch them the plan. | **None are AI-native.** The whitespace is real: no AI-native MSPO readiness player found as of August 2026. > [!warning] The incumbent's reach is narrower than its client count suggests > The ~18% implied by LintraMax's own marketing is self-reported, undated, and counts Malaysia, Indonesia and PNG against a Malaysia-only denominator. As an enterprise system it skews to the 2,374 entities **above 500 ha**, so penetration inside the 40.46–500 ha target band is likely **low single digits**. > > Which cuts both ways: the incumbent is weaker here than it looks, and there is **no installed base to sit on top of**. → [[Rimau/Plantation OS - The ERP Question]] ## The impartiality line — why this is a business at all > [!important] The rule that creates the market > Certification bodies must be **independent third parties** and cannot consult for the clients they certify, with a three-year independence rule (MSPO scheme document; ISO/IEC 17065). That rule is *why* the expensive consultant layer exists as a separate market. Rimau replaces the slow, expensive prep and lodgement work — **not** the certification body. The CB still audits and certifies; Rimau keeps the estate continuously ready for them. This is the same side of the line on which **Vanta** (~US$300M ARR) built its category. It also means the 23 accredited certification bodies are a **channel, not a competitor**: clean, organised evidence makes every audit they run faster. > [!success] Resolved: Rimau stays on this side of the line — and the rule protects it > The team considered becoming an accredited body and decided against it. The stronger reading of ISO/IEC 17065 is the inverse of the obvious one: **the 23 accredited bodies can never enter Rimau's category without surrendering accreditation.** The regulation fences the incumbent certifiers permanently out of the readiness market. That is a barrier competitor capital cannot cross. → [[Rimau/The Accreditation Question]] Better still, the certifiers are best understood as **supply, not channel**: 4,506 certified entities across 23 largely interchangeable bodies is ~196 each, and whoever owns the estate relationship routes the audit. Consultant proxies already aggregate that demand manually. There is also a softer read of the consultant: they hold trust and relationships that are not technological, which makes them plausible **customers, acquisition channels and eventual acquisition targets** rather than pure competition. ## Why consultants will not build this > [!note] The incentive wall > Flat-fee software that shrinks the work cuts a consultant's own revenue. The billing model punishes the product. Meanwhile, estates actively want to **reduce dependence on outside reviewers** — and Rimau hands the estate both the tool and ownership of its own data. See [[AI Eats Services Not Software]]. > [!important] The real comparable is the stack > Framing Rimau against the consultant alone understates the opportunity and overprices the product. The estate pays **two** vendors — compliance and ERP — and the ERP line is far larger. Collapsing both into one system, where operational record and compliance evidence are the same record, is the position neither incumbent can reach. → [[Rimau/The Stack Not the Certificate]] ## The moat, stated plainly **Help clients become compliant, never conceal.** The data stays in the client's organisation, in writing. That posture is unavailable to the government rail (which reports outward) and to the consultant (who *is* the outward eye). See [[Rimau/The Transparency Paradox]]. Long term, the differentiation is **ground-level data capture** — the team is physically in plantations, which almost no technology company is willing to be — feeding an organisational map of how these companies actually run. See [[Rimau/The Flywheel and Rimau Sentient]]. ## Related - [[Rimau MOC]] - [[Rimau/Wild Asia and the Proxy Market]] - [[Rimau/Business Model and Go-To-Market]] - [[Defensibility Principles MOC]] - [[Technical Moat Assessment Framework]] - [[7 Powers]]