# OpenSpec landing-page Growth Score report

Lazyweb publishes a public search API over its indexed pages; the guide is at https://www.lazyweb.com/agent-access.

Source: https://www.lazyweb.com/yc-w26/openspec
Source observed: 2026-10-08T01:43:46.862Z
Last checked: 2026-10-20T08:31:20.266+00:00
Indexed: 2026-10-08T03:59:05.277+00:00

---

# OpenSpec landing-page Growth Score

We analyzed OpenSpec, a lightweight and configurable framework for creating and managing software specifications. OpenSpec’s stated goal is to help teams capture what they want to build, keep the team and coding agents aligned, refine requirements, validate that they describe the right thing, and verify that the implementation matches. Its headline is **“The spec framework for building the right thing and building it right.”**

Product site: [http://openspec.dev/](http://openspec.dev/)

[← Back to YC W26](https://www.lazyweb.com/yc-w26)

## Overall result

OpenSpec’s Growth Score is **66**, updated **September 22, 2026**. The weakest category is **CTA**, scored **48**.

| Category | Score | Rating or purpose |
|---|---:|---|
| CTA | [48](https://www.lazyweb.com/yc-w26/openspec#gs-cta) | Poor |
| Mobile web | [62](https://www.lazyweb.com/yc-w26/openspec#gs-mobile_web) | Fair |
| Information hierarchy | [68](https://www.lazyweb.com/yc-w26/openspec#gs-information_hierarchy) | Fair |
| Trust | [72](https://www.lazyweb.com/yc-w26/openspec#gs-trust) | Fair |
| Value props | [82](https://www.lazyweb.com/yc-w26/openspec#gs-value_props) | Strong |

[Fix CTA](https://www.lazyweb.com/plans/checkout?plan=individual&source=growth_score_feature_build_fixes)

## How OpenSpec ranks

1. [GitHub Spec Kit — 69](https://www.lazyweb.com/growth-score/site/github.com)
2. [Kiro — 69](https://www.lazyweb.com/growth-score/site/kiro.dev)
3. OpenSpec — 66
4. [Tessl — 65](https://www.lazyweb.com/growth-score/site/tessl.io)

## Score over time

The tracked reports show these observations:

1. **September 22, 2026 — 66**, live: overall +1, mobile web +4, information hierarchy +2.
2. [September 9, 2026 — 65](https://www.lazyweb.com/growth-score/history/2026-09-09): overall −1, CTA −6.
3. [August 31, 2026 — 66](https://www.lazyweb.com/growth-score/history/2026-08-31): overall +4, value props +26, CTA −14.
4. [August 12, 2026 — 62](https://www.lazyweb.com/growth-score/history/2026-08-12): overall +2, CTA +14, mobile web −6.
5. [July 1, 2026 — 60](https://www.lazyweb.com/growth-score/history/2026-07-01): overall +1, trust +6, CTA −3.
6. [June 6, 2026 — 59](https://www.lazyweb.com/growth-score/history/2026-06-06): overall −1, trust −10, mobile web +6.
7. [May 19, 2026 — 60](https://www.lazyweb.com/growth-score/history/2026-05-19): first tracked report; strongest category was Trust at 72 and weakest was Value props at 52.

## CTA — 48, Poor

The CTA assessment considers copy, size, verb, and cost-feel: whether the primary CTA earns the click.

![OpenSpec CTA comparison capture](https://zlfyzdmohcskkucuunmk.supabase.co/storage/v1/object/public/sites/growth-score/site/openspec.dev.jpg?v=2026-09-22T20%3A07%3A39.628%2B00%3A00)

The comparison labels the examples **OpenSpec in-product action**, **Tessl**, **GitHub Spec Kit**, and **Kiro**. OpenSpec’s CTA has these problems:

- It sits at the bottom edge of the desktop fold.
- It is absent from the mobile fold entirely.
- It is styled as documentation rather than an action.
- It has no action verb or payoff copy.

CTA rankings in this category are Tessl 86, GitHub Spec Kit 72, Kiro 68, and OpenSpec 48.

[Rewrite this CTA](https://www.lazyweb.com/backlog?site=openspec.dev#opt-cta-writing) — our CTA rewrite studio generates primary and secondary CTA options grounded in OpenSpec’s offer and visitor objections.

## Mobile web — 62, Fair

The mobile assessment treats the phone experience as a first-class citizen.

![Mobile web annotations on the mobile capture](https://zlfyzdmohcskkucuunmk.supabase.co/storage/v1/object/public/sites/growth-score/site/openspec.dev-mobile.jpg?v=2026-09-22T20%3A07%3A39.628%2B00%3A00)

1. **Synopsis body paragraphs:** Monospace body text barely scales down and wraps into nine dense lines, pushing the install CTA far below the fold.
2. **Decorative wave graphic:** A large ornamental band consumes prime viewport space while the primary install action remains off-screen.

[View mobile fixes](https://www.lazyweb.com/backlog?site=openspec.dev#opt-mobile-web) — our mobile fix plan converts these findings into a prioritized implementation checklist.

## Information hierarchy — 68, Fair

This category asks whether the design helps or inhibits what the page is trying to say.

![Information hierarchy annotations on the desktop capture](https://zlfyzdmohcskkucuunmk.supabase.co/storage/v1/object/public/sites/growth-score/site/openspec.dev.jpg?v=2026-09-22T20%3A07%3A39.628%2B00%3A00)

1. **Install command block:** The only actionable element sits at the fold’s bottom edge with the same muted weight as body copy, so visitors do not find it in one second.
2. **GitHub stars navigation link:** The red “/ 69.9k stars” is the highest-contrast header element, pulling attention toward an exit before any on-page action.
3. **Inline anchor link:** The underlined “build the right thing and build it right” link reads as the page’s most prominent action but competes with the install CTA below.
4. **Navigation link row:** Four equal-weight exits—CHANGELOG, BLOG, DOCS, and GITHUB—lack subordinate styling and draw attention before the value proposition lands.

[View layout plan](https://www.lazyweb.com/backlog?site=openspec.dev#opt-information-hierarchy) — our layout priority plan turns these callouts into a sequenced keep, move, merge, or remove plan.

## Trust — 72, Fair

The trust review focuses on proof that the product is real, competent, and safe to try.

| Product | Trust read |
|---|---|
| OpenSpec | “69.9k GitHub stars” and “265,000 developers a month” appear in the ADOPTION section. |
| GitHub Spec Kit | A code-editor screenshot shows tabs “game.ts”, “characters.module.css”, and “bonus-level.ts”. |
| Kiro | A real IDE screenshot shows a sessions list and a PR pane labeled “feat(dashboard): collapse turn-recovery injections” #842, with passing checks visible in the supplied text. |
| Tessl | A product UI panel titled “Improve skills from real usage” shows a code-review scorecard with Quality 89%, Impact 99%, and a Security value that is cut off in the supplied text. |

Trust rankings are OpenSpec 72, Kiro 58, GitHub Spec Kit 50, and Tessl 48.

[Build proof section](https://www.lazyweb.com/backlog?site=openspec.dev#opt-trust-signals) — our proof section builder helps choose proof signals and their copy and placement.

## Value props — 82, Strong

The value-proposition review covers the title, subtitle, and hero.

> **The spec framework for building the right thing and building it right**
>
> OpenSpec is a lightweight and configurable framework for creating and managing software specifications.

### What works

- The headline names the category and its dual outcome in one line.
- The page includes rare proof points: **69.9k stars** and **265k developers per month**.
- The synopsis spells out the value of alignment with coding agents.

### What could improve

- There is no emotional hook for the pain of building the wrong thing.
- The hero art decorates rather than demonstrates the product.
- The proof numbers are buried below the fold line.

Value-proposition rankings are OpenSpec 82, Kiro 76, GitHub Spec Kit 56, and Tessl 52.

## Competitors

We identify competitors from product, audience, and value proposition:

| Rank | Product | Site | Score |
|---:|---|---|---:|
| 1 | [GitHub Spec Kit](https://www.lazyweb.com/growth-score/site/github.com) | github.com | 69 |
| 2 | [Kiro](https://www.lazyweb.com/growth-score/site/kiro.dev) | kiro.dev | 69 |
| 3 | OpenSpec | openspec.dev | 66 |
| 4 | [Tessl](https://www.lazyweb.com/growth-score/site/tessl.io) | tessl.io | 65 |

## Available report actions

- [Fix CTA](https://www.lazyweb.com/plans/checkout?plan=individual&source=growth_score_feature_build_fixes)
- [Rewrite this CTA](https://www.lazyweb.com/backlog?site=openspec.dev#opt-cta-writing)
- [View mobile fixes](https://www.lazyweb.com/backlog?site=openspec.dev#opt-mobile-web)
- [View layout plan](https://www.lazyweb.com/backlog?site=openspec.dev#opt-information-hierarchy)
- [Build proof section](https://www.lazyweb.com/backlog?site=openspec.dev#opt-trust-signals)

---

[Read this page’s summary](https://www.lazyweb.com/api/public/v1/page-tldr?url=https%3A%2F%2Fwww.lazyweb.com%2Fyc-w26%2Fopenspec&trace=t_bc7e1c4e5b07)

## Ask a follow-up about this page

Need a more specific answer? Ask the exact question you have. It returns a fresh, cited answer from Lazyweb’s knowledge base. No account or API key required.

Open this URL with your own question, URL-encoded. Only q is required. No account or setup.

`GET https://www.lazyweb.com/agent/faq?q={question}&trace=t_bc7e1c4e5b07`

[Tool guide and examples](https://www.lazyweb.com/agent-access) · [OpenAPI](https://www.lazyweb.com/api/public/v1/openapi.json) · [Page TLDR form](https://www.lazyweb.com/agent-tools/page-tldr?url=https%3A%2F%2Fwww.lazyweb.com%2Fyc-w26%2Fopenspec). Opening a form does not execute a tool.