Imagi-Tech

Software

Custom Software Cost for a Small Business: What Sets the Price

Custom software cost for a small business is set by scope, not by the hour count anyone guesses on a first call: how many screens and workflows it needs, who uses it and where, what it connects to, and how much old data has to come across. We quote each build as a fixed price in writing after a free audit.

Most people asking how much custom software costs want a number before they call. We don’t publish one, and you should be wary of anyone who quotes a price before they understand the job. What we can show you is how the price is built, so you can size your own project first.

What does custom software cost?

It depends on what the software has to do, and two projects that sound alike can be very different jobs. Our own work shows the spread. A point-of-sale rebuild for Thomson’s Landscaping kept the cashiers’ hotkeys and connected to an inventory system we had built for them years before. The ERP we built for Grimm Scientific Industries covers invoicing, cost accounting down to the individual part, and engineering change orders, and we still extend it. Both are custom software, and they are not the same size of job.

Every project starts the same way: a free audit of what you run now, then a fixed quote in writing with the scope, the price and the schedule, before anything is billed.

What moves the price up or down

Custom application development cost moves with a short list of things you can mostly count yourself:

  • Screens and workflows. Each form, list and step people click through is work to design, build and test. One job done well costs less than five jobs done at once.
  • Users and roles. Three people in one office is a different build from twenty across two sites, each seeing only what their role allows.
  • Where it runs. A desk-only app is simpler than one that also works on a phone in the field, and offline use adds more again.
  • Connections. Accounting, payroll, an online store or an existing database. Each one is a piece to build and test.
  • Old data. Years of records from a spreadsheet or an Access file have to be cleaned and moved, and cleaning costs less before the move than after.
  • Reports that must match. If a report has to come out to the penny against the old one, it takes longer to build.

The price comes down when the first release is kept to the one job costing you the most, with the rest added in stages.

What a prototype costs and what it tells you

We don’t sell the prototype on its own. Clickable screens come early in every build, and checkpoints are part of the quoted scope, not an extra. What they tell you is worth more than their cost. Hand somebody a written specification and they will approve it. Hand them a screen and ask them to do Tuesday’s work on it, and within minutes they find the thing nobody wrote down because everybody knew it.

A change caught at that stage means an edited diagram. The same change after the data model is built touches the screens, the reports and the migration plan, and costs far more. Our post on why prototypes save money covers the reasoning.

Monthly costs after launch

Custom software keeps costing something after launch, and a fair quote says so up front:

  • Hosting and backups, so the system runs on a proper server and the data can be restored.
  • Maintenance, because operating systems, browsers and the services it connects to keep changing.
  • Changes as the business grows. The Proz has had us building and improving JobTrax for more than eight years, and Grimm’s ERP has grown with a company four times the size it was.

You own the system, the data and the documentation, so you could move that upkeep to someone else if you ever needed to.

When you should buy instead of build

We start most conversations by trying to talk people out of building. Buying is usually cheaper and faster, with less risk. Buy when the process is standard for your trade and a product does it well enough. Build when the way you do the work is the reason customers choose you, when nothing exists for your niche, or when the real job is connecting systems you already have. Our post on build vs buy has the full test.

Not sure which you need? The scoping quiz asks seven questions and hands back a written brief on the shape of the project, without asking for an email. Our custom software page covers how we build, and our page on custom software in Cincinnati covers that market.

Free audit

Let's get started

Tell us what's giving you trouble, in your own words. "Our Access database is dying" is plenty to go on.