The call usually comes within a week of the launch. "Our competitor just released an app. We need one too. How fast can you build it?" I have taken some version of this call a dozen times, and my first answer is always the same: before we build anything, let us read the competitor digital strategy behind that app, because the app itself is not the strategy. It is the visible artifact of a strategy you cannot see yet.
This distinction matters more than any technical decision that follows. An app is a screenshot. A strategy is the reason the screenshot exists. Companies that copy screenshots spend hundreds of millions of rupiah reproducing a competitor's surface while missing the machinery underneath, and they usually end up with an app nobody downloads and a strategy they still do not have.
So this is an anti-panic piece. Your competitor launching an app is information, not an emergency. Here is how to extract the information.
First, decode what the app is actually for
Download the competitor's app. Use it for a week as a customer would. You are not evaluating its design, you are asking one question: what behavior is this app trying to create or capture? In my experience, an SME competitor's app is almost always one of four plays.
The ordering-habit play
If the app's core loop is reorder, saved favorites, delivery tracking, they are trying to become the default. The insight behind it: in repeat-purchase categories, whoever owns the reorder moment owns the customer. A rice distributor, a catering service, a building-supplies store, all fit this pattern. The app is a habit machine.
The data-capture play
If the app pushes registration hard, asks for birthdays and preferences, and runs a points program, the product is the database. They are converting anonymous walk-in traffic into named, reachable, segmentable customers. Every promo they send later costs almost nothing because they own the channel. The app is a customer-list builder wearing a loyalty costume.
The cost-cutting play
If the app moves interactions from staff to self-service, order status checks, booking, account balances, document uploads, they are attacking their own operating costs. Every customer who checks status in the app is a phone call their admin team does not answer. The app is headcount leverage.
The financing-or-signaling play
Sometimes the app exists for an audience that is not the customer at all: a bank, an investor, a franchise prospect, a big corporate client whose procurement team scores vendors on "digital maturity". The app is a brochure. These are the easiest to over-react to, because they often look impressive and do very little.
A week of honest usage usually tells you which play it is. Notice what the app nags you to do. That nag is the strategy.
Then, judge whether the play is working
Launching is cheap. Working is rare. Before you respond, gather evidence:
- Store metrics. Check download counts, ratings, and the review dates on Google Play. A thousand downloads with reviews clustered in launch week means employees and family. Steady weekly reviews mean real adoption.
- Update cadence. An app updated monthly is alive and funded. An app untouched for six months is already abandoned, and many SME apps die exactly this way, because maintaining an app is a payroll commitment, not a one-time build.
- Ask customers. You share customers with this competitor. Ask five of them casually whether they use the app and why. Five honest conversations beat any analytics you cannot see anyway.
- Watch their operations, not their marketing. If the app is real, it changes their behavior: shorter queues, promos that reference the app, staff pushing installs at the counter. If nothing operational changed, the app is decoration.
A large fraction of SME apps fail quietly within a year. If you panic-build in month one, you may be copying something that will not exist in month twelve.
Respond with your strengths, not their artifact
Here is the strategic core: even when the competitor's play is real and working, cloning their app is usually the weakest possible response, because you would be fighting on ground they chose, a year behind, with less conviction.
Instead, take the play you decoded and ask: what is the cheapest way to counter the underlying goal using what we are already good at?
| Their play | Panic response | Smarter counter |
|---|---|---|
| Ordering habit | Clone the app | Make reordering effortless on channels customers already use, a WhatsApp catalog and saved-order flow can capture the same habit for a fraction of the cost |
| Data capture | Clone the loyalty app | Start collecting customer data at your own touchpoints, even a simple registration incentive at checkout builds the same asset |
| Cost cutting | Clone the self-service | Fix your highest-volume internal process first; their app tells you where the industry's cost pressure is |
| Signaling | Clone the brochure | Ask whether the audience matters to you; if yes, there are cheaper credibility signals than an app |
Notice the pattern: the counter targets the goal, not the artifact. If they built a habit machine, you need a habit answer, not necessarily an app. For most Indonesian SMEs, WhatsApp is where the customer already lives, and a well-run WhatsApp catalog beats a mediocre native app on adoption every single time, because it requires no download, no registration, and no new habit.
And sometimes the right response is genuinely nothing. If the competitor is chasing a segment you do not want, or making a play that your positioning already answers, watching is a strategy too. Write down what you observed, set a reminder to re-check their traction in three months, and spend your budget on your own bottleneck.
If you do decide to build, build from your strategy
Occasionally the analysis concludes that yes, an app or a serious digital investment is right for you too. Fine, but then it must come from your numbers: which customers, which behavior, which cost line, what result in what timeframe. That is a strategy question before it is a development question, and it is exactly the discipline I argued for in why your business needs a technology strategy, not just a website. A build motivated by "they have one" has no success criteria, which means it cannot succeed, only cost.
The takeaway
When a competitor launches an app, run this sequence before spending a single rupiah:
- Use their app for a week and name the play: habit, data, cost, or signaling.
- Check whether it is actually working: store signals, update cadence, five customer conversations.
- Counter the goal with your strengths, usually cheaper channels you already own, not a clone.
- If you build, build from your own strategy with explicit success criteria.
Competitors are free market research. They spent hundreds of millions of rupiah testing a hypothesis in public, and you get to read the results before betting anything. Copying artifacts wastes that gift. Reading strategy compounds it.