Deal Qualification Scoring
Use a discovery call to score the deal against your ICP—and show the evidence behind the score.
The Fortune 100 AI Prompt Library™
Pick something you already do. Copy the instructions into Claude or ChatGPT, add your notes or documents, and check the result. Start with one task and build from there.
The name refers to the Fortune 100 company list. You'll find 100 workflows here, including templates we've created at Technical Leaders.
Try it with meeting notes
From notes to clear next steps
Your task
Turn meeting notes into a plan your team can follow.
Try this workflow
Meeting Decisions & Action Items
Add your transcript or notes. Get a draft of the decisions, who's doing what, and when it's due.
Before you share it
Check the decisions, owners, and dates against your notes. Confirm anything the meeting left open.
Each workflow tells you what to bring, what to copy, and what to check.
Try one task today
Pick a task below and open the workflow. It'll show you what to bring and what to paste into Claude or ChatGPT. Use your own notes or documents, then check the draft before you use it.
Find a task for your team
Search for something on your to-do list, or choose a category. Each workflow includes the notes or files you'll need, instructions to copy, a sample prompt, and checks for the result.
Showing 100 of 100 workflows
Search by task, team, or the notes and files you have. Choose a category to narrow the results.
Level 1 · Everyday workflows
Start with a task you know well. Bring the notes or files it needs and decide what a useful result should include.
Use a discovery call to score the deal against your ICP—and show the evidence behind the score.
Prepare questions that test a prospect's needs, decision process, and fit before the first call.
Build evidence-backed responses and practice follow-up questions for recurring sales objections.
Turn an agreed buying process into a draft plan of milestones, owners, and dependencies.
Prepare a sales review that highlights stale opportunities, missing evidence, and actions for deal owners.
Give the delivery team a clear record of the customer's goals, sold scope, and unresolved promises.
Turn a marketing request into a brief with a clear audience, offer, message, and success measure.
Plan a realistic publishing calendar around audience questions and the team's available capacity.
Draft a landing page that connects an audience need to a supported offer and one clear next step.
Find recurring customer needs and useful language without treating a few interviews as market-wide proof.
Draft a sequence that helps interested prospects understand the offer and choose a sensible next step.
Turn a marketing idea into a measurable test with a clear hypothesis and decision rule.
Prepare a timed webinar plan with speaker cues, audience activities, and technical contingencies.
Locate delays in a process and propose small improvements supported by the available evidence.
Sort reported quality issues into evidence, impact, immediate containment, and investigation questions.
Compare committed work with available team hours and make overload visible before deadlines slip.
Turn approved process documents into an internal FAQ with source links and clear ownership.
Build a practice scenario that tests a team's documented response to an operational disruption.
Define team metrics consistently so reports use the same formulas, sources, and exclusions.
Organize a spending request into costs, assumptions, alternatives, and questions for the budget owner.
Explain supplied cash-flow scenarios and identify which assumptions create the largest timing risks.
Compare invoices with purchase orders and receipt records to prepare exceptions for accounts payable.
Prepare a renewal decision using contract terms, actual usage, and the owner's business needs.
Compare two policy versions and prepare a source-linked change summary for the policy owner.
Organize a business request so counsel receives the facts, documents, deadline, and decision needed.
Turn a product request into a problem statement, bounded scope, and testable acceptance criteria.
Compare feature requests using a consistent rubric while exposing weak evidence and uncertain estimates.
Prepare neutral interview questions that reveal how users currently complete a task.
Turn scattered issue reports into a clear reproduction brief with expected behavior and missing evidence.
Assemble release evidence and unresolved blockers so the accountable owner can make a go/no-go decision.
Document a technical decision with its constraints, alternatives, tradeoffs, and revisit conditions.
Turn rough notes into an email with the right context, a clear request, and a useful next step.
Shape a presentation around the decision leaders need to make and the evidence they need to assess it.
Adapt one approved message for different audiences while preserving its facts and commitments.
Compare options in a concise memo with evidence, tradeoffs, and a clearly stated decision request.
Build a leadership agenda that gives decisions and unresolved cross-team issues enough discussion time.
Turn a supplied task list into a feasible week with explicit priorities, deferrals, and capacity limits.
Expose handoffs between teams and clarify which missing decisions are blocking a shared objective.
Give a designer a clear brief with audience, content, approved assets, and acceptance criteria.
Inventory brand files and identify obsolete, duplicate, or unapproved assets before a team reuses them.
Turn scattered design comments into a clear revision brief with conflicts and priorities exposed.
Draft a helpful customer reply grounded in the case facts and approved service policy.
Prepare an escalation that gives the next team the impact, history, evidence, and decision needed.
Find recurring support needs and recommend focused improvements using a dated ticket sample.
Turn verified troubleshooting steps into an article customers can follow and support can maintain.
Build a customer onboarding plan around the promised outcome, milestones, and actual readiness.
Prepare an account review that separates observed adoption, customer feedback, and uncertain risk signals.
Compare approved ways to address a service failure and prepare a fair response for review.
Prepare a customer review that compares agreed goals with documented outcomes and next priorities.
Draft a role description grounded in the work to be done and clearly separated essential requirements.
Prepare consistent, job-related interview questions and an evidence rubric for human interviewers.
Build an onboarding plan with role-specific practice, access prerequisites, and manager check-ins.
Prepare a useful one-on-one around the employee's priorities, obstacles, and support needs.
Turn team preferences into a proposed agreement about communication, decisions, and handoffs.
Summarize anonymized employee feedback while preserving confidentiality and contradictory views.
Write specific appreciation that connects a documented contribution to its effect on the team.
Make shared responsibilities, decision rights, and unowned work visible for the team to resolve.
Identify which work problems training can address and which need process, tools, or clearer expectations.
Build a practical lesson around one outcome, a worked example, and a learner activity.
Write scenario questions that check whether learners can apply the lesson, with clear answer explanations.
Prepare a facilitator to run a workshop with clear cues, practice time, and recovery options.
Turn a completed workshop into a short practice plan with manager support and observable work outcomes.
Prepare a source-linked review of learning materials and flag accessibility checks that need direct testing.
Define a project's objective, scope, success criteria, and decision rights before work begins.
Turn progress notes into a status update with evidence, blockers, decisions, and next milestones.
Organize potential project risks with evidence, triggers, responses, and accountable owners.
Show how a requested change affects deliverables, effort, cost, dependencies, and timing.
Compare project outcomes with the original charter and turn supported lessons into actionable improvements.
Define purchasing requirements and acceptance criteria before requesting supplier proposals.
Put supplier quotes on comparable terms and expose omitted costs or mismatched scope.
Prepare a risk-based checklist of supplier evidence and the specialists who must review it.
Compare supplier delivery with agreed service measures and prepare evidence for a review conversation.
Turn discovery notes into a proposal with the right proof, pricing, and next step for that prospect.
Keep competitive intel current and give reps responses that fit the objection in front of them.
Find the patterns behind wins and losses across CRM notes, call transcripts, and deal data.
Turn one strong piece of long-form content into useful, channel-ready formats.
Turn a process walkthrough into an SOP your team can find, follow, and keep current.
Turn a meeting transcript into clear decisions, owners, and deadlines.
Pull the terms that matter from NDAs and MSAs into one consistent tracker.
Look across retrospectives to find recurring issues, not just the problem from the last sprint.
Walk into the call with the company news, contact context, and talking points that actually matter.
See why a campaign is underperforming, then get a short list of fixes worth testing.
Check every draft against your brand rules before it goes out.
Track how competitors are moving and find the position they aren't claiming.
Write personal follow-up that reflects what actually happened at the event.
Compare vendors against the same criteria, with evidence behind every score.
Explain a change at the right level of detail for each audience without losing the core message.
Turn financial variances into a plain-English explanation a board can act on.
Check expense submissions against policy and explain every exception it flags.
Make the assumptions in a financial model explicit, testable, and easier to challenge.
Pull the right ledger and policy support together before the auditor asks twice.
Compare a contract with your playbook, suggest edits, and include a fallback position.
Check a document against specific requirements and cite the provision behind each finding.
Give legal a structured view of the facts, risks, and open questions behind a business decision.
Turn a pile of tickets and reviews into the product themes customers are actually asking for.
Turn code comments and architecture decisions into documentation the rest of the team can follow.
Turn commits and tickets into release notes customers can understand.
Level 2 · Advanced & automation
Ready to go further? Connect your tools and reuse the instructions for work with more steps. Keep a person responsible for checking the result.
Study one week of messages you wrote, then build a reusable skill that changes your voice by channel, relationship, and audience seniority.
Turn email, Slack, ClickUp, and your calendar into an hourly, linked priority brief organized as Do, Delegate, or Discuss.
Turn approved brand materials and strong examples into a reusable visual-design skill for websites, slides, documents, and social graphics.