I'm going to teach you how to set up GTM agents to grow your one person business. I'll give you the exact tools and how to get the best out of them in a shared environment.
The machine has three versions, one for agencies, one for SaaS, one for infoproducts and communities (plus one very fast setup using Viktor)
pick your chapter, set up the workflows in it one at a time, and the agents find and keep customers while you do the actual work
if you want to get access to more workflows like this -> weeklyaiops.com
what's inside this guide
- the shortcut: one AI employee that already does most of this
- the knowledge base: what every workflow reads before it writes
- how the full build works, in four simple parts
- chapter 1 - agencies: signal outbound, warm outbound, the proposal from the call, the retention loop
- chapter 2 - SaaS: demo-first content, competitor placements, warm outbound for SaaS, the money loop
- chapter 3 - infoproducts and communities: owned email, the content batch, borrowed rooms, member health
- the SEO and answer engine layer all three share
- what to build first
- the build sheet
the shortcut: one AI employee that already does most of this
before i give you the full custom build, i have to be honest with you: there is an AI employee that does 80% what i am about to teach you out of the box, and he is called Viktor
he lives inside Slack or Microsoft Teams like a new colleague, so you talk to him in a channel the same way you would talk to a person, and he goes off, does the work in his own cloud workspace, and comes back with the result as a sheet, a document, a deck, a draft or a report
the part that makes him useful for go-to-market is the connectors, because he's plugs straight into the classic GTM tools you already pay for:
- Apollo and Clay for lists and enrichment
- HubSpot or Attio for the CRM
- Instantly or lemlist for sequences
- Stripe for payments
- Meta and Google for ads
- beehiiv or Kit for the newsletter
- Google Analytics or PostHog for the numbers
so every workflow in this guide can be given to Viktor as a sentence, for example "every monday, refresh the prospect list from Apollo, enrich it through Clay, and post the top rows here with a first message drafted for each"
and when a tool has no connector, he reads the api docs and builds one, or just uses a browser like you would
here is how you set Viktor up, once:
- open one channel per workflow (outbound, content, pipeline, members)
- pin one message at the top of each channel that says what you sell, who buys, what this channel produces and what never sends without you
- and then set the permission per tool so he can read and draft on its own, has to ask you before anything sends or spends, and cannot touch the tools that should never reach the outside
he remembers your corrections between runs, so a rule you set once holds, and every research sheet he produces carries a confidence note per row, so bad research shows itself before it reaches you
get $100 credits to try Viktor: viktor.com
he's a great option to have workflows running on autopilot, without much setup... the rest of this guide is about building your own custom GTM pipeline
the knowledge base: what every workflow reads before it writes
every workflow in this guide reads from one shared brain before it drafts anything, and the strongest version of that brain is embarrassingly simple, a folder of markdown files
an Obsidian vault is the operator favorite here, because it is exactly that... text files on your disk, linked to each other, readable by you and by every agent you run
structure it by what your go-to-market needs to know, one note per thing
- what you sell, at what price, what is included and what you refuse to do
- who buys, which verticals, what a qualified lead looks like and what a bad-fit lead looks like
- how you write, the words you never use, and five of your best messages and posts as examples
- the market map, meaning your competitors, the category pages that list them, and the rooms your buyers already sit in
- how each workflow runs, stage by stage, with the checklist the agent follows and the point where it stops for you
- every decision you have made about outreach, pricing or content that should never be re-argued
that last note is the one nobody builds and everyone needs, because every time you correct an agent, the correction gets one line there, and every agent reads it before working, so a correction becomes permanent instead of repeated
why does this matter more for distribution than anywhere else? because the research behind the message is what makes people reply, and the vault is where that research goes to live... a prospect note written today feeds the follow-up next month, the proposal after the call, and the case study a year from now, without anyone typing it twice
the knowledge base is the training... the agents are interchangeable, the vault is the business
and this transfers straight back to the shortcut, because on Viktor the pinned message at the top of each channel is this vault in miniature, and it deserves the same care
how the full build works, in four simple parts
every workflow in this guide has the same four parts, so once you know them you can read any chapter in a minute
first - something starts it, like a new post crossing a threshold, a call ending, or a payment failing
second - the agent reads a source, like your CRM, your prospecting database, or a transcript
third - it produces something for you, like a research sheet, a list, or a draft message
fourth - it waits for you to approve it, and this is the rule of the whole system: nothing sends, publishes, or spends money until you have said yes
anyone can send now, so the research behind the message is the only thing left to sell
last rule: build one workflow at a time, run it until it produces on its own, then add the next one, because that is the only way one person runs a dozen of these without drowning
chapter 1 - agencies
an agency of one sells time and outcomes to other businesses, so the job here is a steady flow of researched conversations with the right companies, and keeping those clients past the first quarter
how to run signal outbound so the first message is about them
signal outbound is outreach that starts from a change at the prospect's business, so instead of writing to a cold list you write to a company that just did something: raised money, posted a job for the role you replace, hired a new head of marketing, or left its website untouched for a year
the agent watches for those signals in a prospecting database like Apollo filtered to your client profile, enriches every row through Clay so the empty fields get filled by the next provider down, and drops the weak rows before it writes anything
what you get back is a research sheet with one row per prospect: what changed, what you can see at their business that your service fixes, and a confidence note on how solid the read is
then it drafts a first message for the top rows only, and each message opens with the workload you spotted at their business, two short paragraphs, no pitch in the first line
every message waits in the channel until you read it and send it from your own inbox, and you will see within a month in your sequencer's reports that the specific messages get replies and the broad ones do not
how to turn the people who already engaged into warm outbound
the people who like and comment on your posts are the warmest list you own, and almost none of them will ever write to you first, so you go to them
when one of your posts crosses a small engagement threshold, the agent exports everyone who liked, commented, or reposted, matches them against your client profile, keeps the ones who fit and drops the rest
for the best matches it drafts a direct message that gives them something useful about the topic they engaged with, and for everyone else it drafts an email that does the same, so you end up with a short list and one draft per person
you send every one of those yourself, from your own account, one at a time, because the platforms ban automated messaging and because the list is short enough that you do not need a robot for it
how to get the proposal written from the call itself
this one starts the second a discovery call ends, when the transcript comes off whichever notetaker sits on your calls, Granola, Fireflies, or the one built into your meeting tool
before it writes anything, the agent checks the transcript for a buying signal, meaning a price agreed, a scope asked for, or a start date discussed, and if the call ended in a maybe it writes a follow-up note and no proposal
when the signal is there it picks your proposal template, fills in what the call answered, leaves blank what it did not, and posts the draft link in your channel with its assumptions listed underneath, so your review takes minutes and the price stays your decision
after you approve, the proposal goes out, the deal moves a stage in the CRM, and the follow-ups run off the document's own read receipts
how to keep clients with a retention loop that runs on the calendar
the client you close is the one client you never have to find again, and agencies lose them at the exact moment the early numbers flatten and nobody has shown them the pipeline
so the calendar runs this one, weekly during the ramp and monthly after, and each time it comes round the agent pulls the client's numbers from wherever they live into one sheet and writes a short summary with the pipeline in it: what moved, what is queued, what you changed and why
if you also run their outreach or their ads, once a month it refreshes the audience list and the copy so the campaign never goes stale on its own, and after the first documented win it drafts the referral ask as a request for an introduction to a specific kind of business
you send the summary and you send the ask, and that is the whole loop
that is the agency version, four workflows that all end with you pressing send, and the SaaS version starts from the opposite end
chapter 2 - SaaS
an indie SaaS sells access to software, so the job here is the right people seeing the product do the thing every week, plus a money loop that keeps the ones who already paid
how to run demo-first content without it becoming a launch calendar
every time you ship a use case, record the product doing one specific job for one specific kind of user, and give the agent that recording plus the questions people ask under your posts
it drafts the demo post, then a run of daily short posts for the platforms where your buyers already read, each one written from what the last ones taught, and it puts one manual task on your list, which is to make the first outputs by hand for the people who commented, because a stranger who got a personalized result tells someone
every post waits in the channel for your edit and your approval, and a launch is one beat inside this workflow rather than the plan, because a launch on several surfaces buys you a day of attention, some backlinks and some feedback, and the real work is the audience you built before it and the follow-up to everyone who tried the product after it
how to borrow your competitors' placements
your competitors have already found every page that sends them customers, and those pages are public, and a page that lists several of your competitors is a category page, which means it will list you too if you ask
pick a keyword you want to own, and the agent takes the top results, pulls the pages that link to the products already ranking, and keeps only the domains that link to several of them, because those are the roundups, resource pages and directories that matter, while the paid placements and one-off news links get dropped since they do not repeat
you get back a placement sheet with one row per page: what they list, what a better entry would say, who maintains it, and a drafted ask to either add you or swap their entry for the more complete one you wrote
you send every ask yourself, because a maintainer answers a person and deletes a script, and one caution on directories: submit only where the listing shows a real link, and treat the whole batch as an afternoon of housekeeping rather than a traffic channel
how to nail warm outbound for SaaS
this is the same setup as the agency version with one change in the source, because next to the people who engaged with your posts you add the followers of the accounts your buyers already trust
the agent matches all of them against your profile, keeps the fit, drafts a message that references what they engaged with, and hands you a tracked list with a small weekly cap on how many people you touch
that cap does more than it looks, since a run with no replies is a message or profile problem, and sending more of it teaches you nothing
how to set up the money loop before anything else
this is the workflow everyone sets up last and should set up first, because it is the only one that makes revenue from customers you already have
it starts on a payment event, a failed charge or a cancellation, coming out of Stripe or whatever processor you run and joined with the customer's history from your CRM
a failed charge gets a retry timed by the failure reason plus a short email, a cancellation gets a short exit survey and then a win-back message written for the reason they gave and sent within a day or two, and every event writes one row to a churn list split into "card failed" and "chose to leave", so the two get fixed differently
the emails and the win-back message wait for your approval, and recovered revenue is the cheapest revenue in the whole system
the SaaS setup uses the product to sell itself and the payment processor to keep the sale, while the creator setup has something neither of those has, an audience that already trusts the person
chapter 3 - infoproducts and communities
a creator sells a course, a template, a cohort or a membership, so the job here is owning the audience you sell to instead of renting it, and keeping members past the second month
how to turn one good post into owned email
it starts with a post that performed, and the agent knows which one because it reads the platform's numbers, so it spots the post that deserves a lead magnet before you do
from that post it builds a short guide, the landing page copy for it, and the welcome sequence behind it, and the sequence carries a small offer right away, a low-ticket product in the same format as the guide, because a subscriber who bought once is a different list than a subscriber who only read
from the first email every subscriber gets a referral link and a reason to use it, so the list grows on its own readers, and each week you get a report of what came in from where
the guide, the page and the sequence all wait for your read before anything goes live under your name
how to run the week's content batch from receipts instead of guesses
every week starts the same way, with the agent reading what already worked, your top posts, your transcripts and your replies with the most engagement, the way an editor would read them to find the angles that earned attention
it drafts the week's batch for each platform in your voice, flags the strongest one and tells you why, and adds a poll for the newsletter so your readers choose the next topic and the next batch starts from a receipt and not a guess
nothing publishes on its own, every draft waits for your edit and your approval, and the corrections you make become the standing rules the next batch is written under
how to find the borrowed rooms your audience already sits in
the audience you need already exists in rooms someone else built, the newsletters your readers open, the podcasts they follow, the small creators posting in your niche, the community threads where they ask questions, and paying for a place in those rooms beats paying a platform for reach
once a month the agent studies your own audience's behavior:
- what they share
- who they cite
- which small accounts they engage with
and fills a room sheet with three kinds of rows:
- small creators who could make short videos about the product for a fixed fee plus a bonus that only pays on verified views
- newsletters and podcasts that sell a placement to their readers
- and the weekly conversation in your niche you can join with a real contribution
each row comes with a drafted first message, every message waits for your approval, and if this sounds familiar it is because competitor placements in the SaaS chapter is the same idea in a room that ranks on google
how to keep members past the second month
a paid community loses its members in the second month, and almost always for the same reason, which is that the member never did the first thing
so from the moment of checkout the agent runs a sequence of small actions you only see when one fails:
- a welcome within the hour with one first action to take
- a check that a small win happened inside two days
- a weekly ritual on a fixed day so the week has one thing to show up for, an inactivity nudge after a week and again after two
- and an at-risk list posted to your channel with the win-back drafts attached
the win-back drafts wait for your approval, and one setting belongs here too, because a quarterly option at signup drops the monthly cancel decision to four a year
the SEO and answer engine layer all three share
search is now two things, the google ranking you know and the answer engines like ChatGPT that read the web and cite what they trust, and the basics for both are the same, so this is one more workflow in the same four parts
once a month the agent runs a small set of prompts, the questions your buyer would ask an answer engine, and reads everything you publish and every profile you own against four checks
first - entity consistency, meaning your name, your offer, your category and your facts are stated the same way on every profile, because answer engines match you across sources before they cite you
second - answer blocks, meaning every page you want cited opens with a direct answer in everyday words, with the facts under it and the proof near the top, because engines pull passages, so a self-contained passage is what gets used
third - mentions in places you do not own, earned by taking part in them for real before you ever mention the product
and fourth - third-party hosts, reddit, medium, youtube, the press-release wires, a bare google sites page, where pages still rank and still get cited on one condition every host states in its rules, which is that the content has to be worth its place
what comes back is a fix list per page and per profile, drafts for the host posts, and a diff of who got cited this month and who dropped, and every host post is posted by you from an account that took part first
what to build first
the mistake i see most is building all four workflows at once and watching none of them, so build one, then add the next when the first passes the 7am test, meaning it produced this morning without a message from you
agencies start with signal outbound, because it is the workflow that moves revenue first, SaaS starts with the money loop if there are paying customers and with demo-first content if there are not, creators start with owned email because everything else in that chapter fills a list that does not exist yet, and the search layer comes last for all three because it builds slowly and needs pages worth citing
stop at the last workflow that keeps the calendar full, and do not be surprised if that means running two of them well for a long time before the third earns its channel
the build sheet
compressed to the block worth saving:
- one workspace, one channel per workflow, the context pinned at the top
- every workflow is a trigger, a source, an output, and your approval
- anything that sends, publishes, or moves money waits for your yes
- the research is what you sell... the send is a formality you do yourself
- launches and directories are one beat inside content, never the plan
- the money loop before the acquisition workflows when there are paying customers
- borrowed rooms before bought reach
- one workflow at a time... next one when the last passes the 7am test
set up Viktor this week and give him the first workflow of your chapter... the free credits at viktor.comcover the whole build, no card
sales teams were the only way to run all of this before, and a one person business could not afford one, and that changed, which is why this is the version you can afford
paid partnership
