Four desks you can hand over.

• Content and copy edits, new sections, image swaps
• Broken links, 404s, redirects and form failures
• Page-speed and Core Web Vitals regressions
• Mobile and cross-browser layout fixes
• Uptime and SSL checks, with an alert path that reaches a human
• Plugin, dependency and CMS updates on a schedule

To start we need: Hosting or repo access, a staging URL if one exists, and the brand rules you want us to hold to.

• Ticket triage, reproduction steps and severity tagging
• Bug reports written so an engineer can act without a follow-up
• Release-day cover and regression sweeps
• Feature requests captured, de-duplicated and routed
• Status-page and incident comms written in your voice
• Escalation to your engineers against an agreed rota

To start we need: Access to your issue tracker, a test account, and the escalation rules you want enforced.

• Welcome sequence and kickoff scheduling
• Account setup, data import and configuration
• Live walkthroughs and recorded training for the customer team
• A written handover so the customer knows what they own
• Check-ins at day 7, 14 and 30 against adoption signals
• Churn-risk flags raised to you early, not at renewal

To start we need: A product walkthrough, your ideal-customer notes, and the milestones you count as "onboarded".

• Sub-account creation and snapshot deployment
• Pipelines, stages and custom fields set up to your template
• Calendars, forms, surveys and booking flows configured
• Automations, workflows and triggers built and tested end to end
• Domain, email and phone verification walked through with the client
• A recorded handover session so the client can run it themselves

To start we need: Agency-level access, the snapshot you want loaded, and the client details for the sub-account.