How to discuss a software project budget
A price becomes comparable when you know what it includes, how it will be delivered and what it costs to run. Start with written scope and reviewable milestones.
Describe what must work
List users, tasks, platforms, languages and integrations. A “booking app” still needs decisions about availability, confirmation, changes and operating roles.
Review content, data migration and external accounts. Missing inputs can delay delivery even when designs are ready.
Separate building from running
Ask for development costs and then hosting, external services, store fees, support and maintenance as applicable.
Agree who owns accounts and pays invoices. Ask which usage assumptions inform the estimate and what would change it.
Connect payments to clear deliverables
Agree each milestone’s output and acceptance process. A prototype, a trial release and a production launch are different deliverables.
Use a written change process: describe the request, assess its time and cost impact, then agree before implementation.