Questions, answered straight

Foothold Foundry is the venture operating system for AI-era founders: one place to take an idea from first spark to first customers. It handles everything but the code: validation, branding, naming, positioning, requirements, pricing, launch, outreach, and growth, so the venture around your product gets built as fast as the product itself.

Foothold Foundry deliberately does not write your application code. It does the venture work around the code: validating the idea, branding it, specifying it, launching it, and growing it. Your code comes from you, your team, or an AI coding agent; the Launch Packet hands any of them a complete, structured brief.

Founders at three moments: first-time founders who need a whole team's worth of hats, developers who want to build the product and skip the marketing busywork, and operators running several ventures at once. If you can bring an idea and make decisions, the Foundry carries the rest.

A chat gives you answers that scroll away; Foothold Foundry gives you a venture that accumulates. Every tool writes into your venture's project memory, so the pricing work builds on the personas, the pitch builds on all of it, and the output is structured documents, records, and a sendable campaign, not a transcript.

No. Foothold Foundry does not host or build your website or app; it produces the thinking and the assets behind one: positioning, messaging, page-ready landing copy, a brand kit, and requirements. Pair it with your site builder or coding tool of choice and paste the copy in.

Yes. Ventures are first-class: each gets its own lifecycle modules, brand, audience, and analytics, and a cross-venture dashboard shows every bet at a glance. Plans set how many ventures you can run at once, and the Feedback tool feeds what customers say back into your next idea.

Yes. Workspaces support members with roles, invited by email with a strict-match accept flow. A cofounder can own Grow while you live in Build, and everyone works against the same venture memory. Joining an existing workspace is by invitation only; a fresh signup always creates its own workspace.

Start by pressure-testing the idea before you build anything. Write it down, check who else solves the problem, and put a price on it. Foothold Foundry's Concept stage walks exactly that path: definition, customer discovery, competitive analysis, market sizing, pricing, and a validation scorecard. It is free to start.

Name it, brand it, write the landing copy, and go where your users already complain about the alternatives. Foothold Foundry's Build and Grow stages do that work: naming with availability checks, a brand kit, messaging, landing copy, a launch plan, Product Hunt and Show HN copy, and outreach you approve before anything sends.

No. Each stage lays out the path in plain language: what this step is, why it matters, and what good looks like. The tools draft the work, then teach you what they did, so first-time founders learn the craft while shipping it. Experienced operators can skip any step; the Foundry adapts around what you ignore.

No, and that is deliberate. The product covers everything but the code. What it does produce is what a builder needs: requirements as reviewable records from a virtual PM, architecture decision records from a virtual CTO, and a Launch Packet you can hand to an engineer or an AI coding agent like Claude Code or Cursor.

The tools run on Anthropic's Claude models. Model use is metered in credits, and you always see what a run costs before you start it. Your owned data, meaning your contacts and lead lists, is never part of what goes to the model; see the AI transparency page for the full boundary.

No. Your data is not used to train AI models, ours or anyone's. Stronger than that: your owned data, your contact rows, lead lists, and personal information, is never sent to an external AI provider at all. AI features draft templates with placeholders; the real details merge on our servers at send time.

No. Nothing sends, posts, or spends on its own. Every outbound email requires a human trigger behind an always-on preview gate, suppression list, and one-click unsubscribe. Every credit spend shows its price before it runs. The Foundry drafts and recommends; the operator decides. That split is a design rule, not a setting.

There is a free plan with credits included every month, so you can validate an idea without paying anything. Paid plans add more credits, more ventures, and higher sending allowances, and you can buy credit packs when a big push needs them. Current prices are on the pricing page. Cancel anytime; no lock-in.

Credits are the meter for the AI work. Each tool run has a visible price in credits, your plan grants a fresh allowance each month, and purchased packs cover spikes. You see the cost before you run anything, and failed work is never charged. Sending email does not use credits; plans include a send allowance.

You keep everything through the end of the period you paid for: access, granted credits, and your data, with no clawback. Purchased credit packs stay usable for their normal life. Your work is exportable as a structured document tree via the Launch Packet, so nothing you made is trapped here.

Only when you tell it to, through sending infrastructure you own. Campaigns go out through your own Amazon SES identity, so your deliverability reputation is yours. Suppression, one-click unsubscribe, and CAN-SPAM compliance are always on, and a human triggers every send. Nothing fires on autopilot.

Yes. The briefs, brand kit, copy, requirements, decisions, and plans generated for your venture are yours, and the Launch Packet exports them as a portable docs tree (a README plus structured markdown) you can hand to anyone. We claim no rights over your venture's content. Your data leaves when you do.