The Fractional One-Pager

What this is for

You know how to fix a specific, expensive problem inside a company. What you lack is a document that says so in a way a decision-maker acts on in one read. This is for the moment before a discovery call or warm intro turns into real money.

Before you start

• Have a rough answer to "what's the most expensive mistake I've watched companies make in my field."
• Pull up three past projects where you fixed that mistake, with any numbers you remember.
• Have your numbers thought through; if you haven't set them yet, Pricing Your Expertise comes before this document, not after.

The 5 required blocks

In this order. Skip one and the reader has to do work to say yes, which means they won't.

1. The expensive problem. Named specifically, in the reader's language, with a cost attached.
2. Proof. Two or three lines showing you've solved this exact problem before, with a real number.
3. Scope. What you actually do, as deliverables, with a duration. Not "strategic guidance."
4. Price. Three tiers, so the reader picks a number instead of deciding whether to spend at all.
5. The next step. One sentence. One action.

Prompt 1: Draft the one-pager from a career interview

Use ChatGPT or Claude; Claude edges ahead if you paste more than a few thousand words of raw notes.

ROLE: You are a positioning consultant who writes one-page
fractional-services offers for experienced operators moving into
consulting.

CONTEXT: Use only what I tell you. No invented achievements, numbers,
or clients. If an answer is too thin, flag it as a gap instead of
filling it with generic language. My answers:
1. Industry/function and years: [YOUR BACKGROUND, e.g. 22 years,
   mid-market manufacturing operations, plants of 150-400 employees]
2. The most expensive recurring mistake I've watched companies make:
   [THE MISTAKE, e.g. they promote plant managers on tenure, not
   systems ability, and it takes 18 months and $400K in scrap and
   turnover to find out]
3. 2-3 times I personally fixed this, with company type, what I did,
   measurable result: [YOUR PROOF, e.g. auto parts supplier, rebuilt
   shift-handoff during a quality crisis, cut defect-driven returns
   31% in 5 months]
4. What I'd actually produce in a focused engagement, as concrete
   deliverables: [DELIVERABLES, e.g. process map, 90-day corrective
   action plan, trained internal owner, written playbook]
5. Realistic duration: [DURATION, e.g. 6 weeks]
6. Lowest price for a scoped-down version, and price for the full
   build: [YOUR TIERS, e.g. $2,500 diagnostic, $8,000 full build]

CONSTRAINTS:
- 300-400 words total. One page, not a proposal.
- No hype words, no exclamation points. First person, plainspoken,
  short sentences.
- Proof section uses only my examples. Don't generalize them into
  vaguer claims.
- If an answer is too thin to build a block from, say so under
  "Needs more input" instead of guessing.

OUTPUT FORMAT: Markdown with these headers in order:
# [Benefit-first title, not my name]
## The Problem
## Why Me
## What You Get (deliverables + duration)
## Investment (three tiers: name, price, one-line scope difference)
## Next Step (one sentence, one action)

Prompt 2: Cut it down when it's bloated

Use whichever tool already has the draft.

ROLE: You are a ruthless editor whose only job is to protect the
reader's time.

CONTEXT: Below is a draft one-page fractional offer, currently too
long or vague to read in under 90 seconds. [PASTE YOUR CURRENT DRAFT]

CONSTRAINTS:
- Final version readable aloud in under 90 seconds; aim for 300-350
  words.
- Cut any sentence describing a feeling or approach instead of a
  fact, number, or deliverable.
- Cut adjectives that aren't load-bearing ("innovative,"
  "comprehensive").
- Keep all five blocks: problem, proof, scope with duration,
  three-tier pricing, next step. Even if reduced to one sentence
  each.

OUTPUT FORMAT: The revised one-pager in markdown, then a "Cut for
length" list showing what you removed and why.

Worked example: former operations director

Problem: Manufacturing companies with $20M-$80M revenue lose $300K-$500K a year to scrap, rework, and turnover because plant managers are promoted for tenure, not systems skill.

Proof: 24 years running operations for a Tier 2 auto supplier. Rebuilt shift-handoff and quality-hold processes during a 2019 quality crisis; cut defect-driven returns 31% in 5 months. Reduced new-hire time-to-competency from 11 weeks to 6 across three plants.

Scope (6 weeks): Current-state process map of your top two failure points. A 90-day corrective action plan with named owners. One trained internal process owner. A written playbook your next plant manager can run without me.

Price:

• Diagnostic only (2 weeks, process map + findings memo): $2,500
• Core engagement (6 weeks, full scope above): $5,000
• Extended (6 weeks + 60 days of async support while your team runs it): $7,500

Next step: Reply with your two worst-performing lines and I'll tell you in one call whether this fits.

How to actually send it

The document doesn't close anything sitting in your drafts folder. The send:

• Format: attach it as a one-page PDF, named like a deliverable ([YourName]-Operations-Diagnostic.pdf), not one-pager-v7-final.pdf. A PDF survives forwarding to the CFO intact; pasted text doesn't.
• The email is three sentences, not a pitch:

Subject: The scrap problem we talked about

[NAME], you mentioned [THE SPECIFIC PROBLEM, in their words] when we
talked [WHEN]. I put what I'd do about it on one page, attached,
including what it costs. Worth 90 seconds; if the fit's there, the
next step is at the bottom.

• Send it to one person who owns the problem, not a generic inbox, ideally within 48 hours of the conversation that prompted it while you're still in their working memory.

The two replies that come next

"Could we start with a trial period?" They're asking to reduce risk, not price. Point at your bottom tier: "That's what the diagnostic is. Two weeks, $2,500, and you'll have the process map and findings whether or not we go further. It's the trial, with a deliverable."

"Can you send a full proposal?" Sometimes real, often a soft no or a procurement reflex. Qualify before you write: "Happy to. So the proposal answers the right questions: who besides you needs to sign off, and is the [MIDDLE TIER PRICE] range workable if the fit is right?" If the answers are vague, the one-pager already did its job; a longer document won't change the outcome.

Where this goes wrong

• The problem is framed from your side, not theirs. "25 years of operations expertise" tells the reader nothing. "You're losing $400K a year and don't know which shift it's coming from" gets read.
• Pricing has one number instead of three. A single price forces yes/no, and no is easier. Three tiers turn it into "which one."
• Deliverables are really just promises. "Ongoing strategic support" is a promise. "A written 90-day plan with named owners" is a deliverable. If you can't picture the document, it's not one yet.
• It's perfect and unsent. The fifth revision is procrastination wearing a work costume. Ninety-second read test, then send it to one real person this week.

The 2-minute version

Answer the six interview questions from Prompt 1 in a text file, paste them into Prompt 1, and get a draft. Read it aloud; if it takes over 90 seconds, run Prompt 2. Attach it as a PDF to the three-sentence email above and send it to one warm contact today.

---

Want to know where you actually stand with AI? The free AI Readiness Assessment takes 10 minutes and gives you a personalized roadmap.

Weekly, on Tuesdays. The Gen Xcelerator: practical AI intelligence for people who already know how to do the job. Subscribe free.

Experience Is the API. GenXcelerate