agentleFS
jpeslar1jpeslar1/john-peslar-ai-skills/first-meeting-30-day-sprint/SKILL.md

first-meeting-30-day-sprint

Skill12 starsChanged 5 months agoMITView on GitHub

Build a 30-day acquisition sprint toward a first qualified sales meeting using one channel, a scored 25-50-person prospect list, and a small reply-first test. Use when an automation freelancer or agency has a buyer hypothesis and needs a concrete route to conversations.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If only eight candidates can be verified, deliver eight and the search plan for the remainder.

    line 26
  2. Distinctive:

    Read references/channel-playbooks.md for the selected route.

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

First Meeting in 30 Days

Work toward one buyer-confirmed meeting about a real problem within 30 days. Combine channel choice, list quality, and the first message test. Do not interpret a completed ICP worksheet or ten research invitations as a meeting booked.

Select one route

Use the ICP, offer, access to buyers, existing audience, channel preferences, weekly hours, and prior results. If the ICP is untested, reserve the first seven days for pain/pay/reach conversations and label outreach as a hypothesis test. Prepare a provisional offer if needed. Do not wait for perfect documentation to learn from buyers.

Compare warm introductions, an existing audience plus a useful magnet, and cold-ish outreach. Recommend the route with actual access to relevant buyers. Pick one primary channel for 30 days, preserving any legitimate incoming opportunities. Do not choose LinkedIn automatically or launch three channels at once. An internal operator can use a stakeholder list and internal introductions.

Source and score 25-50 people

Research actual candidates with available tools or use the user's supplied list. For each record capture name/ID, role, company, source URL or supplied reference, observation date, pain evidence, timely trigger, tool/workflow context, authority/funding evidence, chosen contact path, and disqualifier check.

Tool usage alone is not purchase intent. Distinguish a prospect's explicit statement from your inference. Exclude hard disqualifiers before ranking. As an adjustable sorting aid, score pain, trigger, and reachability 0-2 each: 0 absent or unverified, 1 indirect/weak, 2 direct/relevant. Record authority and funding as confirmed, plausible, or unknown. A score is prioritization, not a purchase probability; direct disqualifying evidence overrides totals.

If only eight candidates can be verified, deliver eight and the search plan for the remainder. Do not fill the list with fictional people. Choose the first ten for a small test, explaining weak evidence that needs qualification.

Prepare only the selected channel

Read references/channel-playbooks.md for the selected route. Produce the actual opener and follow-up drafts, not just advice to personalize. Base each personalized assertion on a recorded source. Use bracketed fields only where required facts are missing; label such copy as a template needing completion.

For a magnet route, create the small useful asset itself (for example, a checklist or diagnostic worksheet) and the delivery plus optional call-invitation messages. A lead magnet title is not a finished asset. If delivery requires private data or unavailable tools, give a usable minimal version and name the dependency.

Schedule the experiment

  • Days 1-7: resolve ICP/offer uncertainty, select the channel, source and rank the initial list.
  • Days 8-14: test the opener with ten real matches after authorization to send; handle replies and capture buyer language.
  • Days 15-21: review fit, channel delivery, and reactions; change one weak variable and test another small cohort.
  • Days 22-30: continue useful conversations, invite qualified interested buyers, follow through on confirmations, and review the evidence.

These windows are adjustable working defaults. Start sooner if prerequisites already exist. Give realistic daily tasks and time budgets. Do not increase volume to compensate for an unverified list or an inaccessible channel.

Count the real result

A qualified booking requires a matching buyer or credible decision path, evidence of a relevant problem, and explicit agreement to a time and purpose. Track booked, held, rescheduled, and no-show separately. A calendar link sent or a vague yes does not count. A research chat counts only if the buyer also agrees to a sales-fit discussion.

Track unique people contacted, replies, positive replies, bookings, and meetings held by cohort. Separate bounces or unavailable channels from uninterested buyers. If a tiny batch is silent, inspect delivery, evidence, and the ask before declaring the ICP wrong. Missing denominator data means unknown rates, not zero.

Deliver

  • Channel decision and 30-day calendar with the first test.
  • Sourced list or honest partial list plus completion plan.
  • Channel-specific assets and reply-to-meeting script.
  • Scorecard, stop conditions, and next review date.
  • At review: actual outcome, earliest failing step, and one next experiment. Do not claim the goal succeeded without booking evidence.

Working agreement

Use context already supplied. Ask only for missing facts that change the next decision, preferably in one short batch, then make a useful first draft. Label assumptions and distinguish buyer evidence from your interpretation. Never invent interviews, prospect facts, results, testimonials, budget, or meetings. A target date is a planning goal, not a promised commercial outcome. Use plain sentences and normal hyphens in generated copy.

Create drafts and plans within the requested scope. Sending messages, booking meetings, publishing, changing a CRM, or committing the user to commercial terms requires authorization for that action. A request for advice alone does not authorize execution. Work from pasted notes if tools are unavailable; identify what remains unverified.

Source

Agent J Sales 101 curriculum-deck.pdf, pages 6-9; week1-icp-deck.pdf, pages 3-10; week2-offer-deck.pdf, page 13. The outline credits Josh Braun for 4T. Channel schedules, scoring anchors, and drafted messages here are practical adaptations, not verbatim educator scripts. These are practical adaptations by John Peslar AI, not endorsements by the referenced educators. The skill is self-contained; the original decks are not required at runtime.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.