11. The First Outreach Channel
Summary
Turning a page and a list into one channel you can judge
The offer page is live, the captioned demo is exported, and three invented prospects (a plumber, a roofer, an electrician) sit in HubSpot. Every business, reply and figure is made up, and a pretend reply says nothing about real demand. The method has five steps: research each prospect from public evidence, write one short approach using only that evidence, send it yourself, log every send and follow-up in HubSpot, and write down before any replies what result earns more effort.
Research runs in Claude Code with the evidence-checked-drafting skill, asking for each finding with its page and exact words. Prospect pages are untrusted data, and HubSpot exports stay out of any session that fetches outside pages. Claude Code security covers the protections and says no system is completely immune. The web fetch tool cannot read JavaScript-built sites or pages blocked by a robots file, so unreadable pages are marked "not reported". The electrician's entry is thin for this reason.
The roofer's draft opened with their "within two working days" callback line. An unsourced claim about losing jobs to voicemail was struck and listed.
Email rules differ by place. The CAN-SPAM guide covers US opt-out requirements. In the UK, PECR rules on electronic marketing treat limited companies and sole traders differently. This is a reading, not legal advice.
Logging uses the HubSpot connector for Claude, with Write tools set to Needs Approval. It cannot delete, caps bulk changes at ten records, and has no sequences on the free plan. Check the contact's timeline yourself, because a task once went in with no due date and the report didn't show it.
In the example, the roofer booked a look; the other two stayed silent. The rule, written first and committed with the other stopping rules: thirty real sends must produce at least three booked looks and one paid trial within six weeks.
Billing the first customer and keeping books
The heating engineer pays $270 a month through a Stripe subscription anchored to the agreement date. Claude Code uses a new restricted key. Subscription creation offers automatic card charging or invoicing, and an invoiced subscription is active whether or not it is paid. Smart Retries try a failed payment up to eight times over two weeks, and the end-of-retries setting should be checked. Failed-payment emails are switched on in the dashboard.
On an illustrative basis, Stripe Billing pricing leaves about $259.98 of $270 after fees. The books start with four accounts: Bank, Stripe Clearing, Digest Revenue and Card Fees. Each charge is a double entry, and Stripe Clearing should match the Stripe balance. The ledger is on a cash basis, while the trial was counted on an accrual basis. Confirm the reporting method with an accountant.
One channel you can judge
A published page and a short list of names do not bring in customers yet. To turn them into one channel you can judge, follow five steps. Research each prospect from public evidence. Write one short approach that uses only that evidence. Send it yourself. Record every send and follow-up in HubSpot. And before any replies arrive, write down what result earns more effort. That last step is what lets you call it a channel. Without a rule set in advance, any result can be made to look like progress.
The show's example carries on from last time. The offer page is live, the captioned demo is exported, and three invented prospects sit in HubSpot: a plumber, a roofer and an electrician. Every business, reply and figure in this chapter is invented. A pretend reply proves nothing about whether real owners want the digest. The example is here to show how the work runs.
Start the research in Claude Code, in the Digest Prototype folder, using the evidence-checked-drafting skill we built earlier. Ask for each prospect's public evidence: the website, the contact routes it lists, and any sign that the business misses calls. That might be a line saying "leave a message and we'll call back", a form with no phone number, or opening hours that leave evenings uncovered. Ask for each finding with the page it came from and the exact words.
Two rules protect this session. First, a prospect's page is untrusted data. If a page contains text that reads like an instruction to the agent, it stays material to read and never becomes an order. Second, keep your HubSpot exports and customer files out of the same session that fetches outside pages. When an agent reads strangers' web pages with private records in reach, a hostile page could try to get those records sent somewhere. Anthropic adds protections, such as letting Claude fetch only addresses already in the conversation, and Claude Code asks your approval before network commands. Anthropic also says no system is completely immune. Keeping the private records out of the session closes that route on your side.
Expect some gaps. Anthropic documents its web fetch tool as unable to read sites built with JavaScript, and it refuses pages a site blocks through its robots file. When a page cannot be read, the research should say "not reported" instead of guessing at what the page probably says. In the example, the electrician's site is one of those, so its entry is thin. That is a correct result.
Next, ask Claude to draft one approach per prospect, three sentences each, tied to what that business shows. Here is how it went for the roofer. The research found a contact page saying calls are returned "within two working days", with a quote from the page. The draft opened with that fact, said in one sentence what the digest does, and offered a ten-minute look at the sample, which is the same action the offer page asks for. The draft also included the line "you're probably losing jobs to voicemail". The claim-check list had no source for it, so it was struck. It is plausible, and it is exactly the kind of story a model invents. The kept version says what the page shows and stops. The struck line goes in a list at the bottom, so you can see what was removed.
Before you send anything, check the email rules where you and the recipient are. In the United States, CAN-SPAM applies to business-to-business email as well as consumer email. It works on opt-out, not prior consent, but every message needs accurate sender and header details, a subject line that doesn't mislead, a clear statement that it is an advertisement, a valid physical postal address, and a working way to opt out. You must honour an opt-out within ten business days, and the opt-out has to keep working for thirty days after you send. Penalties reach fifty-three thousand and eighty-eight dollars per violating email.
In the United Kingdom, the rules on electronic marketing, called PECR, treat companies and individuals differently. A limited company needs no consent for marketing email. Sole traders and ordinary partnerships count as individuals, and many plumbers and roofers are sole traders. A cold email to one of them generally needs consent. The soft opt-in exception covers existing customers only, not prospects. UK data protection law still applies to the names and addresses you keep. That is a reading of the rules, not legal advice. Check the rules for your own country, and check how the business you are emailing is set up.
Then send each email yourself, from your own mail account. The agent researches and drafts. You decide what goes out under your name.
Logging goes through the HubSpot connector for Claude. It needs a paid Claude plan and an active HubSpot user. Only one HubSpot account can connect to each Claude account, and if you aren't a Super Admin in HubSpot, one of them has to approve the connection. In Claude's connector settings, set Write tools to Needs Approval, which HubSpot recommends. Every change then shows up as a proposal you confirm. For each send, ask Claude to log the email on the contact and create a follow-up task. Read the proposal before you approve it: the task title, the due date and which contact it is attached to. Then open the contact in HubSpot and look at its timeline and task list. Last time a task went in with no due date, and the agent's report didn't show it. The record is the only proof.
Three limits shape this work. The connector cannot delete anything, so a mistake is fixed by editing, or by deleting it yourself in HubSpot. Bulk create or update is capped at ten records at a time. And sequences, HubSpot's automatic follow-up emails, aren't in the free plan, so follow-ups are dated tasks you act on.
Once the sends are logged, ask Claude Code for a short report of sends, replies and booked looks, built from the HubSpot records. In the invented run, three emails went out. The roofer replied and booked a look at the sample. The plumber and the electrician stayed silent, and their follow-up tasks are due next week.
That one booking tells you little until you compare it with the rule you wrote before sending. In the example the rule was dated and committed to git with the other stopping rules. It says: carry on with direct email only if thirty real sends produce at least three booked looks and one paid trial within six weeks. Otherwise, change the approach or try another route. Your numbers can be different. They just have to be written down first.
Here is your task. Pick one real business that could buy from you. Have Claude Code collect its public evidence, then draft a three-sentence approach with a claim-check list. Write your channel rule with today's date before you send. It has worked when every remaining sentence points to a source, the struck lines are listed, and opening that contact in your CRM shows the logged send and a dated follow-up task.
The first recurring charge in the books
Meanwhile, the customer who said yes needs billing. Bill them with a Stripe subscription at two hundred and seventy dollars a month, starting from the date of the written agreement, and record each charge in a small set of accounts.
In Stripe, the steps are these. Create a Customer for the heating engineer. Create a Product for the digest with a monthly recurring Price of two hundred and seventy dollars. Then create a subscription for that customer on that price. Stripe calls the billing day the billing cycle anchor, and you set it from the agreement date so every monthly charge falls on that day. Claude Code can make these calls with a restricted key, but not the one we made earlier, which was a test-mode key that could not even read customers. Make a new restricted key with only the permissions this needs, and check the result in the dashboard.
Two settings matter. The default collection method is to charge the saved card automatically, which suits a customer who has agreed in writing. The other option sends an invoice the customer pays themselves. That needs a number of days until payment is due, and it marks the subscription active whether or not they have paid yet. So "active" does not mean "paid". Second, Smart Retries are on by default for new accounts. A failed payment is retried up to eight times over two weeks, though a hard decline is not retried. After the retries run out, the subscription is cancelled, marked unpaid, left past due or paused, depending on your setting. Check which one is set, and turn on the failed-payment emails under Billing, Revenue recovery, Emails.
Billing has a cost. As of November 2026, pay-as-you-go Stripe Billing takes zero point seven percent of billing volume, on top of card processing at two point nine percent plus thirty cents. Check the current pricing page for your country. On two hundred and seventy dollars, this is an illustrative calculation. Card processing is about seven dollars and eighty-three cents plus thirty cents, so eight dollars and thirteen cents. Billing adds about a dollar eighty-nine. The total is about ten dollars and two cents, leaving about two hundred and fifty-nine dollars and ninety-eight cents. Open the first invoice and its payment in the dashboard and compare them with these figures yourself, because exactly where each field appears may differ.
Claude Code adds the row to the payments record, the same file that holds the trial: gross, fee, net, transaction identifier, and the payout identifier left blank until the bank shows it. Now that money comes in every month, it also gets a chart of accounts. That is the list of buckets your money is sorted into. Start with four: Bank, Stripe Clearing, Digest Revenue and Card Fees. Stripe Clearing is the money Stripe holds for you before it pays it to the bank.
Each charge is recorded with double entry: every amount goes into two places so the totals always balance. When the charge succeeds, the illustrative entry is two hundred and fifty-nine ninety-eight into Stripe Clearing, ten dollars and two cents into Card Fees, and two hundred and seventy dollars into Digest Revenue. Those first two are debits, which record what the business now holds or has spent. The revenue is a credit, which records where the money came from. Both sides add up to two hundred and seventy. When the payout reaches the bank, two hundred and fifty-nine ninety-eight moves out of Stripe Clearing and into Bank. Stripe holds the funds in your balance first and pays out on its own schedule, so the clearing account is how you track that gap. Its balance should always match your Stripe balance. If it doesn't, ask Claude Code to bring you the difference with the transactions behind it.
This ledger uses the cash method, where income counts when you receive it and expenses count when you pay them. The accrual method counts income when it is earned, which is how we counted the prepaid trial digest by digest. A monthly charge that covers the month ahead makes the two methods differ slightly. Prepaid amounts also have their own tax timing, so confirm with an accountant which method you report under.
Here is your task for the books. Take one card payment your business has received, or an invented one labeled as invented, and post it by hand to four accounts like these: the net into the clearing account and the fee into fees as debits, and the full amount into your revenue account as a credit. Then post the payout from the clearing account to the bank. It has worked when both sides of each entry add up to the same amount and the clearing account matches your Stripe balance.
You now have a channel with a written rule and a paying customer whose money goes into books you can check. In the example, the roofer's ten-minute look is the next thing on the calendar.
Want a book of your own?
Gnothi wrote and narrated this chapter. Name a subject and it writes you a course, or a story that teaches it, one chapter at a time, delivered to your podcast app.
Get started free