The short answer
Nobody can honestly price custom software before understanding the work. Cost follows things you can identify early: business rules and exceptions, roles and approvals, integrations, data migration, and security, privacy and audit obligations, plus hosting, support and maintenance every year it runs. Budget in three pieces: a fixed-scope discovery, a first release on the most valuable problem, and a yearly running allowance. A quote without them? Ask why.
What actually drives the cost
Screens are not what make software expensive. Rules, connections and data are.
| Cost driver | Why it matters |
|---|---|
| Business rules and exceptions | Every "except when" needs design, code and tests; most effort goes here |
| User roles and approvals | Each role needs permissions, screens and tests, including what it must not see |
| Integrations | Your ERP, CRM, accounting, payment gateway or Microsoft 365 set APIs, limits and data quality |
| Data migration | Old spreadsheets and databases hide duplicates, gaps and unwritten rules |
| Security, privacy and audit | NDPA obligations for personal information; some processes need full audit trails |
| Accessibility and language | Public software must work for everyone, phones first; some need local languages as well as English |
| Hosting, power and connectivity | Office-hours tools cost less to run than around-the-clock ones; patchy connections need software that copes |
What to have ready for each driver
- Rules and exceptions: real awkward cases, not just the normal path.
- Roles and approvals: who does what, and who signs off.
- Integrations: system names, editions and administrators.
- Data migration: sample exports, and an owner who decides what is correct.
- Security, privacy and audit: privacy commitments, retention rules, customer or regulator requirements.
- Accessibility and language: who the users are, their devices, any members of the public.
- Hosting, power and connectivity: how much downtime the business can tolerate, and where users work.
Why quotes for the same project differ so much
Far-apart quotes on one brief usually price different things:
Exceptions
One firm priced the happy path; another, the edge cases you mentioned in passing.
Testing and documentation
Tests, pipelines and handover docs take time. Leaving them out looks cheaper, then costs more to own.
Data migration
Often left vague as "your job". Ask who moves it and how results are checked.
Risk
A fixed price includes a buffer for uncertainty; time and materials shows you the uncertainty instead.
Currency
Naira quotes and dollar-priced cloud or licence items compare only once you see each exchange rate assumed.
Ownership
Source code, infrastructure and accounts should end up in your organisation's name.
On ownership: under Nigerian copyright law the author (or in some cases the employer) is generally the first owner, and an assignment generally has to be in writing, so code from an outside firm needs a written assignment or licence in the contract. Have your legal adviser confirm the wording.
Compare fairly by asking each firm to list its assumptions and exclusions. The cheapest total with the longest exclusion list is rarely the cheapest project.
How to build a realistic budget
- Fund discoveryMaps process, rules, data, systems; ends in scope, release plan, estimate.
- Size release oneThe most valuable problem, not the whole wish list.
- Hold contingencyRequirements change once people see software; dollar items need an exchange-rate allowance.
- Fund running costsHosting, security updates, monitoring, support, small improvements, every year.
- Check tax treatmentDevelopment spend, VAT and withholding tax on supplier invoices, any programmes.
Discovery, estimated in naira (or US dollars where a licence or service is priced in dollars), is the cheapest point to learn the project is bigger, smaller or different. A release that properly replaces one painful spreadsheet or approval beats a broad one done half-way. Unfunded software becomes a risk, however good the first version. Ask your accountant about tax treatment and whether any government or development-agency programme applies; do not count on an incentive until confirmed. General information, not tax advice.
Example: a hypothetical budget structure
Hypothetical budget structure: a mid-sized distributor replacing a spreadsheet-based returns process.
- Discovery (fixed scope): map returns, list exceptions, review ERP integration options, produce scope and phased estimate.
- Release 1: returns requests, approvals and credit notes pushed to the ERP, for two user roles.
- Release 2 (only if release 1 proves its value): customer self-service portal and reporting.
- Contingency: part of each release held for changes found in testing, plus an exchange-rate allowance for dollar-priced items.
- Yearly running allowance: hosting, monitoring, updates and a small block of improvement hours.
Each line carries its own estimate in naira (or US dollars where priced in dollars) and assumptions.
Rather talk it through? We can turn your process into a written scope and a phased estimate before you commit a full budget. Talk to a Promatics specialist
The questions people ask before they call us
"We are too small for custom software." Sometimes true: if a packaged product fits with configuration, buy it. Custom earns its place when the process is yours alone and workarounds cost time every week (build, buy or integrate guide).
"Can AI tools build this for less?" AI coding assistants speed up parts of development, and we use them, with people reviewing the output. They do not uncover your exceptions, settle conflicting rules, test on your real data or answer for the result when it breaks. That judgement and accountability are most of what you pay for.
"What if the project runs over?" Each phased release is scoped, estimated and accepted on its own: you can pause, change direction or stop and still have something usable.
What working with Promatics looks like
- DiscoverA written recommendation, which may be buy or integrate, not build.
- First releaseAgreed scope, delivered in short iterations with regular demonstrations.
- MigrateYour data moved and reconciled.
- Hand overSource code, documentation and infrastructure in your organisation's accounts.
- SupportA separate agreement, so you know exactly each year's cost.
See custom software development for the full approach.
When to bring in help
- You can describe the process, not yet its exceptions or data.
- It will hold personal information or support auditable decisions.
- It must connect to at least one system you do not control.
- Nobody will be funded to maintain it after launch.
- Your quotes cannot be compared because they assume different things.
None apply and the tool is small and internal? A capable in-house developer or low-code platform may do. Two or more? An experienced partner usually pays for itself by getting scope and ownership right before money is spent.
Sources and further reading
Product capabilities and guidance change. These are the primary sources this article relies on, checked on the review date above.
- Nigeria Data Protection Commission (NDPA, GAID 2025, registration and guidance), Nigeria Data Protection Commission
- Web Content Accessibility Guidelines (WCAG) 2.2, World Wide Web Consortium (W3C)
This article is general information, not legal, accounting or security advice for your specific situation. Examples are hypothetical unless stated otherwise.