# Adoption Design — WhatsApp First The core product argument from the **18 Aug 2026** call: in this market, **distribution and interface are the same problem**, and both are solved by refusing to ask the customer to change anything. ## The user, honestly described Owners in their sixties and seventies. Not highly educated. ==Many can barely read English.== No appetite for tech, no onboarding tolerance, no manual-reading. The analogy that landed: family coffee-plantation owners in Mangalore who are *chilling on the porch having coffee* — a completely different working environment from a desk. Pitch them traceability and they look at you blankly. **Conclusion: it has to be dirt simple, or it does not get adopted at all.** ## The WhatsApp thesis > [!tip] Nothing to download, nothing to learn > Build whatever platform, interface and agent stack you want — but **the first point of contact should be a WhatsApp agent.** No app, no website, no login. They already have WhatsApp. *"Guys, you have WhatsApp? Let's get into business."* Two capture modes that fit how these users already behave: - **Photos, not scans.** They will never operate a scanner. They will photograph a document. That single choice eliminates Lintramax's **~RM30,000 hardware-and-setup fee** from the cost comparison. - **Voice notes.** Heavily used and loved in this market. Voice is the cheapest possible interface for a user who does not type and may not read the language of the standard. Telegram/WhatsApp as first contact was already on the team's list from the previous venture. The call promoted it from a channel to **the primary product surface**. Language: **Malay-first, not Malay-also.** Already in MVP scope; the call reinforced it. ## Onboarding as a free service Two moves, both of which trade Rimau's time for the customer's trust: 1. **Free requirements gathering.** Not a sales call. *"I'm not trying to sell you what I'm doing, I'm just trying to understand what you're doing."* These users can fill a simple form, or simply answer questions in a chat. 2. **Free digitisation.** Send someone to the estate for a week and digitise the paper — scan it, photograph it, fax it, whatever works — at no charge, as part of onboarding. It removes the single largest barrier (the data is on paper and in heads) and it puts a person on the ground for a week. Reference point for the discovery mechanic: **Evos** (a Utopia-built platform) — leave it with the operator, they talk to it for an hour or two, and it extracts what is in their head into agents and skills. ## The forward-deployed plantation engineer > [!quote] The operating model > Be out there. Someone who goes to the estate, has dinner with them, is just *there* — asking what's working, what they want, what they don't. As it scales, a dedicated customer-success person per region, ideally on an affiliate/revenue-share arrangement with local people. This is the same fact the pitch deck already claims as a differentiator — *the team is physically in the plantations, which almost no technology company is willing to be* — restated as a **repeatable role** rather than a founder anecdote. Because AI makes bespoke cheap, the constraint is no longer engineering capacity, it is **the system for learning what would make each customer happy.** Small customisations here compound into retention. Relevant risk: [[Rimau/Business Model and Go-To-Market|regional SMB churn concentrates in the first 90 days]]. Everything above is churn defence. ## Related - [[Rimau MOC]] - [[Rimau/Rimau Anthesis - The Wedge Product]] - [[Rimau/Plantation OS - The ERP Question]] - [[Rimau/Buying Committee and Personas]] - [[Rimau/Business Model and Go-To-Market]]