Sign in

Capstone Review Offer

Put finished work in front of an expert and get it scored against a published rubric with specific fixes ranked by impact.

Free simple Knowledge Offers

What it adds

The builder turns your evaluation rubric and review process into a standalone assessment product: the buyer submits completed work, it is scored dimension by dimension, and they receive prioritized corrections. It converts on decision confidence — buyers who have finished something will pay to learn whether it is actually good before they ship it. The goal is a single submission purchase with the work uploaded at checkout.

What your builder is told to do

8

The actual instructions, in order.
  1. 1

    Inspect the supplied rubric and prior review outputs. Extract every scoring dimension, its scale, and the structure of a completed review.

  2. 2

    Publish the rubric in full. A buyer must be able to see exactly what will be judged and how it is weighted before submitting anything.

  3. 3

    Describe the review deliverable concretely: dimension scores, the ranked list of fixes ordered by impact, and the format and length the buyer receives.

  4. 4

    Define submission requirements exactly — what state the work must be in, accepted formats, size limits, and what makes a submission ineligible. This offer only works on finished work, so gate it explicitly.

  5. 5

    State the turnaround time and who performs the review, and describe whether any clarification exchange is included after delivery.

  6. 6

    Build the value argument on decision confidence: the cost of shipping flawed work versus the cost of a review, expressed with the rubric dimensions rather than any outcome promise.

  7. 7

    Specify responsive behavior: on mobile the rubric collapses to per-dimension accordions and the upload flow is a single-screen step; on tablet show rubric and sample review side by side; on desktop present a full rubric table alongside a scrollable annotated sample review.

  8. 8

    Close with one action — submit work for review — with the upload step integrated into checkout rather than deferred to a follow-up email.

Edge cases it handles

5

The things an agent skips when you only say "build a capstone review offer".
  • Submitted work is unfinished or out of scope: state the triage policy including whether a partial refund or a redirect applies.
  • The rubric does not cover an aspect a buyer cares about: list explicitly what the review does not assess.
  • Sample reviews contain identifiable work: redact fully or construct an illustrative example and label it as such.
  • Work is submitted in a format that cannot be reviewed as delivered: publish the accepted-format list before checkout.
  • Multiple reviewers apply the rubric differently: describe any calibration process the sources define, or note reviewer variance honestly.

Definition of done

7

Your builder is required to check every one of these before reporting the work finished.
  • The complete rubric with dimensions and weightings is visible before purchase.
  • The review deliverable's structure, including ranked fixes, is described concretely.
  • Submission requirements, accepted formats, and ineligibility conditions are stated.
  • Turnaround time and post-delivery clarification terms are stated or flagged unresolved.
  • Mobile, tablet, and desktop layouts match the specification, including the desktop rubric-plus-sample view.
  • What the review does not assess is explicitly listed.
  • The builder reports which rubric and prior-review files it used, and lists unresolved assumptions such as reviewer calibration or triage policy.

Related offer files

How it works

  1. 1

    Copy the link

    Grab the Markdown blueprint URL for this offer type.

  2. 2

    Give it to your builder

    Paste it into Claude Code, Cursor, Codex, or whatever AI builder is already working in your app.

  3. 3

    It maps, then builds

    Your agent reads the blueprint first, then builds the offer into your app around the product, audience, and stack.

Works with your stack

These blueprints are written to adapt. They tell the agent to detect your framework, match your existing design system, and use your source files instead of guessing the offer.

Need it tighter than that? Customize the offer file and tell it exactly which source docs and stack to use.