A launch window is a dedicated operational period where approved creative assets, software, or digital platforms are migrated from staging environments to live production. During this window, our Technology and Operations teams execute deployment steps, monitor infrastructure, and verify live functionality under controlled conditions.
Scheduling and operating hours All launch windows are scheduled strictly within core studio hours: Monday to Thursday, 09:00 to 17:00 GMT. We do not schedule launches on Fridays, weekends, or bank holidays. This ensures that the specialists who built the system remain on duty to monitor real-time telemetry, address unexpected conflicts, and provide operational stability.
A launch window is agreed upon during the final project review. Depending on the complexity of the deployment—such as database migrations, domain re-pointing, or multi-platform asset rollouts—a standard window spans between two to four hours of focused technical activity.
The deployment sequence Deployments follow a set operational sequence to protect data integrity and avoid unnecessary platform downtime:
1. Environment freeze: Twenty-four hours before the launch window opens, staging environments are locked. No further design revisions, copy changes, or code commits are permitted. 2. Pre-flight backups: The Technology department takes full snapshots of existing production environments, databases, and DNS zone files. 3. Cutover execution: Domain records are pointed, security certificates are issued, and production code or media directories are deployed to live servers. 4. Live verification: The Creative and Technology teams conduct smoke tests. These confirm that typography, colour profiles, dynamic forms, integrations, and responsive layouts function exactly as approved on staging. 5. Client review: Operations alerts you via the Ask Xylo chat on this portal that the build is ready for live verification. 6. Telemetry monitoring: The Technology team observes server logs, error tracking, and response times for the remainder of the agreed window.
Department responsibilities Each of our three internal departments carries specific tasks during a launch:
- Technology: Executes deployment scripts, reconfigures DNS routes, provisions SSL certificates, connects production databases, and verifies third-party API keys.
- Creative: Conducts visual quality checks across standard viewports to verify that typography rendering, asset compression, and visual alignments match approved deliverables.
- Operations & Client Services: Coordinates milestone timing, logs deployment stamps, and manages client communication through the Ask Xylo chat.
What the client must supply Delays during a launch window are almost always caused by missing credentials or external account restrictions. You must provide the following at least 48 hours prior to the window:
- Full administrative or delegated access to target domain registrars, hosting environments, and DNS management consoles.
- Production API keys and active logins for connected third-party tools, such as transactional email providers, CRM tools, or payment gateways.
- Formal, written sign-off confirming acceptance of the staging milestone.
- Availability of a designated decision-maker who can review live output and confirm approval via the portal.
Failure cases and rollback protocol If an unforeseen problem arises that cannot be resolved within 30 minutes, our lead engineer will execute an immediate rollback:
- External DNS or infrastructure outages: If external registrars or service providers fail to propagate records properly, the deployment is halted to prevent broken user journeys.
- Critical defects: If an unexpected conflict emerges between the production server environment and the codebase that was not present on staging, systems are reverted to the pre-flight backup.
- Rollback execution: A rollback returns the platform to its exact pre-launch state, typically within 15 minutes. Once restored, the launch window is formally closed, the underlying issue is investigated, and a revised launch schedule is communicated via Ask Xylo chat within our standard 24-hour reply window.
Deposits are non-refundable once your production slot is held. Before work begins, sums not yet earned are refunded pro rata; after work begins, completed work and booked time are charged. Defects are fixed free of charge within the acceptance window. The full terms are on the Refund Policy page of the main site.
Pre-launch checklist Ensure the following items are confirmed before your launch window begins:
- Staging milestone formally signed off in writing.
- All content, copy, and visual assets locked with no outstanding edits.
- DNS and third-party account credentials verified by our Technology team.
- Designated client reviewer available online between 09:00 and 17:00 GMT on the launch date.
- Post-launch feature requests catalogued separately for future production cycles.