first-client-offer-builder
Skill12 starsChanged 4 months agoMITView on GitHub
Package a first automation service, retainer, or internal pilot into one evidence-based offer paragraph with a Value Equation review, delivery stack, bounded risk reversal, and three-buyer test. Use after choosing a buyer and before writing acquisition copy.
In this repository110 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- 30mpc-voiceSkill
- adam-robinson-voiceSkill
- ai-workflow-architectSkill
- alex-costa-grooming-advisorSkill
- alex-garcia-voiceSkill
- alex-hormozi-voiceSkill
- amanda-natividad-voiceSkill
- andrew-gazdecki-voiceSkill
- andrew-wilkinson-voiceSkill
- ann-handley-voiceSkill
- april-dunford-voiceSkill
- automation-pricing-and-closeSkill
- balaji-srinivasan-voiceSkill
- barbara-corcoran-voiceSkill
- bob-hoffman-voiceSkill
- byron-sharp-voiceSkill
- chamath-strategy-coachSkill
- chris-orlob-voiceSkill
- chris-walker-voiceSkill
- claude-code-build-auditorSkill
- claude-hopkins-voiceSkill
- codie-sanchez-voiceSkill
- daniel-priestley-voiceSkill
- dan-kennedy-voiceSkill
- dan-koe-voiceSkill
- dave-gerhardt-voiceSkill
- david-ogilvy-voiceSkill
- david-perell-voiceSkill
- dhh-voiceSkill
- first-client-90-day-planSkill
- first-meeting-30-day-sprintSkill
- fletch-pmm-voiceSkill
- founder-content-engineSkill
- gary-bencivenga-voiceSkill
- gary-halbert-voiceSkill
- gary-vaynerchuk-voiceSkill
- george-mack-voiceSkill
- grant-cardone-voiceSkill
- greg-isenberg-voiceSkill
- guillaume-moubeche-voiceSkill
- harry-dry-voiceSkill
- hormozi-hooksSkill
- hormozi-pitchSkill
- hundred-million-offersSkill
- icp-validation-sprintSkill
- jack-butcher-voiceSkill
- jasmin-alic-voiceSkill
- jason-fried-voiceSkill
- jay-clouse-voiceSkill
- jen-allen-knuth-voiceSkill
- jesse-itzler-voiceSkill
- john-carlton-voiceSkill
- josh-braun-voiceSkill
- julian-shapiro-voiceSkill
- justin-welsh-voiceSkill
- katelyn-bourgoin-voiceSkill
- kellen-copy-coachSkill
- kevin-dorsey-voiceSkill
- kevin-oleary-voiceSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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
- Distinctive: line 12
Create one offer a real buyer can repeat and the seller can deliver.
- Distinctive: line 16
Use the ICP sentence, disqualifiers, conversation evidence, delivery capabilities, available support hours, proof, and existing draft.
- Distinctive: line 22
Use the equation with explicit grouping:
- Distinctive: line 46
Use this shape, simplifying it if that improves readability:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
Files
First-Client Offer Builder
Create one offer a real buyer can repeat and the seller can deliver. Optimize for a first paid engagement within the user's acquisition window, usually 90 days. Keep that seller goal separate from the result and timeline promised to the customer.
Ground the offer
Use the ICP sentence, disqualifiers, conversation evidence, delivery capabilities, available support hours, proof, and existing draft. Prefer three buyer quotes if available. Without buyer evidence, produce a provisional offer and the questions needed to test it. Do not treat a guessed niche as validated.
Identify the buyer's desired outcome, current workaround, trigger, feared effort, and risk. Translate tools into the business job they perform. Choose one outcome and a measurable acceptance condition. Preserve an existing scope the user has chosen unless evidence exposes a delivery problem.
Diagnose the four levers
Use the equation with explicit grouping:
Value = (Dream Outcome x Perceived Likelihood) / (Time Delay x Effort & Sacrifice)
Rate each lever 1-5 with reasons. For dream outcome and likelihood, 5 is stronger. For time delay and effort, 5 is a greater burden and worse. An unknown gets unknown, not an invented middle score. These are qualitative diagnoses, not measurable probabilities; do not multiply them into a fake conversion prediction. Price is considered separately from this equation.
Repair the weakest supported lever first. Strengthen likelihood with relevant proof, a demonstration labeled as such, a smaller pilot, or clear acceptance criteria. If the user has no results yet, do not invent a case study. Reduce time to the first useful result and specify the customer's required work.
Build one stack
Describe each component, the obstacle it removes, delivery method, owner, and boundary:
- Core deliverable that produces the promised result.
- Speed aid that shortens the route to first value.
- Ease aid that reduces customer effort.
- Support with a clear duration and response scope.
- Risk reversal with a measurable trigger and capped remedy.
A speed or ease aid should be useful, not an unrelated bonus added to inflate value. Avoid six packages and invented bonus valuations. For automation, name the workflow, included integrations, required data/access, handover, monitoring, and excluded custom work when they affect delivery.
Choose a credible risk reversal: a paid pilot, acceptance-based revision window, or exit clause can be more feasible than promising revenue or meetings. Specify eligibility, measurement, deadline, buyer dependencies, exclusions, remedy, and maximum exposure. Do not propose unlimited free work. Treat commercial terms as a draft until the user approves them.
Write and test
Use this shape, simplifying it if that improves readability:
I help [ICP] get [outcome] in [delivery timeframe] without [unwanted effort/risk]. Includes [core plus speed/ease aids] and [support]. If [measurable failure condition], [bounded remedy].
A first-time provider might offer a scoped working workflow with a measured baseline instead of guaranteeing the buyer a $3k retainer in 30 days. Numerical examples in the deck illustrate phrasing; they are not evidence that the user can promise those results.
Adapt the packaging by lane: a freelancer's bounded first engagement, an agency's pilot before an ongoing service, or an operator's two-week pilot with sponsor, resources, and success metric. Keep retention tied to ongoing value.
Prepare a say-it-back test for three real matching buyers or warm contacts: who is it for, what changes, what must they do, what happens if it fails, and what feels unclear or hard to believe? Record exact reactions. AI role-play may reveal confusing language but cannot substitute for these three people.
Deliver
- One recommended offer paragraph, plus alternatives only when useful or requested.
- Four-lever scorecard with evidence and the weakest-lever fix.
- Delivery stack, exclusions, dependencies, effort, and draft risk reversal.
- WEAK / REWRITE / STRONG assessment: features only; real outcome with unclear terms; or clear, credible, feasible, and repeatable by buyers. Without buyer tests label any STRONG assessment provisional.
- Three-person test script and a reaction log, followed by the next revision decision.
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 week2-offer-deck.pdf, pages 3-12; curriculum-deck.pdf, page 5. The deck credits Alex Hormozi / Acquisition.com and $100M Offers for the Value Equation, stack, and risk reversal; the without phrasing follows the deck's Josh Braun influence. 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.
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
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.

