Turn a meeting transcript into decisions, owners and dates
Converts a raw transcript into the three things anyone actually needs afterwards: what was decided, who owns it, and by when.
Free tools
Free, copy-and-paste AI prompts for sales, marketing, operations, finance, HR, support and leadership teams. Each one explains what to change to make it yours.
25 prompts. Free to copy, no signup.
Unlock all 50. Add your email to open these too, and get the whole library as a PDF.All 50 unlocked. Download all 50 as a PDF.
Every prompt, Starter and Advanced. Each one explains what to change to make it yours.
Converts a raw transcript into the three things anyone actually needs afterwards: what was decided, who owns it, and by when.
Writes a short outreach email grounded in one specific, verifiable thing about the company, and refuses to write it if you have not supplied one.
Writes the follow-up from what the prospect actually said, in their words, and flags anything you failed to ask.
Separates the objection someone said from the concern underneath it, then drafts a response to the concern.
Extracts the fields you name from a batch of invoices and flags what it could not read instead of guessing.
Pulls the distinct ideas out of an article and gives each one its own post, instead of five paraphrases of the headline.
Extracts renewal dates, notice periods, price escalators and exit terms, quoting the clause for each so you can check it.
Attacks your positioning the way a competitor would, then tells you which parts survive.
Fills the CRM fields you actually use from a call recording, and leaves a field blank rather than guessing at it.
Reads your page as a sceptical buyer with limited time and reports where they would stop reading and why.
Uses what the referrer actually said, so the opening line earns the reply instead of spending the introduction on yourself.
Converts a recorded walkthrough into a numbered procedure, and lists the steps the expert skipped because they know them by heart.
Scores an enquiry against the criteria you define, tells you what is missing, and drafts the one question that would settle it.
Turns scattered notes, messages and commits into a status report that distinguishes progress from activity.
Rewrites copy for a named audience and shows you what it cut, so you can tell whether it lost meaning or only lost padding.
Turns budget-versus-actual lines into explanations a non-finance reader can act on, and separates what you know from what you are inferring.
Tightens what a customer actually said without putting words in their mouth, and marks anything you must check before publishing.
Separates what the customer has actually said from what your team is hoping, then names the one thing to test this week.
Produces subject lines that say what is inside, plus a note on which ones overpromise, so the open does not cost you the trust.
Reads a year of account history for the signals that precede a cancellation, and separates them from ordinary noise.
Reads a sprawling thread and states what was decided, what is still open, and who is waiting on whom.
Turns an interview into a case study built on what the client said, with every claim traceable and every gap listed rather than filled.
Turns your responsibilities into a note someone else can act on, and flags the things only you currently know.
Builds a timeline from the record, separates the trigger from the conditions that let it matter, and proposes fixes at the right level.
Expands a list of steps into a procedure with the judgement written down, and asks about the steps that are ambiguous.
Puts two differently structured proposals onto one comparable footing and names what neither of them tells you.
Explains what a number is and what moves it, in the reader's language, without dropping the accuracy that makes it useful.
Finds the assumptions a forecast rests on, tests which ones it cannot survive being wrong about, and says what to watch weekly.
Writes the chase at the right firmness for how overdue it is and who the customer is, and states the next step plainly.
Checks a batch of claims against the policy you paste in, quotes the clause for every exception, and separates breaches from gaps in the policy.
Turns a hiring manager's rough brief into a job description that says what the work is, not a list of adjectives.
Turns a role into a short scorecard with defined criteria and evidence levels, so interviewers score the same things instead of their impressions.
Produces questions that make a candidate show a skill rather than claim it, with what a strong and a weak answer sound like.
Builds a review from the year's actual record, separates what happened from how it felt, and flags where the evidence is too thin to judge.
Builds a day-by-day plan with a real first task, named people to meet and a check at the end, instead of a folder of documents.
Collates every interviewer's notes against the scorecard, shows where they agree and conflict, and names what is still unknown before anyone decides.
Writes reference questions aimed at the specific concerns from your interviews, so the call confirms or settles them instead of collecting praise.
Sorts a batch of tickets by what they actually need, groups the duplicates, and pulls out anything urgent that is hiding in the queue.
Drafts a reply that acknowledges the real problem, says exactly what happens next, and promises nothing you cannot deliver.
Reads a period of complaints for the causes underneath them, separates one-offs from systemic problems, and sizes each one honestly.
Converts a support thread that ended in a fix into a help article written for the next customer, not for the agent who solved it.
Turns a messy customer thread into an escalation an engineer can act on: steps to reproduce, impact, and what is known versus assumed.
Builds a reusable reply for a question you answer every day, with clearly marked places to personalise so it never goes out generic.
Scores a sample of replies against your own standards, quotes the evidence, and separates coaching points from problems in the process.
Turns the month's numbers and notes into an update that opens with the headline, including the bad news, and ends with what you need from the board.
Lays out a decision as genuine options with their costs and risks, names the recommendation, and states what would change your mind.
Turns your notes on someone into a short plan for the conversation: what to ask, what to raise, and what to leave them to bring.
Imagines the plan has failed, works out the most likely reasons why, and turns the credible ones into things to check or change now.
Writes the message explaining a decision: what was decided, why, what it means for the people reading it, and what is not changing.
Forces a long wish list into three to five priorities, says plainly what is being dropped, and tests whether the result fits your actual capacity.
New prompts as they go up, plus founder essays on shipping AI systems. ~2 emails / month.
Want this built into how your team actually works? See what we do.