We begin with the applications and people involved. A screen recording, spreadsheet or difficult order can explain the problem better than a feature list.
A proposal grounded in the systems
We check the interfaces and investigate questions that could change the build. The proposal sets out the work, price, timetable and responsibilities. We also say when an existing feature or configuration change would do the job.
Working versions to review
The team sees the software before the release. We use representative records and ask the people doing the task to try it. A new requirement is discussed with its effect on cost and timing.
A usable handover
Before launch we cover live access, pending work, hosting and support. You receive the agreed code, configuration and operating instructions. The release checklist explains the practical checks.