A good start makes
the whole project easier.

Bring the essentials

• A short description of the problem and the result you want.
• One person who can approve content, design and scope decisions.
• Your preferred timing and any real deadlines.
• A list of the tools involved and who owns the accounts.
• Any relevant accessibility, language or industry requirements.

For a website

• Business name, service descriptions, service areas and contact information.
• Logo and photographs you have permission to use.
• Existing website and domain details—do not send passwords.
• Examples of websites you like and what you like about them.
• The main action visitors should take, such as requesting a quote.

For a workflow or custom tool

• A walkthrough of the current process from start to finish.
• Roles involved and what each person should be able to access.
• A sanitized sample of the forms or records used.
• Known exceptions, duplicate entries and common failures.
• The check that will tell us the new process is working.

For AI integration

• Approved sources the assistant may use.
• Examples of useful questions, tasks and expected answers.
• Topics it must not answer or actions it must not take.
• A named person for review and escalation.
• Agreement on data handling, usage costs and ongoing maintenance.

Share access carefully

Keep domains and service accounts in your business’s name. Use individual invitations with the access needed for the task. Do not email passwords, payment-card details, customer records or confidential documents before a suitable sharing process is agreed.

What happens next?

We confirm scope, responsibilities, fees and acceptance checks; agree the necessary service terms; establish access and the project schedule; then review a first version with you. Extra features are discussed and quoted before they are added.