Product launch tarot spread: audience, promise, channel and first signal

A product launch tarot spread is useful when it turns a vague hope into testable assumptions. The cards can help you clarify who the first audience is, what problem the product promises to solve, where the message is still blurred, which channel deserves the first experiment and what counts as an early signal of interest. They cannot replace customer interviews, analytics, a budget or a demand test. A good reading should end with a minimum launch: one audience, one promise, one channel, one observable metric and a date for reviewing what actually happened.

I once spent far too long revising the landing page for a small digital product. Every version felt “almost right”, while the team had already moved on to button colours and page order. The Seven of Cups appeared in the obstacle position. I might once have called it an abundance of possibilities. That evening it showed something less flattering: we were preserving five different promises because choosing one would make it possible to fail. We did not draw another card. We reduced the offer to a single use case and sent it to ten people who matched the proposed audience.

What tarot can examine before a launch

People usually search for a product launch tarot spread when the idea already feels exciting but the decision still rests on too few facts. In that situation, the cards can help formulate hypotheses about:

• who experiences the problem often enough to seek a solution;
• what job the person is trying to complete;
• which change the product actually promises;
• where the wording only makes sense to the team;
• which channel makes a useful conversation possible;
• what can be shown or sold before the full version exists;
• which user action is stronger evidence than praise;
• what analytics and interviews should investigate after the test.

Tarot cannot calculate market size, acquisition cost, conversion, profitability or legal readiness. It cannot prove that an audience is “meant” for the product. Those conclusions require observable behaviour and professional checks where relevant.

A productive question is:

“Which assumptions about my audience, promise and channel need testing before a full launch, and what minimum experiment could provide the first reliable signal?”

“Will this project succeed?” is too broad. It invites a persuasive story but gives you little to do on Monday morning.

Before the cards: record the starting facts

Write down what is already known. Do not confuse the team’s intention with the audience’s behaviour.

“Every freelancer needs this” is not a fact. A more useful note might be: “In six interviews, specialists managing three or more projects said they lose agreements between chat threads and private notes.” That still does not prove willingness to pay, but it creates a hypothesis that can be tested.

The Minimum Launch spread

Use eight positions and write them down before revealing any cards.

1. Audience. Which group should the first test focus on?
2. Problem. What real difficulty must not be softened into general language?
3. Promise. Which result should be understandable without the team explaining it?
4. Ambiguity. Where is the message overloaded, scattered or promising too much?
5. Channel. Where can you obtain a meaningful response from suitable people?
6. Minimum launch. What can be shown, delivered or sold before the complete product exists?
7. First signal. Which observable action would matter at this stage?
8. Retrospective. What question should be asked of the data and the users after the test?

Instead of adding an “outcome” card, ask:

“Which fact two weeks from now would make us continue, revise the hypothesis or stop?”

That turns an outcome into a decision rule.

Open a spread and save your launch hypotheses in Reflecta

The cards do not choose a channel for you

The same image can support several marketing hypotheses. Context and available resources matter more than a convenient keyword.

I would not treat the Three of Pentacles as an instruction to hire an influencer, or the Eight of Wands as a command to buy ads. A card suggests a line of inquiry. The channel is chosen by access, cost, feedback speed and the quality of information it can produce.

Full example: a weekly summary service for project teams

This is a composite case. A small team planned to launch a service that turned notes from work chats into a weekly project summary. The founders described the audience as “all distributed teams”. The landing page promised time savings, transparency, schedule control, lower stress and automated management at once.

Facts recorded before the spread:

• eight interviews had been completed with managers of small teams;
• five people regularly assembled a weekly report by hand;
• three already used complex systems and did not want another tool;
• the prototype could produce only one type of report;
• there was no budget for broad advertising;
• the founders had access to two professional communities;
• no one had placed a paid pre-order;
• a decision about a full release was expected within a month.

The cards:

1. Audience — Queen of Pentacles.
2. Problem — Ten of Wands.
3. Promise — The Magician.
4. Ambiguity — Seven of Cups.
5. Channel — Three of Pentacles.
6. Minimum launch — Page of Pentacles.
7. First signal — Ace of Swords.
8. Retrospective — Judgement.

Interpretation one: narrow the audience and run a manual pilot

The Queen of Pentacles may describe not a generic remote team but the person who actually maintains order: a project lead or operations manager in a small company. The Ten of Wands points to the specific burden of collecting updates manually rather than to general workplace stress. The Magician supports a clear promise—“turn notes you already have into a usable weekly summary”—while the Seven of Cups warns that five simultaneous benefits make the offer less credible.

The Three of Pentacles favours professional communities and live demonstrations of the workflow. The Page of Pentacles suggests avoiding a wait for full automation. The team could provide four reports manually during a paid or commitment-based pilot and observe what users value. The Ace of Swords makes the first signal a clear action: a request to add another team, willingness to continue after the pilot or agreement to pay for the next month. Judgement asks the retrospective to compare the original problem with the outcome.

Working conclusion: one audience, one promise, ten personal invitations, three pilots and a review after twenty-one days.

Interpretation two: the problem is real, but the product has been defined too early

The Queen of Pentacles may show that the proposed user already has a workable organisational system and is not looking for replacement software. The Ten of Wands confirms workload but does not prove a desire to delegate it to an algorithm. The Magician may then describe the founders’ fascination with their technology. The Seven of Cups points to an unresolved choice between reporting, control, communication and analytics.

In this reading, the Three of Pentacles recommends working sessions with managers before selling. The Page of Pentacles supports a simple template or service without further development. The Ace of Swords becomes a signal of clarity: several people independently describe the same job and willingly provide data for a test. Judgement may lead to removing features, changing the product or stopping the idea.

Working conclusion: do not buy traffic. Conduct six more interviews using the same script, show a manual prototype and observe what people are willing to do.

Neither interpretation answers whether the product is destined to succeed. Both create inexpensive ways to obtain new evidence.

Choosing the first signal

An early signal should involve some effort from the user. The lower the effort, the weaker the evidence.

There is no universal number that makes a launch successful. The team should choose a criterion appropriate to the stage before seeing the result. For an early pilot, it may be three users who repeat the central action twice and agree to an interview. For a paid test, it may be several purchases at a stated price. What matters is setting the rule before the data arrives.

Treat the channel as a hypothesis

Ask four questions:

1. Where does the audience already discuss this problem?
2. Can the channel generate feedback rather than impressions alone?
3. What is the cost of one meaningful contact?
4. Can the experiment be repeated in roughly the same way?

Ten warm introductions to suitable managers may teach more than a large advertising campaign. If people search for a specific solution, a search landing page can be tested. If trust depends on seeing the workflow, a workshop or partner demonstration may fit. The cards may suggest the form of contact, but behaviour decides whether it works.

The retrospective needs data and conversation

After the test, do not ask only how many people arrived. Compare four layers:

• message: what people understood from the page or invitation;
• behaviour: what they actually did;
• result: which job the product helped them complete;
• reason for stopping: what prevented continued use.

Analytics reveal a path—view, application, activation, return. Interviews help explain motives. Either one alone can mislead. A high conversion rate may reflect a price that is too low, while a low rate may reflect an unclear promise despite a real problem.

Write two competing explanations of the result. For example:

• “People do not need the product.”
• “People did not understand the exact job the product performs.”

Then design the next test to distinguish between them.

Common mistakes

Repeating the spread until a success card appears

That is reassurance-seeking, not research. Complete the selected experiment and wait for new facts.

Explaining poor metrics through the cards

Low conversion is not caused by the “wrong energy of the day”. Check the traffic source, wording, price, technical problems and audience quality.

Building too much for a minimum launch

The minimum launch tests the largest risk; it does not need to display the entire vision. A manual service, prototype, pre-order page or five interviews may be enough.

Choosing a flattering metric

Views and followers feel good but may have little connection to use or payment. Choose a metric that addresses the next uncertainty.

Treating interview approval as validation

People often support an idea politely. Ask about past behaviour and request a concrete action.

A fourteen-day launch exercise

Complete this form:

• Audience: one specific group.
• Problem: one observable event.
• Promise: one outcome without a list of features.
• Minimum version: what can be shown or delivered manually.
• Channel: one place or contact method.
• First signal: an action requiring effort.
• Criterion: a pre-agreed rule for continuing, revising or stopping.
• Retrospective date: fourteen days from the start.

Example:

Project leads in small remote teams who assemble a weekly status by hand. We offer a usable summary from existing notes without moving the team into a new system. Over fourteen days we invite ten people from two professional communities, run three manual pilots and treat repeated use or willingness to pay for the next cycle as a strong signal. We then compare product analytics with five short interviews.

At the review date, return to the original note. What was confirmed? What needed explanation? Which action happened without reminders? What is now the largest uncertainty? Only then does another spread make sense, because the question has changed.

Frequently asked questions

Can tarot show whether a product will be profitable?

No. Profit depends on demand, pricing, costs, retention, channels and execution. Tarot can help frame assumptions; a financial model must be tested with numbers.

Which deck should I use for a launch spread?

Use a deck you know well enough to interpret in context. Clear positions and recorded facts matter more than finding a “business tarot” deck.

Should I draw one card for every marketing channel?

Usually not. Remove channels that are inaccessible or too expensive using ordinary evidence first. You can compare the risks and test formats of two or three realistic options, but no card guarantees a winning channel.

When should I repeat the spread?

After a minimum launch, a set of interviews or a material change in conditions. Repeating it on the same day creates no new information.

What is a useful outcome from the reading?

A defined experiment: who, what, where, which action, which criterion and when you will review the result.

Save the starting facts, two interpretations, the minimum launch, the metric and the review date in Reflecta. After the real test, return to the note and compare the hypothesis with audience behaviour rather than retrofitting the cards to whatever happened.

— Daniel Aster, Official Author at Reflecta