How I Run My Business with Three AIs: Muse, Instinct and Tab
i'm dylan goodrich. i'm a creator (@dylangoodrich), and i run unresourced, the anti-agency creator studio i built with my fiance alex.
here is the part people do not believe: there is no big team behind us. it is me, alex, and three ais. and this setup outproduces agencies ten times our size. this is exactly how it works, including the parts that broke.
meet the team
august is my chief of staff. he runs on muse, by meta. research, operations, quality control, building pages and tools, scheduled checks around the clock: if something needs thinking, verifying or organizing, august owns it. he also coordinates the other two, so i am never the middleman.
jordan runs all of our outbound. she runs on instinct. every pitch, every follow-up, every brand and hotel conversation we start by email goes out through jordan. she never forgets a follow-up, and she sends in my voice, first person, like i typed it myself.
sofie builds, and she owns the words. she runs on tab. research dives, live-site checks, the viral edits program, and every line of copy that ships from her lane. when something needs to exist, sofie makes it.
alex is the human on the other side of the business: client programs, partnerships, and the relationships only a person can hold.
one founder, one co-owner, one chief of staff, one sender, one builder. that is the whole org chart.
how the three ais work as one team
the structure is the whole trick. anyone can open three chat windows. making them one team takes rules.
lanes, with one owner each. every workstream has exactly one owner: sofie builds, jordan sends, august coordinates and quality-checks. no duplicate work, no two of them editing the same thing, no "i thought you had it."
parallel, with coordinators. big jobs split into small pieces. workers run under coordinators, up to fifty on a single task and more than a hundred live across lanes on a big night, and every batch passes a dedicated qa check before it reaches me. speed without the gate is how mistakes ship.
two updates a day. i get one consolidated update in the morning and one in the evening: what shipped, the numbers, what needs me, what is next. nothing in between unless something is genuinely blocked. my days stay clear for creating and closing.
verify, then report. nothing counts as done because one of them says so. it is done when the sent box, the live site or the calendar proves it. that rule came from real mistakes, and it has saved us more than once.
one night, as receipts
this is not theory. in a single night this week, the team rebuilt our platform to match, feature for feature, the biggest creator platform in our space, shipped it live, and proved the whole loop end to end: a brand posted a campaign on its own, a creator joined, sent in a deliverable, and the brand approved it. the same night produced a finished phone app build and live client campaigns, including the creator programs we run for parents are human.
that platform is unresourced, and it is live now: creators join free, find campaigns and gifting, and get paid on fixed dates. the gifting library alone tracks more than 1,600 open brand application forms, every one checked live. i directed all of it from my phone, from hawaii.
what broke, and what it taught us
the honest version matters, because the failures wrote the rules.
an unclear send result once got read as "not sent," and the same email went out twice. now the rule is: an unclear send counts as sent until the sent box proves otherwise. nobody re-fires on a guess.
a late-night deploy once missed one folder and took our forms funnel down for a few minutes. the fix took minutes too, but the real fix is the checklist that deploy follows now, written down where every future deploy sees it.
and early on, work got reported to me as finished before anyone had checked it where it actually lives. that is where verify-then-report comes from. the ais are fast and confident. confidence is not evidence, so we check.
none of this made me trust the system less. it made the system worth trusting.
who muse is for
if you are a creator, an operator, or anyone running something real with an inbox, a calendar and a backlog, you do not need a bigger team first. you need one august: a chief of staff that researches, builds, checks its own work and reports back with proof.
muse is the one i chose for that seat, and it is the highest-leverage addition i have made to this business. i put the full walkthrough on its own page, but the short version is this: join muse, then enter my invite code CJT8TA within 48 hours of joining (settings, then redeem token on mobile; settings, general, usage on the web). the bonus lands in both accounts, yours and mine.
referral disclosure, in plain words: muse is a product i use every day. if you join with my code, we both get a bonus on our accounts, and i may earn referral rewards. that is the whole deal, nothing hidden.
FAQ
what does each of the three ais actually do? august (muse) is the chief of staff: research, operations, quality control, building and reporting. jordan (instinct) sends all outbound email: pitches and follow-ups. sofie (tab) builds, researches and owns copy and live-site checks. alex and i make the human calls.
how much does it cost to run a business on three ais? less than one junior hire, by a lot. the subscriptions together cost a fraction of a single salary, and the output covers operations, outreach, research and building.
do the ais ever make mistakes? yes. a duplicate email, a wrong number and an overconfident report have all happened here. the system works because every batch passes a qa gate, and every claim gets verified where it lives before it reaches me or goes public.
can a solo creator copy this setup? yes, and you do not need all three on day one. start with one chief-of-staff agent, give it clear lanes and a verify-then-report rule, and add a sender and a builder when the work outgrows one seat.
how do i get muse with dylan's invite code? join muse at muse.ai, then within 48 hours enter the code CJT8TA in settings (redeem token on mobile, or settings, general, usage on the web). the bonus lands in both accounts. the full walkthrough is on the muse page.