# Messaging Library All pitch variants, message pillars, and ready-to-use copy. Derives from `brand.md`. If anything here conflicts with the north star, update this doc. --- ## Core pitches ### Positioning statement For serious builders who need software they can keep, Solid is Production AI: the AI you use when what you build has to work. Unlike walled-garden tools optimized for the demo and fragmented tool chains that leave the user coordinating, Solid optimizes for the outcome: durable software through better judgment, visible operation, and outputs you can keep. ### One-sentence pitch Solid is Production AI. It builds software that holds up, not prototypes that look good on day one. ### Ten-second pitch The AI you use when the prototype needs to become a real product. Not an AI builder. Production AI. ### Elevator pitch Solid is Production AI: the AI you use when the prototype needs to become a real product. It works under a higher standard, shows its progress, and leaves you with software you can keep improving. ### The verb pitch When you want to build something real, you use Solid. ### The brand thesis The market taught buyers to ask: Can it generate an app? Solid teaches a better question: Is this built for production, or just for the demo? --- ## Audience-specific pitches ### Non-technical builders You know what you need. You are willing to put in real time and effort to build it. The problem is that current tools waste that effort: the first draft looks impressive, then the app falls apart with every iteration. Solid is Production AI. It carries the work forward under a higher standard, so the result holds up past the first impression. ### Technical buyers Use Solid when you want leverage without inheriting a cleanup project. Production AI means the output is held to a standard: inspectable, keepable, and built to go past the prototype. ### Pricing pitch At $40-640/mo, Solid is cheap compared to what it replaces. The alternative is not a cheaper AI tool. The alternative is a rebuild after low-quality output, slow contractor cycles, engineering cleanup time, or the cost of not shipping at all. ### Comparison pitch 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. Solid is Production AI. It optimizes for the outcome. --- ## Message pillars ### 1. Real software, not just a first draft Two failures define the current market. Walled gardens build inside closed environments tuned for impressive first impressions, but the code underneath is unmaintainable. Fragmented tool chains spread the work across disconnected AI products, leaving the user doing project management for AI. Both optimize for their own step, not for the outcome. Solid optimizes for the outcome. **Useful language:** - Built to go past the prototype - Software you can keep - Optimized for the outcome, not just the demo - What matters after the first impression - Not a walled garden. Not a fragmented chain. Production AI. ### 2. Judgment, not just generation The differentiator is not more output. It is better decisions under constraints. Architecture and scoping matter. Tradeoffs matter. The system should not need perfect instructions for every small choice. **Useful language:** - A better standard of decisions - Built with judgment, not just output - Serious work needs more than autocomplete ### 3. Visible operation, not black-box magic Trust rises when users can see progress, inspect outputs, and recover when the work changes. Solid should feel like a calm, visible system rather than a black box performing tricks. **Useful language:** - See the work take shape - A visible build process - Clear progress, recoverable workflow ### 4. Artifacts you keep The result should outlast the session. Outputs become durable assets. Users can keep, refine, hand off, and build on the work. The value is not trapped in chat. **Useful language:** - The artifact is what you keep - Work that remains after the session - Durable outputs, not disposable generations ### 5. A higher standard, not a louder story Solid should feel premium because the quality bar is materially higher, not because the brand is trying to sound elite. Seriousness over spectacle. Quality over cheapness. Restraint over hype. **Useful language:** - Worth paying for when the software matters - A higher standard, not a lower price - Serious software for serious work --- ## Product truths Use these as support, not as headlines. Lead with what the user gets, then explain the mechanism. | Truth | Outcome language | |---|---| | Multi-model orchestration | Uses different strengths at different stages instead of forcing one model to do everything | | Strict quality rules | Output is held to a standard, not simply accepted because it exists | | Controlled execution environments | Work happens in a repeatable system, not an opaque performance | | Conversation as recovery | When direction changes, the user steers instead of starting over | | Durable artifacts | The result can be reviewed, handed off, edited, and kept | --- ## Reasons to believe ### What the user should understand - Solid uses a more disciplined process, not just a bigger promise - Solid carries work forward instead of dumping a first draft - Solid leaves users with work they can keep improving - Solid makes the build process visible enough to trust ### Proof forms to prioritize - Before-and-after stories from users who hit the prototype trap elsewhere - Demos showing progress, revision, and recovery - Examples of artifacts that survive beyond the first session - Evidence of reduced cleanup or rebuild work - Concrete output comparisons, not adjective-heavy claims --- ## Campaign angles - Other tools wow you on day one. Solid matters on day thirty. - Build it once. Keep it. - What happens after the demo? - Production AI. Build software that holds up. - Not a prototype tool. Production AI. - Is this built for production, or just for the demo? - The demo is the easy part. Solid is for what comes after. - Your current AI optimizes for its step. Solid optimizes for the outcome. --- ## Testing Track messaging experiments and feedback here. What are you trying, what worked, what didn't. ### Open questions - Does "Build software that holds up" outperform "Production AI. Build something real"? - How quickly does "Production AI" register as a category vs. an adjective phrase? - Which proof signals matter most to the primary audience: speed, recoverability, code quality, handoff quality, or post-build stability? - How strongly should we lean into prototype trap contrast on the homepage vs. deeper pages? - Does the "two failures" framing (walled gardens + fragmentation) resonate more than the simpler "prototype trap" framing? - Does "Is this built for production, or just for the demo?" work as a standalone question in ads and social? ### Settled by brand.md - "Autonomous" is a supporting descriptor at most. Useful in technical explanation and sales, not the hero of the brand. - Primary audience is non-technical builders with real stakes. Technical builders are a recognized secondary audience with their own pitch (see "Audience-specific pitches" above). ### Experiment log | Date | What we tested | Result | Next step | |---|---|---|---| | | | | |