Every few months a business owner tells me, half joking, that they want to "build the super app" for their industry. My answer is always the same: please do not. But underneath the over-ambition there is a genuinely useful question, which is what super app business lessons actually transfer from Gojek, Grab, and Shopee down to a business with fifteen employees and no venture capital.

Quite a lot, it turns out. The giants did not win because they had more features. They won because of two disciplined plays: they made themselves part of a daily habit, and they relentlessly removed friction from things people already wanted to do. Both plays work at any scale. Neither requires building an app at all.

Strip away the billions in funding and the strategy is legible. Let me pull out the parts you can copy this quarter.

Lesson 1: Frequency Is the Whole Ballgame

Notice what sits at the center of every Indonesian super app: not the most profitable service, the most frequent one. Gojek anchored on ride-hailing and food, things people need daily. Payments, groceries, insurance, and investments were attached to that habit later. The high-margin services ride on the high-frequency ones, never the reverse.

The transferable principle: the business that interacts with the customer most often gets first shot at everything that customer buys. Frequency builds the habit, habit builds trust, trust carries the expensive purchases.

Now scale it down. A building materials store sells someone cement twice a year at best, a low-frequency relationship. But contractors buy weekly. One toko bangunan I know restructured around exactly this: contractor accounts with a WhatsApp fast-order lane, monthly invoicing, and priority delivery. Contractors became the anchor habit; the store became their default. Retail walk-ins continued as before, but growth came from owning the frequent relationship.

Ask the question of your own business: who could plausibly need us weekly, and what would make us their default for that need? A salon might not see a customer weekly, but a "product refill via chat, delivered" service touches them monthly between visits. An accountant's clients need them at tax time, but a short monthly cash-position summary makes the relationship continuous. You are not adding features, you are adding heartbeat.

Lesson 2: Remove One Friction Per Quarter

The second super app play is friction removal, and the textbook case is payments. GoPay and OVO did not spread because Indonesians were desperate for e-money as a concept. They spread because they removed specific, nameable annoyances: no cash for the driver, no waiting for change, no ATM queue for a top-up.

Every removed friction produced a measurable jump in usage. That is the discipline worth copying: not a grand redesign, but a steady cadence of eliminating one concrete annoyance at a time.

Run this exercise with your team. List every step a customer takes from "I want this" to "I have it", then mark where they stall, repeat themselves, or wait without knowing why. Typical SME findings:

  • Customers ask price via chat and wait hours for a human to answer the same twenty questions.
  • Payment means manual transfer plus sending a screenshot, then waiting for confirmation.
  • Repeat customers re-explain their order history every single time.
  • Nobody knows delivery status without asking.

Then remove one per quarter, properly. A WhatsApp catalog with prices kills the price-question stall. A payment gateway with automatic confirmation, which costs well under Rp10 juta to integrate into most systems, kills the screenshot ritual. A simple customer record kills the re-explaining. Each removal is small, but compounding four of these a year transforms how your business feels to buy from. On the operational side, the same logic applies internally, which is why I keep pushing owners toward moves like the ones in Automate Your Invoices and Admin Busywork This Month.

Sequencing matters more than owners expect. One friction per quarter sounds slow, but a fix that actually sticks beats three fixes that half-ship and confuse staff and customers alike.

Lesson 3: Bundle Around the Anchor, Not Around Your Ego

Once the super apps owned a frequent habit, they bundled adjacent services onto it. The subtlety everyone misses: they bundled around the customer's context, not around what the company wished to sell. Food delivery attached to rides because the same person, in the same moment of "I am hungry and busy", was already in the app.

SMEs get this wrong by bundling around their own ambitions: the fashion store adds an unrelated coffee corner because the owner likes coffee. The super app version of the question is: when a customer buys my anchor product, what else do they need in that same moment?

  • A car rental firm's customer, mid-trip, plausibly needs a driver, a child seat, out-of-town insurance. Bundle those.
  • A wedding photographer's client, in booking mode, needs makeup artists and venues. A referral bundle with revenue share costs nothing to build.
  • A pet groomer's customer needs food restocked on a predictable cycle. A subscription bundle rides the existing grooming habit.

Note that GoTo itself, after the Gojek and Tokopedia merger, spends enormous energy connecting contexts that genuinely belong together, commerce, delivery, and payments. When even the giants stay disciplined about adjacency, an SME has no business bundling randomly.

Lesson 4: What Not to Copy

Some things about super apps do not scale down, and copying them is how SMEs burn money:

  • Do not build an app. Super apps earn their home-screen icon with daily usefulness. Your customer will not install an app for a monthly relationship. WhatsApp, Instagram, and a fast website are your distribution; the giants already paid for the install.
  • Do not subsidize your way to habit. Gojek could burn investor money on promos for years. Your discounts must pay back within the quarter, or they are just margin donation.
  • Do not chase breadth before the anchor is solid. Every failed super app clone, and the market has seen several attempts since 2019, died from adding services before any single one was a habit. If your core product has quality problems, bundling multiplies the disappointment.

The Takeaway

The honest summary of super app business lessons for an SME: own a frequent interaction, remove one friction per quarter, bundle only around real adjacency, and refuse the vanity moves. Frequency before features. Habit before breadth. Anchor before bundle.

The practical starting point is a single question at your next management meeting: what is our anchor habit, and what one friction, removed this quarter, would strengthen it? Write the answer down and ship it before December. That is the entire super app strategy at your scale, and unlike building the actual app, it is nearly free. If the answer touches how customers pay you or reach you online, make sure the foundations fit into a plan, not a pile, something I argued in Why Your Business Needs a Technology Strategy, Not Just a Website.