Skip to content

About

An independent collection of Go-To-Market (GTM) strategy assessments, positioning teardowns, and messaging audits for high-growth platforms.

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

GTM Teardowns

I review what buyers can verify before a sales call. Each teardown traces a public claim to its source, explains why it matters and recommends a change.

Prepared by Arunim Shukla.

One finding. SquadStack's llms.txt gave Choice India a 200% reduction in customer acquisition cost. The linked case study said 70%. The file presented itself as the canonical source. Read the finding.

Published reviews

Sr. no. Review Key takeaway Findings Last checked
1 SquadStack.ai A customer result changes between the case study and the facts file. 15 7 November 2026
2 Arcanna.ai The homepage omits the scope that makes named SOC outcomes useful. 10 7 November 2026
3 Zaperon The reporting guide leaves buyers to verify integrity and retention controls. 2 7 November 2026
4 Palm Olympia Similar-looking enquiry routes and image-only offers obscure the buying terms. 8 7 November 2026
5 Massive · machine-readable review Two public facts files disagree about the same company and its products. 14 11 August 2026
6 ChainSecurity The audit PDFs contain proof buyers cannot scan on the website. 16 3 August 2026
7 Bolt.new The homepage leaves out the technology behind Bolt's cost advantage. 5 July 2026
8 Massive The public FAQ describes a business the company had already left. 9 July 2026

At a glance

Findings by impact. 29 high, 39 medium, 9 low, 2 informational.

17 of 29 high-impact findings have fixes estimated in hours.

Start here

What these reviews test

Pattern What to check Examples
Headline metrics lose their scope Can a reader find the population, period and denominator beside the number? Arcanna's homepage figures · Massive's partner earnings
Marketing and documentation leave different expectations Can a buyer trace a product or compliance claim to a workflow, control or rule? Arcanna's confidence bands · SquadStack's recovery-call hours
Useful evidence is hard to retrieve Can the intended reader find the evidence and reuse it without reconstructing it from images or multiple pages? Palm Olympia's construction milestones · Arcanna's older articles
The site carries forward an older strategy Do the homepage, FAQs and editorial programme describe the business and buyer the company pursues today? Massive's former business · Bolt's editorial audience

Method

Every review declares its scope, access limits, sources, comparison set, and date of checking. Observations are separated from recommendations, company claims are identified as company claims, and findings are prioritised by their consequence to the buyer rather than by the amount of work required to fix them.

Findings that do not survive a second check are removed before publication. Comparators are selected for a specific question, such as evidence presentation or category framing, rather than treated as interchangeable competitors.

The complete process, impact definitions, limitations, and corrections policy are documented in METHODOLOGY.md.

Independence and limits

The external reviews are independent and were not commissioned. The standard is to share each review with the company before publication. Advance delivery is unconfirmed for Arcanna.ai, Palm Olympia, SquadStack.ai, and Zaperon. The collection also covers Bolt.new, ChainSecurity, and Massive. The Palm Olympia review discloses the reviewer’s project-side relationship.

The reviews use public pages, public repositories, and published interviews. They do not assess product quality, website analytics, page speed, paid acquisition, or internal commercial performance. Any checks of responsive styles or rendered pages are described in the relevant review. No buyer interviews, funnel data, or win and loss data were available.

A review can establish what evidence a public page presents. It cannot establish how that page converts. Recommendations are reasoned inferences from the observed public surface, not claims about internal performance.

Corrections

Websites change. Every report records the period it describes, and its findings should be checked against the current page before being quoted as current fact.

Factual corrections are welcome through GitHub Issues. A correction should identify the report, finding, current source, and date checked.

About the reviewer

I work across technical product marketing, security, and open-source infrastructure. My related analyses of accepted open-source fixes are documented in Open Source Fix Analysis.

Licence

The written analysis is released under CC BY 4.0. Company names, product names, and trademarks belong to their owners and are used for identification and commentary. No affiliation or endorsement is implied.

About

An independent collection of Go-To-Market (GTM) strategy assessments, positioning teardowns, and messaging audits for high-growth platforms.

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages