CLARITY BEFORE COMMITMENT
Know what we agree together.
A shared brief
You bring the ambition, existing materials, constraints and a decision-maker. Together we confirm the problem, audience and success criteria.
An explicit scope
Deliverables, exclusions, dependencies, budget, payment terms and dates belong in an agreed written proposal—not assumptions on a website.
Clear approvals
Agree who can approve, how feedback is consolidated and how many review rounds are included. Changes to scope require a revised agreement.
A considered handover
Confirm final formats, access, documentation, training and acceptance criteria. Ownership, third-party licences, maintenance and support must be agreed in writing.
We agree responsibilities, timing, pricing, rights and support in a written proposal before work begins.
THE SERVICE BEHIND THE WEBSITE
From enquiry to follow-through.
Proposed service blueprint—not a live tracking portal. Scope and responsibilities are agreed for each project.
- 01
Understand the need
Review the outcome you want to achieve.
- 02
Discuss the direction
Clarify where we can help and what needs defining.
- 03
Agree the work
Confirm deliverables, fees and timing before starting.
More about delivery and support
- 01
Enquiry
Accountable role: Enquiry coordinator
Confirm successful receipt only after the enquiry is securely recorded.
If something goes wrong
If saving fails, preserve the draft and offer a clear retry; never show a false success.
- 02
Acknowledgement
Accountable role: Enquiry coordinator
Provide a reference, a named contact and an approved response window.
If something goes wrong
If delivery fails, retry through the agreed channel and flag the issue to the owner.
- 03
Discovery
Accountable role: Discipline lead
Clarify the need, fit, decision-makers, constraints and the next agreed action.
If something goes wrong
If the fit or timing is wrong, say so clearly and agree whether to close or revisit.
- 04
Proposal
Accountable role: Engagement lead
Explain scope, exclusions, fees, milestones and approval requirements in writing.
If something goes wrong
Resolve questions or revise the proposal before asking for acceptance.
- 05
Onboarding
Accountable role: Project lead
Confirm contacts, access, inputs, communication rhythm and a shared delivery plan.
If something goes wrong
Record missing inputs and agree their effect on the plan before work depends on them.
- 06
Delivery
Accountable role: Project lead
Show progress at agreed checkpoints; record decisions and obtain approvals.
If something goes wrong
Raise risks early, agree changes and document the recovery plan.
- 07
Handover & follow-up
Accountable role: Project lead / support owner
Check acceptance, transfer agreed assets and access, and agree the follow-up date.
If something goes wrong
Route unresolved issues to a named owner; separate fixes from new scope and support terms.