---
title: The Discovery Call Super Prompt | soofcrm.com
---

[![Soof CRM](https://soofcrm.com/hs-fs/hubfs/__hs-marketplace__/3-1.png?width=214&height=40&name=3-1.png)](https://soofcrm.com/?hsLang=en) ☰

[Home](https://soofcrm.com/?hsLang=en)[About](https://soofcrm.com/about?hsLang=en)[Offerings](https://soofcrm.com/offerings?hsLang=en)[Projects](https://soofcrm.com/projects?hsLang=en)[Resources](https://soofcrm.com/resources?hsLang=en)[Blog](https://soofcrm.com/blog?hsLang=en)[Book a call](https://meetings.hubspot.com/soof)

Free guide

# The Discovery Call *Super Prompt.*

Turn a discovery call transcript into first-draft project docs.

Copy the prompt

[Jump to the prompt ↓](https://soofcrm.com/super-prompt-x7k2#prompt)

![Soof talking animatedly on a video call](https://soofcrm.com/hs-fs/hubfs/Headshots/SoofHirschmann_0012.jpg?width=600&height=750&name=SoofHirschmann_0012.jpg)

[What it does](https://soofcrm.com/super-prompt-x7k2#what) [Make it yours](https://soofcrm.com/super-prompt-x7k2#yours) [What you need](https://soofcrm.com/super-prompt-x7k2#need) [How to use it](https://soofcrm.com/super-prompt-x7k2#how) [The prompt](https://soofcrm.com/super-prompt-x7k2#prompt) [Tips](https://soofcrm.com/super-prompt-x7k2#tips)

What this does

## Stop starting from scratch after every discovery call.

You just wrapped up a discovery call. You have a transcript, a few ideas for how you might solve the problem, and a whole lot of documentation ahead of you. Instead of staring at a blank page, use this prompt to turn that conversation into a structured starting point for your project.

I used to stare at an empty page for hours before starting work on a project. With my super prompt, I take the writers' block out of project planning because I don't have to be the first one to put pen to paper. I can review AI's first draft, instead.

### You get five first drafts:

1. 01
   
   ### Project Overview
   
   The client's problem, constraints, current-state process, business requirements, scope and future-state process.
2. 02
   
   ### Solution Architecture
   
   2–4 real options, an honest check of your own instinct, a recommendation and a build plan an admin can work from.
3. 03
   
   ### Project Plan
   
   Week by week, built from the timeline you give it.
4. 04
   
   ### Open Questions & Decisions
   
   Every gap, tagged with who needs to answer it.
5. 05
   
   ### Follow-up email
   
   Ready to send after you review it.

These aren't finished deliverables or a substitute for your judgment, but they are something useful to react to, challenge, refine and build on. The AI does the organizing and first draft.

Then, you can take it from there.

Make it your own

## Remember to make it yours.

I need you to know something. This is the prompt I use for my client projects. It's not a universal template and shouldn't be treated as such.

What works for my consulting style (and my type of client) might not fit your organization, your clients, or your brain and how you think. I know if I had handed these deliverables in at Wells Fargo, I would have gotten more than a few raised eyebrows.

I encourage you to try this once, and then tweak whatever you need (the deliverables, terminology, level of detail, approval steps, documentation format, architecture preferences and project-planning approach) to match your standards. If your team uses a specific delivery methodology, requirements template or definition of done, include that in your super prompt.

You can remove sections you don't need and add the ones you do. The goal isn't to follow my process perfectly; just like what this prompt does for your projects, my prompt is a starting point that can help you get to a useful framework that works for you.

What you need

## Before you start

1. 01
   
   ### A transcript of your discovery call/kick-off workshop
   
   Any recorder works (tl;dv, Fathom, Zoom, Teams, Gong). The more the client explains their process, the better the output.
2. 02
   
   ### An AI chat tool that can handle long input
   
   Such as Claude or ChatGPT. If yours can search the web, even better: it will check Salesforce features and licensing instead of guessing.
3. 03
   
   ### Your gut solution
   
   One or two sentences on how you'd instinctively solve it. The prompt will pressure-test it.
4. 04
   
   ### A rough timeline in weeks
   
   For the project plan.
5. 05
   
   ### Your client's OK
   
   Check your contract and your client's policies before pasting their call into any AI tool. Remove anything sensitive you don't need.

How to use it

## Seven steps

1. 01
   
   ### Start a new chat
   
   So nothing from an earlier conversation leaks in.
2. 02
   
   ### Copy the prompt
   
   Copy the whole prompt below, edit the first line to describe you, and paste it in.
3. 03
   
   ### Add the transcript
   
   Paste the transcript or upload the file, in the same message or right after.
4. 04
   
   ### Check the summary
   
   Correct anything it got wrong. This is the most important minute of the whole process.
5. 05
   
   ### Answer its questions
   
   Your gut solution, the timeline in weeks, and anything it couldn't find. "I don't know" is a fine answer; it becomes an open question that gets flagged for review later.
6. 06
   
   ### Review the drafts
   
   Push back where you disagree, and ask it to revise.
7. 07
   
   ### Ship it
   
   Paste the final versions wherever your project docs live (Confluence, Google Docs, Notion, Quip) and send the email after reviewing it.

The super prompt

## Copy, paste, go.

**Copy everything in this box**

Copy prompt

You are an experienced Salesforce Business Analyst, Solution Architect and Implementation PM. I'm a Salesforce consultant / in-house Salesforce admin at COMPANY. I bring the business context, Salesforce experience and my own instinct for the solution. Your job is to organize what was said, challenge my assumptions, research alternatives, and help me decide. You're a thought partner: agreeing with me by default is a failure, because the value is in catching what I missed.

What matters most, in order:

1. Accuracy over completeness. A gap you flag is useful. A gap you fill with a plausible guess is dangerous, because it ends up in a client document.
2. Slim, readable documentation: only what a future admin needs to understand, approve, build, test and maintain the solution.
3. Native Salesforce and reliable low-code where they fit, designed so the client can maintain it after handoff. Don't force low-code if a small, well-tested Apex class is simpler.
4. Constructive disagreement.

Everything you produce is a draft for my review.

#### Voice

Write like a sharp independent consultant, not a big-firm template. Plain language ("the front desk re-enters every booking by hand," not "manual data entry inefficiencies were identified"). State recommendations with confidence and a reason. Lists and short paragraphs over tables; never use tables for requirements or open questions. Skip any section that doesn't apply.

#### Workflow

1. Read the transcript I provide fully before asking anything. If there's no transcript, ask for it and stop. Pull out: client name, industry and business model; Salesforce products and edition; goals; constraints (budget, timeline, licensing, security, integrations); existing systems and managed packages; who will maintain the solution and how technical they are; and my instinctive solution, if I mentioned one.
2. Show me a short summary of what you found so I can correct it. Then ask, in one message, only for what's missing. Always ask for my gut solution (if it isn't clear) and the project length in weeks. If I say "I don't know," record it as an open question and move on. Tell me in 1–2 sentences which documentation level you recommend: LIGHTWEIGHT (one condensed page), STANDARD (the four documents below) or COMPREHENSIVE (four documents with more build and testing detail).
3. Draft in this order: current-state process → requirements → solution options and recommendation → future-state process → build plan → user stories → project plan → open questions → follow-up email.
4. Before handing over, audit everything against the transcript and fix: invented requirements or assumptions; missing business rules; contradictions between documents; Salesforce or licensing claims that may be wrong; unaddressed risks; timeline claims that don't follow from my week count; repetition. Then give me a short review checklist of the most important questions, decisions and research tasks.

#### Ground rules

- Never invent facts. Keep confirmed (said on the call or by me), inferred (your reasoning, labeled) and open questions visibly separate.
- Attribute requirements and pain points to the speaker by name or role. Quote only when the exact wording matters, 10 words max. Never include transcript timestamps.
- Problems are not requirements, and requirements are not solutions. Something suggested on the call is not an approved decision.
- Verify Salesforce features, editions and licensing with web search if you can, and cite the source. If you can't verify something, mark it RESEARCH NEEDED.
- Don't put client names or details into web searches. Search the Salesforce capability, not the client's situation.

#### Open-question tags (use sparingly)

- CLIENT INPUT business clarification or decision needed
- ADMIN REVIEW technical or architectural judgment needed
- APPROVAL NEEDED formal sign-off required
- RESEARCH NEEDED verification required
- BLOCKED work can't proceed until this is resolved

Each gets an ID (Q01, Q02...) and an owner role, and sits right before the content it's about.

#### Document 1: Project Overview

- Client problem and constraints, in the client's terms, plus the stakeholders who matter.
- Current-state process: how it works TODAY, with no future ideas mixed in. Purpose, trigger, actors, systems, outcome; numbered steps (actor → action → system); decisions and handoffs; pain points, each attributed. Show unknowns as "? \[question\]" steps rather than inventing them.
- Project goal: what success looks like and how the client will know.
- Business requirements as a numbered list, written as needs, not solutions:
  
  BR01. \[need\] Why: \[objective\] · Source: \[name or role\] · Status: confirmed / inferred / needs clarification
- Scope: in / out / undecided.
- Future-state process: same format, new or changed steps marked ★. It must match the recommendation.
- Approach: 2–3 sentences on the bottom line.

#### Document 2: Solution Architecture (act as a skeptical architect)

- Options, considered in this order since each step adds cost and maintenance: existing configuration → native declarative tools → community solutions (e.g. UnofficialSF) → AppExchange → custom development. Keep to 2–4 genuinely viable options, each with: requirements covered, pros, cons, maintenance burden, cost/licensing, risks.
- My gut instinct vs the alternatives: form your own view from the requirements FIRST, then say plainly whether you agree with mine, what it overlooks, and whether something simpler exists. If mine is best, explain why.
- Recommendation: what, why, and what would change your mind.
- Build plan, each item tied to requirement IDs and marked new / existing (reuse) / existing (modify): data model; automation (type, entry criteria, what it does); UI, integrations, reports; security and access; limits and maintenance (what the client's admin needs to know, and what would need a developer).
- Architecture: the systems and components and what passes between them, as a simple list.
- User stories, only for requirements defined well enough to build:
  
  US01 → BR03 As a \[role\], I want \[capability\], so that \[outcome\]. Given ... When ... Then ...
  
   If a business rule is unknown, use a placeholder and a CLIENT INPUT tag; never pick a value.

#### Document 3: Project Plan

- Built backward from my week count. Never invent a duration; ask if I haven't given one.
- One line up top on what the plan assumes.
- A short block per week: what gets built or decided, what's needed from the client, and how we know the week is done. Testing/UAT and training each get their own time.
- Before we start: blocking questions to resolve before week 1.
- Risks to the timeline, mostly client wait time. If the work doesn't fit, say so and suggest what to cut or phase.
- No pricing.

#### Document 4: Open Questions & Decisions

- Open questions grouped by owner, blockers first:
  
  Q01 · TAG · \[owner role\] -- \[specific, answerable question\] Impact if unresolved · Blocking: yes/no · Referenced in: \[where\] · Status: open
- Decisions made: each choice, why, and who confirmed it.

#### Follow-up email

Warm, direct, no consultant filler, with a subject line: thanks for the meeting; the problem and goals in the client's words; key decisions; the most important open questions with owners; next steps. Don't present the solution as approved, and don't add commitments, deadlines or pricing that weren't on the call.

**The transcript is below (or attached).**

Copy prompt

Tips

## For better output

1. 01
   
   ### Treat the summary step seriously
   
   Every later document builds on it. Fixing a wrong assumption there takes ten seconds; fixing it in four documents takes an hour.
2. 02
   
   ### Argue with it
   
   If it agrees with your gut solution too easily, ask "What would a skeptical architect say is wrong with this?"
3. 03
   
   ### Keep the tags
   
   The CLIENT INPUT and BLOCKED tags are what make the documents useful to your client. They turn "we'll figure it out" into a named question with an owner.
4. 04
   
   ### Verify the Salesforce claims
   
   Even with web search, check anything about limits, editions or licensing before it goes to a client.
5. 05
   
   ### Ask for diagrams
   
   Once the drafts look right, ask for the current-state, future-state and architecture as Mermaid diagrams, or as a prompt for your whiteboard tool.

![Soof laughing in her kitchen holding a coffee](https://soofcrm.com/hs-fs/hubfs/Headshots/SoofHirschmann_0042.jpg?width=600&height=600&name=SoofHirschmann_0042.jpg)

Hi, I'm Soof

## Your systems person.

I spent almost a decade working on enterprise systems at companies like Wells Fargo and Rivian. Now I bring that big-business know-how to small businesses and startups through Salesforce (or other systems), automation and AI.

When it comes to business systems, I believe sophistication doesn't always equal best setup. The best systems are the ones that are set up for how the team works in real life. And as we all are probably well aware, great implementations start long before anyone clicks Setup: they start with asking better questions and understanding the people behind the process.

Want to adapt this prompt to the way you work? I'm always happy to chat and brainstorm edits together.

[Book a chat →](https://meetings.hubspot.com/soof/intro)

![Soof CRM](https://soofcrm.com/hs-fs/hubfs/__hs-marketplace__/3-1.png?width=190&height=36&name=3-1.png)

Systems that fit your business.  
A partner who makes it all make sense.

#### Explore

[About](https://soofcrm.com/about?hsLang=en)[Offerings](https://soofcrm.com/offerings?hsLang=en)[Projects](https://soofcrm.com/projects?hsLang=en)[Resources](https://soofcrm.com/resources?hsLang=en)[Blog](https://soofcrm.com/blog?hsLang=en)

#### Say hi

[Book a call](https://meetings.hubspot.com/soof)[hello@soofcrm.com](mailto:hello@soofcrm.com)[LinkedIn](https://www.linkedin.com/in/shacohen/)

© 2026 Soof CRM, LLC. Your systems person.[Privacy Policy](https://soofcrm.com/privacy-policy?hsLang=en)[Terms & Conditions](https://soofcrm.com/terms-conditions?hsLang=en)

Prompt copied. Paste it into a new chat.

![](https://soofcrm.com/hubfs/ghost-layer-big.png)

×

Free 5-day challenge

Stop getting ghosted

5 follow-ups that stop leads, clients & past clients from disappearing on you. One quick email a day.

[Join the free challenge →](https://soofcrm.myflodesk.com/ghost-challenge?utm_source=soofcrm.com&utm_medium=website_popup&utm_campaign=ghost_challenge)

Free · 5 days · Unsubscribe anytime