Session #51

Clear agent-operated hosting pitch with transparent usage-included pricing, YC backing and a named founder testimonial.

Suggestion: Show a short real deploy recording in the empty dashboard mockup above the fold instead of the 'Waiting for first deploy' placeholder.

Concrete deployment, backup and incident-handling details make the production-autopilot promise more credible than a generic infrastructure pitch.

Suggestion: Add a worked monthly bill showing compute, database and bandwidth charges beyond the included cloud credit.

Letting developers paste a single skill URL into their coding agent to provision AWS infrastructure is a sharp, well-executed hook.

Suggestion: Clarify the relation between your open-source library and managed cloud on the homepage so developers know what runs locally versus on your servers.

Concrete deployment, recovery and regional infrastructure details pair well with transparent usage-inclusive pricing and substantive founder accounts.

Suggestion: Link a complete sample application repository and deployment walkthrough directly beneath the coding-agent command.

Production cloud on autopilot is sharply positioned for AI-era builders, with concrete regions, backups, monitoring, pricing and a coding-agent deploy path.

Suggestion: Show one named app with real uptime, deploy history and monthly usage cost on the homepage to substantiate the autopilot claims.

Production-cloud-on-autopilot story is concrete, with Y Combinator backing, an active repo and clear tiered pricing.

Suggestion: Add a public changelog and visible customer logos to strengthen evidence of traction beyond the text line.

YC backing, named customers and a concrete autopilot story make this a credible production backend platform for developers.

Suggestion: Show one real deployed app's dashboard and metrics rather than only schematic diagrams to prove the autopilot claims.

The evidence is unusually complete: a real config file, a live status page, named regions and customer quotes, backed by YC and an active open-source repo.

Suggestion: Reconcile the no-code wording in the description with a homepage that now speaks to coding agents, and add a public contact route besides support.

YC backing, an active open-source repo, region-level infrastructure detail and a specific 150k-line founder testimonial make the production claims credible.

Suggestion: Clarify on the homepage how Modelence differs from Lovable or Supabase, since 'production cloud on autopilot' needs one contrast sentence.

The 'deploy via skill.md into your coding agent' pitch is a clean, specific positioning that matches how many teams actually ship today.

Suggestion: Surface real production status and a public changelog on the home page so the 'autopilot' promise is backed by evidence, not just screenshots.

A live agent number and a no-signup agent builder let visitors test the product directly, backed by named local customers.

Suggestion: Put the one-line value prop above the 'Say yes' video so the first screen explains the product.

A callable agent, signup-free website demo and named local customers make the missed-call proposition unusually tangible.

Suggestion: Move the business-number headline and agent demonstration above the large introductory video.

Letting visitors call a live number or generate a temporary agent from their own website without signing up is an unbeatable product demonstration.

Suggestion: Replace the vague 'Say yes.' video thumbnail text with a caption showing the live call transcript so visitors who do not click play still get the point.

A callable agent, named customer stories and a genuinely usable free tier make the missed-call proposition unusually tangible.

Suggestion: Add a short privacy explanation covering call recordings, transcripts and customer data retention near the agent demo.

A live agent number, website-built trial agent, named local testimonials and clear free-to-premium limits make the missed-call value easy to test.

Suggestion: Add a short recorded before-and-after call example with transcript beside the live agent number so cautious owners hear the quality first.

Clear AI phone agent story with named customer quotes and a callable demo number; the free tier is genuinely usable.

Suggestion: Add a short product video of the agent answering a real call, placed above the fold on the homepage.

Outstanding clarity and proof - a live number to call and named local customers make the AI answering agent feel real and buyable.

Suggestion: Surface the free-tier limits (30 minutes, 100 replies) on the homepage so prospects know exactly when they hit the paywall.

Named local businesses with real quotes and a try-it-now agent builder make this one of the more believable AI phone tools on the page.

Suggestion: Fix the 9.99 starting price quoted in the description so it matches the 29.99 Premium plan actually shown on the pricing page.

A live demo number, a build-your-agent box from your website, and named local customers make this the most convincing product proof on any page here.

Suggestion: State who is behind Neuron and how the AI handles sensitive caller data, since callers will not know an agent is answering.

Letting visitors text the app a link and call a live agent on the homepage is a more convincing demo than screenshots alone.

Suggestion: Add a short example transcript of the agent answering a real caller so the 'reads your site and answers' claim is shown, not just described.

Honest security copy, including what it can't do, and a fair never-held-hostage pricing policy build strong trust.

Suggestion: Link an independent security review or open technical write-up from the security section.

Clear security limits and free export after cancellation make the local encrypted vault proposition notably respectful of user control.

Suggestion: Publish an independent security assessment covering key storage, recovery and the decoy mechanism.

Explaining both the Secure Enclave architecture and what the app cannot do builds rare credibility in a category full of dark patterns.

Suggestion: Add a short video clip showing the transition into the decoy vault so users can see how natural the duress flow looks.

The duress-code decoy, local encryption explanation and guaranteed export rights address privacy concerns with unusual specificity and restraint.

Suggestion: Publish a plain-language security architecture and independent review status on the Security page.

Honest limits, no-account on-device encryption, free export and a clear duress-code decoy make this privacy product exceptionally trustworthy and distinct.

Suggestion: Link an independent security review or detailed encryption specification from the hero security section to support the Secure Enclave claims.

Honest security page that states plainly what the vault cannot do, plus a no-account design and clear pricing.

Suggestion: Add an Android roadmap or timeline to answer the most obvious question visitors have after iPhone-only.

Exceptionally honest trust building - a what-it-cannot-do page, Secure Enclave detail and a never-held-hostage export guarantee.

Suggestion: Add an Android or cross-platform roadmap note, since iPhone-only limits the audience for a privacy tool people want everywhere.

The duress-code decoy is a real differentiator, and the security page states plainly what the app cannot do instead of overselling.

Suggestion: Add the missing terms page and state on the pricing page how a one-off lifetime licence funds ongoing development.

The decoy and duress-code angle is a real differentiator, and the honest 'what it can't do' framing plus free export build rare trust.

Suggestion: Add App Store rating and review count near the download button to convert the strong trust signals into installs.

Trapdoor's honest 'what it can't do' page and clear separation between code, duress code and recovery words is rare for a privacy app.

Suggestion: Surface a public security audit or attestation so trust doesn't rely solely on the maker's own security explanation.

A working widget demo, clear plans and real workspace screens make a niche offer easy to evaluate.

Suggestion: Add one named store using the widget with its trade-in volume on the homepage.

The embedded widget and real workflow screens connect customer estimates to inspections, approval and payout with unusually clear plan limits.

Suggestion: Add a short walkthrough showing price-list import and how condition rules change a sample device offer.

Embedding an interactive valuation widget in the hero and walking through the four-step inspection workflow leaves zero doubt about how the product works.

Suggestion: Display your company registration details and physical address in the footer to build stronger trust with international merchants handling high-value devices.

Real workflow screens, platform guides and precise limits make the complete trade-in operation easy to evaluate before registering.

Suggestion: Add a named retailer case study showing monthly request volume, revised-offer rates and time saved.

The interactive widget, real workspace screens, device catalogue and zero-commission pricing make a narrow buyback workflow unusually tangible.

Suggestion: Add a named store result showing monthly requests, completed buybacks and payout value from using the widget.

Widget demo, real workspace screenshots and an explicit 0% commission make the offer concrete and easy to trust.

Suggestion: Show two or three named customer stores using the widget, with their monthly request volumes.

A live widget demo, real workspace screenshots and 0% commission make this a clear, trustworthy fit for electronics buyback sellers.

Suggestion: Add a customer story with buyback volume numbers to show the widget actually drives trade-ins, not just collects requests.

The workflow from estimate to handover is shown in labelled real screens, and the 0% commission and no-card trial remove most buying friction.

Suggestion: Show at least one full-size screenshot of the widget embedded on a mock storefront so buyers can picture it on their own site.

An interactive widget demo, real workspace screenshots, honest plan limits and a two-line install make this unusually complete for a niche tool.

Suggestion: Add one named customer store using the widget live, since every screenshot today is demo data.

Showing a live widget alongside real workspace screenshots on the same page is an unusually effective way to prove the product works.

Suggestion: Add a short ROI example (e.g. monthly requests to recovered revenue) so a non-technical shop owner can see payback before the trial.

Detailed pricing with per-endpoint counting is strong, but the hero leads with e-signatures while the listing promises PDF generation.

Suggestion: Make the hero mention both PDF generation and signatures so API buyers recognise the product.

Signature verification, audit trails and explicit API operation pricing give the combined document workflow useful substance.

Suggestion: Add a complete code example that generates a PDF, sends it for signature and retrieves its audit record.

Charging only for completed signatures and detailing exact API endpoints on the pricing page makes the offering transparent and developer-friendly.

Suggestion: Unify the homepage hero message to highlight both HTML-to-PDF generation and electronic signatures, rather than burying the PDF API halfway down the page.

Detailed documentation, transparent usage pricing and signing safeguards make a broad document platform credible despite intense competition.

Suggestion: Lead with the unified API workflow and show a code sample above the fold, rather than opening as another e-signature service.

Clear signature workflow, GDPR and eIDAS signals, dashboard visuals and transparent usage pricing make the combined PDF and signing offer easy to trust.

Suggestion: Put a live API example and one-click PDF generation demo above the signature testimonials to prove the developer claim.

Transparent usage-based pricing with exact overage rates and listed API endpoints makes the product easy to evaluate.

Suggestion: Add a public changelog and a no-card sandbox key so developers can run one conversion immediately.

Combining PDF generation with legally binding e-signatures and audit trails is a coherent, well-documented developer offering.

Suggestion: Lead with the API and a code snippet in the hero, since the signature-first hero buries the developer-first positioning.

The pricing page is unusually precise, listing every counted endpoint and overage rate, which makes the per-conversion model easy to trust.

Suggestion: Put a working code sample or sandbox response next to the API section on the homepage so developers can see the single POST before signing up.

Transparent usage pricing, real docs, compliance badges and endpoint-level FAQ detail make this unusually easy to trust for an API product.

Suggestion: Sharpen the homepage positioning: it leads with e-signatures against DocuSign-class rivals while the differentiated PDF API is buried below.

The pricing page is unusually transparent about what counts as a conversion and what overage costs, which is exactly what API buyers want.

Suggestion: Move the generated-PDF capability higher on the homepage instead of burying it under e-signatures, since it is the more common developer entry point.

A published real report is strong proof, but the pricing page shows AGPL licensing rather than research plan prices.

Suggestion: Put research-platform credit pricing on the pricing page, separate from open-source licensing.

A published research run and passage-level inspection provide strong evidence, but the supplied pricing page concerns software licensing rather than research subscriptions.

Suggestion: Link the trial disclosure directly to research subscription prices, credit costs and the exact post-trial charge.

Publishing an unedited, inspectable research run directly on the homepage proves the quality of your cited synthesis better than any marketing claim.

Suggestion: Align the pricing page with the homepage by clearly listing the credit costs and monthly SaaS plans alongside the open-source commercial licensing.

The published investigation and passage-level citations demonstrate a meaningfully more inspectable alternative to conventional AI research answers.

Suggestion: Separate research subscription pricing from StateFrame commercial licensing so buyers can understand the actual product cost.

Cited passages, graded sources, gaps and a real published report differentiate it strongly, though the pricing page focus on open-source licensing confuses research costs.

Suggestion: Replace the licensing-heavy pricing page with clear research-run pricing by Lite, standard and Deep tiers before the trial signup.

A published, citable sample report and AGPL open-core licensing give rare, checkable evidence in the deep research category.

Suggestion: Put the credit cost per run on the pricing page so buyers can compare directly with Perplexity Pro.

A published, inspectable research run with cited passages is exactly the proof a verifiable-research product needs, and the design is distinctive.

Suggestion: Put the main deep-research plan prices on the pricing page, not only the open-source license, so buyers see the cost to run.

A published full research run with cited passages is strong proof, but the headline wordplay and the licensing-shaped pricing page obscure what the product costs.

Suggestion: Split the pricing page so product subscription pricing and AGPL commercial licensing are two clearly separate sections.

Publishing a full real research run is strong evidence, but the page mixes a SaaS trial with AGPL commercial licensing copy that confuses the offer.

Suggestion: Separate the deep research product from the open-source licensing story, and show SaaS plan prices, not just trial credits.

Linking every claim to the exact passage and openly flagging gaps is exactly what a careful buyer of research wants.

Suggestion: Move the credit trial terms (250 credits, card required) above the fold near the main CTA so the price of trying it is not a surprise.

Named enterprise clients like JD Group and Lebara give credible proof, but every tier hides its price.

Suggestion: Show a starting price for the Tech Only tier on the pricing page.

Named customer accounts, a partner reward network and managed programme services support a credible enterprise retention offering.

Suggestion: Add typical implementation timelines and starting contract ranges to each pricing tier.

Backing up the white-label platform pitch with named case studies from JD Group, Lebara, and HelloFresh gives enterprise buyers solid proof of scale.

Suggestion: Add starting price ranges to the three consultation tiers on the pricing page so mid-market teams know if they qualify before booking a call.

Recognizable deployments, named customer results and a large reward network substantiate its end-to-end enterprise loyalty offer.

Suggestion: Add indicative implementation timelines and starting budget ranges for the three pricing tiers.

Strong named enterprise examples, partner network and managed service angle, but request-only pricing makes budget fit hard to assess.

Suggestion: Publish indicative pricing bands or a worked enterprise example beside the ROI calculator so buyers can qualify themselves before booking.

Enterprise loyalty platform with credible named brands like JD and HelloFresh behind its case studies.

Suggestion: Publish a starting price for the Tech Only tier instead of request-pricing on every plan.

Enterprise logos like JD Group and HelloFresh plus managed service give strong proof, but request-only pricing hides the cost.

Suggestion: Publish at least a starting price or range per tier so a marketing lead can qualify the budget before booking a demo.

Named enterprise clients, real campaign screens and a 1,000-brand partner network make the white-label loyalty pitch concrete.

Suggestion: Say which of the three tiers is right for which size of audience on the pricing page instead of repeating Request Pricing three times.

Named JD Group and HelloFresh quotes plus a 1,000-brand partner network give real enterprise credibility, though pricing stays hidden behind consultations.

Suggestion: Publish starting price ranges per tier so smaller prospects stop bouncing before booking a demo.

Pricing pages show three tiers but every tier says 'Request pricing', which makes comparison impossible before a sales call.

Suggestion: Publish indicative starting prices or at least the included request/partner counts per tier so buyers can self-qualify before booking a demo.

Task-bias detection and path replay are genuine differentiators, though the company behind it is not named.

Suggestion: Add a short panel-recruitment pricing section and a named team or company line.

Task-bias checks and path replay distinguish the free tree-testing offer, while paid recruitment provides a plausible supporting business.

Suggestion: Explain panel recruitment pricing and participant-quality controls beside the free-response promise.

Built-in checks for leading task wording and visual path replays solve genuine methodology problems in information architecture research.

Suggestion: Fix the grammatical error in the hero headline ('Know your users get where') and add a pricing section explaining what paid participant recruitment costs.

Task-bias checks, path replay and scenario completion show research depth beyond standard tree-testing metrics.

Suggestion: Add a visible funding and panel-pricing section explaining how unlimited free testing is sustained.

Free unlimited tree testing with task-bias checks, path replay and concrete result screens is specific, credible and unusually focused on study quality.

Suggestion: Explain on the homepage how free unlimited testing is funded and what paid panel recruitment costs per participant.

Free tree testing with unlimited responses is a real deal, but the page never says who pays for the paid recruitment panel.

Suggestion: Add a visible pricing or contact page explaining exactly how the UXbeam paid panel is charged.

Task-bias detection, path replay and full-scenario completion are genuinely advanced and the free unlimited responses lower the barrier well.

Suggestion: Add a pricing page and a contact or company page so teams know who runs the paid recruitment panel and what it costs.

The free tree testing tool is genuinely clear and the study-quality checks and path replay go past what rivals show at this price.

Suggestion: Publish the paid UXbeam Panel recruitment pricing somewhere public, since the only funding signal on the site is a single line of grey text.

Task-bias checks and path replay are genuinely thoughtful features, but free with no visible pricing or contact details leaves funding unclear.

Suggestion: Add a pricing or roadmap page explaining how the free tool and the paid panel sustain the product.

The tree-testing explainer is unusually specific and honest about what standard metrics miss, which builds real credibility for a free tool.

Suggestion: Add a visible sustainability story (backer, parent lab or paid panel tie-in) so visitors trust that a no-pricing free tool will still be there next year.

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

Suggestion: Add named customer logos or one case study near the hero, plus starting price guidance.

The worked foreign-exchange reconciliation explains the unified-record benefit well, but explicitly illustrative screens provide limited operational proof.

Suggestion: Publish a recorded sandbox walkthrough completing the illustrated purchase through payment and posted journal entries.

Tracing a single purchase order through foreign exchange losses and balanced journal entries demonstrates deep domain competence.

Suggestion: Shrink and reposition the cookie banner so it stops covering the primary call-to-action buttons on the first screen, and add pricing tiers.

The worked purchase-to-ledger example communicates unified finance exceptionally well, although commercial terms and customer validation remain absent.

Suggestion: Publish plan pricing and target-company limits so finance teams can qualify themselves before booking a demo.

The one-record finance story is polished and detailed, but illustrative data, no visible pricing and no customer proof weaken confidence against established accounting platforms.

Suggestion: Publish starting pricing and name one live customer whose close process improved, since all homepage records are labelled illustrative.

Strong unified-finance pitch with a detailed transaction trace, but no pricing page and no visible cost anywhere.

Suggestion: Publish plan pricing or at least a starting price so small businesses can self-qualify before booking a demo.

The full-context journal and FX tie-out walkthrough is the most concrete finance demo here, but there is no pricing and only a demo gate.

Suggestion: Add a pricing page or at least a starting price so a finance lead can assess fit without committing to a sales call.

The one-record story is well argued, but every screenshot is labelled illustrative, so a buyer never sees the real product.

Suggestion: Replace one illustrative dashboard with a real screenshot or a link into the existing sandbox so the interface can be checked.

Beautifully designed and the PO-to-journal-entry walkthrough is genuinely convincing, but every screen is labelled illustrative and there is no pricing anywhere.

Suggestion: Show real product screenshots or a sandbox tour alongside the illustrative mockups, and publish at least indicative pricing.

Walking a single PO from procurement through to the financial statements with real journal entries is the strongest finance demo I have seen on a homepage.

Suggestion: Publish any pricing or a clear 'talk to sales' threshold on the pricing page so visitors know what to expect before booking a demo.

The hero phone mockup is blank, so the core scan-and-ask experience is never shown.

Suggestion: Replace the empty phone in the hero with a real chat answering a scanned product question.

The scan-to-answer workflow is clear, but categorical promises that AI cannot invent answers weaken an otherwise coherent offer.

Suggestion: Replace the absolute accuracy guarantee with a scannable sample showing sourced answers, uncertainty and support handoff.

The strict grounding in uploaded documents addresses the main buyer fear around AI support, but the blank phone outline in the hero wastes prime space.

Suggestion: Put a live, scannable demo QR code inside the hero phone frame so visitors can test the question-answering flow immediately.

Grounded answers and lead capture are useful, but the blank hero mockup and sweeping use-case list leave the product feeling unproven.

Suggestion: Replace the blank phone with a real scan, question, grounded answer and dashboard follow-up sequence.

The scan-ask-connect idea is instantly clear and pricing is visible, but the sprawling use-case list makes the ideal first buyer feel unfocused.

Suggestion: Replace the blank phone hero with a scannable live demo QR that opens a real sample knowledge-base conversation.

Clean one-page pitch for AI QR codes, but the category is crowded and no live scan demo is shown.

Suggestion: Embed a working demo QR code on the homepage that visitors can scan to try the AI answer.

The no-hallucination guardrail angle is sensible, but the use-case list is scattered and the testimonials read thin.

Suggestion: Pick two or three flagship use cases with a real scanned-to-answer demo video instead of listing a dozen equal cards.

The scan-ask-connect idea is easy to grasp, but the phone mockup is blank and the three short testimonials carry no company detail.

Suggestion: Replace the empty phone frame in the hero with a real conversation on a product QR code, and drop the works-for-anything-in-the-world claims.

A clear scan-ask-connect pitch with honest guardrail copy, but the QR-meets-AI space is crowded and the testimonials are thin.

Suggestion: Replace generic praise quotes with one named case study showing a real QR code and the answers it delivered.

The promise that the AI refuses to invent answers outside the uploaded knowledge base is a strong differentiator from generic chatbots.

Suggestion: Add a live, embeddable demo QR on the home page so visitors can scan and see a real grounded answer in seconds.

Print-driver submission is a practical differentiator, but the pricing page shows no per-piece prices.

Suggestion: Publish a per-page or per-envelope price table on the pricing page.

Desktop print drivers, householding and next-business-day USPS handoff address practical mailing needs, but the all-inclusive price remains unspecified.

Suggestion: Publish an example all-in price for a one-page invoice, including postage and volume assumptions.

The desktop print-driver workflow is easy to grasp for traditional offices, though the interface shown on the laptop screen looks dated.

Suggestion: Publish a sample per-piece rate card on the pricing comparison page so buyers can estimate postage and printing savings without calling sales.

Concrete submission options, next-business-day handling and householding features explain a useful service despite the dated presentation.

Suggestion: Publish example all-in per-piece prices for common invoice and statement volumes beside the cost comparison.

The desktop print-to-mail workflow and next-day turnaround are clear, but the dated presentation gives no visible per-piece price to compare.

Suggestion: Add per-piece example prices for a one-page letter and certified mail to the pricing page comparison table.

Print-to-mail service explains its workflow well but shows no pricing, no privacy page and no platform screenshots.

Suggestion: Add a per-piece price table and link privacy and terms pages from the footer.

Clear print-to-mail pitch with a useful in-house comparison table, but the dated template and missing privacy and terms pages undercut trust.

Suggestion: Add linked privacy and terms pages in the footer and refresh the hero with a real product screenshot instead of stock imagery.

The outsourcing pitch and next-business-day claim are clear, but the dated layout and stock imagery make a paid B2B service look unmaintained.

Suggestion: Add a screenshot of the actual print driver and tracking dashboard, and publish a terms and privacy page for a service handling customer statements.

The service is explained clearly, but the dated design, no visible privacy or terms, and pricing only by contact all undercut confidence in a mail-handling vendor.

Suggestion: Publish even sample per-piece pricing and add visible privacy and security policy pages for a service handling invoices and medical mail.

The site feels dated and the home page reads like a 2010s brochure, with no pricing or visible customer logos to back the claims.

Suggestion: Add a transparent per-piece price on the pricing page and one named customer story with measurable savings so a buyer can compare to in-house mailing.

Claims of 'consent-based' identification with income and home data are not explained, and pricing says 'upon request'.

Suggestion: Explain on the homepage exactly how visitor consent is obtained for person-level identification.

The person-level identification offer is explicit, but consent mechanics receive far less explanation than the extensive personal data available.

Suggestion: Show the actual consent journey, data provenance and opt-out handling beside the person-identification claim.

Promising person-level home addresses and income estimates for anonymous visitors raises serious privacy skepticism that generic stock photos cannot overcome.

Suggestion: Replace the stock photography with real dashboard screenshots and explain the exact consent mechanism that makes your data collection privacy-compliant.

Person-level identification is distinctive, but repetitive promotional copy and unsupported capture claims weaken an otherwise clear sales proposition.

Suggestion: Replace repeated benefit sections with identification accuracy methodology, consent mechanics and one annotated matched-visitor record.

The lead-identification promise is clear, but 40 personal data points and a 35 percent capture claim raise consent questions the page does not answer.

Suggestion: Explain exactly how visitor consent is obtained and show a sample identified record with sources beside the privacy claim.

Loud claims about capturing 35% of visitors with consent-based ID, backed mostly by stock photos and an empty awards strip.

Suggestion: Publish a privacy whitepaper explaining the consent mechanism and swap stock imagery for real dashboard screenshots.

Identifying individual visitors with income and address data is a strong sales hook but a serious privacy liability despite the consent claim.

Suggestion: Explain precisely how consent is obtained and add a plain-language privacy explainer on the homepage to defuse the obvious objection.

The page leans on dense stock photography and unverifiable claims like capturing 35% of visitors, which undercuts the privacy-compliant positioning.

Suggestion: Replace the Reached 40 data points of data wording and the stock photos with one screenshot of a real identified visitor record and its source.

The promise of identifying visitors by name, income and home ownership reads as invasive, and 'consent-based' is asserted rather than explained.

Suggestion: Explain on the homepage exactly how consent is obtained for the 40 data points, with a link to the mechanism, not just a compliance badge.

The 'consent-based identification' framing on the homepage sits awkwardly next to claims of capturing 35% of visitors by name and email without opt-in.

Suggestion: Replace stock-photo people and vague testimonial counts on the homepage with one named customer and a concrete lift metric.