Discovery prep pack
Arrive at a discovery call with the stakeholders mapped, the questions already answered, and the gaps worth spending the limited time on.
One hour before a discovery call, read the account notes and past call summaries, then post four questions worth asking.
The job, and what good looks like.
Reps walk into discovery asking the buyer to explain their own company back to them, because the account history lives in three emails and one call note from a colleague. The pack exists so the call does not start from zero. This workflow assembles it the day before the meeting. It pulls the last several calls and emails, the stakeholders named in each, and the questions already asked and answered, then scores the transcript for the questions that came up and were never followed through. The pack opens with who is in the buying group, who has actually spoken, and what they care about in their own words, so the rep is not quoting a third-hand summary. It ends with the gaps: the unasked question, the person nobody has met, the objection that appeared once and was never resolved. Anything sitting in another rep's territory is marked before the call rather than after it. A human still decides which questions are worth the time available, and what the rep is actually trying to learn. The pack shortens the preamble so the call can be spent on what the account has not said yet.
When it is handled
- Every call starts with a written pack
- No question asked twice
- Stakeholder map current before the call
- Gaps named before they waste the call
Works with tools like
- Gong
- Fireflies.ai
- Attention
- Salesforce
Ready-made automations. Pick the one that fits.
Each one is a plain-language document. Run it as it is, or change the timing, the rules and the tools to match your team.
You stay in charge.
At every step.
It does the legwork. You decide what reaches a customer.
- Nothing reaches a customer unasked
Replies and follow-ups wait in your drafts until you send them, or until you pre-approve them.
- Undo what you don't want
Every step is recorded, and a file it changed can be put back.
- Only the CRM and inbox you allow
Each automation reaches only the apps and folders you connect for it.
Prep question draft
Approve before it posts in Slack?
Before you download.
- Where does it run?
- On your Mac or Windows computer, in the background. It keeps working after you close its window, and only reaches the folders and apps you connect for each automation.
- How does it connect to our CRM and other tools?
- Through each app's own connection where it offers one, signed in once by you, or by using the app in a browser the way you would. Each automation gets only the connections you give it, and the tools a page names are examples you can swap for your own.
- Does it run when my computer is asleep?
- It keeps your computer awake while a job runs and just before a scheduled one. While the computer is closed or off, nothing runs; when it wakes, it checks the inbox, calendar and other sources it watches for anything that arrived meanwhile.
- How does my team use it?
- Each person who runs automations installs the app. Keep a project in a shared folder, such as Google Drive or a network drive, and teammates can open it and follow every run, while one person owns it and runs it.
- Do I need anyone technical to set it up?
- No. Download the app, add an automation in plain words, and connect only what that job needs. Nothing runs until you switch it on.
Already have tools for this? Here is the difference.
Your CRM's workflow rules
Updating fields and assigning records the same way every time.
They can't read a call, research a company or write a follow-up that sounds like you.
Flowchart automation tools
Moving data between apps at high volume.
Every exception becomes another branch someone has to build and maintain.
AI chat assistants
Drafting a reply when you ask for one.
Nothing happens until you come back and ask again, and the routine lives in a chat.
AUTOMATE.md
Your routine, written in plain words. It runs on its own, follows your rules, handles the exceptions a flowchart can't, and asks you when it matters. The file stays yours, whichever AI model runs it.
Related workflows.
Account research briefs
Keep a one-page brief per target account: the people who matter, what changed there recently, and the reason to reach out this week.
7 automations
Opportunity recap notes
Write the deal record back from the call itself: the pain, the people, the decisions, and the next step with an owner and a date.
5 automations
Start with one job.
Make it your own.
macOS — coming soon- 1
Get the app
It runs on your computer, next to your files.
- 2
Add the automation
Paste the instructions into the app, or save them as a file next to your work.
- 3
Try it, then turn it on
Run it once and check the result. It only runs on its own once you switch it on.