POSITIONING
Outcomes first. The means second.
Where we play
I sit between the behemoths and the prompt-to-prototype tools: the layer that makes software safe to run, own and ship, for you and your clients. Outcomes open the conversation; the elements below are what neither flank sells today.
| Company | Class | Their words | Where they stop (2026-09-21) | Where we differ |
|---|---|---|---|---|
| Bolt | Prompt-to-app builder | “Create stunning apps & websites by chatting with AI.” — Bolt | On 2026-09-21 its homepage describes Bolt Cloud hosting, databases and user management inside one interface; it does not describe a recorded dev-test-production promotion ladder. (source) |
LIVE You get a recorded path from test to production and typed checks before anything is called done; they keep you inside one hosted stack without that ladder. |
| v0 | Prompt-to-app builder | “Deploy to production immediately, or open a pull request for review.” — v0 | On 2026-09-21 its docs homepage describes deploy to Vercel and PR review; it does not describe grant-locked production state doors. (source) |
LIVE Production state moves only through validated doors, not casual edits; they deploy to Vercel and review pull requests without grant-locked carriers. |
| Cursor | Coding agent | “Cursor is your coding agent for building ambitious software.” — Cursor | On 2026-09-21 its homepage markets an IDE coding agent for repositories; it does not sell a governed three-platform app outcome for your clients. (source) |
IN BUILD A governed three-platform app outcome for your clients, not just faster edits in a repository. Today: the web shell and iPhone simulator path run under typed checks and three switchable looks. |
| GitHub Copilot | Coding agent | “GitHub Copilot is an AI assistant that helps you write, understand, and ship software.” — GitHub Copilot | On 2026-09-21 GitHub Docs describe Copilot inside issues, pull requests and repositories; they do not describe runtime-switchable Trio themes on shipped apps. (source) |
LIVE Every shipped app carries three complete looks you switch at runtime; Copilot assists inside GitHub and does not ship that on your product. |
| Squarespace | Site builder | “Join millions of entrepreneurs who run their business on Squarespace.” — Squarespace | On 2026-09-21 its homepage FAQ states paid subscriptions start at 19 US dollars per month after a trial; it does not describe native iPhone and Android apps from one contract. (source) |
IN BUILD iPhone and Android apps from the same effort as the site. Today: the site, three switchable looks, and a recorded path from test to production on what already runs. |
| Webflow | Site builder | “Webflow gives every team the tools to build, manage, and grow a website” — Webflow | On 2026-09-21 its homepage headline scope is websites that drive revenue; it does not describe an ethics gate on every build. (source) |
IN BUILD An ethics gate on every build before work proceeds. Today: the ethics gate exists in the line; the full generation line has not run clean end to end. |
| Framer | Site builder | “Framer is the design agent for every step from idea to launch” — Framer | On 2026-09-21 its homepage markets design agents, CMS and hosting on Framer; it does not describe democratic-country-only model routing policy. (source) |
LIVE Model routing sends personal data only to democratic-country endpoints by policy; Framer sells design agents and hosting without that contract. |
| Factory.ai | Stack behemoth (engineering) | “Delegate complete tasks without replacing their existing tools.” — Factory.ai | On 2026-09-21 its homepage targets engineering teams delegating repository and CI work; it does not describe outcomes priced per partner app for non-engineering buyers. (source) |
LIVE Outcomes and guardrails for buyers who are not engineering orgs delegating repository work; state moves through validated doors and checks run before judges. |
| Warp | Stack behemoth (engineering) | “Infrastructure to build, measure, and interact with agents across your SDLC” — Warp | On 2026-09-21 Warp Factories is Early Access for engineering teams (Slack/Linear/GitHub → mergeable PR, cost-per-PR insights); it does not describe outcomes priced per partner app, Trio themes, or grant-locked production doors. (source) |
LIVE Outcomes and guardrails for buyers who are not engineering orgs; production state moves through validated doors and checks run before judges. |
| Salesforce Agentforce | Stack behemoth (CRM suite) | “Agentforce is the AI agent platform that delivers 24/7 autonomous support” — Salesforce Agentforce | On 2026-09-21 its homepage describes agents inside the Salesforce Customer 360 stack; it does not offer portable, operator-ratified contact records outside that suite. (source) |
LIVE Your contact records stay portable and operator-ratified, not locked inside Customer 360; that substrate runs in production today. |
LIVE: on the public record in production today. IN BUILD: named on the ladder but not yet fully demonstrated end to end.
Human-in-the-loop channel (not competitors)
Figma: design source and handoff for agencies who keep craft and client relationships.
Canva: brand surfaces and kits that feed declared themes without discarding the designer.
Adobe: Creative Cloud libraries and exports as inputs; the person keeps taste, the system takes assembly.
What I sell, and what I don't.
The proposition is an outcome for a named buyer: a working app for a partner, or a studio’s client screens that ship.
I describe the machinery to people I already work with; I do not lead with it in public.
Outcomes open the conversation; the differentiators close it.
Who it is for.
Two channels exist today: design studios and small agencies who keep the brand, taste, curation and the client; and partners who bring a product and a market.
A third is for outcome customers who want the means to change the result themselves, inside an existing relationship.
How pricing works.
Pricing is per outcome, never per project of generated code.
Nothing is priced until an outcome has shipped.
What I will not claim.
No claim above what runs, no zero-hallucination claim, no “replaces your engineers”, no comparison on price, no speed multipliers, no endorsements or testimonials until a shipped outcome exists, and no per-project prices.
Why this shape.
Black-box stacks ask designers to throw away their craft; this approach preserves it.
The person keeps taste and the client; the system takes the technical grind.