Sign in

Certification Renewal Offer

Keep existing credential holders current with a short update cycle that revalidates what has changed since they passed.

Pro simple Knowledge Offers

What it adds

The builder works from your version history, updated standards, and prior certification records to produce a renewal offer aimed only at people who already hold the credential — focused on the delta, not the full curriculum. It converts on the credential's expiry mechanic plus a far smaller effort ask than the original certification. The goal is renewal purchases from an existing holder list before their expiry dates pass.

What your builder is told to do

8

The actual instructions, in order.
  1. 1

    Inspect the supplied standard-version files and the original rubric. Produce a change list showing what was added, revised, or retired between the holder's version and the current one.

  2. 2

    Address the audience as existing holders throughout. Do not re-sell the original credential; the buyer has already made that decision.

  3. 3

    Publish the change list on the page. Renewal converts when the holder can see concretely what they do not yet know.

  4. 4

    Define the renewal path: the update material covering only the delta, the shortened assessment, the passing threshold, and the effort required in hours — contrasted explicitly against the original certification's effort.

  5. 5

    Make the expiry mechanic clear using only what the sources establish: the validity period from the original credential, how a holder finds their expiry date, and what status they hold if they lapse. Never invent a deadline the credential terms do not create.

  6. 6

    Handle lapse cases directly: whether a lapsed holder may renew or must recertify fully, and any grace window the sources define.

  7. 7

    Specify responsive behavior: on mobile the change list renders as filterable added/revised/retired cards with the renewal deadline pinned; on tablet show change list and renewal path in two columns; on desktop present a version-comparison table with the holder's version and the current version side by side.

  8. 8

    Close with one action — renew now — with the holder's expiry status check adjacent to it.

Edge cases it handles

5

The things an agent skips when you only say "build a certification renewal offer".
  • Multiple prior versions exist among holders: branch the change list by originating version rather than showing a single delta.
  • The current standard retired a competency: state retirement explicitly so holders stop teaching or applying it.
  • Expiry dates are not tracked in the sources: provide a lookup step instead of asserting any individual's date.
  • The delta is trivially small: reduce the renewal scope and price accordingly rather than padding the update material.
  • Some holders never completed the original assessment: route them to the full certification path instead of renewal.

Definition of done

7

Your builder is required to check every one of these before reporting the work finished.
  • The page addresses existing credential holders exclusively and does not re-pitch the original certification.
  • A change list distinguishes added, revised, and retired competencies against the prior version.
  • Renewal effort in hours is stated and contrasted with the original certification's effort.
  • Expiry, grace, and lapse handling are described using only terms present in the source files.
  • Mobile, tablet, and desktop layouts match the specified behavior, including the desktop version comparison.
  • No deadline, urgency, or expiry pressure appears that the credential terms do not establish.
  • The builder reports which version-history and rubric files it compared, and lists unresolved assumptions such as untracked expiry dates.

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.