The engagement
What happens after you say yes
Most projects like this don’t fail. They stall — on one unanswered question, for a month, until nobody wants to raise it. So this is written down: what I do, what I need from you, and what happens when it goes quiet.
Start We agree the starting point
Tell me about your business goal, whether you are a direct client or an agency. We review the material and answers already available. Paid research and planning normally belong inside the project; a separate assessment is a selected exception, not the default first purchase.
From youYour goal and any relevant link. Read-only access only where agreed.
Scope You receive a written offer
The offer separates the core website, included planning and content work, selected additions, and any recurring operation or provider costs. Pages, languages, identity/media work, review points, acceptance, timing and payment milestones are explicit rather than assumed. No preset page count or support allowance is implied.
From youConfirm the business goal, factual content, scope, component costs and total, currency, fees and payment milestones.
If it goes quietI identify the unresolved item and explain what can continue before any additional commitment.
Build A complete delivery, with agreed review points
Review the structure and content before they drive the design and implementation. You see a private candidate before launch. AI supports the work; I remain responsible for judgement, factual checks and delivery quality. Corrections to our agreed delivery are not disguised as paid additions; new requests are checked against the scope.
From youConsolidated feedback within each agreed review round and confirmation of any factual or legal claim.
If it goes quietI continue the independent parts, identify the parked items and agree any schedule change with you.
Handover You can operate the completed project independently
Your written agreement defines the client-specific deliverables, source, access map and operating documentation included in the handover. Your domain, accounts, content and data remain yours. The written agreement defines rights for shared delivery tools and components, third-party licences and external costs, so the completed project can be operated and handed over.
From youAcceptance and a separate go-live decision. Build does not require Run.
If it goes quietNothing is published without the agreed go-live approval.
Optional Run Defined ongoing operation
If ongoing operation is useful, we agree its coverage, human-work allowance, response arrangements and recurring cost separately. Website delivery does not automatically include CRM, business operations, marketing strategy, social-channel management or unlimited support.
From youChoose Run only if you need ongoing operation. Agree the monitoring and scope before the paid period starts.
If it goes quietI do not treat silence as approval for extra time or a new scope.
Improve One defined outcome
A focused improvement does not require an ongoing operating arrangement. We agree the baseline, target, scope and acceptance evidence, along with cost and milestones. It is not an open-ended programme.
From youAgree one outcome and the evidence that will demonstrate completion.
If it goes quietI identify the missing acceptance input and preserve the work already completed.
If you go quiet.
You will. Everyone does — a tender lands, someone leaves, the quarter gets busy. It is not a problem unless the process has no answer for it.
I follow up on the channel you actually use
Telegram, phone, or email — whichever you replied on last. Chasing a decision by email because it is convenient for me is how a month disappears.
Work continues wherever it can
An unanswered question parks one item, not the project. You get told what is parked and what it is holding up, so silence has a visible cost rather than an invisible one.
Follow-up has an agreed rhythm
We agree the channel, the decision needed and a useful response window. If the priority changes, we record it rather than silently keep the old deadline or treat silence as approval.
I would rather pause than bill a stalled project
If the work genuinely cannot move, we pause. Restarting is cheap; a retainer quietly charging for a project nobody is progressing is how these relationships end badly.
Everything I will ask you for.
The whole list, not the first instalment of one. If it grows, that is a scope change and I will say so rather than send another request.
- Read access to what already exists — domain, hosting, analytics, whatever you have
- Sign-off on the structure, once, before I build on it
- Your real service descriptions, in your words — I will edit, not invent
- Contact and legal details, confirmed as accurate
- A decision on anything I flag as a claim I cannot verify
- A go-live yes
I answer my own messages, and I would rather tell you a project has stalled than let it quietly cost you another month.
Working together
Tell me what you are starting, what already exists, or what is no longer working. I read every message myself and will tell you plainly whether I can help.