Digital products framework: gates to pass, not a launch date to hit

A calendar date cannot tell you whether a digital product deserves production. Use five gates instead: each one settles a cheaper uncertainty and leaves a usable artifact for the next decision. You can complete them alone within a week, without prices or figures, and stopping when evidence fails is a useful outcome, not a failure.

How can I tell whether readers have a real problem?

Look for a problem a reader can recognize and for evidence that people already spend time or money trying to reach the outcome. Your interest in the subject is not enough; an existing workaround shows that the difficulty already has a cost for somebody.

Write one sentence in the reader's own terms that names what they cannot currently do. Base it on something they wrote to you, said during a call, or asked in public. If the wording comes only from your enthusiasm, gate one is still open; an idea can suit its maker and miss everyone else.

Keep that sentence somewhere visible as the first gate's artifact. Later disagreements about what belongs in the product can be tested against it. If the wording is not something a reader actually used, return to the evidence instead of treating your own excitement as proof.

What should I ask before I make anything?

Ask people directly what they already do about the problem, and listen for a workaround rather than a compliment or interest in your idea. If nobody has a way of dealing with it, do not spend production time trying to persuade yourself that demand exists.

The Small Business Administration describes this kind of direct inquiry in its market research guidance, which fits a one-person business. Ask about the steps people take now, rather than whether your proposed product sounds appealing. The question is whether they have already paid in time or money to get the outcome.

Write down the alternatives people currently use; that list is the second artifact, and an empty list means stop. This check cancels more projects than the other four gates together, and each cancellation saved a month. A workaround is the strongest signal because it shows the problem already costs time or money.

Can I use every asset in the product?

Check permission for every item before production, including fonts, images, code, music, templates, quoted passages, commissioned work, and contributions from collaborators. Do not assume an asset is usable just because it is available to download or already sits in a draft.

A license for personal use may not permit resale, and the terms applying when you downloaded an item do not establish what is allowed now. Consult the Copyright Office's overview of what copyright covers before deciding to include an asset in a product you sell.

The Copyright Office's fair use explanation is worth consulting before assuming a quotation or excerpt is safe in a paid product. Record each asset beside the permission that applies. If permission cannot be established, replace that item while doing so is still a morning's work.

What exactly am I promising the buyer?

Set out both what the buyer receives and what happens after delivery, and decide the limits before production. Specify how questions, corrections, updates, access trouble, and refund requests will be handled, then make those terms visible before a buyer pays.

Many first products treat delivery as the finish line, although the support tail can consume the year. The digital products pillar explains why aftercare is regularly the largest hidden cost; digital product mistakes after launch offers a related repair-side reference.

Before making anything, choose how long support lasts, whether updates are included, and what the refund policy says. Set clear boundaries for questions and access trouble as well. Those decisions stop delivery from being treated as the end of the buyer relationship.

The artifact for this check is a one-page description of the product and aftercare, prepared before production. It should state what the buyer receives, how long support continues, whether updates are included, and how access problems or a refund request will be handled.

If buyers pay repeatedly, include cancellation in the design. The Federal Trade Commission's negative option rule page describes expectations for subscriptions and automatic renewals in the United States; those expectations can also guide a fair cancellation flow elsewhere. Put the cancellation route in the buyer's terms before purchase, not in a later afterthought.

How will the people who need this hear about it?

Plan to sell to the audience you already have. Building an audience you merely hope to acquire turns the work into two projects, and the audience-building project is harder than making the product. A product should fit people you can reach now, not an imagined later crowd.

Write down how the people who described the workaround will hear about the offer. If your route relies on a channel you do not have, build that channel first or make the product smaller to fit your current audience. A short list of those people is the first item in an affiliate income framework.

Your first-announcement plan is the artifact for this gate. Use it to test the original problem sentence: if you cannot describe the offer in those terms, the first gate was not truly passed. The announcement needs a real route to people who already explained how they handle the problem.

What if my audience is small or I have no price benchmark?

A small audience does not prevent a useful test: ask people individually and keep the product small enough for the people you already have. People making decisions in your subject matter more than a larger audience that does not make those decisions.

The career paths pillar discusses why a smaller, relevant audience can be preferable to a larger group that does not make decisions in your subject. For pricing, start with the outcome's value to the buyer and what you need the product to do, rather than copying another seller's charge.

The income benchmarks pillar explains why that comparison is not available in a useful form. A free version can test the second gate rather than serve as a marketing device: if people use it, that supports the problem's reality; if nobody opens it, that also tells you something.

Do recommendations or subscriptions change what I need to disclose?

Yes, disclose plainly and close to the recommendation if you earn from something the product recommends or another person promotes it for a share. The Federal Trade Commission's guidance for social media influencers gives a clear, short statement of this disclosure principle.

The same principle applies to an affiliate arrangement inside a paid product; readers may find that more troubling than a recommendation on a free page, not less. Practical details are covered under affiliate income. Make disclosures clear in internet advertising and within the product.

Can I complete the checks in a different order?

You can complete rights and aftercare in either order. The problem and demand checks must happen before production; existing material often tempts people to skip the check that could have helped most. If the early evidence is weak, stop before committing more work.

The sequence up to production should take days rather than weeks. If a check remains uncertain, make the product smaller until that uncertainty is cheap instead of widening the research. Each artifact carries into the next check, so a gap can be addressed before it turns into a more expensive production problem.

What should I do first?

Start by collecting the evidence that makes the next decision inexpensive. Do not begin production just because material is ready; first confirm that readers recognize the problem and already have a way of working around it.