The 10 Terms That Matter When Buying Custom Software

Most expensive software misunderstandings do not come from obscure technology. They come from ordinary words carrying different meanings on each side of the table. ‘Done’, ‘launch’, ‘deadline’ and ‘change’ sound obvious until money and dates depend on them.

The brief is the starting description of the problem, users, core workflows, constraints and business objective. It is not the final specification. A good team will challenge it, ask what is missing and turn it into something buildable.

Scope is the work included in the agreement. If a feature was never part of that agreement, asking for it later is not a bug fix. It is new work, even if the feature feels obvious in hindsight.

A change request is a decision to alter agreed work: a new feature, a changed flow, a different integration or a requirement discovered after planning. Good teams make the impact on hours, budget and timeline visible before implementing it.

‘The developer finished it’ can mean the code exists on a development environment. To a client, ‘finished’ often means tested, approved and live. Define done explicitly: implemented, reviewed, tested, deployed and accepted, or whatever your project requires.

Development is where work is actively changing. Staging is where a release candidate is tested in an environment that resembles the live system. Production is what real users access. Seeing something on staging does not mean it has launched.

Architecture is the set of structural decisions behind the product: where data lives, which systems talk to each other, which parts need to scale independently and where security or reliability boundaries sit. It matters most when requirements change.

The Project Manager owns coordination: dependencies, status, risks, communication and delivery rhythm. They should make uncertainty visible before it becomes a surprise.

The Product Owner decides what the product should do and what matters first. On some projects that person sits with the client; on others the delivery partner supplies the role. The title matters less than having one person who can make product decisions.

A sprint is a short delivery window, commonly one or two weeks, used to plan, build and review a defined batch of work. It is useful because assumptions get tested before months of work accumulate behind them.

A deadline only means something when both sides know what must be true on that date. ‘Code complete’, ‘ready for acceptance’, ‘submitted to the app stores’ and ‘live for all users’ are different milestones. Put the milestone next to the date.

You are not paying a development team so you can learn their vocabulary. You are paying them to make complicated work understandable. These ten terms are the ones worth defining early because ambiguity around them turns into rework, invoices and missed dates.