Automation & Workflow Design prompts
Design the automations behind your outbound: blueprints, n8n workflows, Clay tables, reply agents, and the monitoring that keeps them honest.
53 prompts · paste-ready, no variables to fill · free
These prompts make you the architect of your own outbound machine. They cover the unglamorous work that separates teams who scale from teams who churn through tools: mapping manual processes into automation blueprints, designing n8n workflows and Clay tables, building AI reply agents, planning webhooks and enrichment waterfalls, and deciding what should never be automated at all.
They are written for RevOps leads, founders, and sales leaders who own the stack rather than just use it. Most prompts interview you first and then design with you, so answer with real tool names, real volumes, and real failure stories. The more honest your inputs, the more build-ready the output — several prompts produce specs you can hand straight to n8n, Clay, or an ops hire.
Build a complete 4-touch cold email sequence from scratch
Generates a launch-ready 4-touch sequence where each email plays a defined role — opener, proof, angle shift, close — with word caps, subject lines, and send delays included. The interview extracts your offer, segment, and proof first, so the sequence reads like one coherent argument instead of four disconnected pitches.
Build a system prompt for an AI cold email reply agent
Interviews you about your offer, booking flow, and voice, then generates a complete production system prompt for an AI reply agent — classification taxonomy, response rules, escalation conditions, and a strict JSON output contract an n8n or Zapier workflow can parse. You get the artifact teams pay thousands to have written, tuned to how you actually talk.
Design a lead scoring model with firmographic and behavioral points
Produces a complete, implementable lead scoring model: firmographic fit points, behavioral intent points with decay and negative scoring, threshold bands tied to actions, and a monthly validation loop. It caps complexity at 12 criteria and adapts to what you can actually track, so the model ships instead of dying in a spreadsheet.
Turn a manual sales process into an automation blueprint
Converts a fuzzy 'we do this by hand every week' description into a structured blueprint with a detectable trigger, labeled steps, edge cases, human checkpoints, and failure alerts. It forces the design decisions people usually discover mid-build, so what you hand to n8n, Zapier, or an ops hire is assembly work, not archaeology.
Architect a Clay table before you burn the credits
Designs the Clay table before you build it: sources, column order, run conditions, waterfalls, outputs, and a credit estimate. Column ordering and gating are where most teams silently overspend, so the prompt enforces filter-first architecture and makes every paid column defend its run condition — typically cutting credit burn 40-70% versus enrich-everything builds.
Audit a batch of AI first lines before the campaign sends
Catches the failure modes that only show up across a batch — recycled constructions, swap-test failures, unverifiable claims — before prospects see them. You get a grade, pattern counts, individually flagged lines, and three paste-ready fixes for the generating prompt, turning QA from a vibe check into a repeatable gate.
Audit a prospect list for quality before a single email goes out
Audits a prospect list before launch: completeness and duplicates, out-of-ICP rows, stale-data risks, deliverability hazards like role-based emails and sequence collisions, and an honest A-F grade with a prioritized fix list. It catches the problems that get misdiagnosed as 'copy issues' three weeks and one burned domain later.
Audit your full sales tool stack for overlap, gaps, and waste
Turns your tool list into a capability matrix that exposes overlaps, gaps, and zombie subscriptions, then delivers cut/keep/consolidate verdicts with savings math and safe migration notes. Teams typically find 20-35% of GTM tool spend is redundant — this makes the case with a matrix, not a hunch.
Automate the meeting-booked to CRM to onboarding handoff
Maps and automates every seam from calendar booking to onboarding kickoff: field-mapped CRM creation, automatic AE pre-meeting packages, no-show branches, same-day closed-won handoffs, and scheduled orphan checks at every stage. The leak-detection layer is the differentiator — handoffs fail silently, and this design makes silence detectable.
Build a complete AI reply-agent system prompt for your cold email inbox
Builds the production artifact most teams get wrong: the full system prompt powering an AI agent that answers your cold email replies. The interview extracts your real voice from actual sent emails, defines per-category playbooks, and hard-codes the guardrails — no invented pricing, no replies to hostility, explicit escalation JSON — so the agent is safe enough to actually deploy, not just demo.
Build a deduplication strategy across all your data sources
Designs end-to-end deduplication: a confidence-ordered match key ladder, implementable normalization rules, per-field merge precedence that never destroys activity history, entry-path blocking so duplicates stop at the door, a right-sized review queue, and merge logging for undo. It handles both failure modes — duplicates and bad merges — instead of trading one for the other.
Build a deliverability monitoring workflow you actually run
Turns deliverability from vibes into a maintenance schedule: time-budgeted daily, weekly, and monthly checks with the mechanics specified, numeric if-then decision rules a non-expert can execute, a trend log, and a clear split between what n8n automates and what needs human eyes. Designed to still be running in month six.
Build an AI SDR tool evaluation checklist before the demo
Generates a two-page, weighted evaluation kit for AI SDR platforms: a scorecard tuned to your situation, demo questions engineered to puncture vendor claims, instant disqualifiers, a 30-day pilot design with pre-agreed metrics, and a true total-cost view. It replaces demo-driven gut feel with an evidence process.
Build an engage-then-DM warmup plan for a target account list
Builds a systematic pre-DM warmup operation for a target account list: tiering criteria, a 10–14 day engagement ladder per priority prospect, the warm-signal triggers that greenlight the DM, and a weekly rhythm sized to your actual capacity. Familiarity before outreach is the highest-leverage move in social selling, and this makes it operational instead of vibes.
Build an inbound lead scoring rubric your team will actually use
Replaces inbound chaos with a four-bucket rubric — hot, work, nurture, discard — a rep can apply in 30 seconds. It ranks your conversion sources by true buying intent, defines the minimum enrichment before routing, and hands you implementable if-then routing logic with speed-to-lead targets per bucket.
Build an inbound speed-to-lead automation that responds in minutes
Designs the full submit-to-human pipeline with a time budget at every step: instant enrichment and qualification, honest two-minute auto-response (drafted for you), hot-lane routing, an escalation ladder for slow reps, an after-hours play, and 90th-percentile measurement. Built to attack the hours of dwell time that quietly kill inbound conversion.
Build an outbound experiment backlog with ICE prioritization
Converts a fog of 'we should try...' ideas into a force-ranked ICE-scored backlog with testable hypotheses, kill thresholds, and a WIP limit matched to your team's real capacity. It also seeds proven experiment patterns you haven't considered and installs the log that stops your team from relitigating dead ideas every quarter.
Calculate the real ROI of an automation before you build it
Prices an automation honestly before you commit: manual cost including error and delay drag, build plus run plus maintenance cost, payback period with visible arithmetic, sensitivity analysis, and a one-sentence verdict. It kills both vanity automations and false 'too busy to automate' economics with the same math.
Choose which personalization signals are worth your credits
Turns signal selection from guesswork into portfolio math: which 3–5 signals fit your ICP, offer, and budget, in what waterfall order, with what fallbacks — plus an explicit skip list and a 200-row test plan. It's the planning session that should precede every prompt-heavy Clay build, done in twenty minutes.
Classify an account into one of your defined segments
Assigns every row in your table to exactly one of your named segments, with confidence and a short evidence trail. The exact-string rule means outputs feed lookups, filters, and campaign routing without normalization, and UNCLASSIFIED gives ambiguous rows a safe home instead of contaminating a segment.
Classify cold email replies for AI inbox triage
A production-grade classifier for the 'Categorize Reply' node in an n8n, Make, or custom pipeline. Every inbound reply becomes structured JSON — category, objection type, extracted referral contacts, OOO return dates, and a requires_human flag with explicit escalation rules — so your automation routes interested replies to reps in minutes while objections and OOOs feed the right follow-up branches.
Clean up company names for email merge fields
Converts raw vendor and CRM company names into the natural short form that reads like a human typed it — no 'LLC', no ALL CAPS, no taglines — so 'quick question about {company}' merges cleanly. One of the highest ROI-per-token prompts in outbound: every recipient sees this field.
Decide build vs buy for outbound: in-house SDRs or a partner
Puts real numbers on the decision founders usually make on vibes: a fully-loaded 12-month cost model comparing in-house SDRs, an outbound partner, and hybrid — including management time, ramp, and turnover that salary-only comparisons hide — plus a fit assessment, per-path failure modes, and the due-diligence questions that expose meeting mills.
Decide which enrichment result wins in a waterfall
Resolves provider disagreements in your enrichment waterfall with explicit arbitration logic: verification over popularity, recency over rank, and a hard ban on blended values. Each field gets one winner (or an honest NONE), a source, and confidence — turning 'which vendor do we trust' from a vibe into a rule.
Decide which tool should own any job in your outbound stack
Turns 'which tool should I use for X' from a Reddit-thread lottery into a structured decision: restates the real job, checks your existing stack first, gives one primary pick with a budget alternative and upgrade path, and tells you when doing it manually is the honest answer. Anti-shopping bias built in.
Defuse angry and unsubscribe replies with an exit that protects your domain
Produces the two-sentence exit that keeps an angry prospect from escalating to a spam complaint — the deliverability event that actually damages your sending domain. Past-tense removal confirmation, zero defensiveness, zero selling. Includes the full suppression checklist and CRM note so the contact never resurfaces in anyone's sequence, plus a legal-language flag when replies mention GDPR or CCPA.
Design QA guardrails for AI-generated outreach before it sends
Builds a pre-send QA layer for AI outreach: automated factual, personalization, format, and compliance checks with detection logic written out, a volume-appropriate human sampling plan, a severity ladder, an automatic kill switch, and a weekly feedback loop that turns caught failures into permanent prompt fixes.
Design a prompt chain for a multi-step research pipeline
Designs a production research pipeline as a chain of single-job prompts with strict JSON contracts, validation gates, model-tier assignments, and cost math — then writes every step prompt for unattended execution. It converts the flaky mega-prompt most teams start with into a debuggable assembly line where failures surface at gates instead of polluting output.
Design a scraping pipeline with compliance guardrails built in
Designs a scraping pipeline that survives contact with reality and review: API-first source plans, rate-limit politeness, source-specific compliance flags with GDPR minimization and retention rules, validation and quarantine before data reaches campaigns, breakage monitoring, and explicit kill criteria. It treats compliance as architecture, not a disclaimer paragraph.
Design a trial-to-paid conversion plan for a prospect
Turns a hope-based trial into a designed conversion path: pre-agreed success criteria, an engineered first-value moment in the opening days, value-add touchpoints tied to trial days, a mid-trial readout with honest bad-usage branches, and a conversion conversation booked before day one. Built to fix wherever your trials currently die.
Design alerting for your outbound infrastructure before it burns
Designs a complete monitoring layer for sending infrastructure: a per-domain metric catalog, volume-tuned warning and critical thresholds, check cadences with the tool that runs each, anti-fatigue alert routing, runbooks for the five likeliest incidents, and a weekly drift digest. Problems surface in hours instead of after a burned domain.
Design an A/B test automation for your outbound campaigns
Builds an outbound testing system honest about statistical power: a testability check that kills underpowered tests before they waste weeks, single-variable test templates with minimum samples and stopping rules, sequencer-level automation mechanics, and a learning log so wins compound. Its distinguishing feature is telling you what not to test at your volume.
Design an enrichment waterfall that stops wasting spend
Builds provider waterfalls per field — email, phone, firmographics — ordered for your specific ICP rather than someone else's template, with validation, stop conditions, and a shown-math cost model. It converts enrichment from a flat subscription habit into an engineered pipeline where every provider position is justified by coverage and price.
Design an n8n workflow for any sales process
Produces a node-by-node n8n build plan with trigger choice, data shapes between nodes, error workflows, edge cases, and a five-record test plan. It replaces the usual approach — dragging nodes until something works — with a design you can build in one sitting and debug six months later without the original builder.
Design lead routing logic that never drops a lead
Produces a complete routing spec: an explicit decision tree, tiebreakers, SLA clocks with breach behavior, implementation notes for your CRM, and guards against the three classic silent failures. It turns 'we sort of round-robin' into logic precise enough to build in an afternoon and audit in a quarter.
Design the data schema for your outbound operation
Produces a complete data architecture for outbound: entity model, typed field dictionary with source-of-truth per field, stable cross-tool keys, legal lifecycle transitions, system write permissions, and a check that the schema answers your actual reporting questions. It's the difference between owning your data and renting fragments of it from five tools.
Generate A/B test variants of your best cold email
Turns your control email into a disciplined test plan: a diagnosis of its current mechanics, four variants that each isolate one variable — angle, proof, CTA, or opener — and a ranked prediction of which to test first. It also checks whether your send volume can even power a meaningful result.
Generate a note-taking template for your sales motion
Designs a discovery note template where every field has a downstream customer — the follow-up email, demo build, forecast, or handoff — plus a during-call versus after-call split, one-keystroke red-flag codes, and both plain-text and markdown formats. Kills both blank-page notes and the 40-field CRM form nobody fills.
Generate realistic story data for your demo environment
Generates a coherent demo dataset — realistic records in your prospect's industry language, deliberately planted records that make each demo beat land, background texture so the plants don't stand alone, and living timestamps. Replaces 'Test Company 123' with set design that lets prospects see themselves in the product.
Map what NOT to automate in your sales process
Scores every step of your process on judgment, relationship stakes, and blast radius, then sorts it into automate, hybrid, and human-always lists with mechanical tripwires that yank records out of automation when context changes. It answers the question most automation content skips: where automation should end — without letting sentiment keep everything manual.
Mine out-of-office replies for triggers, referrals, and timing intel
Turns the replies your sequencer ignores into send-timing data, new contacts, and account intel. Each OOO gets a structured extraction: return date with a smart re-send date, named colleagues assessed against your ICP, organizational signals, and the exact next plays — including how to reference a colleague without sounding like you're surveilling the inbox.
Normalize messy job titles into seniority and function
Turns the chaos of raw titles — emojis, slashes, vanity titles, abbreviations — into two controlled-vocabulary fields plus a decision-maker flag. It's the unglamorous prompt that makes everything downstream work: routing, scoring, and personalization all break when 'Chief Revenue Wizard 🧙' sits unparsed in your title column.
Optimize the timing and cadence of your follow-up sequence
Diagnoses where your sequence timing crowds, gaps, or quits too early, then rebuilds the cadence with day offsets, day-of-week guidance, and reasoning per touch. It refuses to invent statistics — where your data is thin, it designs the cadence test instead, so changes rest on your numbers, not folklore.
Plan the webhooks and integrations between your stack tools
Produces a full integration architecture for your GTM stack: connection map, webhook event catalog, a source-of-truth table per field, idempotency and retry rules, failure detection, and a dependency-aware build order. It prevents the classic outcome — five tools, six versions of the truth — by settling ownership before anything gets wired.
Run a yes/no ICP match classifier on any account
Puts a strict tri-state gate (YES / NO / UNKNOWN) at the front of your pipeline: accounts fully matching your written ICP proceed, confirmed misfits exit with the failed criterion named, and thin-data rows queue for enrichment instead of being silently misjudged. The named-criteria output makes every rejection auditable.
Score a scraped snippet's relevance before it reaches copy
Adds a QA gate between scraping and writing: every snippet gets a 1–5 usability score, the single best fact extracted, and a reason. Gating your first-line prompt on score 4+ is the difference between personalization built on real research and confident emails built on cookie banners.
Scrub spam trigger words without killing your message
Audits your cold email for deliverability risk across five categories — trigger words, salesy patterns, formatting, links, and HTML — then rewrites it clean without flattening your message into corporate mush. The residual-risk note tells you when the problem is your infrastructure, not your copy.
Spec a CRM hygiene automation that keeps itself clean
Generates a maintenance-grade CRM hygiene spec: field standards, entry gates, scheduled sweeps with explicit detection logic, flag-queue ownership, and KPIs. Unlike a one-off cleanup checklist, it designs the system that prevents re-accumulation — the difference between mopping the floor and fixing the leak.
Translate your ICP into Apollo, Clay, and Sales Nav filters
Closes the gap between your ICP document and an actual list: exact Apollo and Sales Navigator filter builds with title variants and exclusions, plus a Clay enrichment layer for the criteria native filters can't capture. The spot-check protocol catches list contamination before it burns your reply rates and domain reputation.
Turn a call transcript into structured CRM notes
Converts a rambling transcript into a sub-250-word CRM note structured around what deals actually run on: ranked pains with owners and costs, stakeholder map, timeline triggers, agreed next step, and open questions. Consistent enough that anyone on the team can pick up the deal cold — and consistent enough to automate.
Write a build spec a VA or ops hire can execute without you
Interviews you about a workflow, then writes a delegation-grade build spec: precise field-level flow steps, complete if-then decision rules, edge-case behavior, contractual acceptance tests, secure credential handling, and handover requirements. It eliminates the guess-filling that makes delegated builds technically work while doing the wrong thing.
Write a cold email from a prospect's tech stack
Converts raw technographic data into ranked implications about how the prospect operates, then writes a sub-85-word email that leads with the implied friction instead of reciting their tool list. It draws the line between insight and surveillance, and tells you when your stack data is too generic to use.
Write personalized first lines for an entire prospect list
Processes a pasted prospect list and returns a spreadsheet-ready table of first lines, each under 22 words and built from that row's data. Weak rows get flagged instead of padded with filler, so you know exactly which prospects need more research before they enter your sequence.
Frequently asked questions
It can design them to build-ready detail if you force structure. These prompts require explicit triggers, node-by-node plans, error handling, and human checkpoints — the parts most people skip and then pay for later. The AI won't click the buttons in n8n or Clay for you, but it will hand you a spec precise enough that the build becomes assembly rather than invention.
More prompt categories
Want this running on autopilot instead?
We wire prompts like these into a full outbound system — data, personalization, sending, and replies orchestrated end to end. You own the infrastructure. We guarantee the results.
Apply for a Pilot Spot →