Ruben Hassid
How to AI
800,000+ subscribers

For influencer managers

You manage creators. An agent should manage the paperwork.

It drafts deal terms, chases signatures, and tracks every code. It never messages a creator. The full build guide is on this page, free. Subscribe and it unlocks.

Enter a valid email address.

Takes you to Substack. Subscribe there, then come back — this page will be unlocked.

Unlocked
The guide is right here. Subscribe free and come back. This page stays unlocked for you.

Build the agent that does your mundane work

You took this job to work with creators. Instead, half the week goes to drafting contracts, chasing signatures, and updating the deals spreadsheet. This guide shows you how to build the agent that takes the mundane half, with the exact architecture and the order to build it in.

What it does

  • Drafts the deal terms straight from your email thread, as a Schedule A attached to your master agreement
  • Flags what's missing before anyone signs: usage rights, whitelisting, exclusivity, kill fee
  • Sends the contract for e-signature and chases it until it's signed
  • Keeps the dashboard current on its own: every deal, deliverable, code and payment
  • Briefs you mid-negotiation: what you're about to agree to, what you forgot to ask for

What it never does

  • Message a creator. The relationship is the job. It stays yours.
  • Negotiate. It briefs you; you make the calls.
  • Touch your master agreement. It only fills the per-deal schedule.

1. The contract pattern: master agreement + Schedule A

Your lawyer-approved master agreement never changes. Every deal's specifics live in a one-page Schedule A the agent drafts per deal. The master agreement just has to reference "Schedule A" so the attachment is legally connected. This is the single most important design decision: the agent fills a schedule, it never edits a contract.

SCHEDULE A — DEAL TERMS
Attached to the Creator Services Agreement between YourBrand, Inc. and Maya Torres ("Creator")
Deliverables
3 TikTok videos, 60 to 90 seconds each
Fee
$4,500 flat, net 15 after final approval
Usage
Paid ads for 90 days, whitelisting via Spark Ads
Exclusivity
No competing promotions for 30 days
Revisions
Two rounds included
Brand signature ________Creator signature ________
A Schedule A the agent drafted from an email thread. Sample data.

2. The architecture: five services

This is a real web app, not a prompt. Five services, each doing one job. All five have free or cheap tiers, and none of them requires writing infrastructure from scratch.

Email threadyou CC the agent
→
Postmarkinbound email webhook
→
Your appNext.js on Vercel
Claudereads the thread, drafts Schedule A, runs the audit
↔
Your appdashboard + logic
↔
Supabasedatabase + your login
Your app
→
SignWelle-signature + reminders
→
Creator signswebhook flips the deal to Signed
The whole system. The agent's only outbound email is the signature request, and the e-signature service sends that.
  • Vercelhosts the Next.js app: the dashboard, the API routes, the webhooks. Deploys from a Git repo in minutes.
  • Supabasethe database (deals, creators, terms, statuses) and your login. The dashboard reads and writes here.
  • Postmarkgives the agent its email address. CC it on a thread and Postmark posts the message to your app.
  • Claude APIthe brain. One prompt drafts the Schedule A from the thread; a second runs the 12-term audit; a third answers coach questions.
  • SignWellsends the master agreement + Schedule A for e-signature, sends the reminder nudges itself, and calls your webhook when it's signed. This is why the agent never has to email anyone.

3. The dashboard, not a spreadsheet

Every deal gets a row: creator, deliverables, fee, whitelisting code, status, signature. The rows update from webhooks, not from you. When a deal moves, the dashboard moves.

deals.youragency.app/dashboard
Deals
Templates
Analytics
Settings
Active deals
CreatorPlatformDeliverablesFeeCodeStatus
@maya.buildsTikTok3 videos$4,500MAYA20 Signed
@thefinanceguyIG Reels2 reels + story$2,800TFG-ADS Sent for signature
@lena.codesYouTube1 integration$6,000LENA-WL Drafting
@dailyaiguyTikTokUGC bundle$1,200— Negotiating
The dashboard on your own domain. Sample data.
Want to skip the build?

Join the community and the whole app is yours right now: the code, the templates, the deploy guide. Paste, deploy, done.

Join and get the files

4. Where to start: the build order

Do not start with the email inbox. Start where you can see progress the same day, and add the plumbing last. This order works in a weekend with Claude Code doing the heavy lifting:

Day one. Create the Supabase project: a deals table and a creators table, plus login for yourself. Then the dashboard: a Next.js app on Vercel that lists deals and opens one deal. Fake two rows by hand so you have something to look at.

Day one, afternoon. The drafting endpoint: a page where you paste an email or DM thread, the app sends it to Claude with your Schedule A template, and saves the drafted terms to the deal. This is the agent's whole brain, working, before any email plumbing exists.

Day two. Wire Postmark: the agent gets its own address, and CC'ing it does what pasting did. Then SignWell: a Send for signature button on the deal page, and the webhook that flips the deal to Signed when the creator signs.

Describe each of these steps to Claude Code in plain English and review what it builds. The order matters more than the code: brain first, plumbing last.

5. CC the agent on the deal thread

Once Postmark is wired, the paste step disappears. When a deal starts coming together, CC the agent. It reads the thread, extracts what was actually agreed, drafts the Schedule A, and files the deal on your dashboard with everything still unresolved flagged.

Re: TikTok collab, March
Maya Torres → you · cc deals@youragency.app
Maya: $4,500 for the three videos works. I can have drafts by the 14th.
You: Deal. We'd also want to run the best one as an ad.
Deal detected → Schedule A drafted → 2 terms unresolved: usage duration, whitelisting access
The CC flow. The agent reads; it never replies. Sample data.

6. Coach mode: what you are forgetting

Mid-negotiation, in email or DMs, paste the thread. The agent answers with two lists: what you are about to agree to, and what is not covered yet. This is where deals stop leaking money, because the expensive terms are the ones nobody mentions.

Here's my DM thread with Lena so far. Are we good to send the contract?
You are agreeing to: 1 YouTube integration, $6,000, drafts by Apr 2, two revisions.
  • Not yet covered: ad usage rights beyond organic
  • Not yet covered: whitelisting access
  • Not yet covered: kill fee if the video never ships
Coach mode. It briefs you; it never messages the creator. Sample data.

The audit runs against a fixed list. These are the 12 terms every creator deal should settle before anyone signs:

Ad usage rights + duration
Whitelisting access
Exclusivity window
Deliverables + due dates
Revision count
Fee + payment schedule
Kill fee
Approval process
Disclosure (FTC)
Content ownership
Renewal terms
Termination

7. Signature, and the one email the system sends

When the schedule is complete, the app sends your master agreement plus the Schedule A through SignWell, and SignWell chases the signature with its own reminders. That is the one outbound email in the whole system, it is about a document, and the e-signature service sends it. The agent itself never emails a creator. When it's signed, the webhook flips the deal to Signed and the code gets tracked.

This week's challenge: build yours, get it certified.

Join the community and it works like this:

  1. The whole app is yours the moment you join: code, templates, deploy guide.
  2. The live class walks the build with you. Do the challenge in the class, or on your own time.
  3. When it works, submit it. Your build gets scored and validated, and you take your spot on aicertified.world, the leaderboard of AI-native humans. Put it on your LinkedIn.
Join the community
This week's challenge The app, the class, your spot on aicertified.world.
Join the community