AI Visibility Audit: Tally

Tally is strongly recognised by all three platforms: it was mentioned in every answered question. Recognition did not translate into consistent recommendation: preference depended on the buyer need, and specific competitors owned specific use cases — Fillout for database-centric workflows, Jotform for complex calculations and approvals, Typeform for polished customer-facing UX.

Three findings matter most. First, Perplexity's answer ended after 9 of 18 questions, so half the buyer questions were never answered there. Second, Gemini made two claims stronger than the vendor's own published facts (“encrypted end-to-end”, “GDPR compliant by default”). Third, third-party listicles and competitor pages shaped answers more visibly than Tally's own buyer-facing evidence.

Technically, the official Cloudflare Agent Readiness scan places the site at level 1/5 (Basic Web Presence): crawlable and discoverable at the basics, with the newer agent-facing standards not yet adopted. The recommendations in section 11 target the visibility and evidence gaps, which are independent of that technical result.

Cloudflare is the source of the technical Agent Readiness result. This audit is an independent service and is not affiliated with or endorsed by Cloudflare. Agent readiness measures whether automated agents can discover, read and interact with a website — it does not show whether AI assistants recommend the brand, which is what the rest of this report tests.

• Entity naming — needs attention: platforms and pages alternate between “Tally” and “Tally.so”, weakening entity consistency.
• Trust signals — needs attention: the sampled public pages expose few visible identity, authorship and policy signals.
• Structured data — partial: Organization and product-type JSON-LD present on sampled pages; no FAQ schema on answer content.
• Citation surface — passed: concrete, quotable pricing and feature claims, with external references present.

These are our own bounded-scan observations (four public pages, 2026-07-25). They are reported without a score and are independent of the official Cloudflare result above.

ChatGPT, Gemini and Perplexity, using the publicly accessible guest/default experience on 2026-07-23. One combined prompt asked each platform to answer the same 18 buyer questions separately, rank a shortlist, and explain trade-offs, followed by human fact checking. No vendor was described as a client. Paid, logged-in or personalised modes may answer differently; see section 13.

The 18 questions covered ten buyer-intent categories. A customer audit derives its prompt set the same way — from the customer's five seed questions, expanded to 15–20 prompts.

Every platform recognised the brand in every question it answered: ChatGPT 18/18, Gemini 18/18, Perplexity 9/9 answered (50% prompt coverage — its response ended after question 9). Recognition included the correct category, core features and European positioning.

Recommendation strength tracked the buyer need, not overall brand strength: the platforms recommend whoever owns the evidence for that specific use case.

Unrequested competitors appearing in answers is exactly what an audit is designed to surface.

1. 1

   Publish an evidence-first buyer page

   Answer the 18 tested questions directly with concise, dated claims and links to the relevant official documentation.

2. 2

   Separate privacy facts from legal conclusions

   State company location, storage region, DPA availability and optional subprocessors independently; explicitly avoid claims about legal immunity.

3. 3

   Strengthen the workflow feature evidence

   Create one practical example showing conditional logic, Stripe payments and signed/retried webhooks working together for a lead or onboarding flow.

4. 4

   Create a maintained comparison evidence pack

   Use factual tables for Tally vs Typeform, Fillout and Jotform, with plan/date caveats and no unsupported superiority claims.

5. 5

   Improve entity consistency and independent references

   Use the same product name across titles and structured data, then earn citations from credible independent software and privacy publications.

1. Weeks 1–2 — quick fixes. Entity-naming consistency, trust signals, and the highest-priority evidence page from the recommendations.
2. Optional — Action Plan (€299). The findings expanded into an exact page, content, entity, schema, authority and measurement backlog. €49 credited if ordered within 7 days of the audit.
3. Optional — Implementation Sprint (from €900, scoped separately). We implement the priority fixes on the website and supporting content.
4. Retest. Re-run the same prompt set against the same platforms and compare against this dated baseline.

• One test run per platform on 2026-07-23; outputs can change without notice.
• Guest/default experiences may differ from paid, logged-in or personalized modes.
• The combined prompt may create context effects between the 18 questions.
• Perplexity returned only questions 1–9 before ending; coverage is shown explicitly.
• Only citations visible in the captured interface were recorded.
• The official Agent Readiness result reflects Cloudflare's scanner on its scan date; the scanner and its checks evolve.
• Our website observations sample at most four public HTML pages; they are bounded and unscored.
• This is not legal advice and not an exhaustive technical audit.
• No ranking, citation, inclusion or traffic outcome is guaranteed.