What Custom Software Actually Costs in Zambia

Nearly every first conversation we have starts the same way: how much is this going to cost? Most agencies deflect it. We would rather answer it, because a business that cannot budget cannot plan, and a quote that arrives three meetings later has already wasted everyone's time.

What actually drives the price

Custom software pricing is not arbitrary, but it is also not a per-page rate. Four things move the number more than anything else:

• How many distinct user roles there are. A system where everyone sees the same screens is dramatically cheaper than one where an administrator, a manager and a customer each need different permissions, different views and different workflows. Every role roughly multiplies the interface work.
• Whether it has to talk to anything else. A self-contained system is straightforward. One that has to synchronise with an accounting package, a payment provider and a supplier's inventory feed carries the cost of every one of those integrations — plus the cost of handling them failing.
• Whether money moves through it. Payments raise the stakes on testing, error handling, reconciliation and security. A system that takes payment is not a system with a payment button bolted on.
• How much of the process is undecided. If you know exactly how the workflow should run, we can build it. If the project is partly about working out what the workflow should be, that discovery is real work and it has to be paid for somewhere.

Roughly what each budget buys

These are broad bands, not quotes, and they assume a reasonably well-defined scope.

Entry level. A focused tool that does one job well for one type of user. A booking form that writes to a database and emails a confirmation. A stock list your team can update from a phone. No integrations, no payments, no complex permissions. This is where most small businesses should start, and many never need more.

Mid range. A real business system: several user roles, a proper admin area, reporting, and one or two integrations — commonly payments or an existing accounting tool. This is the level at which software starts replacing meaningful amounts of manual work rather than just digitising a form.

Upper range. Multi-location operations, custom integrations with systems that were never designed to be integrated with, offline capability, or anything where downtime costs real money. At this level the engineering is often the easy part; the difficulty is in the edge cases.

Our published package prices sit at the lower end of these bands deliberately. They cover well-defined work where we already know the shape of the problem. Anything genuinely bespoke gets scoped on a call, because quoting it from a form would mean guessing.

The costs people forget

The build is not the whole cost. Budget for these too, or they will surprise you:

• Hosting and infrastructure — modest for most business systems, but ongoing and non-optional.
• Third-party services — payment gateway fees, SMS costs, mapping APIs. These scale with your usage, which means they grow exactly when you are busiest.
• Maintenance — dependencies need updating, security patches need applying, and browsers change. Software is not a building; it decays if left alone.
• The change you did not scope — six months in, you will want something you did not think of. That is normal. Leave room for it.

When you should not build

We turn work away for these reasons more often than people expect:

• An existing product already does it. If an off-the-shelf tool covers 80% of what you need at a fraction of the cost, take the 80%. Custom software is for the cases where the missing 20% is the whole point of your business.
• The process is not settled. Building software around a workflow nobody has agreed on produces expensive software that nobody uses. Fix the process on paper first.
• Nobody owns it internally. A system with no internal champion gets abandoned. If no one on your side is accountable for it succeeding, the money is better spent elsewhere.

How to get a real number

Write down, in plain language: who uses it, what each of them needs to do, what it has to connect to, and what happens today without it. That single page is enough for any competent team to give you a realistic range. If someone quotes you without asking for it, be careful.