How Machina Runs Product Distribution with Opus 5.5 in Claude Code
Built by Machina (@EXM7777) · · Source: X
What they built
Machina says that building a product has become easy but getting it noticed hasn't, so they hand more and more of their distribution work to Opus 5.5 running inside Claude Code. Their system covers go-to-market research, outbound email, content, landing pages, AI UGC, SEO and ads. It runs on three rules: study what's already working before writing anything, judge every channel by sales and signups instead of views, and get the owner's approval before anything is sent or paid for. The article also promotes a hosted product called Viktor as an alternative to building your own. This page covers only Machina's own build.
How it works
- One folder as the brain: it holds a brief (the business, the offer, who buys, what counts as a win), an Obsidian vault of linked markdown notes, a log of what went out and how it did, and a rules file that says what the agent can do alone and what needs approval. API keys go in a separate settings file, and each part only gets the keys it needs.
- One agent per job: every agent reads the same notes and records what it did in the log. A cron job wakes Claude Code up and tells it which job to run.
- Go-to-market first: agents research competitors and engaging posts in the niche, plus the doubts buyers raise. They write one note per competitor and a positioning note, which Machina then checks line by line.
- Outbound: Apollo for prospects, a sending tool like Instantly, and replies synced back to the CRM. First lines are written around recent events at each company. The agent checks Google Postmaster Tools every morning and sends less if deliverability drops. Every new sequence needs Machina's approval.
- Content: each week the agent collects what's working on each platform and writes drafts with the source posts attached. For YouTube, it saves competitor videos into the vault as notes and uploads finished videos as private so they can be reviewed first.
- UGC and SEO: UGC scripts are built from a vault of ads that already sell, with word counts calculated rather than guessed. For SEO, the agent starts by looking for one page where ranking higher would actually make money.
How to build something similar
- Before connecting any tools, write a short brief that defines your offer and what counts as a win.
- Give each job its own agent. Have them all read from one shared notes folder and write to one log.
- Put approval rules in a file the agents must follow, especially for sending email and spending money.
- Keep API keys out of your prompts and notes, and give each agent only the access it needs.
The original post
https://x.com/i/article/2108917628962250752 Anyone can build a product in a weekend now... the hard part is getting people to see it, and i've been handing more and more of that job to Opus 5.5 inside Claude Code because building got easy, and getting noticed didn't a good product nobody hears about is still a product nobody buys so in this one, i'm giving you ONE system that handles distribution for you: go to market, outbound, content, landing pages, UGC, SEO and ads the whole thing runs on three simple rules: look at what's working before writing anything judge every channel on sales and signups, never on views nothing gets sent or paid for until you say yes if you just want this running fast without building anything, start with Viktor in the next section everything after that is my own build, set up inside Claude Code with Opus 5.5 doing the work the fast and easy route: Viktor i'll be straight with you, the Claude Code build below is awesome, but plenty of you don't want to build anything, you just want distribution handled while you run the business for you there's Viktor... he's an AI employee who joins your Slack or Microsoft Teams like a new colleague you message him in a channel the same way you'd message a person, he goes and does the work on his side, and he comes back with the finished thing: the research, the drafts, the sheet, the report what i like about him for this: you connect your tools once, most of them in one click you ask for things in plain English, no setup language you set a weekly job once and he repeats it on his own nothing goes out until someone on your team approves it your whole team sees his work, so nobody starts from zero the only real setup is picking which tools to connect, and you don't need ten of them... here's the ONE i'd plug in for each part of this article: research and go to market: Apify outbound email: Apollo.io X: Typefully Instagram and TikTok: Blotato YouTube long-form: YouTube landing pages built for SEO: Wordpress lead capture forms: Typeform email sequences: Kit SEO: DataForSEO ads: Meta Ads SaaS payments: Stripe ecommerce store: Shopify courses and communities: Whop then you just type what you want, something like: every monday, find what's trending in my niche, write five posts for X with the sources attached, and wait for my ok and that's your setup done try free at @viktor_com... $100 in credits, no card my Claude Code build on Opus 5.5 building it yourself gives you full control, your data stays on your computer, and nobody can change the system on you i run it in Claude Code with Opus 5.5 as the model, because this work is mostly long research, careful writing and checking pages against a brief, and that's what it's best at the whole setup is one folder on your computer, and that folder is the brain of your distribution agent: a brief: your business, your offer, who buys, what counts as a win a knowledge base: an Obsidian vault, basically a folder of notes a log: what went out, how it did, what changed this week a rules file: what the agent does alone and what needs your ok the knowledge base sounds fancy but it's just markdown files linked together, that you and every agent can read then you connect your tools... almost every tool in this article has an API, which just means a door that lets Claude Code use the tool for you once you give it a key keep those keys in a separate settings file in the folder, never in the brief, and only give each part the keys it needs then you put it on a schedule with a cron job (an alarm clock for your computer) that wakes Claude Code up and tells it which job to run the mistake i see all the time is one giant assistant with one endless prompt trying to do everything so my rule is one agent per job, every agent reads the same notes, and every agent writes down what it did in the log before building any of it, open Claude Code in the folder and let it interview you: that one conversation writes half your brief for you go to marke
Want to build something like this?
Join the Shipping Skool community free. Paid members get live bootcamp calls every week.
Join Shipping Skool — Free