WORK WITH CONFIDENCE
Four conversations before a project begins. Each one belongs in your written proposal.
Included features, exclusions, milestones and third-party fees.
What will the first release include? List the price, payment milestones, hosting and recurring service costs. Agree how changes will be estimated before they are built.
An agreed demo and acceptance checklist for each milestone.
Choose who reviews each milestone, the workflows to demonstrate and the checks needed for acceptance. Record feedback and resolve the agreed issues before signing off.
Know which accounts, licences, files and documentation you receive.
Document who owns the domain, hosting, application accounts and business data. Specify source-code rights, third-party licences, data export, training and the handover format in your proposal.
Agree contacts, coverage, response targets and ongoing costs.
Separate bug fixes from new features. Agree support hours, response targets, maintenance fees, backup responsibilities and how access is transferred if the engagement ends. Coverage follows the written plan.
Use this as a discussion checklist. The agreed proposal defines your deliverables, rights and support.
START A PROJECT
