Discover
Understand the people, problem, and current workflow.
Typical output: A shared problem statement and a list of constraints.
Define
Agree priorities, scope, assumptions, and acceptance criteria.
Typical output: A written proposal with deliverables and a project plan.
Build
Develop in manageable stages and review the important user flows.
Typical output: Working increments for feedback against the agreed scope.
Test
Check core tasks, integrations, and relevant failure cases.
Typical output: A documented acceptance review and a list of any remaining issues.
Launch
Plan deployment, access, handover, and operating responsibilities.
Typical output: An agreed release and practical handover documentation.
Support
Address scoped maintenance needs and plan future improvements.
Typical output: A support arrangement or a prioritized next-work list, when agreed.
How timing and changes are handled
Delivery dates are estimated after scope and dependencies are understood. Feedback, data availability, third-party access, and scope changes can affect the schedule. We discuss changes to scope, cost, or timing before adding the work. There is no universal completion time or promised reduction in weeks.
What to bring to the first conversation
- A short description of the problem and who experiences it
- The tools you use today and the steps you repeat
- The most important outcome for a first release
- Known deadlines, constraints, and any budget context you wish to share
Keep the initial information non-sensitive. We can agree a suitable way to share private project materials if needed.