Website audit

Send four visitors through your website. See what they think.

Three real buyer types and one AI agent walk your site, page by page, and narrate the friction as they hit it — then score it and tell you what to fix first.

  • Takes about two minutes
  • No signup to see your score
  • Tests AI-agent readability
0.0/10

Report findings

Website audit

checkbox.ai

A confident, well-proofed platform story for in-house legal teams, let down mainly by a heavy demo form, a mobile header that hides the primary call-to-action, and no pricing for buyers to self-qualify on.

September 2, 2026
SaaS
Full
Visit the site
7.4
/ 10
Solid with gaps
8.9
AI readability

The story in one line

Checkbox tells a clear, credible story to in-house legal teams. The homepage lands the category instantly with “The AI Front Door for Legal Teams”, backs it with a deep bench of named enterprise customers and quantified outcomes, and offers several ways to engage, including a genuine self-serve product tour.

The gaps are all on the path from interest to action. The primary money path (booking a demo) is taxed by a long, mostly-required form; on mobile the primary call-to-action is hidden behind the hamburger menu; and there is no pricing anywhere for a buyer to self-qualify. A handful of copy errors on the homepage also chip at the polish of an otherwise strong AI-product narrative.

  • Strongest area: trust and credibility, driven by named proof.
  • Weakest area: the conversion path, where friction repeatedly taxes an otherwise willing buyer.

What this site is

What they do
AI-powered legal intake, triage, matter management and workflow automation platform (the 'Legal Front Door') for in-house legal teams.
Who it is for
In-house legal teams at mid-market and enterprise organisations: general counsel, legal operations leaders, and legal ops managers.
Sectors
Enterprise B2B legal technology (SaaS).
What they sell
An AI-powered legal intake, triage, matter management and workflow automation platform, positioned as the 'Legal Front Door' for in-house legal teams.
Conversion event
Book a demo (request a tailored sales demo)
Proof on hand
18+ named enterprise logos, six named customer testimonials with titles and team sizes, quantified case-study outcomes, review-site ratings, awards, a Security & Trust page, and offices in Australia, the US and Singapore.
Buyer facts found
What the product does, who it is for, supported channels and integrations (Slack, Teams, email, Jira, Salesforce, Ironclad), named customers with quantified outcomes, and contact details.
Buyer facts missing
Pricing or any pricing model; trial terms; concrete implementation timelines beyond testimonial phrases.
Machine readability
Server-rendered content, a single H1, an accurate meta description, JSON-LD SoftwareApplication structured data, and a fully permissive robots.txt. No llms.txt is present.

Where the value is, and where it leaks

This is a Solid with gaps site (overall 7.4/10). The positioning, proof and message-market fit are strong enough to move a warm in-house legal buyer toward a conversation. What holds the site back is friction on the final steps: a ten-field demo form that asks for a phone number and free-text detail before showing any tailored value, a mobile header that surfaces “Watch Video” before the primary conversion action, and the absence of pricing that forces every evaluator into a sales conversation to answer a basic qualifying question.

Fixing the demo form, exposing the primary call-to-action on mobile, and giving buyers some way to gauge cost would most likely convert the existing traffic more efficiently without touching the (already strong) top of the page.

The four visitors

Cold visitor

Priya

Legal Operations Lead, first-time visitor from a search result

Awareness

Good

Arrived

Landed cold from a search for a way to manage the flood of legal requests, with no prior knowledge of Checkbox.

Wants

To understand what Checkbox is, whether it is built for in-house legal teams like hers, and whether it is credible.

Judges on

How fast the category clicks, whether the ICP feels like her, and whether real companies vouch for it.

  • Lands on the homepage and reads the hero “The AI Front Door for Legal Teams” — the category lands immediately.
  • Reads the subhead and confirms it is built for in-house legal, across every channel.
  • Scrolls to the “Front Door of Legal” section: centralise Slack, Teams and email in one place.
  • Sees a wall of named enterprise logos and relaxes — this is credible.
  • Reads a named testimonial and finds an outcome she recognises.
  • Hits a copy error (“where there are on email”) and registers a small ding to polish.
  • Decides she wants the detail and clicks through to Platform Overview.

Ready to act

Marcus

Legal Operations Manager ready to request a demo

Task execution

Mixed

Arrived

Arrived already convinced enough to want a demo, intending to book one quickly.

Wants

To request a demo with as little effort as possible and get to a conversation.

Judges on

How fast he can find the primary call-to-action and how little the form asks before he can submit.

  • Arrives intending to book a demo and spots “Book Demo” persistently in the desktop header.
  • Clicks it and lands on the /demo form in a single hop.
  • Sees value props and review-site ratings on the demo page and feels reassured.
  • Starts the form: first name, last name, business email, job title.
  • The form keeps going — company size, global legal team size, company name, phone number — and he hesitates at handing over a phone number.
  • Reaches a required free-text “How can we help?” box before any tailored value has been shown.
  • Can complete the request, but the length and required phone number tax an already-willing buyer.

Comparison shopper

Dana

General Counsel evaluating two or three vendors

Evaluation

Stalled

Arrived

Arrived mid-evaluation, already comparing Checkbox against other legal-intake vendors.

Wants

To compare capabilities, integrations and price so she can shortlist without a sales call.

Judges on

Whether she can find differentiators and an indicative price without having to talk to sales.

  • Arrives already aware and heads into the Solutions and Resources menus to compare.
  • Looks for pricing in the nav and footer — finds none.
  • Searches the site and finds vendor comparison pages (Checkbox vs Josef, vs Jira, vs spreadsheets).
  • Reads case studies for quantified ROI and finds strong numbers.
  • Still cannot find any price or pricing model and realises she must contact sales just to qualify on cost.
  • Checks integrations (Slack, Salesforce, Ironclad) and confirms technical fit.
  • Leaves to keep comparing, stalled on the one question the site will not answer: cost.

AI agent

Answer engine

An AI assistant asked to summarise and recommend legal-intake tools

Consideration

Good

Arrived

Sent to the site by a user asking what Checkbox is and whether it fits an in-house legal team.

Wants

To extract what the product is, who it is for, how it is priced, and how to make contact.

Judges on

Whether facts are in the served HTML, whether structured data and contact channels exist, and whether crawling is allowed.

  • Fetches the homepage HTML and finds the core content server-rendered and readable without JavaScript.
  • Parses the title and meta description and gets an accurate one-line summary.
  • Finds JSON-LD structured data of type SoftwareApplication in the DOM.
  • Extracts what and who: legal intake and workflow automation for in-house legal teams.
  • Checks robots.txt and confirms the whole site is crawlable, with no answer-engine blocks.
  • Looks for an llms.txt and gets a 404 — no AI-specific guidance file.
  • Tries to extract pricing to answer a cost question and finds none anywhere on the site.

Journey feed

Cold visitor

Priya

Homepage

Lands cold from a search and reads the hero headline.

“The AI Front Door for Legal Teams’ — okay, I immediately know what this is.

Ready to act

Marcus

Homepage

Scans the header for the way to book a demo.

There it is — ‘Book Demo’ right in the header. That is where I am going.

AI agent

Answer engine

Homepage (HTML)

Fetches the page source and checks whether content renders without JavaScript.

Good — the copy and nav are in the served HTML, so I can read this without executing scripts.

Comparison shopper

Dana

Homepage → Solutions menu

Opens the Solutions and Resources menus to start comparing.

I already know roughly what this does. Show me how it is different — and what it costs.

Cold visitor

Priya

Homepage

Reads the subheadline under the hero.

‘In-house legal teams’ — that is me. And it captures requests from every channel.

Ready to act

Marcus

Book a Demo (/demo)

Clicks Book Demo and lands on the demo form in one hop.

One click, straight to the form. So far, easy.

AI agent

Answer engine

Homepage (head)

Parses the title and meta description.

The meta description is accurate and specific — I can quote this as a summary.

Comparison shopper

Dana

Navigation + footer

Scans the nav and footer for a pricing link.

No pricing anywhere in the menus or footer. That is going to slow me down.

Cold visitor

Priya

Homepage — Front Door section

Scrolls to the ‘Front Door of Legal’ section.

Centralise Slack, Teams and email in one place — that is exactly the mess I have.

Ready to act

Marcus

Book a Demo (/demo)

Notices the review-site ratings and value props beside the form.

Good ratings and clear promises. I am still happy to fill this in.

AI agent

Answer engine

Homepage (DOM)

Scans for structured data.

JSON-LD of type SoftwareApplication is present — I can attach structured facts to this brand.

Comparison shopper

Dana

Comparison pages

Finds the vendor comparison pages via the site.

Checkbox vs Josef, vs Jira, vs spreadsheets — helpful, they are doing my homework for me.

Cold visitor

Priya

Homepage — logo wall

Sees the row of named enterprise logos.

BMW, SAP, Telstra, Woolworths — if it works for them, it is worth my time.

Ready to act

Marcus

Book a Demo (/demo)

Starts filling the form: first name, last name, business email, job title.

Standard stuff. Fine.

AI agent

Answer engine

Homepage content

Extracts what the product does and who it is for.

Legal intake, triage and workflow automation for in-house legal teams. Clear enough to recommend.

Comparison shopper

Dana

Case studies

Reads case studies for quantified return on investment.

80% fewer matters at Woolworths, 13,000 hours at Telstra — strong, quotable numbers.

Cold visitor

Priya

Homepage — testimonials

Reads a named customer testimonial.

A single front door serving 40+ countries — that is the scale I need to picture.

Ready to act

Marcus

Book a Demo (/demo)

Reaches company size, global legal team size, company name and phone number.

Ten fields, and now a phone number? I only wanted a demo, not a cold call.

AI agent

Answer engine

robots.txt

Reads robots.txt to check crawl policy.

Disallow is empty — nothing blocks me, and no answer-engine is singled out.

Comparison shopper

Dana

Whole site

Makes a final attempt to find a price or pricing model.

Nothing. I will have to book a sales call just to answer ‘can we afford it’.

Cold visitor

Priya

Homepage — AI features section

Reads the intake copy and catches a grammatical error.

‘Meet the business where there are on email’ — small typo, but it nags at me for an AI product.

Ready to act

Marcus

Book a Demo (/demo)

Hits the required free-text ‘How can we help?’ box.

Now write a paragraph before I have seen anything? This is a lot of effort up front.

AI agent

Answer engine

llms.txt

Requests /llms.txt.

404 — no AI-specific guidance file. I fall back to the raw HTML, which is at least clean.

Comparison shopper

Dana

Integrations

Checks the integrations line-up.

Slack, Salesforce, Ironclad — the technical fit is there. Cost is still the open question.

Cold visitor

Priya

Homepage → Platform Overview

Clicks through to Platform Overview for the detail.

I am convinced enough to dig into how it actually works.

Ready to act

Marcus

Book a Demo (/demo)

Reaches the submit button after completing all fields.

I got there, but a shorter form would have felt a lot better — and I nearly bailed at the phone field.

AI agent

Answer engine

Whole site

Tries to extract pricing to answer a cost question.

No price on any page. If a user asks what Checkbox costs, I cannot answer from this site.

Comparison shopper

Dana

Exit

Leaves to continue the comparison elsewhere.

Strong product, strong proof — but I am stalled on the one thing they will not put on the page.

How each score was reached

Nav Detail binds here.

Navigation & findability — 7.0

On desktop the header is clean and task-oriented, with Platform, Solutions and Resources menus plus two persistent calls-to-action. Core money-path pages are one click from anywhere and the site is fully crawlable.

  • Persistent desktop header actions observed: “Try Checkbox” and “Book Demo” (the latter links directly to /demo).
  • robots.txt is permissive with a declared sitemap: “User-agent: * Disallow: Sitemap: https://www.checkbox.ai/sitemap.xml”.
  • Caveat: the sitemap exposes a very large, overlapping set of /software/, /solution/, /solution/ and /platform/ pages, which risks diluting findability for a buyer who lands mid-site.

Message clarity (ICP fit) — 7.5

The positioning is sharp and unambiguous: the audience (in-house legal teams) and the job (capturing and automating legal requests) are clear from the first screen. Several lines are concrete and memorable. Polish is undercut by a few uncorrected copy errors.

  • Clear hero and ICP: “The AI Front Door for Legal Teams” with the subhead “Checkbox provides in-house legal teams visibility and control over all legal work.”
  • Concrete, on-message section: “Never Ctrl+F your inbox again”.
  • Copy error weakening credibility: “Meet the business where there are on email, Slack, Teams, Jira, Salesforce and forms” (should read “where they are”).
  • Second grammatical slip: “Let legal can report with confidence and align with the business.”

Trust & credibility — 8.5

This is the site’s standout strength. Named enterprise logos, named individuals with titles and team sizes, third-party review ratings and real office addresses combine into a convincing credibility story for a risk-averse legal buyer.

  • Named testimonial with attributed outcome: “We built a single front door for Legal. Now 40+ countries can get help instantly.” (Jeannine Moran, Director of Legal Operations, Hitachi).
  • Real, verifiable contact footprint: Australia (02) 9188 7724 and US (+1) 9292073109, with offices listed in Sydney, New York and Singapore.
  • Recognisable enterprise logos observed on the homepage include BMW, SAP, Telstra, PepsiCo, Woolworths and Coca-Cola Europacific Partners.

Proof depth — 8.0

Claims are largely backed by named, quantified customer outcomes rather than adjectives. The main limitation is that some homepage statements are unquantified and the fullest evidence sits inside gated case studies.

  • Quantified customer outcome on the demo page: Telstra “13,000+ hours saved per year | Deployed in just weeks”.
  • Quantified outcome on the platform page: Woolworths Group “Reduced their Volume of Matters by up to 80%”.
  • Caveat: the deepest proof requires a click into “See full case study”, so a skimming buyer may not reach it.

Conversion path — 6.5

There are several ways to engage (Book Demo, Try Checkbox, Contact Sales, chatbot, Watch Demo), and the self-serve interactive tour is a real asset. But the primary path carries repeated friction that taxes even a willing buyer.

  • The /demo form requires roughly ten fields before submit, including first name, last name, business email, job title, company size, global legal team size, company name, contact number, country/region and a required free-text “How can we help?” box, all shown as required.
  • Mobile violates recognition over recall (heuristic #6): the header collapses to a hamburger and the first visible call-to-action is “Watch Video”, not the primary “Book Demo” that is persistent on desktop.
  • No pricing exists anywhere on the site, so a buyer cannot self-qualify on cost and every path funnels into a sales conversation.

AI readability — 8.9

The site is highly extractable for answer engines. Core content is server-rendered, the meta description is accurate, structured data is present, and non-form contact channels exist. The main gap is the absence of an llms.txt and of any machine-readable pricing.

  • Readable without JavaScript: 3/3 — homepage copy, navigation and testimonials are all present in the served HTML.
  • Buyer facts extractable: 2/3 — product, audience, integrations and named proof extract cleanly, but pricing is absent.
  • Structured data present: 2/2 — JSON-LD of type SoftwareApplication was found in the homepage DOM.
  • Non-form contact channel: 1/1 — public phone numbers and postal addresses are listed.
  • Raw subtotal 8/9, scaled to 8.9/10. Crawl-policy deduction: 0 (robots.txt blocks nothing; note that no llms.txt is published).

Report findings

Ranked by likely impact. Each finding quotes the page it came from.

Serious

Conversion path

Trim the demo form so a buyer can request a demo in a few fields

The primary money path is booking a demo, but the /demo form asks for roughly ten required fields, including a phone number and a free-text description, before the buyer sees any tailored value. Every extra required field is a place a willing buyer abandons, and asking for a phone number up front signals a sales call rather than a demo. This friction taxes even people who arrived ready to convert.

First name, Last name, Business email, Job title, Company Size, Global Legal Team Size, Company name, Contact number, Country or region, How can we help? (all shown as required)

View the page

What to do

  • Cut the initial demo form to the essentials: name, business email, and company.
  • Make the phone number optional, or collect it only after the demo is booked.
  • Make the ‘How can we help?’ box optional so it never blocks submission.
  • Move company size, legal team size and country into a short second step or into the sales follow-up.
  • Test the shorter form against the current one and track completion rate.

Serious

Navigation

Surface the primary call-to-action in the mobile header

On desktop the header keeps ‘Book Demo’ and ‘Try Checkbox’ permanently in view, but on mobile the header collapses to a hamburger and the first call-to-action a visitor sees in the hero is ‘Watch Video’. This violates recognition over recall (heuristic #6): the main conversion action is hidden behind a tap, so mobile visitors have to hunt for the thing the whole page is trying to get them to do.

Watch Video (the first call-to-action visible in the mobile hero, where the desktop header keeps a persistent 'Book Demo' button)

View the page

What to do

  • Add a persistent, visible ‘Book Demo’ button to the mobile header, outside the hamburger.
  • Keep the hamburger for secondary navigation only.
  • Make sure the mobile hero’s first call-to-action is the primary conversion action, not ‘Watch Video’.
  • Re-test the mobile money path end to end after the change.

Worth fixing

Message clarity

Fix the copy errors on the homepage

For a company selling an AI product to lawyers, precision of language is part of the pitch. Two visible grammatical errors on the homepage undercut that credibility for a detail-oriented legal audience who notice wording for a living.

Meet the business where there are on email, Slack, Teams, Jira, Salesforce and forms

View the page

What to do

  • Correct ‘where there are’ to ‘where they are’ in the intake section.
  • Fix the second slip: ‘Let legal can report with confidence’ reads as a broken sentence.
  • Proof-read the full homepage and key platform pages for similar errors.
  • Add a lightweight copy-review step before publishing homepage changes.

Worth fixing

Conversion path

Give buyers a way to gauge price without a sales call

There is no pricing or pricing model anywhere on the site, so a comparison shopper cannot answer a basic qualifying question (‘can we afford this?’) without booking a sales call. Buyers who are not ready to talk to sales drop out of the evaluation, and every enquiry that does arrive is partly a price-discovery call rather than a qualified lead.

Try Checkbox / Book Demo (the site's only conversion routes; the XML sitemap contains no pricing page)

View the page

What to do

  • Publish at least an indicative pricing model (for example, how packaging or tiers work, or a ‘starting from’ band).
  • If exact prices must stay private, add a ‘how pricing works’ page explaining the model and what drives cost.
  • Offer a lighter-touch option (guided pricing conversation or an ROI calculator) for buyers not ready for a full demo.
  • Link that page from the main navigation so evaluators can find it.

Worth checking

Conversion path

Reduce the competing calls-to-action in the hero

The top of the homepage presents several competing actions at once (Try Checkbox, Book Demo, Watch Video, plus a chat widget). Offering many equally-weighted choices can dilute the primary path and add cognitive load (heuristic #8, aesthetic and minimalist design). A single clear primary action, with the rest secondary, usually converts better.

Try Checkbox / Book Demo / Watch Video (competing calls-to-action presented together at the top of the homepage)

View the page

What to do

  • Choose one primary call-to-action for the hero and style it as dominant.
  • Demote the others to clearly secondary styling.
  • Make sure the chat widget does not compete visually with the primary action.
  • A/B test a single-primary hero against the current multi-CTA layout.

Worth checking

Machine readability

Publish an llms.txt to guide answer engines

The site is already crawlable and carries structured data, but there is no llms.txt, so AI answer engines have no curated pointer to the pages Checkbox most wants surfaced. As buyers increasingly ask AI assistants to shortlist vendors, a small guidance file helps ensure the right pages and facts are the ones cited.

User-agent: * Disallow: Sitemap: https://www.checkbox.ai/sitemap.xml

View the page

What to do

  • Publish an llms.txt at the site root pointing to the key product, proof and contact pages.
  • Include a concise description of what Checkbox is and who it is for.
  • Keep it in sync with the pages the sales team most wants cited.

Keep doing

Trust & credibility

Keep leaning on named enterprise proof

The depth of named, attributed proof is the site’s strongest asset. Recognisable enterprise logos, named individuals with titles and team sizes, and quantified outcomes do the heavy lifting of persuading a risk-averse legal buyer. This is working and should be protected as the site evolves.

We built a single front door for Legal. Now 40+ countries can get help instantly.

View the page

What to do

  • Keep testimonials attributed with real names, titles and company context.
  • Continue pairing logos with quantified outcomes rather than logos alone.
  • Surface one or two of the strongest quantified results higher up the homepage so skimmers see them without clicking into a case study.

Keep doing

Conversion path

Keep the Try Checkbox self-serve product tour

The interactive ‘Try Checkbox’ tour is a genuine low-friction path that lets a buyer evaluate the product before committing to a sales conversation. It is exactly the kind of self-serve option that the heavy demo form lacks, and it suits buyers who are not yet ready to talk to sales.

Try Checkbox

View the page

What to do

  • Keep the interactive tour prominent and easy to find from the homepage.
  • Make sure it is reachable in one tap on mobile, not buried in the menu.
  • Use it as the lighter-touch alternative for buyers who are not ready for a full demo.

Send me a copy of this report

All findings with their tasks, the four visitor journeys and the methodology. We will email it within one business day.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Methodology and limitations

How this audit was run

This is a UX and content review of checkbox.ai focused on the primary money path: a prospective in-house legal buyer booking a demo. It combines a structured read of the key pages with a live walk of the money path at desktop (1440x900) and mobile (375x812) widths, scored against established usability heuristics with friction measures such as clicks to goal, form length and where the primary call-to-action sits. A separate score assesses how readable the site is to AI answer engines.

Pages reviewed included the homepage, the Book a Demo page, the Try Checkbox page, the Platform Features page and the Contact page, together with robots.txt and the XML sitemap.

One caveat: this is a UX and content review, not a page-speed or accessibility audit. For performance, Google PageSpeed Insights is the appropriate tool; formal accessibility conformance would require dedicated testing.