How I work
Before I build, we agree what done means.
We’ll talk through the goal, current setup, and constraints. If it’s a fit, I’ll write down the deliverables, review points, responsibilities, timing, fees, and known third-party costs for you to consider before work starts.
A simple project path
A clear route from first talk to handover.
Select a step to see what happens. We agree on scope and timing before work begins.
Step 01 · Talk
Tell me the goal, current tools, and constraints so I can understand the task.
Scope-dependent handover
What you leave with.
The written scope says what is included, who reviews the work, and what happens after delivery. Depending on the project, that may include:
Handover notes
A practical record of what was built, how to use it, and known limits.
Access and ownership
We agree which accounts and permissions are needed, and who owns or manages each tool.
Training walk-through
A review of the agreed setup and the steps people will use day to day.
Further support
Maintenance, monitoring, or additional improvements are separate work unless the scope says otherwise.
Funding note
Check project and supplier eligibility directly with the funding body before relying on support. Eligibility and approval depend on the specific program and applicant.
Start with the task or website goal.
Share what happens today, which tools are involved, and what you hope to improve. I’ll set out timing and fees after the work is understood.
View contact status