Session #46

Sharp niche: a live preview with your shop name, real Fire TV and iOS apps, and one flat price make it easy to try.

Suggestion: Add a few named cafes using it, with a photo of their board, near the pricing section.

The interactive staff-to-TV preview, concrete device support and single location price make adoption easy to understand.

Suggestion: Add a short counter-service pilot report documenting setup time and changes in customers asking whether orders are ready.

Laser-focused positioning around filling Square's missing customer-facing order screen, backed by interactive board previews and real App Store and Fire TV links.

Suggestion: Add one or two named cafe or bakery customer quotes with photos of their actual counter TVs to prove real-world reliability.

Real Fire TV and iOS apps, register integrations and a live board preview make the simple counter workflow immediately credible and easy to trial.

Suggestion: Add a short setup video showing a real Square order travelling from checkout to Ready on both staff phone and television.

Square, Clover and Toast connections, one-tap Ready and a single per-location price address counter crowding directly.

Suggestion: Add photos or a short video from a real counter during service to prove readability and staff workflow.

The live sample board shows exactly what customers see on the TV, making the product instantly understandable.

Suggestion: Name one real location or customer using the board to add social proof in a one-player niche.

Live in-browser board previews and the explicit Square gap make the product feel finished and the niche obvious.

Suggestion: Add one named shop using it with a photo of their real counter TV to convert the strong demo into social proof.

The live TV board, app downloads and Square/Clover/Toast integrations are concrete and easy to understand, making the offer feel immediately usable.

Suggestion: Show a short setup video and a sample board with real order names, so buyers can see the counter experience before the trial.

Crystal-clear pitch, a live no-account board preview, real Fire TV and iOS apps, and a simple per-location price; the Square gap it fills is genuine.

Suggestion: Show one or two named customer locations or quotes, as the page currently relies entirely on sample data.

Solved a real and obvious pain point with a live demo, fourteen board styles and a no-card trial.

Suggestion: Add one short customer testimonial with a name and venue to back up the strong demo.

Multi-broker coverage with audit trail and a free Kafka edition is real, shown with dated releases and a video.

Suggestion: Add a short list of teams running it in production near the download button.

A recent release, walkthrough and explicit licensing support the differentiated promise of consistent controls across four broker technologies.

Suggestion: Publish a reproducible audit-verification example showing a destructive operation, its recorded reason and detection of a modified audit record.

Unifying Kafka, Redis, RabbitMQ, and Artemis under one self-hosted control plane with transparent per-installation term pricing is a standout offer for engineering teams.

Suggestion: Replace the abstract wireframe diagram in the hero section with the actual multi-broker dashboard screenshot currently sitting further down the page.

Detailed console screenshots, a walkthrough, current release notes and precise multi-broker controls support the operational claims far better than generic infrastructure marketing.

Suggestion: Add a documented production case study with deployment size, migration effort and audit outcomes to complement the strong feature demonstration.

One self-hosted permission, guardrail and audit model across Kafka, Redis, RabbitMQ and Artemis is a clear operational differentiator.

Suggestion: Put a short guided product tour with real broker data beside the download, before the topology diagram.

An active source repo, a dated 1.4.0 changelog and a docker compose quickstart prove this is a maintained, real product.

Suggestion: Link the public repository and roadmap from the top navigation so visitors can verify activity in one click.

The multi-broker fragmentation argument, real dashboard screenshots and active repo make this a credible self-hosted console.

Suggestion: State the Community edition's Kafka-only limit next to the download button so the free path and the paid upsell are unambiguous.

The multi-broker scope, production guardrails and tamper-evident audit trail are clearly documented, and the commercial term licence is unusually transparent.

Suggestion: Add a hosted demo or sandbox link so evaluators can try the console without standing up Docker Compose.

The multi-broker one-console pitch is a real differentiator against Conduktor and KafkaHQ, backed by a video walkthrough, dated 1.4.0 release and an honest term-licence pricing page.

Suggestion: The dark, dense homepage buries the free Community download; put a prominent Kafka-only free tier pitch higher for teams not ready to buy.

Concrete, technically specific product with a free Community edition and a transparent one-time commercial price.

Suggestion: Add a short customer logo or production reference to reduce the perceived risk of a new self-hosted tool.

The salon booking story and own-SIM texting with no per-text fees make a strong, concrete case.

Suggestion: Clarify in the hero that AI booking costs $94 total, since $47 appears both as base and add-on price.

The salon booking demonstration connects a costly missed-enquiry problem to clear pricing and a distinctive own-number workflow.

Suggestion: Add a carrier compatibility checklist beside the Android requirement, covering automated messaging restrictions, phone uptime and fallback behavior.

Routing automated SMS and AI booking through an existing Android phone and carrier plan eliminates per-message markups and keeps the business's familiar number.

Suggestion: Explain carrier fair-use limits and any Android background-running requirements upfront on the homepage so buyers know the technical trade-offs of SIM-based texting.

The after-hours salon booking demonstration, own-number delivery and interactive payback calculator connect a clear operational problem to an unusually tangible solution.

Suggestion: Label the Trustpilot quote's Inst8 connection beside the review, and add an Activ8-specific customer example with measurable booking results.

The after-hours salon booking demo makes the value tangible, with calendar checks, reminders and no per-text fees from Activ8.

Suggestion: State the full monthly cost with the AI Assistant in the hero price box, not as a separate add-on.

The recorded in-app booking demo plus sourced stats on missed leads makes the ROI case unusually concrete.

Suggestion: State the iPhone limitation (WhatsApp or US/CA number only) in the hero copy, not just in a feature card.

The interactive booking demo, real Trustpilot quote and own-number no-per-text-fee model make the value concrete and credible.

Suggestion: Lead the ROI calculator with a default that matches the salon example so the payback math lands without the visitor editing inputs.

The after-hours booking demo and own-phone model make the value clear, though the price is high for a one-person business.

Suggestion: Add a smaller starter tier or a clearer payback calculator for solo businesses before the first paid month.

The own-SIM texting angle cuts costs versus SimpleTexting and Podium, and the site proves the workflow with a step-by-step replay and honest pricing including the AI add-on.

Suggestion: Surface more real customer proof beyond one Trustpilot quote, since the story rests entirely on one persona and one review.

Persuasive scenario-based demo and a clear cost story (no per-text fees) that addresses a real pain for small operators.

Suggestion: Add an Android setup screenshot or short video so non-technical owners trust the QR-code install step.

Unusually honest security copy, including what it cannot do, and a duress code set it apart from typical vault apps.

Suggestion: Link a terms of service page from the footer beside the privacy policy, since users store sensitive files.

Local-only storage, explicit recovery mechanics and continued export after cancellation form a coherent privacy-focused offer.

Suggestion: Add a dated security-review status beside the encryption explanation, distinguishing independently verified protections from implementation claims.

Exceptional trust-building through plain-English security architecture, honest explanations of what the app cannot hide, and a promise never to hold photos hostage.

Suggestion: Add a Terms of Service link alongside the Privacy Policy in the footer, and display the App Store rating or review count near the download button.

Specific Secure Enclave details, honest capability limits and permanently free export make this privacy product substantially more trustworthy than typical vault claims.

Suggestion: Add an independent security review or link the technical design to reproducible verification steps on the Security page.

The decoy and duress-code concept is distinct, while local encryption, recovery words and free export are explained with unusual honesty.

Suggestion: Link the App Store listing and its Data Not Collected label directly beside the download button.

The duress-code decoy vault plus on-device-only encryption is a genuinely distinct answer to forced-unlock situations.

Suggestion: Add a terms-of-service page; the footer links privacy but no terms page was found.

The plain-language security page that states what the trapdoor cannot do is unusually honest and builds real trust.

Suggestion: Surface the App Store Data Not Collected label and Secure Enclave detail higher on the homepage where first-time visitors see them.

The decoy vault and no-account encryption are unusually clear and well documented, making it credible for a privacy-sensitive iPhone app.

Suggestion: Add a visible terms page and a short App Store review summary to close the remaining trust gaps.

The decoy and duress-code angle is genuinely different from KeepSafe and Private Photo Vault, and the site is unusually honest about what the product cannot do.

Suggestion: Explain why a buyer picks this over the iPhone's built-in Hidden album lock in the first screen, since that is the real competition.

Stands out by clearly stating both what it does and what it cannot do, with a privacy stance that matches the product.

Suggestion: Add a short screen-recorded demo of the duress-code flow so the trapdoor idea is immediately visible.

Working generator in the hero and a clear promise that printed codes never die, though the page sprawls across many products.

Suggestion: Move Spot Live guest requests to its own landing page so the homepage focuses on the generator.

The immediate generator and explicit cancellation behavior address practical printing concerns, while QR Studio adds tangible design depth.

Suggestion: Qualify the editable-code permanence promise with service-dependency limits beside the printed-code guarantee.

Putting a live generator right in the hero with an explicit guarantee that printed codes never die immediately addresses the biggest user fear in this category.

Suggestion: Separate the Spot Live guest request tool into its own dedicated landing page or clearer navigation tab so the homepage stays focused on QR creation.

The usable no-account generator, print-ready exports and never-die printed-code promise address practical QR concerns directly, while free dynamic codes broaden appeal.

Suggestion: Split the crowded navigation into Create, Guest requests and Resources so first-time visitors can find the generator's paid upgrade path.

The working generator is immediate, and the promise that printed dynamic codes lock rather than die is a strong differentiator.

Suggestion: Simplify the top navigation by grouping Spot Live, Labs and Studio under one secondary menu.

A working generator on the homepage and a written never-die guarantee for printed codes are concrete, checkable promises.

Suggestion: Reconcile the $5 per month tagline with the $4 Starter plan shown on the pricing page.

The working on-page generator and printed-code-never-dies promise are solid, but the QR space is heavily served.

Suggestion: Lead with the Spot Live guest-request flow, which is the least commoditized feature, instead of burying it below the generator.

The free generator and editable codes are clear, and the print-ready design tools give it more depth than a commodity QR tool.

Suggestion: Make the free-to-paid upgrade boundary visible on the generator itself, so users know what locks before they print.

A working generator right on the homepage, honest free tiers, a printed-code guarantee and clear pricing make this unusually trustworthy for a QR-code market full of dark patterns.

Suggestion: Sharpen the positioning against QRTiger and Uniqode on the homepage, since the never-die codes guarantee is stronger than the generic headline.

A thoughtful, privacy-aware generator with a generous free tier and a clear promise that printed codes never die.

Suggestion: Add a one-click Google review and UPI/Pix template on the homepage so first-time visitors land on a finished code.

Flat-versus-directed audio samples show the steering idea well, but a large blank area appears below them in the page capture.

Suggestion: Fix the empty lower half of the homepage so the voice library and steps sections render on load.

Flat-versus-directed audio examples demonstrate the core benefit, though the captured page leaves a large blank area below them.

Suggestion: Reconcile the pricing claim that every plan includes commercial rights with the homepage statement restricting commercial use to paid plans.

Letting visitors compare flat reads against bracket-directed reads side by side on the homepage is a great way to demonstrate voice steering.

Suggestion: Add clear company ownership details and a physical business address in the footer to build stronger commercial trust around voice cloning rights.

Flat-versus-directed audio comparisons demonstrate the core advantage clearly, while free daily generations and explicit commercial licensing make experimentation low risk.

Suggestion: Add voice-cloning consent requirements and misuse safeguards beside the cloning controls, then link the complete policy from the playground.

Voice steering is demonstrated clearly with flat versus directed reads, 260 voices and an immediate free playground.

Suggestion: Add named creator testimonials with listenable finished videos beside the voice steering demos on the homepage.

Voice steering in plain English, shown live in the hero demo, is a real differentiator among AI voice tools.

Suggestion: Add named creator customers or case studies under the 'Hear what people make' section to back the examples.

The voice-steering flat-versus-directed examples are a compelling, concrete hook in a crowded text-to-speech market.

Suggestion: Add a side-by-side audio quality claim or blind test against the leading alternative to justify switching from established tools.

Voice steering and free daily generations make it easy to test, but the crowded AI voice market means the page must prove quality and licensing.

Suggestion: Show a side-by-side comparison of the same script in several voices with a downloadable commercial license example.

The voice-steering demos with flat-versus-directed comparisons are a real, testable feature, but the overall product is a close follower of ElevenLabs and Play.ht at lower prices.

Suggestion: Make steering the headline everywhere, not just a section, and show a side-by-side price comparison with ElevenLabs for the same output volume.

Clear demo of the sound-tag steering feature with real audio samples and a transparent credit-based pricing page.

Suggestion: Add a published latency or quality comparison versus ElevenLabs so buyers have a benchmark.

Transparent usage pricing and real API endpoints, but the hero says e-signatures while the name and listing promise HTML to PDF.

Suggestion: Rewrite the hero to state both PDF generation and signing via one API, matching the product name.

Concrete signature safeguards and detailed API allowances make the combined document workflow credible.

Suggestion: Add a pricing example showing the total charge for generating and signing 100 documents, including conversion and signature allowances.

Combining HTML-to-PDF conversion endpoints with e-signature workflows and charging only for completed signatures is a practical bundle for document-heavy apps.

Suggestion: Update the homepage hero headline to mention both PDF generation and e-signatures, matching your API-first positioning and pricing page.

PDF generation, processing and signatures share clear usage pricing, but the signature-first homepage gives developers little immediate evidence of the API workflow.

Suggestion: Put a runnable HTML-to-PDF request and response beside the hero, with a separate e-signature path for business buyers.

Pricing, audit trails and compliance claims are concrete, but the homepage pivots from developer PDF API to business signatures.

Suggestion: Lead with one audience and workflow, then move the secondary signature or API offering into its own clear section.

Charging only for successfully signed documents, with unlimited team members, is a clear and fair pricing stance.

Suggestion: Put copy-paste SDK snippets for JavaScript, Python and PHP directly on the homepage next to the API claim.

Clear usage-based pricing and named G2 reviews help, but PDF and e-sign APIs are a deeply crowded category.

Suggestion: Open with a runnable code snippet and response for the single POST request the review praises, instead of the marketing hero.

Combines PDF generation and e-signature in one API, but the homepage leads with signatures and hides the PDF-generation breadth.

Suggestion: Make the first screen name both PDF generation and e-signature, then show a developer code sample and the API endpoints.

Very complete product story with docs, compliance badges and a transparent usage-based pricing table, but it is a crowded e-signature and PDF-API space where it looks much like DocRaptor plus DocuSign.

Suggestion: Lead with one concrete reason to switch from incumbents, such as a live comparison of your signing flow against a named alternative.

Clear API docs and pricing, but the market is crowded with established alternatives and the product lacks a memorable differentiator.

Suggestion: Lead with one technical proof point (benchmark on a hard HTML job) instead of generic industry sections.

Charming, focused idea with clear $12 per race pricing, but it serves an occasional need.

Suggestion: Show a real finished race story link above the fold so visitors see the replay before signing up.

Account-free contributions and route-based replay offer a focused keepsake, with unusually explicit storage and retention limits.

Suggestion: Add a playable sample story showing the route replay, contributor upload and owner approval before visitors create an account.

Thoughtful privacy touches like automatic GPS stripping and 200-metre route trimming show deep empathy for runners sharing their race day.

Suggestion: Embed a live, clickable example of a finished race replay story on the homepage so runners can experience the map timeline before signing up.

Private contribution links, route privacy controls and per-race pricing fit families unusually well, though the infrequent use case limits recurring value.

Suggestion: Add one complete public example story with its route replay, so visitors can experience the finished keepsake before creating a race.

The private link, no-account uploads and route timeline solve a specific race-day sharing problem very clearly.

Suggestion: Show a complete sample race story with its map, timeline and replay above the pricing section.

Route replay with music and GPS removal on public photos show real care for spectators' privacy.

Suggestion: Name the company or team behind RaceTale on the homepage to match the privacy promises.

Warm, specific copy and a clear one-link flow, but the inactive source repo and once-per-race fee raise longevity doubts.

Suggestion: Show two or three real published race stories with permission so the emotional payoff is visible before anyone pays twelve dollars.

The private link and route-privacy tools are thoughtful, but the per-race price may be hard to sustain for a narrow occasion.

Suggestion: Add a family or club bundle for multiple runners and show a completed story without the RaceTale mark.

A charming, privacy-respectful product with a clear $12 one-off price and no-signup friends, but race days are infrequent and one-off purchases make recurring revenue unlikely.

Suggestion: Add an annual or club plan so marathoners, clubs and race organisers give you repeat revenue instead of one race at a time.

Genuinely differentiated for a real moment (race day) with sensible privacy defaults, though the one-time $12 per race is a niche revenue model.

Suggestion: Show one finished example story on the homepage so visitors grasp the end product before signing up.

Clear upload-a-chart pitch with a no-account demo, but AI trade plans at $35.99 a month face a skeptical, crowded market.

Suggestion: Publish a dated log of past scans with their outcomes so traders can see how reads performed over time.

The upload demo lowers trial friction, but unspecified scan allowances and inconsistent three-engine claims undermine the paid offer.

Suggestion: State exact scan allowances for each plan and reconcile the universal three-engine claim with Elite's additional analyst engine.

Showing when the three AI engines disagree and enforcing a 1.5R quality floor is much more credible than promising guaranteed trading signals.

Suggestion: Replace vague scan allowance descriptions like 'a little each day' and 'far more' on the pricing page with exact daily and weekly scan numbers.

The free full-read demo reduces trial friction, but consensus labels and hardware-style engine names do not demonstrate dependable chart or trade analysis.

Suggestion: Replace engine-brand claims with dated sample scans, input screenshots and transparent outcome tracking, including failed reads and cases returning no setup.

The screenshot workflow and three-engine consensus are clear, but trade-plan quality is asserted without verifiable performance evidence.

Suggestion: Publish a dated set of sample scans with outcomes and failures so traders can assess read quality before paying.

Three-engine consensus reads with levels drawn from the chart's own price axis are demonstrated concretely in the demo scan.

Suggestion: Publish a changelog and any track record of past reads so traders can verify the engines over time.

The three-engine consensus and honest neutral verdicts are a real differentiator, and the live AAPL read shows the product working.

Suggestion: Add a short accuracy or backtest note explaining how often the consensus read matched later price action, to earn trader trust.

Clear multi-engine chart read with a no-account demo, but the trading accuracy claims are not backed by visible performance evidence.

Suggestion: Publish a transparent accuracy or backtest page showing how the consensus calls performed on real past charts.

The consensus engine and honest weak-setup messaging are good, with a real free tier, but no named team and the inherent unreliability of AI price-level reads make this a hard tool to trust with money.

Suggestion: Publish an accuracy audit with real historical examples readers can verify, and name the people behind the product.

Strong demo flow and a free tier, but the product sells discretionary AI signals as a trade aid without disclosing win rates or backtests.

Suggestion: Add a results page with audited historical read accuracy so traders can judge the signal before paying.

The PO-to-journal-entry walkthrough is concrete, but every screen is marked illustrative and no customers or pricing appear.

Suggestion: Show at least one named customer and a starting price or pricing range next to the demo button.

The foreign-exchange reconciliation example explains the value clearly, but illustrative records provide limited assurance of production readiness.

Suggestion: Publish a recorded sandbox walkthrough completing the illustrated purchase, payment and journal workflow in the actual application.

Walking through a single €9,000 laptop purchase order all the way to FX loss journal entries explains unified accounting better than any feature list.

Suggestion: Publish starting price tiers and list supported banking and tax jurisdictions so finance teams can qualify themselves before booking a demo.

The illustrated purchase-to-journal workflow makes an ambitious unified finance platform feel concrete, but hidden pricing and absent customer proof weaken buying confidence.

Suggestion: Publish starting prices, implementation requirements and two named customer examples beside the demo request.

The single-record story from purchase order to journal is detailed, but illustrative screens and demo-only access leave adoption unproven.

Suggestion: Publish starting prices and one named customer example before asking finance teams for a demo.

Every figure on the page is labelled illustrative, with no pricing page, no docs and no named team, so trust is thin.

Suggestion: Publish a pricing page and name the company, team and customers; right now buyers cannot tell cost or accountability.

The unified-record story is clear, but every screenshot is labelled illustrative and there is no pricing, so it reads as a concept.

Suggestion: Publish at least a starting price band and one real customer record or case so the platform looks shipped rather than mocked up.

The unified finance story is coherent, but the illustrative dashboard and missing pricing make it hard to assess whether the product is real.

Suggestion: Publish real pricing and a live product tour or demo screenshots instead of illustrative records.

The unified-ledger story is told well with concrete tie-out examples, but every screenshot is labelled illustrative, there is no pricing and no visible team, against entrenched rivals like Xero and QuickBooks.

Suggestion: Replace the illustrative mockups with real product screenshots or a live sandbox, and show the team and customers behind the platform.

Exceptionally clear walkthrough of how one record ties purchasing to the close, though pricing is gated behind a demo.

Suggestion: Publish at least a starting price band so small teams can self-qualify before booking a demo.

A tidy set of free guitar utilities funded by affiliate links, though the scripture songwriting angle muddles who it is for.

Suggestion: Add a one-line explainer that Songwriter Suite targets worship songwriters so general guitarists are not confused.

The task-based tool directory is useful, with affiliate support disclosed and no signup required.

Suggestion: Place the tuner and transposer links above the large Songwriter Suite feature so visitors can reach common tasks immediately.

A clean, well-organized hub of practical guitar and songwriting calculators that avoids clutter and clearly discloses its Amazon affiliate model.

Suggestion: Embed one interactive mini-tool, such as the tap-tempo delay calculator or chord transposer, directly on this directory page so visitors get instant value.

The practical tool chooser, no-signup access and disclosed affiliate funding make this a useful, honest collection rather than a thin directory.

Suggestion: Embed the tuner and chord transposer directly on this page, letting visitors complete common tasks before browsing the remaining utilities.

A broad set of genuinely free, no-signup guitar tools is easy to scan, with a helpful guide to choosing one.

Suggestion: Move the guitar tuner and chord transposer above the featured Songwriter Suite for visitors arriving for a quick tool.

Twelve specific free tools with a 'which tool do I need' map are useful, but ads and affiliate links are visible.

Suggestion: Add a screenshot of one tool in action, like the tuner, so visitors see the product rather than a list.

A genuinely useful free toolkit with no signup, but the tools are commodity and the page leans on ads and affiliate links.

Suggestion: Promote the Songwriter Suite as the headline product with a working in-page demo, since the utility tools alone do not stand out.

The free tool set is broad and clearly labelled, but ads and affiliate links are the only visible funding and may limit growth.

Suggestion: Reduce the privacy-consent and ad clutter on the first screen and add a clearer 'why this is free' note.

A tidy, honest collection of genuinely useful free tools with transparent Amazon affiliate funding, but most utilities duplicate what Ultimate Guitar and free web calculators already offer.

Suggestion: Feature the Songwriter Suite as the differentiator up top and demote the commodity calculators that competitors also cover.

A practical collection of well-scoped free tools with a clear Amazon Associate funding line, though the page mixes tools with content marketing.

Suggestion: Move the embedded Amazon gear links into a separate section so the tool list stays focused.

Honest about being simulated, but the counting 76,300 figure and phone-number signup weaken confidence.

Suggestion: Drop the phone field from account creation and put a contact email in the header or footer.

Simulation disclosures are clear, but large persona counts lack visible evidence that they improve useful predictions.

Suggestion: Publish a benchmark comparing simulated objections with actual customer interviews, explaining errors and whether larger persona counts improve results.

Upfront disclaimers that responses come from AI personas rather than real buyers keep the promise honest, and one-time pricing fits occasional concept checks.

Suggestion: Stop redirecting the Pricing nav link to a $149 signup gate where phone numbers are required, and show a public comparison table of all tiers instead.

The site clearly labels its results as simulated and offers a free sample, but impressive participant counts cannot establish that the feedback predicts customers.

Suggestion: Publish side-by-side comparisons of simulated reports and real customer interviews, including where the simulations missed important objections.

The simulated focus group is easy to try and honestly labelled, but AI personas cannot evidence real buying intent.

Suggestion: Show a full sample report with its persona generation method and limits directly beside the free test button.

The site is honest that results come from AI personas, not real people, which caps how much the reports can prove.

Suggestion: Add a contact page and support email so buyers can ask questions before paying one-off fees.

Sharp positioning and a free snapshot, but the simulated-not-real caveat caps how much a buyer can trust the verdict.

Suggestion: Show one full sample PDF report inline so visitors see the actual objections and validation steps they would pay for.

Honest that results are AI-simulated, but the lack of contact and team details weakens trust in a paid research tool.

Suggestion: Add a named team, contact page, and a real example report showing how simulated reactions map to validation decisions.

Honest that results are simulated, and the free snapshot is a genuinely low-friction way in; but there is no named team or contact page, and simulated reactions are weak validation evidence.

Suggestion: Show a named team or company and a contact route, and publish one full sample report link directly on the homepage.

Clear value proposition and a polished page, but the product is AI-simulated reactions, not real market data, and the disclosure sits in the footer.

Suggestion: Surface the simulated-not-real caveat in the hero so first-time visitors understand what they are paying for.