All guides

Guide

How to write a one-page memo before you build

Six questions to answer before you build anything, so you know what you are making, who it is for, and when it is done.

By Austin Marchese · Updated November 17, 2026

Your next step

Have Claude interview you

Paste this into Claude. It asks each question, pushes back on vague answers, and writes the memo with you.

Copy this prompt

Why write a memo before you build

Before a big build, my team writes one page on what we are building and why. Companies like Amazon and Meta work the same way: the memo comes before the work.

With Claude, building is fast. Knowing what to build is the slow part. A one-page memo gives you and Claude the same target, and tells you when you are done.

Example memo

Six questions, one short answer each. Select a question to see its part of the memo.

# Client onboarding automation
1## What is this?
Sends every new client a welcome email, a kickoff
call link and an intake form the moment they sign.
2## Who is it for?
Sarah, our account manager. She does this by hand
for every new client.
3## What is it not?
Not a CRM. It stops at the kickoff call.
4## What does done look like?
Sarah signs a client and does nothing else
until the kickoff call.
5## Smallest version that proves it
The welcome email alone, sent when a contract
is signed.
6## Features
- Starts when a contract is signed
- Welcome email with the kickoff call link
- Intake form
- A Slack message to Sarah when it is done

What not to put in a memo

Each of these makes the memo long. Here is where to put each one instead.

How you will build it

Leave it to the build. The memo says what and why. Claude works out the how once the memo is clear.

Every feature you might want one day

A later list. The memo holds what the first version needs. Ideas for later go in their own note so the build stays small.

Research and background

Its own doc. Link to it in one line. The memo stays one page so anyone can read it in two minutes.

Or write it yourself

Answer each question. Your memo fills in below, ready to copy or download.

One or two sentences on what it does, in plain words.

Name one real person. If you can't name them, stop here.

What you are leaving out on purpose.

How you will know it works.

The least you can build to find out if it works.

For an automation, what's in it. For a product, the core functionality.

Your memo

Your memo shows here as you answer the questions.

Test your memo

Before you build, run this with your memo. It checks your plan against proven frameworks and points out what is missing.

This command comes with BuildPartner.ai. Get BuildPartner.ai →

Questions about the memo

Why write a memo before building with AI?
Claude builds fast, so the slow part is knowing what to build. One page answering these questions keeps you and Claude on the same target and tells you when to stop.
How long should the memo be?
One page. Each answer is a sentence or two. If an answer runs long, the idea is not clear yet.
What if I can't name one person it is for?
Stop and find one before you build. A build without a real person to use it rarely gets used.
What do I do with the memo once it is written?
Paste it into Claude at the start of the build, so every step is checked against it. Keep it next to the project and update it when the plan changes.

From the program

The Executive AI Program

This guide is one of the resources in the program, where members build their AI system step by step.

  1. 1.1 · Get set up
  2. 1.2 · Company Brain
  3. 1.3 · Enhance your setup
  4. 1.4 · Your BuildPartner.ai tools
  5. 1.5 · Research your market
  6. 1.6 · Writing style
  7. 1.7 · Automate your system
  8. 1.8 · Optimize your token usage
  9. Part 2 · Your AI Team
  10. Part 3 · Go deep
Learn more