Presumption in action
Watch the lead-to-CRM workflow
The existing sales demo shows the general lead discovery and CRM workflow—not a filmed agency campaign.
Start with a market, not a giant contact list
The useful question is not ‘How many emails can I scrape?’ It is ‘Which businesses could benefit from the kind of website I actually build?’ A local restaurant needs different evidence and a different offer from a professional-services firm. Pick one niche, one region, and one clear service before you automate anything.
For this walkthrough, imagine an agency offering website redesigns to independent home-service businesses in Southwest Florida. That is an example audience, not a customer case study or a promise of results.
- Audience: independent home-service businesses in your chosen region.
- Offer: a useful website improvement conversation—not an invented audit or a guaranteed revenue lift.
- Starting batch: up to 20 businesses with publicly listed business contact details.
- Success measure: qualified conversations and booked calls, not the number of scraped records.
1. Prepare your agency and your sending account
Add your agency’s website, brand details, and actual offer in Presumption. The agent needs to know who you are, what you sell, and what it must not promise. Use your real portfolio or a specific service description instead of asking it to invent credibility.
For email, connect your own Resend account in Settings → Connections. Use a sender address on a domain you have verified with Resend. Complete your business name and physical mailing address in Settings before sending; those details belong in your outreach footer.
- Have a verified sending domain and your own Resend API key ready.
- Set a real sender name, reply address, business name, and postal address.
- For a new domain, consider the optional domain-warming daily send limits. They control volume; they do not guarantee inbox placement.
- Check the marketing and privacy rules for your recipients’ locations. A publicly listed email address is not automatic permission to market to it.
2. Ask the agent to find relevant, reachable businesses
Give the agent a bounded search. Presumption searches public sources, reads available pages, and can check business websites for published contact details. Contacts are saved in the built-in CRM with notes and sources, so the research does not end up in another spreadsheet.
Ask it to distinguish an observation from an assumption. An old-looking design is not proof of lost sales. A published contact address is not a verified deliverable inbox. Research may return fewer than your target when useful sources, contacts, time, or credits run out.
The agent brief
Find up to 20 independent home-service businesses in Southwest Florida that could be relevant to my website design agency. Use public business sources and their own websites. Save contacts to the CRM only when a real email or phone appears on a cited page; never guess an email. Include the business website, source URL, and a short factual reason for fit in the notes. Exclude existing CRM duplicates. Do not claim a website issue unless you can observe it, and say when you cannot verify something.
3. Qualify the first batch in the CRM
Open People and read the results before writing to anyone. Is each business in your service area? Does it match your niche? Is there a genuine, specific reason to reach out? The CRM requires an email or phone and blocks duplicate normalized emails or phone numbers within your account; that does not make every record a qualified buyer.
Remove poor fits and make your outreach audience explicit. A contact with a phone number only is not an email recipient. Keep a dedicated batch or status where available, and verify the email automation’s audience before running it—do not assume a chained step automatically targets only the leads found in the last run.
- Confirm the website and business details against the cited source.
- Check that your offer is relevant and the recipient has a published business email.
- Keep existing clients, unrelated contacts, and opted-out recipients out of the campaign.
- Review any website issue yourself before making it part of the pitch.
4. Write an introduction that earns a reply
The first message should explain why this business, why your agency, and why now—in a few sentences. Personalization means using something true and relevant from the research, not inserting a first name into a generic pitch.
Start with drafts held for approval. Read the recipients and the actual copy, including the footer. If you have not audited a site, the message should not say you have. If you do not have a verified outcome, do not promise one.
The agent brief
Create a Resend email outreach automation for the qualified CRM audience I select. Draft a short introduction from my website agency using only facts in the contact’s notes and cited sources. Explain our actual website design offer and ask if a brief conversation would be useful. No invented audits, customer results, urgency, or revenue guarantees. Skip contacts without an email and anyone unsubscribed. Keep auto-approve off for this first batch so I can review the recipients and every message before sending.
5. Connect the workflow, then switch on automatic sending
Once the first batch looks right, connect the lead-finding step to the outreach step. Chained automations wait for their predecessor to finish; steps held for approval wait for those decisions. The next step gets the prior run’s written context, while the contacts themselves live in the CRM. Check the saved audience configuration rather than treating the connection as a perfectly isolated mailing list.
Turn on Auto-approve on the outreach card only when you intend messages to send without another review. It is real sending permission, not a draft shortcut. Start with a small audience, confirm the sender and offer, and monitor the first automatic run. Leave auto-approve off whenever the message needs a human decision.
- Lead discovery → CRM qualification → Resend outreach is the operating sequence.
- Put the schedule on the parent step; a chained step follows its parent.
- Automatic sending still depends on a working Resend connection, available credits, and applicable send limits.
- Presumption adds unsubscribe handling and suppresses recorded opt-outs. You still own lawful targeting and truthful claims.
6. Read the run history, not just the lead count
Inspect what was found, what was drafted, what sent successfully, and what failed. An attempted send is not a delivered email; an accepted email is not proof it reached the inbox. Check delivery information in Resend and review replies through your configured reply address.
After your first batch, compare qualified replies and booked conversations with the research and credit cost. If fit is weak, narrow the market. If replies are weak, improve the offer and the message. Do not answer either problem by immediately increasing volume.
- Research: how many relevant contacts had a usable source and an email?
- Execution: which sends succeeded, failed, or waited on a limit?
- Business result: how many replies became useful conversations?
- Next decision: improve targeting, change the offer, or cautiously expand the batch.
What this replaces—and what it does not
The usual process is a chain of tabs: directories, a scraper, a spreadsheet, a writing tool, and a separate campaign sender. Presumption brings research, contact records, drafting, approvals, and execution into one working system. Your Resend account remains the email delivery service.
It does not replace your judgment about who to contact, your legal obligations, or the sales conversation after someone replies. It also does not build the client’s website in this tutorial. The point is to give a website-building agency a repeatable way to start the right conversations—not to promise clients on autopilot.