- The Intempt Recipe Marketplace is open for submissions. A recipe is one recipe.md file: a plan Blu runs step by step inside your own workspace, using your access, and nothing runs until you approve it.
- Submit from your coding agent, the Intempt CLI or the web form. A person on the team reads every submission within two business days.
- Published recipes carry your name, and creators on the Build track earn when other teams run them. Installing recipes straight into the console ships separately.
The Intempt Recipe Marketplace is open for submissions. If you've run a GTM play that works, you can write it down as a recipe, send it in today, and a person on our team will read it within two business days.
Published recipes carry your name. Creators on the Build track earn when other teams run them. Here's what a recipe is, what's in the marketplace now, the three ways to submit, and what we turn down.
What a recipe is
A recipe is one file, recipe.md. It's a plan Blu runs step by step inside your own workspace, using your access. Blu is the agent inside the agentic GTM software we build, and it never acts on a recipe on its own. Nothing runs until you approve the plan.
Each step builds one thing. A segment. An email. An image. An attribute. That rule keeps a recipe readable: you look at the plan and know what will exist in your workspace when it's done.
Every recipe also says whether it can run today. The label comes from the steps, not from the author:
- Install now. Every step builds something the engine builds today.
- Coming soon. At least one step waits on a builder that hasn't shipped yet, and the recipe names what it's waiting on.
What's in the marketplace today
The Intempt Collective Marketplace opens with 302 recipes. People on the Intempt team curate them, and the curator's name sits on each recipe page.
| Status | Recipes | What it means |
|---|---|---|
| Install now | 68 | Every step builds something the engine builds today |
| Coming soon | 234 | At least one step waits on a builder that hasn't shipped |
| Total | 302 | Browse all of them at /recipes |
We published the Coming soon recipes on purpose. They show what the engine needs to build next, and they give creators a target. If you know a better version of a play, write it.
Why we opened it to submissions
The best GTM plays don't live in a vendor's help center. They live with the operators who've run them for years. Anyone can write "email inactive users." The part worth sharing is which users, by which event and window, what the email says, and why that timing works.
A recipe is how that judgement gets written down once and run by anyone. It's the same idea behind Claude Code skills: a file that forces a stated method, so the agent does the same thing every run.
Three ways to submit
Pick the route that matches what you already have. All three land in the same review queue.
1. Your coding agent
Paste these two prompts into Claude Code, Codex, Cursor or any coding agent, one at a time:
Set up the Intempt recipe creator by following the steps in https://github.com/intempt/recipe-creator
Create an Intempt recipeThe recipe creator interviews you for the judgement behind the play and drafts the steps. If you start from a segment or attribute that already works in your workspace, it reads the setup, never the rows. Before anything leaves your machine, it shows exactly what it will send and waits for your yes.
2. The Intempt CLI
The recipe command is rolling out in the Intempt CLI now. Until your version has it, use your agent or the web form.
intempt login
intempt recipe new my-recipe
cd recipes/<your-name>/my-recipe
intempt recipe validate recipe.md
intempt recipe submit recipe.md- new writes a recipe.md from a template that already passes validation.
- validate checks the file and tells you whether it's Install now or Coming soon.
- submit previews exactly what would be sent first. It only sends after you confirm.
3. The web form
Go to the submit page. Drop or paste your recipe.md and a live preview shows the title, the step count and whether it's Install now or Coming soon. Add your creator profile, confirm you have the right to share it, and send. The form refuses anything that looks like an API key or token.
What you do, and what we do
You keep the thinking. We handle the machinery. Rough drafts are welcome.
| You bring | We handle |
|---|---|
| The insight that shapes the recipe | Writing each step so the engine can run it, one thing per step |
| The title and summary, in your own voice | Marking it Install now or Coming soon, honestly |
| Your creator profile: name, work email, byline | Group, persona and tags, plus formatting, safety and QA checks |
What we turn down
We'll help with almost anything. Not these five:
- Unsafe recipes. No copying data to another service, no hidden comments or invisible characters, no step that says to go get the real instructions from a link.
- Made-up results. Don't claim outcomes the recipe can't show. If a step needs a specific event, declare it as a prerequisite.
- Steps the engine can't run. Vague steps, two jobs in one step, and strategy with nothing to build come back for another pass.
- A tool pitch with no play underneath. Building on one tool and naming it is fine. A thin recipe whose real point is a sale is not.
- Real customer data. No names, emails, ids or lists. The recipe describes the play; the installer's workspace supplies the data.
Need Shopify, HubSpot or Slack? Declare the connector under prerequisites. Integrations connect in the installer's own workspace with their own credentials, so a key never goes in the file.
How review works
Every submission gets read by a person on the Intempt team, and you hear back within two business days.
- Send it from your agent, the CLI or the form.
- Keep the submission ID you get on screen. It's how you and we refer to the same submission.
- A person reads it. Somya Nayak, who runs the Intempt Collective, checks it for safety, usefulness and whether it runs, and replies within two business days.
Then curation, and we'll be straight about it. Some submissions merge into a similar recipe. Some come back for another pass. Some don't publish. Where two recipes overlap we merge them or keep the stronger one, and a no comes with the reason.
You keep your copyright. Published recipes carry your name and live at a permanent path in the public intempt/recipe-creator repository and on intempt.com. To withdraw one, email hey@intempt.com with "Recipe withdrawal, for Somya" and your submission ID. The full rules are in the submission guide.
Get paid when other teams run your recipe
Creators on the Build track of the Intempt partner program earn on every run once a recipe is accepted and published. You get a share of the credits your recipe uses in other customers' workspaces. Runs in your own organizations don't count, and you keep the IP.
Build has no application review. You join from your profile, and a recipe starts earning once it's published. If you also refer the team that runs it, the referral commission and the recipe royalty stack.
The rest of the Collective
The marketplace is one part of the Intempt Collective. Blu Slack is where GTM operators trade prompts, workflows and teardowns, and it's a good place to test a play before it becomes a recipe. Claude for GTM collects free, open-source Claude skills for marketing, sales, design and analytics.
Write your first recipe
Start with a play you've already run and would explain to a new hire. Pick a route above, read the submission guide, and send it in. We'll read it within two business days. The recipe marketplace grows one play at a time, and every published recipe is a plan Blu runs inside Intempt.
