Define the job.
Understand the business goal, current setup, constraints, and who needs to be involved.
A considered result starts with a clear working relationship. Here is how we structure the decisions, deliverables, and handoff.

Understand the business goal, current setup, constraints, and who needs to be involved.
Document deliverables, responsibilities, review rounds, exclusions, costs, and timing.
Share the direction before a full build. Make changes against the agreed goal, not guesswork.
Test the agreed requirements, transfer the appropriate access and files, and explain ongoing support.
If the project changes, review the impact on cost and timing before expanding the work.
Identify who owns accounts, assets, subscriptions, and ongoing maintenance. Separate third-party licensing from project deliverables.
A form error, an unavailable integration, or an uncertain AI answer should have a defined next step.
The final acceptance criteria belong in your proposal. These are examples of what to consider.
Review content and mobile layouts, test inquiry paths, check key links, and document hosting and content ownership.
Review permitted data, test outputs against examples, check approval steps, and document errors, usage costs, and a manual fallback.
Agree on the message and visual direction, review required formats, and confirm the files and usage guidance included in handoff.