A practical one-page brief defines your project objective, deliverables, technical boundaries, and timeline clearly enough for our studio to issue a firm bespoke quote within 48 hours.
It removes ambiguity from the outset, allowing Operations & Client Services to route your requirements to our Creative or Technology departments without open-ended discovery rounds.
The structure of a workable brief
A brief does not need to be exhaustive, but it must be definitive. Keep your brief strictly to one page (under 500 words) using the following five headings:
1. Objective and context State the commercial or operational problem you are solving in one or two sentences. Explain what success looks like upon completion. Avoid generic statements such as "modernise our online presence"; specify the exact operational outcome, such as "rebuild our internal client portal to reduce onboarding queries by half."
2. Exact deliverables Provide an itemised list of what you expect to receive at completion. Distinguish between core requirements and optional additions: * Explicit scope: specify exact page counts, core features, interactive elements, or creative asset counts. * Out of scope: list what should explicitly not be tackled in this phase.
3. Technical parameters and existing assets List the technical infrastructure and design materials currently in place. Note down: * Target tech stack, existing content management systems, or hosting environments. * Required third-party integrations, APIs, or software licenses. * Existing brand guidelines, design systems, or vector assets, noting whether they are production-ready or need updating.
4. Milestones and hard constraints Identify whether your completion date is an internal preference or a strict deadline driven by an external factor (such as an event, product launch, or contract renewal). If third-party sign-offs or external compliance audits are required, state these clearly.
5. Commercial context and referrals If your requirements align with standard service tiers, check the packages page for pre-scoped delivery options. If you were referred to Xylora Studios by an existing client or partner, state their full name or company so we can verify their ambassador programme record. Verified referrals typically receive a 10–30% discount, which we confirm in writing directly on your quote.
Review and quotation sequence
Once your brief is prepared, submit it through the Ask Xylo chat on this portal. The review follows an established sequence:
1. Receipt and triage: Operations & Client Services logs your document during studio operating hours (Monday to Thursday, 09:00–17:00 GMT). Our first reply target is within 24 hours to confirm receipt and verify document completeness. 2. Departmental assessment: The brief is allocated to either the Technology or Creative department (or both) to assess technical feasibility, resourcing, and timeline constraints. 3. Information request (if incomplete): If critical technical requirements or asset details are missing, we pause the quotation clock and request clarification. 4. Formal quote issue: Once the brief is verified as complete, we supply a bespoke quote within 48 hours. This includes the itemised project scope, milestone schedule, and fixed fee. 5. Authorisation and commencement: Work is scheduled upon written agreement of the quote and payment of the initial deposit. 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.
Common failure cases to avoid
Briefs that lead to stalled quoting or scope disputes generally suffer from the same issues:
* Vague design language: Terms like "clean," "intuitive," or "disruptive" convey personal preference rather than operational scope. Replace these with direct functional requirements or reference sites. * Hidden technical debt: Failing to disclose an outdated codebase, undocumented database schemas, or restricted server access slows production once onboarding begins. * Unidentified decision-makers: If your project requires sign-off from external directors or legal counsel, omit them from the brief at your own peril. List every approval gate upfront. * Omitting content readiness: Delays frequently occur because copywriting, photography, or data structures are not ready. State plainly whether the studio must create the content or if your team will provide final copy.
Pre-submission checklist
Before sending your brief through Ask Xylo, ensure you can tick off each item:
- [ ] The brief fits on a single page or under 500 words.
- [ ] Deliverables are explicitly listed as discrete items.
- [ ] Any fixed, non-negotiable launch dates are highlighted.
- [ ] Current hosting, technical stacks, or brand assets are documented.
- [ ] If referred, the ambassador's name is noted to apply the 10–30% discount.
- [ ] You have confirmed that required internal stakeholders agree with the listed scope.