Most custom software has two kinds of cost. The first is building it. The second is keeping it running, safe and useful after launch. Many buyers budget for the first and are surprised by the second.
The build: a one-time project
A good build starts with a short discovery: goals, users, must-have features and risks. From that comes a written scope and a fixed quote. Payment is split into milestones, so you pay as you see working software, not all up front.
Changes happen. The difference between a calm project and a stressful one is that changes are written down, priced and agreed before anyone starts on them.
After launch, a warranty period covers bugs in what was agreed. New features are not bugs; they go on the roadmap.
After launch: a monthly care plan
Software doesn't stay still. Browsers, phones and libraries update every month, security patches appear, and your team will want improvements. A care plan covers hosting, monitoring, backups, updates and a set amount of development time, with response times in writing.
The alternative, calling a developer only when something breaks, usually costs more: problems are found late, nobody remembers how the system works, and fixes are rushed.
What to ask any supplier
Who owns the code and the accounts? What happens if you want to leave? What exactly does the warranty cover? What are the response times, and are they in the contract? Clear answers to these questions matter more than the day rate.
