Software Strategy
How Much Does Custom Software Cost for a Small Business?
Custom software is priced around the work it must do: users, workflows, integrations, data and the responsibilities after launch. A useful budget separates the first release from recurring operation and later improvements. Start with a bounded scope that a supplier can estimate and that your team can accept with a practical test.

Section 01
Define the first result you are buying
A request for an app is too broad to compare proposals. Describe one completed task: a customer submits documents, an employee approves a request, or a manager sees an agreed report. Identify who uses it, which information changes and what should happen when an input is missing.
Ask the supplier to distinguish included work, assumptions and optional additions. A proposal for a customer portal with one user role cannot be compared directly with one that includes several roles, historical migration and connections to billing. Use the same brief when asking for estimates.
Section 02
Compare three common project scopes
These are planning examples, not packages or estimates. Each can be small or extensive depending on its rules and dependencies.
| Project | Possible first release | Questions that change the estimate |
|---|---|---|
| Customer portal | Sign-in, one request form and request status | Which roles, documents, approvals and notifications are required? |
| Internal operations tool | A shared job record and one useful report | What data must migrate, who may edit it and how are exceptions handled? |
| Software integration | One defined action between two existing tools | Are the required API actions available, and how will failed or repeated requests recover? |
Section 03
Separate implementation from the cost of running it
Include discovery, design, development, testing, migration, deployment and handover in the implementation discussion. Ask which activities are fixed in scope and which depend on information or access you still need to provide. Write down how a requested change will be estimated and approved.
Recurring items can include hosting, database usage, third-party subscriptions, support and maintenance. Microsoft documents that customers retain responsibilities for their data, identities and configuration even with cloud services. Agree who handles those responsibilities in your project. AWS also recommends accounting for operational effort when evaluating automation; a subscription invoice alone does not capture the work of running a system.
Section 04
Use a worked estimate with visible assumptions
Suppose a fictional first release is estimated at 24 hours of discovery and design, 72 of implementation and 24 of testing and handover. The total is 120 hours. At an agreed hourly rate R, the illustrative labor allowance is 120 × R. These hours are invented to show the calculation, not a CARRAS estimate or a delivery commitment.
Add quoted setup charges separately, then list recurring services with their billing period. If an additional integration needs another 24 hours in this example, the labor allowance becomes 144 × R, a 20% increase. That change needs a reason and an approval. A fixed-price proposal should state the corresponding deliverables and assumptions rather than imply an unlimited number of changes.
| Budget line | What to enter |
|---|---|
| First release | Agreed scope and price, or estimated effort × agreed rate |
| Setup and migration | Quoted one-time costs and responsibility for preparing data |
| Recurring operation | Provider charges, support and maintenance by billing period |
| Uncertain work | Named assumption, investigation needed and approval before extra work |
| Later improvements | A separate prioritized list, outside acceptance of the first release |
Section 05
Make acceptance and ownership part of the quote
A budget is more useful when everyone can tell what completion means. For a portal, a test might cover an authorized user submitting a request, staff reviewing it, and the user seeing the correct status. Include the missing-document path and check what a different user must not see.
Ask who owns the code and accounts, what documentation is supplied, which environments are included and what happens after handover. Confirm export and recovery arrangements, maintenance scope and how defects differ from new features. These are questions to resolve in the agreement, not assumptions about every supplier.
Section 06
Prepare a useful project brief for CARRAS
Bring one workflow, the roles involved, the tools that must connect, examples of the required records without customer data, and the outcome you need to test. Mention known deadlines and dependencies. We can review whether existing software, a focused integration or a custom application fits before preparing a scoped proposal.
- Describe the first useful release and what can wait.
- List migration, integration and access requirements.
- Separate implementation, recurring services and future changes.
- Agree on acceptance tests and responsibility after launch.