India
UAE
KSA
USA
UK
Canada
Oman
Kuwait
Australia
Thailand
← Compare solutions
Before we scope the work
A useful project starts with a clear brief.
Describe the problem, the people it affects and what needs to change. This checklist helps you prepare for a conversation about brand, web, growth, automation or partnerships.
You do not need every answer to get in touch. Mark unknowns as questions to resolve together.
Your project preparation checklist
Use the checkboxes as a reading aid. They are optional, are not submitted, and are not saved when you leave. Keep your answers in your own document, or print this page using your browser.
-
- Who is the audience, and in which markets or languages?
- What do they need to do? Where does the current experience break down?
- What is the most important improvement? Share a specific example and any existing evidence.
-
- Which pages, assets, channels or workflow steps are essential?
- What is out of scope? What existing brand elements, content, URLs or systems must be preserved?
- What are your preferred timing, budget constraints and fixed dependencies? Separate a preference from a hard deadline.
-
- Brand
- Audience and positioning priorities, existing logo and guidelines, required asset formats and an approver.
- Build
- Current site or product, essential user journeys, content inventory, integrations and supported devices.
- Grow
- Target markets, current landing pages and reports, a conversion definition and the process for following up enquiries.
- AI
- One workflow example, approved knowledge sources, permission boundaries, failure examples and a human handoff.
- Partners
- Offer details, markets, allowed traffic sources, attribution setup and rules for accepting or rejecting activity.
-
- List the systems involved, who owns them and what access the work might require.
- Use redacted examples. Do not send passwords, API keys, customer records or other sensitive data through the enquiry form.
- For integrations or automation, agree on permitted data sources, access limits and human review before connecting systems. Arrange any necessary access through a suitable secure method after the scope is agreed.
-
- How will you decide that each deliverable is ready? Name the reviewer and the evidence they need.
- For a website, describe a complete mobile enquiry journey. For AI, include expected answers, failure cases and escalation rules. For partnerships, define valid attribution and accepted activity.
- Agree on review checkpoints, required handover materials and who can approve release. Keep launch checks separate from longer-term performance measurement.
-
- Who supplies content, approves creative, manages technical access and handles enquiries?
- Which dependencies need another team's or provider's input?
- List unresolved questions and the decisions needed before work can start.