When Should You Buy Existing Software?

The instinct to build is strong among Nigerian business owners, partly because so many foreign products fit the local market badly. But buying is the correct answer far more often than building is, and the businesses that get the most from technology are usually those that bought well and built narrowly.

This article covers when the buy route is right, what it genuinely costs once you include implementation, how to evaluate a product against Nigerian operating conditions, and the situations in which buying quietly becomes the more expensive mistake. When Should You Build Custom Software?.

What "buying existing software" covers

"Buying" spans four quite different models, and the differences matter for cost, control and risk.

• Global SaaS subscriptions. Priced per user per month in US dollars, hosted abroad, updated continuously. The broadest choice and the deepest functionality, but the weakest fit for local operating details.
• Nigerian or Africa-focused products. Built for local payroll rules, tax filing, POS operations, school management or logistics. Often better fitted and naira-priced, usually with a smaller feature set.
• Licensed on-premise software. A one-off licence, installed on your own machines or server. Less common now, but still used in manufacturing, accounting and point-of-sale.
• Open-source platforms you host. Free to licence, but you pay for hosting, configuration and support. In practice this is a hybrid: buying the software, building the setup.

A fifth option sits between buying and building: a bought product with significant configuration and custom integrations. For most growing Nigerian businesses, this is the sweet spot — you get the product's maturity and the vendor's updates, plus the specific connections your operation needs.

The five conditions that make buying the right call

Buying is the right decision when most of these hold.

1. The process is standard, not distinctive. Payroll, bookkeeping, leave requests, email, document storage, help-desk ticketing and most sales pipelines work broadly the same way in every business. There is no competitive advantage in owning your own version.

2. You need it working soon. Configuration takes days to weeks. A custom build takes months. If the pain is urgent and the process is standard, speed alone usually settles the argument.

3. Regulatory or security upkeep matters. Payroll and tax rules change. Security patches are constant. A product vendor absorbs that work across thousands of customers; you absorb it alone if you build.

4. Your volumes are modest or uncertain. Below roughly twenty users, subscriptions almost always cost less than owning a system once maintenance and hosting are counted. If you are unsure how the business will look in two years, renting flexibility is worth paying for.

5. The product's gaps are tolerable or bridgeable. Every product will fit imperfectly. The question is whether the gaps can be handled by a workaround, a configuration or a small integration — or whether they force you to change how you serve customers.

That last condition is the one to test hardest. A gap that costs a staff member ten minutes a day is tolerable. A gap that means you cannot accept bank transfers, or cannot price by route, is not.

What buying actually costs

The subscription is the advertised number, not the cost. Plan for the full picture.

Indicative 2026 ranges; actual costs vary with scope, vendor and exchange rate. Request written quotations from two or three implementation partners on identical scope before committing.

Three cost traps recur. Per-user pricing scales badly when you add field staff or seasonal workers who each need a login. Tiered feature gating means the capability you actually need often sits one plan above the one you costed. And annual commitments in dollars lock in a rate you may regret; ask whether a naira-invoiced option or a local reseller exists.

How to evaluate a product for Nigerian conditions

Most product comparison guides are written for markets with reliable power, flat-rate data and card-dominant payments. Use this checklist on top of the standard feature comparison.

• Payments: does it support Paystack, Flutterwave, Interswitch, Moniepoint or bank transfer confirmation, or only foreign card processors?
• Currency: can it handle naira properly, including large figures and multi-currency reporting?
• Tax and compliance fields: does it accommodate Nigerian VAT treatment, withholding tax and TIN fields, or would you be working around it every month?
• Offline behaviour: what happens when the network drops mid-task? Does work queue and sync, or is it lost?
• Mobile: is the mobile experience full-featured on a mid-range Android phone, or a cut-down companion app?
• Data weight: does it load acceptably on metered mobile data outside a fibre office?
• WhatsApp: does it integrate with the WhatsApp Business Platform, or expect customers to use email?
• Support hours: is support available in West African time, and through a channel your staff will actually use?
• Local implementation partners: is there anyone in Nigeria who can configure, train and troubleshoot?
• Payment method for the subscription: can you pay reliably? Verify with your bank what your current international card or transfer limits are.
• Data protection: where is data stored, what does the vendor's processing agreement say, and does it support your obligations under the Nigeria Data Protection Act 2023?
• Data export: can you export everything, in a usable format, without asking permission?

A product that fails on payments, offline behaviour or data export is usually disqualified regardless of how good its feature list is.

What changes for Nigerian businesses

Exchange-rate exposure is a strategic risk, not a footnote. A per-user subscription is effectively a foreign-currency liability that grows with headcount. Model it at a stressed rate before committing to an annual plan, and re-evaluate yearly. This is the single strongest local argument for eventually owning software at scale, and it is why Build vs Buy Business Software in Nigeriae years rather than one.

Paying for foreign subscriptions can be an operational problem in itself. Nigerian businesses have periodically faced constraints on international card spending, and limits change. Before committing to a critical system, confirm with your bank how you will pay for it every month, and whether a reseller who invoices in naira is available.

Support in your time zone changes daily life. A product whose support team answers overnight is workable for back-office systems and painful for anything customer-facing. Where possible, prefer vendors with West African coverage or a local implementation partner on retainer.

Local products often win on fit and lose on depth. A Nigerian payroll or school-management product will usually handle local rules better than a global equivalent. Check its data export, its update cadence and how long the company has been operating before you make it the backbone of your business.

Adoption is the real risk, not licensing. Many Nigerian teams keep working in WhatsApp groups and spreadsheets after a system goes live. Budget for training, appoint an internal owner, and be prepared to insist that the system is the single source of truth.

Data protection obligations stay with you. Using a foreign SaaS provider does not transfer your responsibilities under the NDPA 2023. You remain accountable for lawful basis, notices and retention. Review the vendor's data processing terms, and verify current requirements with the Nigeria Data Protection Commission (https://ndpc.gov.ng/).

Example (hypothetical): an Abuja professional services firm

The following is a hypothetical illustration, not a Linestech client result.

A 26-person consulting and advisory firm in Abuja runs proposals in Word, timesheets in Excel, invoices in a desktop accounting package and client communication in email and WhatsApp. Partners cannot see which projects are profitable until months after delivery.

What they considered building: a custom practice-management platform covering pipeline, timesheets, project profitability and invoicing. Indicative quotes came in around ₦14,000,000 with maintenance on top.

What they did instead: bought a professional-services management product on subscription, plus an accounting package that supports Nigerian VAT and withholding tax handling. Implementation, configuration and data migration ran to roughly ₦2,800,000 through a local partner. They then commissioned one small custom integration — pushing approved invoices from the practice system into the accounting package with the correct tax codes — at an indicative ₦1,200,000.

Why this was the right call: timesheets, pipelines and project profitability are standard processes. The firm's differentiator is its advisory work, not its back office. They got the system running in eleven weeks rather than eight months, avoided ongoing maintenance responsibility, and spent custom-build money only on the one gap that actually mattered.

What they accepted: per-user fees in US dollars that grow as they hire, a support window that does not fully overlap Nigerian working hours, and a reporting layout they would have designed differently. All tolerable; none of them touched how the firm serves clients.

When buying is the wrong call

Buying becomes the expensive decision in these situations.

• The product forces you to change how you make money. Changing an internal habit to fit a product is fine. Changing your pricing model, service promise or customer experience is not.
• A hard local requirement is unmet. Offline capture, bank transfer reconciliation, route-based pricing, multi-branch stock movement, regulatory fields. Workarounds around a hard requirement become permanent manual labour.
• Per-user costs are scaling faster than value. If you need logins for 80 field staff who each use the system for four minutes a day, per-seat pricing punishes you.
• You need five products to cover one process. A stack held together by manual re-entry is usually more expensive and more fragile than one fitted system.
• Your data is trapped. If you cannot export your customers, transactions and history in a usable format, you are renting your own information.
• Software is your product. If you sell the software, you build it. Website vs Software: What Does Your Business Need?.

The practical signal is manual re-entry. When staff routinely copy data out of one bought system to put it into another, the buy strategy has stopped working and either integration or a custom module is due.

Decision framework: buy, configure heavily, or build

Score each statement 0 (no), 1 (partly) or 2 (yes).

1. The process is standard across businesses like ours.
2. We need a working system within the next three months.
3. Regulatory or security updates matter and we do not want to own them.
4. We have fewer than about twenty people who need access.
5. Existing products meet our hard requirements, including payments and offline use.
6. We can export our data from the product at any time.
7. We can reliably pay a foreign subscription every month, or a naira-invoiced option exists.
8. The gaps can be closed with configuration or one small integration.
9. We have someone who will own implementation and drive adoption.
10. Our processes are still changing as the business grows.

15–20 — Buy. Choose a product, budget properly for implementation, and resist the urge to build.

9–14 — Buy and configure heavily, with targeted integrations. Expect to spend as much on setup and connections as on licences in year one.

0–8 — Investigate building. Work through When Should You Build Custom Software?.

Implementation: how to buy software well

1. Write down the process and the must-have requirements first. Three pages is enough. Buying without a requirements list is how businesses end up with impressive software that nobody uses.
2. Shortlist three products, not ten. Two global options and one local option is a sensible spread for most categories.
3. Run a real trial with real data. Load your actual customers, prices and a week of real transactions. Demos are designed to succeed; your data is not.
4. Test the hard requirements deliberately. Take a payment, process a refund, work offline for ten minutes, export everything, generate the report your MD asks for.
5. Price the full first year. Licences, implementation, migration, integration, training and support, at a stressed exchange rate.
6. Check the exit before you enter. Export formats, notice periods, what happens to your data after cancellation.
7. Negotiate. Annual prepayment discounts, extra seats, onboarding support and training are commonly negotiable, particularly with local partners and resellers.
8. Appoint an internal owner and set a go-live date. Then switch off the old spreadsheet. Parallel running for more than a few weeks guarantees the old system wins.
9. Review after six months. Usage per user, processes still done manually, cost per user, and whether any gap has become a hard constraint.

Mistakes to avoid when buying software

• Buying on feature lists. Long feature tables reward products that do everything shallowly. Test the five things you will do every day.
• Skipping the trial with real data. Nearly every unpleasant surprise surfaces when real records meet the product.
• Ignoring the implementation cost. A ₦300,000-a-year subscription with a ₦2,000,000 implementation is a ₦2,300,000 decision.
• Letting each department buy its own tool. Fragmentation creates re-entry work and makes reporting impossible.
• Not checking data export. Ask for a sample export file before signing, not after.
• Committing annually in dollars without stress-testing the rate. Build the sensitivity into your budget.
• No internal owner. Bought systems fail from neglect more often than from defects.
• Customising a product beyond recognition. Heavy customisation of a SaaS product creates upgrade pain and eventually costs more than a fitted build would have.
• Forgetting security basics. Role-based access, removal of leavers' accounts and two-factor authentication are your responsibility, not the vendor's.

Conclusion

Buy existing software when the process is standard, the timeline is short, the upkeep is better carried by a vendor and your volumes do not yet justify ownership. That describes most of what most Nigerian businesses need. The discipline is not in choosing to buy — it is in buying properly: real trials with real data, honest implementation budgets, tested hard requirements and a guaranteed route to get your data back.

Reserve building for the one or two processes where no product fits without distorting how you serve customers. The businesses that get this balance right spend less, move faster and keep their custom engineering focused where it actually creates advantage.

Weighing a subscription against a build, or trying to work out which parts of your operation should be bought and which should be built? Linestech helps Nigerian businesses map that split, evaluate products against local requirements and integrate what they buy with what they already run.

Frequently asked questions

Is off-the-shelf software cheaper than custom software in Nigeria?

Usually in the first two years, and often beyond, once you include maintenance and hosting for a custom system. The comparison changes with user count and with the exchange rate: per-user dollar subscriptions grow with headcount, while a built system's cost is largely fixed. Compare total cost over three to five years rather than year one alone.

Can we use foreign SaaS products in Nigeria without problems?

Many Nigerian businesses do, but check three things first: how you will pay the subscription every month, whether support hours overlap your working day, and whether the product handles naira, local payment methods and your compliance fields. Verify payment arrangements with your bank, since international card limits and policies change.

What should I look for in the contract or terms?

Data export rights, notice period, price-increase terms, what happens to your data on cancellation, uptime commitments, support response times and the data processing terms covering NDPA 2023 obligations. For local resellers, confirm who provides support and what happens if the reseller relationship ends.

How do we stop staff going back to WhatsApp and spreadsheets?

Appoint an internal owner, set a firm date after which the old files are read-only, train people on the five tasks they do daily rather than the whole product, and make sure managers ask for reports from the new system only. Most reversion happens because the new system is slower for one common task; find that task and fix it.

Should we buy a Nigerian product or a global one?

Judge on fit for your hard requirements, not origin. Local products often handle payroll, tax fields, POS and school or logistics workflows better and invoice in naira. Global products usually offer deeper functionality, better integrations and stronger export options. Check the local vendor's track record and data export before depending on it.

How much should we budget for implementation?

As a planning figure, expect implementation, configuration, migration and training to cost between half and twice the first year's licence fees, more if several systems must be integrated. Ask shortlisted vendors or partners for a written implementation quotation separate from the licence price so you can compare like with like.

When does it make sense to buy and build at the same time?

Frequently. Buy the standard components — accounting, payroll, help desk — and build only the process that is genuinely yours, then connect them. This hybrid keeps custom scope small and lets the vendors carry routine maintenance. How to Connect Your Business Software.

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)
• Paystack developer documentation
• Flutterwave developer documentation
• WhatsApp Business Platform — Meta for Developers
• OWASP Top 10