Who fills in the brief — me or my client?

Either. Many users draft it live on a kickoff call and send the link for confirmation; the structure makes gaps obvious, so the client corrects the brief rather than discovering gaps mid-project.

Can I share the brief without an account?

Yes — the builder produces a shareable link and a copyable document with no sign-up. The account only matters when you want the brief to become a managed project.

What does the JoeFlow handoff create exactly?

A project in your new workspace with the brief attached: deliverables as tasks, timeline as milestones, and the budget recorded. It is created by the signed link you trigger, so nothing is retyped.

Is the brief legally binding?

No — it is a working alignment document, not a contract. Most users attach it to or reference it from their actual agreement; it makes the contract's scope section easier to write.

What happens when the client changes scope halfway through?

The brief acts as referee: signed deliverables stay signed; scope changes become dated change notes with their own cost, and stale drafts stay archived with their stamp.

Can I see a worked example?

Worked example — a brand refresh. Deliverables: logo suite, 12-page brochure, 40 template thumbnails; timeline: 6 weeks, 2 review rounds; out of scope: signage fabrication, print sourcing. Budget: 9,500 staged 40/30/30 by milestone acceptance.

JoeFlow

Free · no sign-up · runs in your browser

Client brief builder

Turn a vague request into a structured project brief you and your client both sign off on.

Most project friction starts before any work does: the client asked for “a website refresh”, and nobody wrote down what that means. The brief builder walks you through the questions that prevent that — what outcome the client is buying, what is explicitly in and out of scope, which deliverables they receive and when, the budget range, and who approves what. You end with a structured brief you can send as a link, and the client's answers stay attached to the project instead of scattering across email.

Start from a template

Pick the closest industry — every field stays editable, and you can start blank too.

Project name

Client

Industry

Outcome — what success looks like

0/500

In scope0/8

Out of scope — the exclusions that prevent creep0/6

Deliverables0/8

Milestones0/6

Budget (USD)

Budget note (optional)

Approval — who signs off on what

Live preview

# Project brief: Untitled project

**Client:** (not set)
**Industry:** (not set)

## Outcome

(not set)

## Scope

In scope:
- (nothing listed yet)

Out of scope:
- (nothing listed yet)

## Deliverables

- (nothing listed yet)

## Milestones

- (nothing listed yet)

## Budget

(not set)

## Approval

(not set)

Share the brief

Copies a link that reopens this exact brief in the builder — nothing is stored server-side; the whole document rides inside the link.

Carries the brief into a free workspace: deliverables land as tasks, milestones as a timeline, and the budget is recorded — nothing is retyped.

How to use the client brief builder

1
Capture the outcome
Write what success looks like in the client's own words — this anchors every later decision.
2
Mark scope boundaries
List what is explicitly out of scope; exclusions are as important as inclusions.
3
Set deliverables and dates
Name each deliverable, its format, and its due date, including dependencies.
4
Share or hand off
Copy a shareable brief link, or move it into a free JoeFlow workspace where it becomes a tracked project.

The questions that prevent scope creep

The builder structures the brief around the five disagreements that actually derail projects: outcome (what does success look like, in the client's words), scope boundaries (what is deliberately excluded), deliverables (named artifacts with formats), timeline (dates with dependencies, not just a finish line), and approval (who signs off, on what). Answering them in one sitting takes fifteen minutes and replaces the weeks of “just one small addition” that an unwritten brief invites.

From a shared document to a managed project

Sharing the brief as a link settles the conversation; running the project is a different job. With the JoeFlow handoff, the brief becomes a real project in your workspace — the deliverables land as a task list, the timeline becomes milestones, and the budget is attached so you can compare planned against actual as the work progresses. Change requests then have something concrete to amend, which is precisely what makes saying “that's a change order” a normal conversation instead of a conflict.