Describe a task in plain English — research these prospects, send this outreach, handle this inbox, follow up on these deals. Builder plans the work, does it end-to-end, and hands back a finished result. Think of it as a new hire who starts on their hundredth day, not their first.
Configure once, run continuously. Every capability below is a production-grade surface, not a demo.
Every agent is a role: a Lead Research Agent, an Outreach Agent, a Support Agent. You set scope, tools and guardrails once — Builder runs them on a schedule or on demand.
Agents chain steps — research a company, draft outreach, send it, follow up, escalate warm replies — so the result arrives done, not halfway.
Native connectors for CRMs, ticketing systems, data warehouses, inboxes and calendars. Builder reads from them and writes back to them.
Plan, tool calls, sources and output are captured. Approve, edit or override any step — then promote a run to a recurring job.
Drop in 500 prospect companies. Builder visits each website, finds the right person on LinkedIn, checks if they match the kind of buyer you want, and writes a personalised opener for your sales team.
Every Builder module shares the same orchestration layer, the same audit trail, and the same integration fabric — so a win in one surface lands everywhere.
Every agent is a role: a Lead Research Agent, an Outreach Agent, a Support Agent. You set scope, tools and guardrails once — Builder runs them on a schedule or on demand.
Agents chain steps — research a company, draft outreach, send it, follow up, escalate warm replies — so the result arrives done, not halfway.
Native connectors for CRMs, ticketing systems, data warehouses, inboxes and calendars. Builder reads from them and writes back to them.
Plan, tool calls, sources and output are captured. Approve, edit or override any step — then promote a run to a recurring job.
Browse a library of specialists — from SDR to Controller — or clone one into your own. Every agent shares the same planning engine, tool catalogue and audit trail.
Every run opens a live trace: the plan, each tool call, the artefacts produced. Step in at any point to correct course — or approve the whole thing with a click.
Promote a successful run to a recurring job. Trigger on time, on webhook, or on a signal from another product in the Mariete suite.
CLI, SDKs and a single HTTP API. Every product on the platform exposes the same surface — same auth, same idempotency, same observability.
# Kick off a Builder agent from the CLI
mariete run lead-research \
--icp "Series-A SaaS, NA, 50–200 FTE" \
--targets targets.csv \
--output ./briefs
# Promote this run to a weekly job
mariete schedule lead-research \
--cron "0 7 * * MON" --owner marc@acme.coWhat comes in, what goes out, what it runs on. Nothing hidden in a sales deck.
Step-by-step recipes that wrap Builder around a specific outcome. Same agent, plugged into a real workflow your team already cares about.
Drop in a list of prospect companies on Sunday night. Builder visits each website, finds the right person on LinkedIn, checks if they look like the kind of buyer you want, and writes a personalised opener for each one.
Builder groups your prospects, writes an email to each one in your voice, sends at the right time of day, follows up on day three and day seven, and hands any warm reply straight to a rep.
Every week Builder reads your competitors' pricing pages, job posts, press coverage, and review sites — then sends you a short, structured brief before your stand-up.
Builder reads your long-form piece and turns it into LinkedIn posts, tweets, a newsletter, and a short video script — all written in your voice and ready to schedule.
No credit card. No sales call. Run one workflow end-to-end and decide.
