How-To Guides

Finish Sage 7 Discovery faster: prepare your brief with an AI agent

One copy-paste prompt turns a conversation with your AI assistant into a brief Discovery reads first.

· 4 min read · Sage 7 Engineering

image dbf34cab

Discovery is the interview that turns your idea into a blueprint: 14 product categories, then a short round on team, budget and platforms. Answering it cold takes a long sitting, and the questions that stall founders are usually the ones they haven't thought through yet.

There is a faster route. Think the idea through first with the AI assistant you already use (Claude, ChatGPT, Gemini), have it write everything down as one Markdown brief, and attach that brief to your Sage 7 project. Discovery reads the brief before it asks anything. Its first reply lists what the brief already answers, and from then on it only asks about the gaps, the failure cases and the permissions.

What you need

  • Your idea, in whatever shape it's in: notes, a pitch deck, a half-written spec.
  • Screenshots of products you admire (optional): your assistant can describe their screens and steps in words for the brief. Upload the screenshots themselves to the Design System tab later.
  • Your brand tokens (optional): colours, fonts and tone, so they end up in the brief and the design system.

Step 1: Let the assistant interview you

Open a new chat, attach your notes, screenshots and brand files, and paste this prompt:

text
You are helping me prepare a product brief for Sage 7's Discovery interview. Interview meone question at a time until each section below is covered, then write the brief as oneMarkdown document using exactly these headings. Use only what I tell you or what theattached files show. Do not invent features. If something is unclear or undecided, writeit under "Open questions" in that section instead of guessing.
For every feature, also note: what happens when it fails, what the empty state looks like,and which roles can and cannot use it.
If I attach screenshots of other products, describe the screens and the steps a user takesin words, and say which parts I want to borrow. If I attach brand tokens, copy the exactvalues (hex colours, font families, radius, spacing) into the Brand section.
# <Product name>: project brief## Summary (what it is, who it is for, the one problem it solves)## 1. Navigation & IA## 2. Onboarding## 3. Core Workflows## 4. Actions & Controls## 5. Feedback Systems (notifications, loading, errors, success)## 6. Settings & Preferences## 7. Help & Support## 8. Data & State (what is saved, synced, offline behaviour)## 9. Permissions & Roles## 10. Integrations & Dependencies## 11. Admin / Back-office## 12. Security & Compliance   Answer each of these yes or no: users under 13? users in the EU? health data? payment   data? an AI chatbot? user uploads? marketing email? recurring billing?## 13. Growth & Retention## 14. Task / Background Systems## Build constraints   - **Team:** - **Builder tool:** - **Skills:** - **Existing stack:** - **Budget:**   - **Users Y1:** - **Traffic spikes:** - **Regions:** - **Data residency:**   - **Platforms:** - **Must use:** - **Must avoid:** - **Main users:** - **Environment:**   - **Sessions:** - **Data per screen:** - **Mistake cost:** - **Feel:** - **Accessibility:**## Brand (palette with hex values, fonts, tone of voice, three words for the feel)## Reference products (name, what to borrow, what to avoid)

Answer in your own words. "Not sure" is a good answer: an honest gap becomes an open question on your feature map, which is far better than a guess that turns into code.

Step 2: Read it before you attach it

The brief speaks for you, so remove anything the assistant assumed. Check that every feature is one you want, that the Security & Compliance yes/no answers are right (each "yes" becomes a compliance feature), and that undecided items are listed as open questions. Save it as a .md file; Sage 7 accepts up to 60,000 characters.

Step 3: Attach it and run Discovery

In your project, open Discovery, choose Attach brief, and start the interview. Expect follow-ups on what happens when something fails, what an empty screen shows and who may do what. Those answers are what make the blueprint buildable by a coding agent.

Step 4: Bring the brand in on the Design System tab

Discovery decides scope; the look is set on Design System:

  • Attach brand theme: upload your logo or a brand-guide page, then correct the extracted palette to your exact hex values and set your fonts. The palette stays fixed when Sage generates your design system.
  • Reference screenshots: add up to six screenshots of products whose density and feel you like.
  • Describe your design vision: up to 2,000 characters on tone and feel.

Why this works

Discovery was built to surface what founders haven't thought of, not to make them type what they already know. A prepared brief moves the easy answers out of the way, so the interview spends its time on the edge cases, permissions and constraints that decide whether the build holds together.

The full guide, with every limit and tip, is in Sage 7 under Settings → Documentation → Prepare Discovery with an AI agent.

Audit your codebase with Sage 7 before your coding agent drifts

Run a free Quick Audit on a public repo or URL, or start Free Discovery to turn your idea into a verified blueprint.