The first kickoff call establishes project scope, technical dependencies, creative direction, and milestone schedules before any production begins. It is an operational alignment session to confirm technical access and deliverables, rather than an exploratory brainstorming meeting.
Purpose and schedule
Kickoff calls take place only after the proposal is approved, terms are accepted, and the initial deposit has been cleared. 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.
Meetings are scheduled strictly during studio working hours, which run Monday to Thursday, 09:00 to 17:00 GMT. Calls typically last between 30 and 45 minutes. The session is not used to negotiate commercial terms or redraw agreed scopes; its purpose is to confirm the delivery sequence, establish point-of-contact responsibilities, and surface operational blockers before work starts on the studio floor.
Client prerequisites
To keep the kickoff productive, the studio requires specific materials uploaded and confirmed prior to the call. If these prerequisites are incomplete, the meeting will be postponed:
* Design assets: Vector brand marks, complete typography files, brand guidelines, and existing interface libraries. * Copy and media: Final or production-ready draft copy, image libraries, video footage, and legal notices. * Technical access: Staging environments, hosting panels, repository rights, analytics profiles, and third-party API credentials. * Authorised representative: The nominated individual holding ultimate sign-off authority must be present on the call.
Assets should be submitted via the client portal rather than fragmented communication channels. Where technical credentials involve sensitive systems, your team will configure access with the Technology department beforehand.
Agenda and meeting sequence
The call follows a standard operational sequence governed by Operations & Client Services:
1. Scope and boundary verification (10 minutes): We review the deliverables stated in your approved quote or package description. Any requested additions outside this boundary are logged for subsequent scoping rather than absorbed into the active cycle. 2. Departmental handoffs (15 minutes): Relevant leads review implementation details. Creative verifies asset completeness and design constraints. Technology verifies server environments, dependencies, and integration architecture. 3. Milestone schedule and review windows (10 minutes): We lock in production sprints, deliverable drop dates, and your required feedback windows. Studio review windows require prompt turnaround to maintain momentum. 4. Operational logistics (5 minutes): Confirmation of communication paths. Ongoing status tracking and support queries run directly through the Ask Xylo chat on this portal.
Departmental responsibilities
Depending on the nature of your project, specific internal teams will lead segments of the discussion:
* Operations & Client Services: Chairs the meeting, oversees the project timeline, manages stakeholder communication, and records all formal approvals. * Creative: Inspects delivered creative files, clarifies aesthetic and UX benchmarks, and sets expectations for design revisions. * Technology: Verifies codebases, server architecture, data pipelines, integrations, and deployment requirements.
Small package builds may be handled entirely by an Operations lead, whereas bespoke builds typically involve technical and creative leads directly.
Failure states and postponements
A kickoff call fails when required technical access is missing, brand assets are unorganised, or key decision-makers cannot attend. When access credentials do not work or dependencies remain blocked, production cannot proceed.
If the studio cannot confirm access or clarify baseline requirements during the call, the onboarding phase is paused. Stalled onboarding delays the project timeline, shifting agreed milestone dates to the next available studio opening. Work resumes only once all missing dependencies are resolved and submitted through the portal.
Kickoff readiness checklist
Before attending the kickoff call, verify that you have completed the following items:
* Reviewed the approved scope of work or package specification. * Designated a single internal project owner with final approval authority. * Transferred all vector assets, fonts, and brand documentation. * Tested and granted developer access to third-party tools, repositories, and staging servers. * Prepared working availability to meet agreed feedback windows. * Verified your portal login to communicate via the Ask Xylo chat.