First Client in 90 Days

Turn the user's skills, access to buyers, and available hours into a path toward a first paid engagement. Start with the earliest unproven sales step and produce the asset needed to test it today. Do not make a beginner finish a course before talking to buyers.

Establish the starting point

Find the lane (freelancer, agency, or internal operator), start date, weekly sales hours, delivery capability, existing buyer access, proof, current opportunities, and desired engagement. Separate the seller's lane from the buyer's role. Default to a first paid pilot with a bounded scope when a recurring service is unproven. Use a retainer only when ongoing work creates ongoing value.

Define success before planning: for an external sale, signed scope plus the agreed first payment actually received; record contract and payment evidence separately. For an operator, named sponsor approval, resources, success metric, and a pilot start date. A friendly reply, scheduled call, verbal yes, proposal, or unpaid demo is an intermediate event.

Build an evidence-gated calendar

Use these overlapping windows as a starting schedule. Adjust for the user's capacity and existing evidence; never restart validated work just to follow the calendar.

Prepare discovery and a price as soon as a buyer is ready, even in week one. If no meeting is booked by day 30, diagnose the earliest failing step instead of pretending to enter a closing phase. If no client is won by day 90, report the actual outcome and the evidence-based next experiment.

Choose the next skill only if available and useful

All steps can be completed here using the table above. Within this collection, recommend icp-validation-sprint, first-client-offer-builder, or first-meeting-30-day-sprint for deeper early-stage work. Later use sales-discovery-call-coach, automation-pricing-and-close, sales-follow-up-planner, and sales-objection-sorter. Use weekly-sales-loop for execution and sales-pipeline-clinic for diagnosis. Do not require installation of other skills or run all of them for a narrow question.

Make workload and funnel math honest

Budget time for list research, conversation preparation, outreach, replies, calls, and delivery. Reserve same-day reply handling before filling every hour with sends. If illustrative conversion rates help, label them as scenarios, show the assumptions, and replace them with observed cohort rates. Do not backsolve a quota from made-up industry benchmarks or multiply total message touches as though they were unique prospects.

Track sourced prospects, unique people contacted, replies, positive replies, meetings booked, meetings held, qualified opportunities, proposals, signed agreements, and first payments. Each stage needs a definition and actual evidence. Never count an unanswered invitation as a booking.

Deliver

1. Goal, start date, constraints, and current bottleneck.
2. A dated plan with weekly tasks, realistic time budgets, artifacts, and decision gates.
3. The next usable asset: an ICP sentence, research invitation, offer paragraph, or deal next-step script.
4. A simple scorecard with current actuals, explicit unknowns, and next review date.
5. A seven-day experiment with a continue/change/stop rule and today's first action.

At a progress review, compare actuals to the previous plan, retain learning, and change the smallest relevant variable. Avoid replacing an entire niche and offer because one small batch received no replies.

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 2-15; week1-icp-deck.pdf, pages 3-10; week2-offer-deck.pdf, pages 4-12. The 90-day schedule and stage gates below are this skill's implementation of the curriculum, not a timeline promised by the decks. 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.