Foundry Kit: building around ownership, not lock-in
How Foundry Kit's clearest offer became portable website source code instead of a vague website-builder promise.
Case study
Project: Foundry Kit
Date: 2026
Context
Foundry Kit is a website builder for people who want a practical site and a way out. The public surface emphasizes prompt-to-site generation, revision, export, and static hosting.
Problem
Most builder language sounds identical. The useful distinction is ownership: users should be able to leave with ordinary source files that can run on common static hosts.
Constraints
- Avoid claiming broad platform replacement before adapters are mature.
- Keep AI-provider details, costs, prompts, and private implementation data out of public copy.
- Public examples need to click through to credible generated surfaces, not just prompts.
Approach
The product story is narrowed to a concrete promise: describe a website, revise it, export source, and host it anywhere static files run.
Result
Foundry Kit has a live product surface with pricing, docs, templates, security, status, and access routes. The public proof supports a focused website-output tool.
Lessons
The best first sale is the narrowest honest one. Foundry should prove source export and useful sites before expanding into heavier platform claims.