# Competitive Positioning

Market framing and approved comparison language. Derives from `brand.md`.

---

## General rule

Solid is not in the same category as Bolt, Lovable, Replit, or v0. Those tools are the problem context that makes Solid's value self-evident, not the competition.

Two failures define the current market: walled gardens optimized for the demo, and fragmented tool chains that leave the user doing the glue work. Both optimize for their own step, not for the outcome. Frame these failures as the enemy, not named competitors. Let the category separation do the competitive work.

---

## Market framing

### Prototype-first AI builders (Bolt, Lovable, v0, Replit)

Walled gardens tuned for impressive first impressions. The output looks good in the preview but the code underneath is unmaintainable. It cannot connect to existing APIs, cannot be extended, and cannot survive past the demo. The wall keeps the magic visible and the mess hidden.

They are not Solid's competition. They are the experience that drives people to Solid. Solid exists for the people those tools failed.

### Fragmented tool chains

One AI writes code. Another writes tests. Another deploys. Another monitors. No single tool owns the full production lifecycle, so humans do the glue work: coordinating tools, bridging gaps, fixing what one tool broke for another. The promise was less work. The reality is project management for AI.

This is not a specific competitor. It is the market structure that makes Solid necessary.

### Coding assistants (Cursor, GitHub Copilot)

Help developers move faster inside code workflows. That is a different job than building software that holds up without acting as the engineer.

### General autonomous agents (Manus, OpenClaw)

Claim breadth: "do everything." Per Ries & Trout, claiming everything means owning nothing. Manus going broad is Solid's permission to go deep.

The contrast is clean: Manus does a little of everything. Solid builds things that actually work.

---

## Approved comparison language

**vs. Lovable, Bolt, Replit:**

> Those are AI builders. They help you get a prototype started quickly. Solid is Production AI. It is built for what happens after the first impression.

**vs. Cursor, Devin:**

> Those tools are closer to developer productivity and engineering team workflows. Solid builds software forward even when the user is not acting as the engineer.

**vs. Manus:**

> Manus is a general agent. It does a little of many things. Solid is Production AI. It goes deep on building software that holds up.

**vs. the fragmented stack (multiple AI tools):**

> One tool writes code, another tests it, another deploys it. The result is project management for AI. Solid handles the full lifecycle. One tool, one outcome: software that holds up.

---

## When to use direct comparisons

**Use in:** sales conversations, FAQ pages, review and comparison content, influencer content, customer stories.

**Avoid in:** hero headlines, top-level brand lines, launch manifesto copy.

---

## What not to do

- Do not call adjacent tools stupid, fake, or useless
- Do not fight on speed alone
- Do not over-explain the competitive map in hero copy
- Do not accept the frame that Solid is in the same category as prototype tools

---

## Testing

| Date | Comparison context | What we tried | Result |
|---|---|---|---|
|  |  |  |  |