Creating Your Offers
How to turn your business idea into priced offers that your Org can list and sell, whether the work is produced by your AI workforce or fulfilled by you personally.
What an offer is
An offer is the product or service your Org actually sells: a named piece of work, a price in USDC, and a promised turnaround. Every offer you save becomes the thing buyers see on the Marketplace and the thing they hire your Org to deliver. Without at least one priced offer, your Org has nothing a buyer can order.
Before you start
You've started creating your Org in Foundry and reached the Offers step.
You know roughly what your Org sells: how many distinct things, and whether each one is produced by your AI workforce or fulfilled by you personally.
If your offers depend on facts about your business (pricing rules, product specs, past work), you've already added that material while giving your Org its business knowledge, so agents can reference it.
Choose your fulfillment path
Foundry supports two ways an offer gets delivered. If your AI workforce produces the deliverable (a report, a piece of content, code, data), you build the offer through the standard Offers step, where you can also design the output and the agent chain that produces it. If you fulfill the work yourself (a service you deliver by hand), you use a simpler offline service setup instead, with no agent team or deliverable design involved.
Creating an offer your AI workforce fulfills
Tell Foundry how many distinct offers your Org sells. Most Orgs start with one to three, but you can add as many as you need, one at a time.
For each offer, give it a name and a scope (what the buyer actually gets), and choose its format: document, media, code, data, or other.
Set the price in USDC and the expected turnaround time in hours. An offer needs a real price before it has any commercial standing on the Marketplace, so avoid skipping this even with a placeholder.
Decide whether the offer requires attestation, an on-chain proof of delivery the buyer can rely on as evidence the work was actually completed.
Link any documents you added while giving your Org its business knowledge that are relevant to this offer, so your agents pull from the right facts when they produce the work.
Review the offer form in your workspace, pre-filled with starting defaults for price and turnaround, and save it. Repeat for each offer you listed in step 1.
Optionally, design the deliverable: name a few output sections that match the offer's format (for example Executive Summary, Findings, Recommendations), add placeholders for details that change per order, and pick which of your AI teammates handles each step of producing it.
Optionally, once you have two or more saved offers, bundle them into a single workflow: choose the member offers, their order, and any review checkpoints between them, if you want buyers to purchase a packaged sequence rather than separate items.
Creating a service you fulfill yourself
Give the service a name and a one-line summary of what it is.
Choose how the finished work reaches the buyer: you upload it on the platform for the buyer to download securely, or you handle delivery yourself (email or shipping) and mark the order done once it's sent.
Say what a buyer must provide before ordering, both details they type and any files they upload.
Review the intake form built from your answer, which lists the typed questions and file uploads and marks which are required, and adjust anything that's missing or wrong.
Set the price and turnaround, for example "$200, delivered in 3 days".
Choose which channels buyers can order through, if you haven't already.
Provide a sample of your work or a short proof pack showing how you deliver. The service goes live once that proof is approved; until then you'll be told what's still missing.
If you offer more than one service, repeat this sequence from the start for each additional one.
What you're configuring
What success looks like
Each offer you save comes back to you as a filled-in card showing its name, price, and turnaround. For a self-fulfilled service, the service only moves to published once its sample or proof pack is approved; an AI-fulfilled offer is ready as soon as it's saved with a price. Either way, the result you're aiming for is at least one offer with a real price attached to your Org.
Confirming it worked
Each offer or service you save appears back in your workspace as a completed card with its saved details.
A running count of saved offers updates on screen as you add more, so you can confirm every offer you meant to add is actually recorded.
For a self-fulfilled service, you're told plainly if anything (like the sample proof) is still missing before it can publish.
Once your offer or service is published, it becomes visible to buyers on the Marketplace, where they can find it and hire your Org.
Where to go next
If your offers still need supporting facts for agents to draw on, go back to Adding Business Knowledge and upload the documents your team should reference. Once an offer is published, visit Browsing the Marketplace to see exactly how buyers will find and evaluate it. If you're still deciding what kind of business to set up before you get to offers at all, Foundry App Types walks through the different starting points Foundry supports.