From free test to paid report: designing an honest consumer funnel

A free test followed by a paid report is one of the oldest patterns in consumer products: a personality quiz leads to a full profile, a credit check leads to a detailed report, a sample chapter leads to the book. It works because it lets people judge quality before they pay.

It also has a bad reputation, earned by products that give away a teaser and hold the actual answer hostage. "You scored 72% — pay to find out what it means."

Two Oryvelon companies use a version of the free test to paid report funnel: KeşifAtlası, for visa and relocation eligibility, and ZodiVela, for personal discovery readings. This article explains how we design the funnel so it is honest: what we give away, what we charge for, how we earn trust before asking for money, and how refunds work when an AI-assisted report falls short.

Why this model suits some consumer AI products

Not every product should use a free-test funnel. It suits products with three characteristics.

The value is a one-time or occasional answer. A person planning a move abroad needs a clear assessment now, not a monthly subscription. Someone curious about their birth chart may want one detailed reading, then return months later.

Quality is hard to judge in advance. People have been burned by generic answers in both categories. A free result lets them see the quality of the thinking before paying.

The paid product has real extra depth. If the paid report is just the free result with more words, the model collapses. There must be genuinely more to deliver.

Products with continuous value — a daily operations assistant like MerchNivo — suit subscriptions better. See Designing a recurring revenue loop.

The honesty rule: the free result must stand on its own

The single most important design rule we apply is this: the free result must be useful even if the person never pays.

For KeşifAtlası, that means the free test returns the headline eligibility outcome — likely eligible, not eligible on current answers, or needs review — and the main reason. If someone fails a funding requirement, the free result says so. We do not hide the reason behind the paywall.

For ZodiVela, it means the free reading is a real reading: a short reflection on the person's sun, moon and rising signs, or a single-card draw with a proper interpretation. Not a blurred preview.

This can feel commercially risky. Why would anyone pay if the free result already answers the question? In practice, people pay for what the free result makes them want next: detail, structure, sources, a plan, a deeper exploration. The free result creates trust; trust creates the sale. A teaser creates suspicion, and suspicion creates refund requests.

What goes in the free tier and what goes in the paid tier

Drawing the line is a product decision we write down in each company's source of truth. A useful way to think about it:

The paid report is always built from the same underlying data as the free result. For KeşifAtlası, that means the same verified rules database and the same rule-set version; the report simply shows more of what the rules engine already knows. See Rules engines for eligibility. A paid report must never reach a different conclusion from the free result for the same answers. If it did, one of them would be wrong.

Earning trust before the payment step

People decide whether to pay in the few seconds after they see their free result. What they see then should answer the questions they are silently asking.

What exactly will I get? Show a clear list of report sections, and where possible a real sample report for a fictional profile. A table of contents converts better than a promise, because it is specific.

How much, all in? Show the price in the person's currency, including tax where applicable. No surprise fees at checkout.

When will I get it? Most reports generate in seconds or minutes. Say so. If a report includes a human review step, give an honest time range.

Who is behind this? A clear company name, contact route, and privacy notice. For KeşifAtlası, a visible note on when the rules for that route were last updated. The light "An Oryvelon company" endorsement helps here without turning the product into a group brand.

What if it's not right? A plain-language refund policy linked right next to the payment button.

What is this not? For KeşifAtlası: an informational assessment, not legal advice, and not a guarantee of any visa decision. For ZodiVela: a reading for reflection and entertainment, not a prediction or professional advice. Saying this before payment prevents misunderstanding afterward. See Positioning consumer AI as reflection and entertainment.

The broader principle — setting correct expectations early so the AI output is judged against the right standard — is covered in Onboarding and trust in AI products.

How paid reports are generated

A paid report is where AI is most visible, and where quality control matters most. Our pattern is the same for both companies, with different sources of truth.

1. Assemble verified inputs. For KeşifAtlası: confirmed answers, rule-set version, every rule evaluated and its result, sources and plain-language rule text. For ZodiVela: calculated chart placements or drawn cards, and the curated meanings for each.
2. Generate section by section. Each report section has its own prompt and its own output schema. Generating in sections keeps each piece focused and makes failures easier to catch and retry.
3. Validate every section. Outputs are checked against their schema. For KeşifAtlası, every requirement mentioned must map to a rule that was evaluated; nothing may be added. For ZodiVela, outputs are checked for predictive language, instructions and sensitive topics. See Structured outputs and schema validation.
4. Fall back when needed. If a section fails validation after retries, it is replaced with a well-written templated version built from the structured data, rather than shipping a flawed paragraph. See AI fallbacks and degraded modes.
5. Record versions. Each report stores the rule-set version, prompt versions and model route used, so it can be reproduced or investigated later.

All of this runs through the group's AI gateway, which handles model routing, budgets, caching and logging, while each company keeps its own prompts, data and users.

Pricing the report

We are cautious about stating specific prices in general articles, because prices change and differ by market. The principles matter more than the figures.

Price against the value of the decision, not the cost of generation. A relocation decision involves significant time and money; a clear, sourced report that saves hours of research is worth a meaningful fee. A reflective reading is a smaller, more personal purchase.

Keep the cost of generation well below the price. Section-by-section generation, caching of curated content and routing simpler sections to smaller models keep the gross margin healthy. See Cost discipline for AI products.

Offer one clear primary option. Too many tiers at the moment of decision slow people down. KeşifAtlası can offer one standard report per route; ZodiVela can offer a small number of report types clearly distinguished by content, plus credits or a subscription for regular users.

Avoid dark patterns. No fake discounts from an inflated "original" price, no countdown timers, no pre-ticked add-ons.

Refunds: a policy and a feedback loop

AI-assisted reports can occasionally be wrong or poor. A report may have a section that failed silently, contradict the person's answers, or — in KeşifAtlası's case — reflect a rule that changed between test and purchase. A refund policy should handle these fairly and quickly.

A policy that works for both companies:

• Clear grounds. A report is refundable if it is missing promised sections, contradicts the person's confirmed answers, contains a factual error against our own rules database, or was never delivered.
• Simple request. One form or email, no argument required for clear cases.
• Quick decision. A stated response time, kept.
• No refund for disagreement with a correct outcome. If the rules say a person does not currently meet a requirement, a correct report saying so is not a defect. We explain this before purchase so it is not a surprise afterward.
• Consumer rights respected. Local consumer law sets minimums in each market; our policy should meet or exceed them. This is a description of practice, not legal advice.

Every refund reason is tagged and reviewed. Refunds are one of the most honest signals a paid product gets. A cluster of "section missing" refunds points to a generation or validation bug; "didn't match my situation" points to the questionnaire; "expected a guarantee" points to pre-purchase copy. Refund rate per report type is one of the metrics we look at in 30/60/90-day checkpoints.

Worked example: KeşifAtlası

Imagine a graduate in Türkiye considering a skilled-work route in another country. They take the free test: eight to twelve short questions depending on their answers. The result says they look likely eligible for one route and not eligible on current answers for another, because they do not yet hold a job offer. Both reasons are shown in plain language, with the date rules were last updated.

Below the result they see what the paid report contains: a requirement-by-requirement breakdown for both routes, links to official sources, a document preparation checklist, a realistic timeline, what would change the second outcome, and a clear note that the report is informational and that authorities make visa decisions. They see a sample report for a fictional profile, the price in lira, and the refund policy.

If they buy, the report is generated from the same answers and rule-set version, section by section, validated and delivered as a web page and a download. If they have a question the rules cannot answer — say, about a previous refusal — the report offers a route to a person rather than a guess. See Human escalation in AI products.

Worked example: ZodiVela

Imagine someone who enters their birth date, time and place. The free reading gives a warm, well-written reflection on their sun, moon and rising signs, with a journalling prompt. It is complete in itself.

Below it they see the full chart reading: sections on relationships, work and creativity, personal growth and the year's themes, all written as reflection, each with prompts. There is a sample, a clear price, and a note that readings are for reflection and entertainment. Regular users can choose credits or a subscription instead of single purchases.

If they buy and a section arrives visibly broken — say, repeating another section — the refund is immediate, and the defect is logged against the prompt version that produced it.

Data in the funnel

A free test collects personal information from people who have not yet decided to become customers. That calls for care.

• Ask only what the result needs. For KeşifAtlası, every question maps to a rule. For ZodiVela, birth time is optional and explained.
• Separate test data from marketing consent. Taking a free test is not consent to marketing. If we want to email someone later, we ask separately and clearly. See Marketing consent vs product consent.
• Set retention for abandoned tests. Answers from people who never create an account or buy should not sit indefinitely. See Data retention and deletion.
• Measure the funnel without tracking people across the web. Conversion from test to report can be measured with first-party, aggregate analytics.

When the rules change between test and purchase

KeşifAtlası has a problem most report businesses do not: the thing being reported on can change. A person might take the free test on Monday, come back on Friday to buy, and find that a rule for their route changed on Wednesday.

We handle this explicitly rather than hoping it is rare. When a person returns to buy, the product checks whether the rule-set version for their route has changed since their test. If it has, they are told before payment, shown their updated free result, and asked to confirm. The paid report is always generated against the current rules for their intended timeline, and the report states which version it used.

The same logic applies after purchase. If a rule changes shortly after someone buys a report, the report does not silently change, because it records the version that produced it. What we can do is identify affected reports and, where the person has agreed to service messages about their report, let them know an update is available. That is a product decision with a consent question attached, not an automatic marketing email.

What we measure in the funnel

A funnel like this is easy to measure badly. Test completions and purchases alone tell you very little. The metrics we find useful:

• Test completion rate by question step, to find where people give up.
• Free result to report page — the share of people who look at what the paid report contains.
• Report page to purchase, split by outcome. People with a "needs review" outcome behave differently from those with a clear result.
• Refund rate and reasons per report type and per prompt version.
• Validation failure and fallback rate per report section, which predicts refunds before they happen.
• Return visits within a few months, especially for ZodiVela, where a good first report often leads to a second.

None of these require tracking individuals across other sites. Keeping measurement first-party and aggregate is a choice that fits the sensitivity of both products.

Common mistakes

Paywalling the answer. A free test that withholds the result destroys trust and invites complaints.

A paid report that disagrees with the free result. If they are built from different logic, one of them is wrong. Build both from the same source.

Vague report contents. "Get your full personalised report" is not a description. List the sections.

Hiding the refund policy. People who can see a fair policy are more willing to buy, not less.

Ignoring refund reasons. Each refund is a free bug report.

Retargeting everyone who took the test. It feels invasive, and for sensitive categories like relocation it can be.

Summary

A free test to paid report funnel works when the line between free and paid is honest. The free result must answer the headline question on its own; the paid report adds depth, structure, sources and next steps, built from the same verified data so the two can never disagree. At KeşifAtlası that data is a versioned rules database; at ZodiVela it is calculated chart placements or drawn cards paired with curated meanings. Trust is earned before payment with a clear list of contents, a sample report, the full price, delivery time, what the report is not, and a visible refund policy. Reports are generated section by section, validated and versioned, with fallbacks for failures, and every refund reason feeds back into the product.

Questions and answers

What is a free test to paid report funnel?

It is a model where people take a short free assessment and receive a useful result, then can choose to pay for a detailed personal report. KeşifAtlası and ZodiVela both use versions of this model.

What is free and what is paid in KeşifAtlası?

The eligibility test and its headline result are free. The paid report adds a detailed breakdown by requirement, sources, a document preparation list and next steps, all grounded in the same verified rules.

How should refunds work for AI-generated reports?

Refunds should be straightforward when a report fails to deliver what was promised, such as missing sections or content that contradicts the person's answers. Each refund reason is logged so the product can be fixed.

Published by Oryvelon, a digital company builder · About the group · Our companies · More in Marketplaces & Consumer Products

NextWhy a services company lives inside a company builder →