From rough idea to recommended route

Product Idea to Design Brief v1.12

Give the tool a vague product idea and a simple who, what, where, when and why. The tool then suggests the best product type, platform route, files to build and deployment stage.

Core rule: the customer should not need to know whether their idea is a KDP book, Etsy download, website tool, printable, app or POD item. The tool works that out from the answers.

Start planner Jump to recommendation Main Sapiver suite

1. The idea

Capture the raw idea. It can be messy. The recommendation engine will turn it into a product route later.

Rough idea

Where did the idea come from?

What feels unclear or messy?

Do not choose the platform yet. Answer the idea questions first. The recommendation will choose the likely route.

2. The 5W check

These are customer-friendly questions. They describe the idea, not the final file format.

Who is it for?

What would it help them do?

Where would they use it?

When would they use it?

Why would they care?

3. Use signals

These signals help the tool decide whether the idea is probably a book, printable, website, app, POD design, worksheet, game or download pack.

How will it mostly be used?

What does the user actually do with it?

How complex is the first version?

Does it need repeatable versions?

Does it need printing?

Does it need to work on phone?

4. Value test

Mark the value types that fit the idea. This improves the product recommendation.

Entertainment / fun Relaxing / screen-free Solves a problem Educational / teaching Practical / time-saving Giftable / attractive

One-sentence value

5. Niche and audience clues

Use research to understand buyer expectations. Do not copy other products.

Niche or topic

More specific audience

6. Preference and product history

These answers do not force the route. They help the tool make a recommendation that fits the person, not just the idea.

What have you made before?

Where have you sold or shared before?

What do you prefer making?

What do you want to avoid?

What do you already have?

How much time can you give the first version?

Preference rule: personal history can nudge the recommendation, but it should not override the product logic. A strong idea still needs the right format.

7. Design direction

This comes after the idea has been shaped. Keep it practical and test one sample before building everything.

Style/tone

Project/folder name

Must include

Must avoid

What should the first test build prove?

Recommendation

What this tool decides

Customer gives	Tool recommends
Vague idea, who it is for, what it helps with, where/when it is used, why it matters	Best product type: book, printable, download pack, website tool, app, POD design, worksheet or game
Use signals: print, phone, writing, reading, playing, displaying, repeatable versions	Best platform/deployment route: KDP, Etsy, website, POD, classroom/home, static web app or bundle
Design direction and must-avoid notes	Files to build first, suggested specs, test stage and next action

Platform reminder

This tool gives starter suggestions. It is not a replacement for current platform rules. Before publishing final files, check the current upload requirements for Amazon KDP, Etsy, your print provider, website host or whichever route you use.

Next step: paid products and route packs

The free tool helps the customer work out what their idea should become. The paid layer helps them take the next practical step with a matching Sapiver route pack or a more specific product.

Browse paid route packs Browse specific products

Website structure note: this build separates the free tool from the paid layer. Use the main page as the entry tool, use /paid/ for route-pack guidance, and use /products/ for product pages with Payhip checkout links.

Live paid links added: KDP Account + W-8BEN Setup Mini Pack and Indie Publisher Admin Toolkit now have Payhip checkout links wired in. FTPE and Commercial route to Etsy.