Listen.
Clarify the goal, audience and next step. Open questions come first.
Care and support
STAY GOOD.
MOVE FORWARD.
beyond the launch
Updates, maintenance and technical attention with clearly agreed tasks and responsibilities.
Does this fit your situation?
THIS IS
THE START.
Launch is the start of day-to-day use. Good care means knowing who checks what, how changes are requested and when a task falls outside the agreed scope.
- Content changes regularly and needs a reliable process.
- Technical updates and changes need to remain understandable.
- There is no agreed point of contact for questions and small improvements.
What the agreed scope includes
- Review and definition of the supported website
- An agreed list of tasks and maintenance frequency
- An agreed channel for requests and approvals
- Completion of changes covered by the maintenance scope
- Documentation of completed work and relevant observations
- Agreed checks of essential contact and content journeys
- Clarification of backup, recovery and responsibilities
Options to consider
These tasks can be added when needed and are explicitly named in the proposal.
- Additional content work or new pages
- Larger design and technical extensions
- Further integrations or language versions
- A separately agreed process for urgent incidents
What you contribute
You nominate a person for approvals and provide accurate content. Access, licences and third-party contracts remain clarified. Response times, availability, backups and additional work are agreed in writing; continuous on-call support is not automatically included.
Working together
A CLEAR PATH.
Design.
Discuss the structure and designs. Decisions become visible and open to review.
Build.
Develop the agreed solution, check it across screen sizes and review it together.
Think ahead.
Clarify content, responsibilities and future care at handover.
FAQ
GOOD TO KNOW.
What does support include?
This depends on the website and the agreed task list. Content, technical care and development work are named specifically so that scope and responsibilities remain clear.
How quickly will an enquiry receive a response?
Availability and response times are agreed in the relevant proposal. There is no round-the-clock service without a corresponding agreement.
Can an existing website built elsewhere be supported?
That decision follows an initial technical review. The platform, documentation, access and necessary licences need to allow a sensible maintenance process.
What happens with larger changes?
Tasks outside the maintenance scope are described and quoted separately. You decide whether to approve them before that work begins.
A GOOD FIT?
tell us about your idea