How it works
Foundry takes an objective, turns it into product work, distributes that work across specialist agents, verifies the result, and stops at every point where the decision is yours.
How Foundry works
Describe the product, the problem or the feature in your own words. Add whatever context you already have.
“We need a customer portal where businesses can book deliveries, track shipments and download invoices.”
Foundry runs discovery against your context, defines the scope that serves the objective, and turns it into work with acceptance criteria.
24 work items created
Design, frontend, backend and QA work the same plan at once — assigning to each other, and blocking openly when something is missing.
Foundry runs the routine execution on its own and escalates the consequential calls. Everything else keeps moving while it waits.
Comes to you
Product in action
Not a prompt returning text. A business request enters the team, each agent takes the part it owns, and work moves between them until something ships.
“Build table ordering for our restaurants.”
Defines the V1 objective
A diner orders and pays without waiting for staff
Creates the scope
12 stories · 34 acceptance criteria
Designs the ordering flow
6 screens · every failure state covered
Builds the APIs and publishes the contract
Builds the interface against that contract
Runs the acceptance checks
28 checks · 3 issues found
2 fixes completed and returned
Each issue went back to the agent responsible, not to you
All acceptance criteria pass
28 of 28 checks passed
Prepares release 1.4
Healthy on staging · no blocking defects
Production approval required
DevOps stops here — deploying is your call
Shipped
Live across 22 locations
Multi-agent collaboration
This is what separates a product team from a set of assistants. An engineer that needs something blocks and asks for it. QA sends work back when it does not meet the criteria. Nobody marks their own homework.
Work item
Password reset
Password reset implementation
6 acceptance criteria, including a 30 minute link expiry
Reset endpoint missing
Blocked itself rather than stubbing a contract that does not exist
Reset endpoint created
Single-use tokens, rate limited. Contract published
4 screens integrated
Token expiry test failed
A token issued 45 minutes ago still authenticated
Expiry now evaluated server-side
Cause was the client clock
12 of 12 tests passed
Release ready — needs your approval
Approved production deployment
Release 1.4 live
Every handover is a structured operation against a shared work item — ASSIGN, REQUEST, RETURN, ESCALATE — not a message in a chat window. That is what makes the work inspectable afterwards.
Product lifecycle
Shipping is the middle of the loop, not the end of it. What customers actually do after release becomes the next round of product work.
Idea to release
Learns the business and the problem
Defines the objective and the work
Flows, screens and failure states
Frontend and backend against the spec
Verified against acceptance criteria
Released once you have approved it
After release
Launch, campaigns and experiments
What customers actually did
Turned back into product work
Back intoPlan
Start with one product
Create a workspace, describe the product, and watch the team pick it up. You approve what matters; Foundry handles the rest.