01
Understand the business.
Review goals, existing tools and the customer journey. Identify reusable assets, missing pieces and decisions or permissions needed.
Working output: Requirements and asset inventory, with open questions visible.
Process
Good work needs a clear definition of done.
A scoped engagement moves from understanding the business to agreeing the work, reviewing the build and verifying the result\u2014then preparing you to run it.
02
Define the engagement.
Put deliverables, fees, exclusions, responsibilities and acceptance checks in writing. Agree how new requests will be assessed.
Working output: Scoped proposal and prerequisites for starting work.
03
Build and review.
Prepare agreed pages, assets and workflows in draft or staging. Review together, record decisions and keep open questions visible.
Working output: Reviewable implementation with decisions and exceptions recorded.
04
Verify the journey.
Test the agreed customer journey with controlled examples. Record expected and actual results, resolve defects and identify unverified items.
Working output: Observed acceptance results and remaining issues.
05
Make the launch decision.
Review the tested release, open issues and go-live responsibilities. Confirm exact changes to publish and the restoration plan.
Working output: Approved release decision and rollback reference.
06
Hand over with context.
Walk through delivered systems and provide agreed assets, operating instructions and ownership records. Review subscriptions, training and follow-up against scope.
Working output: Handover record, training log and ongoing responsibilities.
Your part
Provide accurate business information, rights-cleared assets, access through approved methods and timely decisions.
Scope changes
Review new requirements for cost, dependencies and schedule before adding them.
Timing
Delivery depends on agreed scope and readiness. The schedule belongs in the proposal.