Foundry Kit: building around ownership, not lock-in

The builder market runs on lock-in. Foundry Kit's whole pitch is the exit: brief in, portable source out — a promise narrow enough to test.

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

Receipt: a live product at foundry-kit.com — builder, pricing, docs, templates, security posture, and status surfaces, all public. The proof supports a focused website-output tool and claims nothing broader; the instrumented revenue answer is the current mission, not a past-tense boast.

Lessons

The best first sale is the narrowest honest one. Foundry should prove source export and useful sites before expanding into heavier platform claims.