EXISTING CLIENTS · AFTER THE CONSULTATION

A clear plan before the build.

Use this after we’ve discussed your project and agreed to work together. We’ll record the scope, approvals, and handover before building. You don’t need this worked out before getting in touch.

Prepare a kickoff email Book a consultation

1. Agree the first useful version.

The problem and the people. Identify who will use the technology and one complete task it should help them finish.
What’s included—and what comes later. Record the features, project boundaries, existing-tool connections, price, and dates we agree.
What a successful result looks like. Write down examples we can check together, including everyday use and what should happen if something changes or goes wrong.
Dependencies and changes. Note any content, account access, or outside decisions needed. Agree changes to scope and their effect on price or dates before adding them.

2. Know who makes the decisions.

Main contact. Name the person who coordinates the project and the business email to use.
Final approver. Agree who can approve scope, price, content, and the finished work.
Feedback and reviews. Name the person who gathers comments, agree the next review step, and record decisions in the agreed written channel.

These details belong to your project. We confirm them before the build starts.

3. Plan the assets, access, and handover.

Content and files. List the copy, images, logos, menus, service details, or other material needed. Record who supplies and approves each item, when it is needed, and its permitted use.
Tools and account owners. Identify any domains, hosting, booking tools, app-store accounts, or payment services involved. We agree the access needed and arrange appropriate account invitations separately.
Ownership and launch. Agree who owns the project files and accounts, who handles launch tasks, and what will be handed over.
Support after launch. Record any agreed maintenance or support and the responsibilities for outside services before building.

List the accounts involved; don’t send passwords, payment details, or customer records in the kickoff email.

EXISTING CLIENTS · AGREED PROJECT DETAILS

Record what we’ve agreed.

Use this after we’ve discussed working together. Review the details, then email them when ready. Fields marked * are required. Everything else can be worked through together.

Your business

Business name

Your name

Business email

Project name (optional)

The first version

Think about one useful task your customers or team should be able to finish.

What needs to work better?

Who will use it, what do they do today, and what gets in the way?

What should someone be able to do? (optional)

Describe one task from start to finish, such as requesting an appointment or placing an order.

Included in the first version (optional)

Save for later (optional)

Features or ideas that can wait until another version.

How will we know it works? (optional)

For example: a customer requests an available appointment and staff can review it. We’ll agree the actual checks together.

Budget range (optional)

Target date or timing (optional)

Decisions and feedback

Who gives final approval? (optional)

Name the person who can approve scope, price, and the finished work.

How should we handle feedback? (optional)

Who gathers comments, and where should we record decisions and the next review?

Assets and handover

Content and assets (optional)

List any copy, images, menus, or brand files, who will supply and approve them, and their permitted use.

Existing tools and account owners (optional)

List tools and account owners only. Arrange access separately; leave out passwords, payment details, and customer records.

Handover and ongoing responsibilities (optional)

What needs to be handed over, and who will handle launch, content updates, or agreed support?

Answers aren’t saved after leaving or refreshing the page. Copy or download the finished brief to keep it. Scope, price, and a start date are agreed separately.