Workflow, Not Wrapper: test an AI product idea, shape the offer and set the price

Here is my product idea [paste]. Score it on this seven-line absorption test [paste].
Give one sentence of evidence per line, mark any score without evidence as 0, and name the weakest line.

Any 0 on truthfulness and compliance stops the idea.

Assume [model vendor] added this feature as a default button tomorrow.
List what my buyer would still need from me. If the list is empty, say so plainly.

An empty list means timing, not a business.

# Workflow, Not Wrapper: test an AI product idea, shape the offer and set the price

A prompt pack and working method by PaperChaseWebb for anyone about to build or sell something on top of a model. A seven-score absorption test, a one-page workflow product spec, a problem mining loop, a channel translation table, a model column check, an offer ladder with pricing rules, a claim check for the success stories you are copying, a fidelity gate for generated media, a failure table, a worked example, a rules block and 14 prompts. Plain .md. Works in Grok Bot, Claude, ChatGPT, Claude Code or Codex.

Most "AI business" advice stops at the model call: pick a tool, put a nice screen on it, charge for it. That screen is the easiest part of the business to copy, and the model vendor can absorb it in a single release. What lasts is the work around the call: the buyer's inputs, the template, the review step, the rules, the delivery format, the records and the channel that brings the buyer back. This pack is about building and pricing that part.

This is a decision method, not financial or legal advice, and not a promise that any idea will sell. Every revenue figure you hear about someone else's product is a claim until you check it.

## Contents

1. The wrapper problem on one page
2. The absorption test: seven scores
3. The workflow product spec
4. Problem mining: read and record, never seed
5. Channel translation: which launch tactics survive your buyer
6. The model column check
7. The offer ladder and pricing rules
8. Check the story before you copy the model
9. The fidelity gate for generated output
10. Failure modes and fixes
11. Worked example: listing videos for real estate agents
12. Rules block and 14 prompts
13. Sources

## 1. The wrapper problem on one page

A wrapper is a clean interface over one model call. It can make money for a while, usually because it got there first or found a channel others missed. It has three weak points:

- **The vendor can add it.** If the model provider makes your feature a default button, your customers have a reason to leave the same week.
- **A competitor can rebuild it in a weekend.** The prompt and the screen are visible from the outside.
- **You inherit someone else's roadmap.** Price changes, policy changes, outages and model retirements land on you without notice.

A workflow product uses the model as one replaceable part inside a job the buyer already does. The buyer pays for the finished result inside a process they recognize, not for access to a prompt box.

Quick test before anything else: **if the platform added your feature tomorrow, what would your buyer still need you for?** If the honest answer is "nothing", you have timing, not a business. Timing can still pay, but price it and plan your exit from it as timing.

## 2. The absorption test: seven scores

Score each line 0, 1 or 2. Write one sentence of evidence next to every score. A score with no evidence counts as 0.

| # | Score | 0 | 1 | 2 |
|---|---|---|---|---|
| 1 | Platform absorption | The vendor's default chat already does it | The vendor could add it as a button | It needs steps, inputs or rules the vendor will not build for one niche |
| 2 | Workflow depth | One input, one output | Several steps, but no review or delivery | Inputs, template, review, approval and delivery in the buyer's format |
| 3 | Data that improves results | None | Saved preferences | Buyer records or past outcomes that visibly make the next result better |
| 4 | Distribution access | You hope people find it | You can reach some buyers | You already sit where buyers gather, or they come back on their own |
| 5 | Model independence | Welded to one model or vendor feature | Swap possible with real rework | Model swap is a config change and a test run |
| 6 | Unit economics | Cost per job unknown | Known, thin margin | Known, with room for retries, refunds and support |
| 7 | Truthfulness and compliance | Output can mislead and nobody checks | A check exists but is optional | A check and a human approval are part of the product |

**Reading the total (0 to 14):**

- **0 to 5:** a wrapper. Build it only as a cheap experiment or a free tool that leads somewhere.
- **6 to 9:** a product with a hole. Name the lowest line and fix that first.
- **10 to 14:** worth a spec. Go to section 3.

Any 0 on line 7 stops the idea until it is fixed, whatever the total. A product that can mislead a buyer's customer is a liability with a checkout button.

## 3. The workflow product spec

One page. If you cannot fill it, you do not yet know what you are building.

```
# Workflow product spec: [name]

Buyer: [one job title in one kind of business]
The job today: [what they do now, in their words, and how long it takes]
Finished result: [what they hand to their own customer or boss]

Inputs: [files, forms, records the buyer already has]
Template or rules: [the format, brand rules, legal lines that never change]
Model step: [what the model does; name it as replaceable]
Review step: [who checks what, against what, before anything leaves]
Approval: [who says yes, and how that yes is recorded]
Delivery: [format, place, and whether it lands inside a tool they already use]
Records: [what is kept, for how long, and who can see it]

Moat lines (from the absorption test): [the two highest-scoring lines and why]
Weakest line: [the lowest score and the fix]
Not doing: [what this product refuses to do]
Cost per finished job: [model, storage, retries, support minutes]
```

Two rules for the spec:

- **The model step is one line.** If the model is most of the page, you are describing a wrapper.
- **"Not doing" is never empty.** It is where the product stops being "videos for anyone" and becomes something a specific buyer trusts.