Skip to content
Resource · r1

The one-page offer rubric

Is my one-page service offer specific enough for a buyer to say yes, no or “tell me more”? For: people writing a first fixed-scope service offer — before they have a website or clients.

Updated

Check yours

Try it on your offer — nothing is sent.

Checked in your browser only — nothing is sent, saved or tracked.

Fill in your offer to see the checks

  • A specific buyer — who pays, not “everyone”
  • The problem in the buyer’s words
  • At least 3 countable deliverables
  • A price with a number
  • A delivery time
  • How the client accepts the work
  • Clear limits and what is not included
  • What you need from the client

Meeting all eight means the offer is clear to read — not that anyone will buy it.

The checks

Eight checks, and why each matters.

  1. 1. A specific buyer — who pays, not “everyone”

    A buyer recognises themselves only in a specific description; “everyone” gives them no reason to read on.

    Passes (synthetic): Owners of online shops in Germany with 100–2,000 products who edit the catalogue in a spreadsheet

    Doesn’t (synthetic): Small businesses

  2. 2. The problem in the buyer’s words

    People answer to their own problem, not to your solution. Their words tell you whether you understood it.

    Passes (synthetic): Duplicates and missing fields get listings rejected before promotions (hypothesis)

    Doesn’t (synthetic): Data quality issues

  3. 3. At least 3 countable deliverables

    Countable items let the buyer picture what they get and compare it with the price.

    Passes (synthetic): Defect report; corrected copy with safe fixes; list of open questions

    Doesn’t (synthetic): A full catalogue optimisation

  4. 4. A price with a number

    A number is the most useful signal a test can get; “contact us” hides it.

    Passes (synthetic): €120 fixed (a price to test)

    Doesn’t (synthetic): Affordable pricing

  5. 5. A delivery time

    A delivery time sets expectations and shows you have thought about the work.

    Passes (synthetic): 3 working days after the file arrives (to agree)

    Doesn’t (synthetic): Fast delivery

  6. 6. How the client accepts the work

    Saying how both sides know the work is done prevents endless rounds and disputes.

    Passes (synthetic): Every flag points to a row, field and rule; protected fields unchanged

    Doesn’t (synthetic): Until you are happy

  7. 7. Clear limits and what is not included

    Limits and exclusions protect your hours and tell the buyer what not to expect.

    Passes (synthetic): Up to 200 rows and 10 fields · IDs and prices never changed

    Doesn’t (synthetic): Unlimited revisions

  8. 8. What you need from the client

    Naming what you need from the client avoids a stalled start.

    Passes (synthetic): One authorised CSV export

    Doesn’t (synthetic): Access to your systems

Method

Each check answers a question a buyer has before they reply. The checks are the readiness checklist the Proofoak offer editor runs. Readiness is not approval and not proof of demand. A short, checkable list with a reason for every line, the same one the Proofoak offer editor runs — usable without an account, and honest about what it can’t tell you (whether anyone will pay).

Limits

  • The rubric tells you whether an offer is clear — not whether anyone will buy it. Only a test with real buyers shows that.
  • Examples are synthetic. They are not a client’s offer or results.
  • It is not legal or tax advice, and not a contract template.

Sources

Changelog

  • r1 · 2026-11-08 — First version: eight checks, why each matters, synthetic examples, browser-only self-check.

Share it freely with this credit: “The one-page offer rubric” by Proofoak (r1, 2026-11-08) — https://proofoak.com/resources/offer-rubric

Next: write it in the one-page service offer template, price it with the pricing calculator, or see the supported route this rubric was written for.