Product teardown
By coExploro · Captured · Updated
Reviewed and edited by coExploro · Independent, not affiliated · Public methodology · Corrections: support@coexploro.com
How this page was made: Drafted by four AI analysts from a capture of calendly.com on . Checked by coExploro’s founder on .
A curated sample showing what coExploro observes about public homepages, pricing pages, feature pages, and UX signals.
Illustrative public sample. coExploro is not affiliated with Calendly.
Sample output
Overall score 87/100
PM 90
UX 82
Summary Card + findings
Summary Card
This public version uses the same compact card pattern as private teardowns: one score, four persona signals, and the strongest findings compressed into a card a product team can forward.
Read the methodologyOverall score
87/100
Confidence
high
PM
90/100
UX
82/100
teardown · captured 2026-08-10
Top findings
Findings
PM
High impact
The team tier is priced monthly per seat while the enterprise tier starts in the thousands per year. Nothing occupies the space between, so a growing team meets a wall rather than a next step.
Marketing
Medium impact
Both identity providers appear in the hero itself, so the opening step is a click rather than a form. Stripe places the same control in the same position — this is a shared pattern in the set, not a distinguishing one.
UX
Medium impact
Inspected in the live DOM on 17 August 2026, the yearly/monthly control renders both role="radio" and role="checkbox" elements carrying aria-checked. Which of the two an assistive technology reports is a browser-level decision we did not test; the duplication itself is what the markup shows.
Design
Medium impact
The plan cards set Teams at $16 per seat a month, billed yearly, beside Enterprise at 'Starts at $15k /yr'. Each card labels its own unit, so the reader compares a monthly seat price with a yearly contract floor.
FAQ
This sample covers pages that were publicly visible on . No account, private data or share link is involved. It carries observations only. The underlying run does produce recommendations, but they are written for someone deciding how to compete with the product, which is not what a public page about that product should say.
No. It reflects what is visible in the captured pages: layout density and how controls are described to assistive technology. It says nothing about the product in daily use.
By inspecting the live page markup, not the screenshots. Where a finding on these pages rests on markup rather than on what is visible in a capture, the text says so.
Next