Sign in

Digital Toolkit

Equip a buyer with every calculator, checklist, and script one workflow needs, arranged in the order they use them.

Free involved Knowledge Offers

What it adds

The builder assembles your mixed assets — spreadsheets, checklists, scripts, reference sheets — into a single workflow-ordered kit where each tool has a defined trigger point in a process. It converts through completeness at a single decision point: the buyer stops assembling tools from a dozen sources because this kit covers the whole loop. The goal is one purchase that replaces an ongoing scavenger hunt.

What your builder is told to do

8

The actual instructions, in order.
  1. 1

    Inspect the supplied assets and process notes. Map the underlying workflow into stages, then assign every asset to the stage where it is actually used, flagging stages with no covering asset.

  2. 2

    Present the workflow diagram first and the asset list second. The organizing idea is the process; the files are what fills it.

  3. 3

    For each tool, state its trigger (when you reach for it), its input, and its output. Kit buyers abandon assets they cannot situate.

  4. 4

    Call out coverage gaps honestly — stages where the kit provides guidance but no tool — because an accurate map builds more trust than a padded one.

  5. 5

    Describe setup: what must be duplicated, connected, or filled in before the kit is usable, and roughly how long that takes based on the assets themselves.

  6. 6

    Build price logic on tool-count-per-stage plus the integration work the kit removes, and state clearly whether the kit assumes any paid software.

  7. 7

    Specify responsive behavior: on mobile the workflow renders as a vertical stage accordion with tools nested inside each stage; on tablet show stages as cards in a two-column grid; on desktop display a horizontal workflow with tools listed beneath their stage in aligned columns.

  8. 8

    End with one action — get the toolkit — and place a compact stage-coverage summary directly above it.

Edge cases it handles

5

The things an agent skips when you only say "build a digital toolkit".
  • Assets span incompatible formats such as spreadsheets and code snippets: group by stage anyway and label the format on each item.
  • A single asset spans multiple stages: place it at its primary trigger and cross-reference rather than duplicating it in the count.
  • Process notes are missing entirely: derive stages from the assets themselves and mark the workflow as inferred.
  • A tool requires configuration credentials or API access: surface that requirement in the setup section, not after purchase.
  • Some assets are reference material rather than tools: separate reference from tools so the tool count stays accurate.

Definition of done

7

Your builder is required to check every one of these before reporting the work finished.
  • A workflow with named stages appears before the asset list.
  • Every asset is assigned to a stage with its trigger, input, and output stated.
  • Stages without tool coverage are explicitly identified on the page.
  • Setup requirements, including any paid software or credentials, are listed before the purchase action.
  • Mobile, tablet, and desktop workflow layouts match the specified behavior.
  • Reference material and tools are counted separately in any advertised totals.
  • The builder reports which source files and process notes it used to derive the workflow, and lists unresolved assumptions including inferred stages.

Related offer files

Knowledge Offers

Workbook System

Guide buyers through structured exercises that end with a personalized document they could not have downloaded.

Build This Offer: Workbook System

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.