When Should a Business Build a Mobile App? Timing Signals for Nigerian Companies

The four readiness conditions

A business is ready for a mobile app when it can honestly answer yes to all four of these:

1. Repeat relationships. The same customers transact with you again and again, so a permanent place on their phone saves them effort.
2. Enough active customers. There are enough repeat customers that even a modest share of installs produces meaningful order volume.
3. Data in a system. Orders, bookings, balances or statuses are recorded somewhere the app can read from and write to, not in a notebook or a WhatsApp thread.
4. Two-year funding and capacity. You can pay for the build and for maintenance, app-store fees, hosting and small improvements for at least two years, and someone in the business will own the app.

Three out of four is "soon", not "now". The rest of this article explains each condition and what to do about the one that is missing.

Why timing matters more than the idea

The cost of being early is easy to underestimate. An app built before the business is ready has a predictable life: a burst of downloads from friends and existing customers, a few weeks of use, then silence. The business keeps paying hosting and maintenance for a product that has become a liability, and the memory of that failure often blocks a sensible app project years later when the timing is actually right. The cost of being late is quieter but real. A business with thousands of repeat customers, staff copying orders from WhatsApp into a spreadsheet and customers ringing to ask "has my order gone out?" pays every day for friction an app would remove. The signal to look for is not "competitors have an app" but "our own operations are straining in ways an app fixes". An honest timing assessment also protects the budget. A focused first version costs roughly ₦1,500,000–₦5,000,000 and a version with accounts, payments, notifications and an admin dashboard roughly ₦5,000,000–₦15,000,000 (indicative 2026 ranges; actual quotes vary with scope, vendor and exchange rate). That is not money to spend on a guess.

Condition 1: repeat customer relationships

An app earns its place on a phone only if the customer expects to use it again. The frequency of the relationship, more than the industry, decides whether that expectation exists.

A business in the bottom two rows can still justify an app if it bundles several occasional needs into one relationship, as some insurers and estate managers do, but it should not build one for a single once-a-year interaction.

Condition 2: enough active customers

Only a fraction of any customer base will install and keep an app, and a smaller fraction will use it regularly. The exact share depends on how much effort the app saves and how well the business promotes it, so treat any percentage you hear as a guess. The safer way to think about it is in absolute numbers. Ask two questions:

• How many customers bought from us more than once in the last three months? That is your realistic pool of installers, not your total follower count or your full customer list.
• If only a small share of that pool used the app regularly, would the order volume through it justify the running cost?

A business with a few hundred genuinely repeat customers can usually justify a focused app. A business with a few dozen cannot, however loyal they are; those customers are better served by a well-run WhatsApp Business account, a catalogue and payment links. There is one important exception. A start-up whose product is the app (a fintech, a marketplace, a ride service) is not building for existing customers and cannot apply this test. It should instead follow the validation and MVP route covered in the articles on how to validate an app idea in Nigeria and how to build an MVP in Nigeria.

Condition 3: your data already lives in a system

An app is a window onto data. It can show a customer their order status, wallet balance, booking time or delivery position only if the business records those things in a system the app can connect to. If the current record of an order is a WhatsApp message and a transfer screenshot, there is nothing for the app to display. This is the condition most Nigerian SMEs fail first, and the cheapest to fix, because fixing it pays off whether or not an app follows. The practical test:

• Can a staff member look up a customer's last five orders without scrolling through chats?
• Is there a single place where order status is updated (a spreadsheet counts, a proper system is better)?
• Do payments get reconciled against orders somewhere other than someone's memory?
• Does the business have a customer list with phone numbers that is not just a WhatsApp broadcast list?

If most answers are no, the correct next project is a simple business management system or web portal, not the app. The app then becomes a relatively small addition on top of a backend that already works.

Condition 4: budget and capacity for two years

An app is a recurring commitment, not a purchase. Beyond the build, a business should expect, as indicative 2026 figures:

• Maintenance: typically 15–25% of the build cost per year, covering operating-system updates, security patches, bug fixes and small changes.
• Hosting and services: cloud hosting for the backend (roughly ₦150,000–₦800,000+ per year depending on load), plus SMS or WhatsApp OTP costs, push notification services and any map or payment gateway fees.
• Store fees: Google Play developer registration is a one-time fee (historically US$25) and the Apple Developer Program is a yearly fee (historically US$99); verify current fees before budgeting.
• A named owner inside the business: someone who answers customer questions about the app, tests new releases, approves changes and watches the numbers. Without this person, apps decay.

Capacity matters as much as cash. If the owner is the only person who can make decisions and is already stretched, the app project will stall at the requirements stage. Timing is right when the business can afford both the money and the attention.

The usual sequence before an app

Most Nigerian businesses that end up with a successful app pass through the same stages. Skipping a stage is possible, but each stage builds the data, customer base and habits the next one needs.

The jump from stage 3 to stage 4 is the cheapest of all, because the backend, admin dashboard and payment integration already exist. The jump from stage 1 straight to stage 4 is the most expensive and the most likely to fail, because the app must be built together with everything underneath it. The comparison of a website versus a mobile app for Nigerian businesses covers the stage 2 to stage 3 choice in more detail.

A mobile app readiness scorecard

Score each line 0 (no), 1 (partly) or 2 (yes). Total the twelve lines for a score out of 24. Customer relationship

• Most revenue comes from customers who buy more than once.
• The typical customer transacts at least monthly.
• We have several hundred customers who bought more than once in the last three months.

Operations and data

• Orders or bookings are recorded in a system, not only in chats.
• Order status is updated in one place and could be shown to a customer.
• Payments are reconciled against orders in a system.
• We hold customer phone numbers and consent to message them.

Demand signals

• Customers regularly ask for order status, balances or history.
• Staff spend significant time on repetitive order-taking or status questions.
• Customers have asked whether we have an app, unprompted.

Capacity

• We can fund the build and two years of running costs without straining cash flow.
• A named person will own the app after launch.

Interpretation (a rule of thumb, not a guarantee):

• 0–9: Not yet. Strengthen WhatsApp and the website; start recording orders in a system.
• 10–16: Close. Build or improve the portal and backend first; plan the app for the following year.
• 17–24: Ready. Define a focused first version and get two or three written quotations on identical scope.

What changes for Nigerian businesses

Several local realities shift the timing decision compared with the generic advice found on overseas blogs.

• Android first, and often low-end Android. Storage is tight on many phones, so customers uninstall apps they do not use monthly. This raises the bar for condition 1: the relationship needs to be genuinely frequent.
• WhatsApp is the incumbent. Your app is not competing with nothing; it is competing with a channel customers already trust and have open all day. It must save the customer real effort (reorder in three taps, see status without asking) to displace the chat. The article on mobile app versus WhatsApp for Nigerian businesses treats this trade-off directly.
• Data costs and connectivity. An app that only works with a strong connection frustrates customers on the road between Lagos and Ibadan or in a poorly covered part of Kano. Readiness includes being able to specify offline behaviour, which in turn requires stable backend data (condition 3).
• Exchange-rate exposure. Hosting, notification services, map usage and store fees are largely priced in US dollars. A business should be able to absorb naira swings in its running costs before it commits (condition 4).
• Trust and payments. Customers will pay inside an app only if they trust the brand and the payment path. Bank transfer with a virtual account, card via a Nigerian gateway and pay-on-delivery should all be possible. Businesses that have already built trust through WhatsApp and a professional website are further along than their download count suggests.
• Compliance. The Nigeria Data Protection Act 2023 applies to customer data held in an app. Having consent, a privacy notice and basic security in place is part of being ready; verify current obligations with the Nigeria Data Protection Commission or a qualified adviser.

Example (hypothetical): a Lagos laundry at three stages

Consider a laundry and dry-cleaning business in Lekki. The scenario below is illustrative, not a client result. Year one: too early. Forty regular customers, orders taken on WhatsApp, pickups arranged by phone, payment by transfer. The owner considers an app because a competitor has one. Scorecard: 5 out of 24. An app here would cost more than a year's profit and most customers would keep messaging anyway. The right moves are a WhatsApp Business catalogue, a short mobile-friendly website with prices and a pickup form, and a spreadsheet of every order. Year two: close. Three hundred active customers, two vans, a spreadsheet that has become a simple web portal where customers log in with their phone number to book pickups and see status. Staff dashboard assigns pickups to drivers. Scorecard: 14. The business is now collecting exactly the data an app would display. An app would work, but the portal is doing most of the job; better to spend the year improving the backend and reminders. Year three: ready. Nine hundred active customers, most booking weekly, drivers complaining about the browser on the road, customers asking for pickup reminders and a faster reorder. Scorecard: 20. The app is now a thin layer over a working backend: phone-number login, one-tap repeat booking, push notifications for "driver on the way", and a driver app with offline pickup lists. Indicative cost sits in the lower part of the ₦5,000,000–₦15,000,000 band because payments, accounts and the dashboard already exist. The same idea, three different answers, decided entirely by timing.

What to do while you wait

If the scorecard says "not yet", the following moves make the eventual app cheaper and more likely to succeed, and each pays for itself regardless.

1. Record every order in a system. A structured spreadsheet at first; a simple order-management tool or custom portal when volume justifies it.
2. Build a customer list with consent. Phone numbers, what they buy, how often. This becomes the launch audience for the app.
3. Tidy the WhatsApp channel. Business profile, catalogue, quick replies, labels; the WhatsApp Business Platform with automation if volume is high.
4. Make the website mobile-first and transactional. Payment links, a booking or order form, status lookup. A progressive web app (a website that installs like an app) can test appetite cheaply.
5. Track the numbers you will need. Repeat rate, order frequency, staff time on status questions. These turn the decision into arithmetic and become the baseline the app is measured against.
6. Write the requirements early. One page describing the one or two jobs the app must do; the mobile app requirements checklist for Nigerian businesses is a useful template.

Mistakes to avoid

• Building because a competitor did. Their timing is not your timing. If their app is poorly rated, it may even be evidence that the market is not ready.
• Treating followers as customers. Instagram followers do not install apps at anything like the rate repeat buyers do. Count transactions, not audience.
• Building the app and the backend in one go from a chat-led business. It doubles the scope and the risk. Build the backend first.
• Ignoring running costs. Budgeting only for the build leaves the app unmaintained within a year, which is worse for the brand than having no app.
• Launching on both platforms out of habit. For most Nigerian customer bases, Android first is the sensible sequence; add iOS when the numbers justify it.
• No adoption plan. Timing readiness is about the business, but launch success is about getting the app installed. Plan the promotion (WhatsApp broadcasts, receipts, packaging, staff scripts) before the build finishes.
• Assuming the app replaces WhatsApp. It supplements it. A hand-off to chat from inside the app is a feature, not a failure.

Conclusion

The right time to build a mobile app is when repeat relationships, a large enough active customer base, systemised data and two years of funding all line up. Until then, the money is better spent on the stages that come first: a tidy WhatsApp operation, a transactional mobile-first website and a portal or backend that records what the app will one day display. Score the business honestly, fix the weakest condition first and revisit the decision every six months. If the scorecard puts your business in the ready range, or you want help deciding which stage to build next, Linestech can review your current systems and outline a sensible path from where you are to a mobile app that customers will actually use.

Frequently asked questions

Should a business build a website before a mobile app?

In almost every case, yes. A mobile-first website is cheaper, reachable through Google search and shareable by link, and it forces the business to organise its information and payments. Most Nigerian businesses that succeed with an app already had a transactional website or portal, which means the app could reuse its backend and payment integration.

Can a start-up use these readiness conditions?

Only partly. A start-up whose product is the app has no existing repeat customers or operational data, so conditions 1 to 3 do not apply in the same way. It should instead validate demand with a landing page, WhatsApp pilot or no-code prototype, then build the smallest version that tests the core assumption. Condition 4, funding for at least two years, still applies.

How many customers do I need before an app makes sense?

There is no universal number. A workable rule of thumb is several hundred customers who have bought more than once in the last three months, because only a fraction of any base installs and keeps an app. Businesses with high-frequency relationships (daily orders) can justify an app with fewer customers; low-frequency businesses need more.

Is a progressive web app a good interim step?

Often, yes. A progressive web app is a website that can be added to the home screen, works partly offline and can send notifications on Android. It costs far less than a native app, tests whether customers want a home-screen shortcut and reuses the same backend a later native app would use. Its limits are weaker iOS support and no presence in the app stores.

What if customers keep asking whether we have an app?

Take it seriously but check the reason. If they want faster reorders and status without asking, that is a real demand signal. If they are asking because they assume every business has one, a well-built mobile website may satisfy them. Ask three or four of them what they would do in the app that they cannot do today.

How long does it take to become ready?

For a chat-led business, typically a year or more, mostly spent putting orders and customers into a system and growing the repeat base. For a business that already runs a portal or web app, readiness may be immediate, since the app can reuse the existing backend. The stage table above shows the usual progression.

Sources and further reading

Figures, platform rules and regulations change. These are the primary references behind this article and the places to check before you act on it.

• Nigeria Data Protection Commission (NDPC)
• WhatsApp Business Platform — Meta for Developers
• Apple Developer Program
• Google Play Console
• MDN Web Docs — web platform reference
• GSMA Mobile Economy research
• Node.js documentation