# Dylan: the full text > Dylan is an AI agent who books B2B sales meetings for you, from his own mailboxes. You approve the plan and pay per held meeting, or on a plan we are testing. The full text of the key pages of https://meetdylan.ai and every post on its blog, generated from the site's own sources each time the site is built. The short version is https://meetdylan.ai/llms.txt. The product pictures on the site show example data; here each one appears as its text description, which starts with "Example". ## Contents - Dylan, home: https://meetdylan.ai/ - How it works: https://meetdylan.ai/how-it-works - Pricing: https://meetdylan.ai/pricing - Security: https://meetdylan.ai/security - If Dylan emailed you: https://meetdylan.ai/emailed - How Dylan writes: https://meetdylan.ai/how-dylan-writes - About: https://meetdylan.ai/about - Enterprise: https://meetdylan.ai/enterprise - Agencies: https://meetdylan.ai/agencies - Developers: https://meetdylan.ai/developers - Docs: https://meetdylan.ai/docs - Join the waitlist: https://meetdylan.ai/waitlist - Ways to pay: https://meetdylan.ai/ways-to-pay - Dylan on a monthly plan: https://meetdylan.ai/ways-to-pay/subscription - Pay per intent: https://meetdylan.ai/ways-to-pay/per-intent - Pay per signup: https://meetdylan.ai/ways-to-pay/per-signup - Pay per qualified opportunity: https://meetdylan.ai/ways-to-pay/per-opportunity - Dylan on your inbound: https://meetdylan.ai/ways-to-pay/inbound - Dylan for partners, wholesale: https://meetdylan.ai/ways-to-pay/partners - Free tools: https://meetdylan.ai/tools - Pipeline calculator: https://meetdylan.ai/tools/pipeline-calculator - SDR cost calculator: https://meetdylan.ai/tools/sdr-cost-calculator - Deliverability check: https://meetdylan.ai/tools/deliverability-check - Cold email grader: https://meetdylan.ai/tools/cold-email-grader - Resources: https://meetdylan.ai/resources - The buyer's guide: https://meetdylan.ai/resources/buyers-guide - Glossary: https://meetdylan.ai/glossary - FAQ: https://meetdylan.ai/faq - Trusted partners: https://meetdylan.ai/partners - Pay per meeting: https://meetdylan.ai/pay-per-meeting - AI SDR: https://meetdylan.ai/ai-sdr - AI appointment setter: https://meetdylan.ai/ai-appointment-setter - Cold email templates: https://meetdylan.ai/resources/cold-email-templates - Compare: https://meetdylan.ai/compare - Dylan vs hiring an SDR: https://meetdylan.ai/compare/hiring-an-sdr - Dylan vs an agency retainer: https://meetdylan.ai/compare/agency-retainer - Dylan vs AI SDR software: https://meetdylan.ai/compare/ai-sdr-software - The film: https://meetdylan.ai/film - Privacy notice: https://meetdylan.ai/privacy - Follow-up email templates: https://meetdylan.ai/resources/cold-email-templates/follow-up - Meeting request template: https://meetdylan.ai/resources/cold-email-templates/meeting-request - Cold email subject lines: https://meetdylan.ai/resources/cold-email-templates/subject-lines - Changelog: https://meetdylan.ai/changelog - Agents judge, people approve, code protects: how Dylan is built: https://meetdylan.ai/blog/agents-judge-people-approve-code-protects - The AI SDR hype is over. Here is what actually survived: https://meetdylan.ai/blog/ai-sdr-hype-what-survived - Cold email deliverability in 2026: the rules that matter for B2B: https://meetdylan.ai/blog/cold-email-deliverability-2026 - Enterprise outbound math: your market is a pond, not an ocean: https://meetdylan.ai/blog/enterprise-market-is-a-pond - How to brief an AI SDR so it books the right meetings: https://meetdylan.ai/blog/how-to-brief-an-ai-sdr - What counts as a held meeting, and what never gets billed: https://meetdylan.ai/blog/what-counts-as-a-held-meeting - Pay per meeting: why Dylan charges only for meetings that happen: https://meetdylan.ai/blog/why-dylan-charges-per-held-meeting - AI disclosure in cold email: why Dylan says he is an AI: https://meetdylan.ai/blog/why-dylan-says-hes-an-ai --- # Page: Dylan, home URL: https://meetdylan.ai/ AI agent · Built by Belkins ## Your week, booked by an agent. Dylan finds the people who buy what you sell, writes to them from his own mailboxes, answers their replies and books qualified sales meetings into your calendar. You approve the plan and pay per held meeting, or on a plan we are testing. Join the waitlist Already know your definition? Send the full brief No card · Nothing is sent without your approval - No mailboxes or domains to set up - Deposit back if no meeting in 60 days - He tells people he's an AI Example: Harrow Line's week in Dylan's calendar. Monday: Priya, Director of Logistics, held; Tomas, Operations Director, no-show, not billed and rebooked. Tuesday: Leo, Head of Fleet, held. Wednesday, today at 11:40: the team offsite and 1:1s, the client's own. Thursday: Maya, VP Operations, just booked at 10:30, Sofia, COO, and Dev, Fleet Manager, booked. Friday: Elena, VP Finance, booked, and two forecast slots. Two held meetings billed, four booked, one no-show not billed. Each new booking arrives as a notification in the top right corner of the window. Built by Belkins - Outbound since 2017 - 1,000+ clients - 50+ industries - 4.9 on Clutch, 230+ reviews - $2B+ revenue generated for clients Figures as published on belkins.io and clutch.co, October 2026. The demo ### Watch Dylan book a meeting. Forty-two seconds, from a website to a held meeting. This is the whole job. Watch it chapter by chapter How it works ### Three steps. Only the last one costs money. You spend a few minutes. Dylan does the rest, from his own infrastructure. A few minutes #### Brief Dylan Your website, who you sell to and who not to contact. He drafts the rest; you correct it. Example brief screen: the website harrowline.com, what Harrow Line sells, the buyers to meet, company size and a do-not-contact list of 14 domains. Within one business day #### Approve the plan How many companies fit, ten real examples, the first email and the price. A person at Belkins reviews your plan and emails it within one business day. Nothing goes out until you say yes. Example plan screen: 1,810 companies fit, 4,420 people, 6 to 13 held meetings per pass, $500 per held meeting, sample companies, the first email, and the "Approved by you" stamp. Week by week #### Take the meetings Dylan writes, follows up, answers replies and books into your calendar. You pay per meeting held. Example: Wednesday to Friday of the week with Maya's meeting settling into Thursday 10:30 beside Sofia and Dev, Elena on Friday, and the invitation Dylan sends before it: who, why now, what they expect. #### From brief to first meeting 1. Day 0 · You brief Dylan 2. Day 1 · Your plan, reviewed by a person at Belkins 3. Days 2 to 3 · You approve the first emails 4. Week 1 · First emails go out 5. Our target · A first held meeting within 3 weeks Why it works ### Everything an outbound team does. Nothing to set up. #### Your domain never sends a cold email. Dylan writes from his own warmed domains and mailboxes, with a separate slice for each client. No DNS, no warm-up, nothing on your side to set up or burn. Powered by Folderly. Example sending screen: Dylan's twelve warm mailboxes for Harrow Line, 148 sent, 4 replies, 2 meetings, and a separate lane for the client's own domain with 0 cold emails. #### He says he's an AI. People reply anyway. Every first email says who he is and who he works for. He answers routine replies himself and hands you anything about pricing, legal or complaints. Example thread: Dylan's first email to Maya opens by saying he is an AI agent working with Harrow Line. Maya asks what it costs; Dylan hands the pricing question to Harrow Line's team and offers Thursday 10:30 or 14:00; Maya picks 10:30; Dylan confirms the booking. #### You approve. He protects. You approve the plan, the first emails of every new angle and any new spend. On his own he only paces, pauses and keeps your do-not-contact list. Every launch has a 60-second undo. Example approvals screen: the plan and the first email approved by you, a new spend waiting for you, three protections locked on (pacing, a cap per company, the do-not-contact list), and an undo toast with a 60-second ring. #### You pay for meetings, not effort. No seats, no price per email. A meeting is billed when someone who matches your brief joins the call. No-shows are free and get rebooked. Example billing screen: two held meetings billed at $500 each, one no-show not billed and rebooked, $1,000 billed this week, and the credit meter: three meetings deposited, two used, one left. Compared ### What you actually pay for. | Question | Dylan | Hiring an SDR | Agency retainer | AI SDR software | | --- | --- | --- | --- | --- | | You pay for | Meetings that happen | Salary, tools and ramp time | A monthly retainer | Seats, contacts or credits | | Mailboxes and domains | Dylan's own, already warm | You buy and warm them | Often yours | You buy and warm them | | If no meetings come | Deposit back after 60 days | You still pay | You still pay | You still pay | | Before anything is sent | You approve | Depends on the rep | Depends on the agency | Often automatic | | Setup on your side | A few minutes | Hiring and training | Onboarding calls | Integrations and setup | Each one in full: Dylan vs hiring an SDR, Dylan vs an agency retainer and Dylan vs AI SDR software. Pricing, beta ### Pay per meeting held. One price per meeting, set by who you want to meet. Beta pricing. Belkins: 4.9 on Clutch, 230+ reviews Lite · $250 · per held meeting · Small companies, founder-led buyers · 1 to 200 employees · Deposit $750 · Three meetings of credit Standard · $500 · per held meeting · Mid-market, directors and VPs · 201 to 1,000 employees · Deposit $1,500 · Three meetings of credit Enterprise · from $900 · per held meeting, quoted · VP and C-level · 1,000+ employees · Deposit: three meetings · At the quoted price #### You decide what counts. Before anything is sent, you set the meeting definition: the titles, company sizes and regions that count. A meeting is billed only when someone inside it joins the call. - Meetings outside your definition are never billed - No-shows are never billed - Companies on your do-not-contact list are never billed - 72 hours to dispute any meeting Example meeting definition for Harrow Line: VP Operations, Head of Fleet and Fleet Manager, at companies of 201 to 1,000 employees, in the United States. #### No meeting in 60 days? Your deposit comes back. Every dollar of it. Sixty days is the whole bet. Day 1 · Day 60 · deposit back - Disputes come back as credit - Pause any time, unused credit stays on your account Built by Belkins ### Built by people who have booked meetings since 2017. > We have booked meetings for more than 1,000 companies since 2017. We know what a meeting costs when people do every step by hand, and which steps they don't need to. Dylan is that experience as an agent: the judgment of our best SDRs, the rules of our deliverability team, and a price that only counts meetings that happen. Vlad Podoliako · Founder and CEO, Belkins 2017 · Outbound since 1,000+ · Clients 50+ · Industries 4.9 · On Clutch, 230+ reviews $2B+ · Revenue generated for clients Figures as published on belkins.io and clutch.co, October 2026. Dylan's deliverability is Powered by Folderly. Questions ### Before you brief him. Short answers. The plan itself answers the rest. 15:00 · What counts as a held meeting? Someone who matches your brief's meeting definition joins a call Dylan booked, with your meeting owner. No-shows, people on your do-not-contact list, duplicates and anyone outside the definition are not billed. 15:05 · Whose name is on the emails? Dylan's. He writes as an AI agent working for you, from his own domains. Your domain never sends a cold email. 15:10 · Do I need mailboxes, domains or a sequencer? No. Dylan brings his own, already warm, with a separate slice for each client. 15:15 · What if my market is too small? The plan tells you before you pay. Sometimes the answer is no, and he says so. 15:20 · Can I bring my own leads? Bring target companies. Contact lists are re-verified and may be refused, to protect the shared sending. 15:25 · Which channels and regions? Email, from Dylan's own mailboxes. US targets first. 15:30 · Does Dylan make phone calls? No. Dylan works by email today. If your buyers answer the phone, ask about adding Belkins callers to your plan. 15:35 · What happens with replies? Dylan answers routine ones (scheduling, questions your brief answers) and hands you anything about pricing, legal or complaints. 15:40 · What if it doesn't work? If 1,000 contacts bring no positive reply, Dylan pauses, tells you what he heard and proposes a new angle. Approve it, or leave with your deposit. And if no meeting is held in 60 days, the deposit comes back. 15:45 · Can I stop? Pause any time. Unused credit stays on your account. 15:50 · Is there a monthly plan? We are testing one with a small group: $1,500 a month, up to 3 held meetings included, then $500 per held meeting. Unused included meetings roll over one month. Month to month. Cancel any time before the next billing date. #### Got an email from Dylan? Dylan is an AI agent. He writes on behalf of the company named in his email, and he stops the moment you ask. Reply "stop" to any of his emails, or leave your address or your company's domain here and no client of his will write to you again. Curious what he would do for your company? Get my meeting plan ### Let Dylan fill next week. Opening a few teams at a time. Brief him now to hold your place. Free preview in 30 seconds · No card · Nothing is sent without your approval --- # Page: How it works URL: https://meetdylan.ai/how-it-works How it works ## From your brief to a held meeting. You brief Dylan, a person at Belkins reviews your plan, and you approve the first emails. Then Dylan writes, follows up, answers replies and books meetings into your calendar. ### From brief to first meeting - You - A person at Belkins - Dylan - Our target, not a promise 1. Day 0 · You brief Dylan · You 2. Day 1 · Your plan, reviewed by a person at Belkins · A person at Belkins 3. Days 2 to 3 · You approve the first emails · You 4. Week 1 · First emails go out · Dylan 5. Our target · A first held meeting within 3 weeks · Not a promise The steps ### What happens, and when. 1. Day 0 #### Brief Dylan Your website, who you sell to and who not to contact. He drafts the rest; you correct it. 2. Day 1 #### Get your plan How many companies fit, ten real examples, the first email and the price. 3. Days 2 to 3 #### Approve the first emails You approve the first emails or ask for changes. Nothing is sent without your approval. 4. Week 1 #### First emails go out Dylan writes, follows up and answers replies. 5. Week by week #### Take the meetings Dylan books meetings into your calendar. You pay per meeting held. What counts ### You decide what counts. Before anything is sent, you set the meeting definition: the titles, company sizes and regions that count. A meeting is billed only when someone inside it joins the call. #### Never billed - Meetings outside your definition are never billed - No-shows are never billed - Companies on your do-not-contact list are never billed A held meeting is someone who matches your brief's meeting definition, joining a call Dylan booked, with your meeting owner. Example meeting definition for Harrow Line: VP Operations, Head of Fleet and Fleet Manager, at companies of 201 to 1,000 employees, in the United States. Approvals ### Nothing goes out until you say yes. You approve the plan and the first emails of every new angle. You see every new claim, reason and tone once, before it is repeated at scale. On his own he only paces, pauses and keeps your do-not-contact list. Example approvals screen: the plan and the first email, each stamped approved by you, and three protections locked on: pacing, a cap per company and the do-not-contact list. Limits ### What Dylan will not do. Dylan will not Send anything before you approve the plan and the first emails. You approve the first emails of every new angle, too. Dylan will not Send a cold email from your domain. He writes from his own warmed domains and mailboxes, with a separate slice for each client. Dylan will not Write to a company on your do-not-contact list. He checks the list when he builds the plan and again as each email is sent. Dylan will not Keep writing to someone who replied. The moment a reply is read, every further scheduled email to that person stops, by rule, before any AI sees it. Dylan will not Pretend to be a person. Every first email says who he is and who he works for. Never a fake name, never a fake person. Dylan will not Answer pricing, legal questions or complaints himself. He answers routine replies and hands those to you. Questions ### Questions about the steps. 15:00 · What counts as a held meeting? Someone who matches your brief's meeting definition joins a call Dylan booked, with your meeting owner. No-shows, people on your do-not-contact list, duplicates and anyone outside the definition are not billed. 15:05 · Whose name is on the emails? Dylan's. He writes as an AI agent working for you, from his own domains. Your domain never sends a cold email. 15:10 · Do I need mailboxes, domains or a sequencer? No. Dylan brings his own, already warm, with a separate slice for each client. 15:20 · Can I bring my own leads? Bring target companies. Contact lists are re-verified and may be refused, to protect the shared sending. 15:35 · What happens with replies? Dylan answers routine ones (scheduling, questions your brief answers) and hands you anything about pricing, legal or complaints. 15:45 · Can I stop? Pause any time. Unused credit stays on your account. ### Get on Dylan's calendar. Tell Dylan your website and who you want to meet. Nothing is sent without your approval. You approve the plan and pay per held meeting, or on a plan we are testing. Join the waitlist Already know your definition? Send the full brief --- # Page: Pricing URL: https://meetdylan.ai/pricing Pricing, beta ## Pay per meeting held. One price per held meeting, set by who you want to meet. Or a monthly plan we are testing. Beta pricing. No seats, no price per email. ### Lite $250 · per held meeting · Small companies, founder-led buyers · 1 to 200 employees · Deposit $750 · Three meetings of credit · Join the waitlist, Lite ### Standard $500 · per held meeting · Mid-market, directors and VPs · 201 to 1,000 employees · Deposit $1,500 · Three meetings of credit · Join the waitlist, Standard ### Enterprise from $900 · per held meeting, quoted · VP and C-level · 1,000+ employees · Deposit: three meetings · At the quoted price · Join the waitlist, Enterprise ### Monthly plan · Status: Testing $1,500 · a month · Up to 3 held meetings included, then $500 each · Standard definition: 201 to 1,000 employees · Billed monthly, month to month · Unused included meetings roll over one month. Testing with a small group. See the monthly plan The deposit is three meetings of credit. Each held meeting draws it down. It is not a fee. See an example plan · Already know your definition? Send the full brief ### Other ways to pay, in testing or by application See every way to pay - Status: Testing · Pay per intent · Price set in your plan - Status: Testing · Pay per signup · Price set in your plan - Status: Testing · Pay per qualified opportunity · Price set in your plan - Status: Testing · Dylan on your inbound · Price set in your plan - Status: By application · Dylan for partners, wholesale · Price set in your partner plan Calculator ### What your meetings would cost. Pick a way to pay and a number of held meetings. Per held meeting, the deposit is three meetings of credit and each held meeting draws it down. On the monthly plan, up to three held meetings are inside the fee. Both totals show side by side. Not sure how many meetings you need? Work it out with the pipeline calculator, or compare your SDR cost. How this compares with hiring an SDR, an agency retainer or AI SDR software. What held meetings cost on each tier | | Lite | Standard | Enterprise | | --- | --- | --- | --- | | Per held meeting | $250 | $500 | from $900 | | Deposit, three meetings of credit | $750 | $1,500 | Quoted | | 1 held meeting | $250 | $500 | Quoted | | 3 held meetings | $750 | $1,500 | Quoted | | 5 held meetings | $1,250 | $2,500 | Quoted | | 10 held meetings | $2,500 | $5,000 | Quoted | | 20 held meetings | $5,000 | $10,000 | Quoted | Each held meeting draws the deposit's credit down. Enterprise is quoted, from $900 per held meeting. The price comes in your plan. #### The monthly plan, next to Standard One month, Standard per held meeting next to the monthly plan | Held meetings in a month | Standard, per held meeting | Monthly plan | Costs less | | --- | --- | --- | --- | | 1 held meeting | $500 | $1,500 | Standard, by $1,000 | | 2 held meetings | $1,000 | $1,500 | Standard, by $500 | | 3 held meetings | $1,500 | $1,500 | Same | | 5 held meetings | $2,500 | $2,500 | Same | | 8 held meetings | $4,000 | $4,000 | Same | At three or more held meetings a month, the plan costs the same as Standard per held meeting. Below three, Standard per held meeting costs less. The plan buys one predictable invoice and Dylan working every month, not a saving. You decide what counts ### What is billed, and what never is. A meeting is billed only when someone inside your meeting definition joins the call. What pay per meeting means at Dylan. #### Billed A held meeting. Someone who matches your brief's meeting definition joins a call Dylan booked, with your meeting owner. Before anything is sent, you set the meeting definition: the titles, company sizes and regions that count. #### Never billed - Meetings outside your definition are never billed - No-shows are never billed - Companies on your do-not-contact list are never billed #### 72 hours to dispute any meeting. If you think a billed meeting should not have been, you have 72 hours after it to dispute, and disputes come back as credit. The deposit ### Your deposit, and how to pause. To start, you prepay three meetings as credit. If you pause, unused credit stays on your account. #### No meeting in 60 days? Your deposit comes back. Every dollar of it. Sixty days is the whole bet. - Disputes come back as credit - Pause any time, unused credit stays on your account ### More on how billing works All posts 5 October 2026 · 4 min read #### What counts as a held meeting, and what never gets billed Booked, held and qualified are three different meetings. How Dylan defines a held meeting, what is never billed, and how disputes and the deposit work. 5 October 2026 · 5 min read #### Pay per meeting: why Dylan charges only for meetings that happen Retainers, seats and per-lead pricing leave you holding the risk. Why Dylan charges per held meeting instead, and where outcome pricing can go wrong. ### Pick the way you want to pay. Join the waitlist and pick one. Picking a way to pay tells us what you prefer; it commits you to nothing. Join the waitlist --- # Page: Security URL: https://meetdylan.ai/security Security and trust ## How this site handles your data. This page covers meetdylan.ai: the brief you send, the waitlist you join, the form to stop Dylan's emails, and how to report a security problem. The privacy notice has the full account. ### The short version - Briefs, waitlist entries, decks, tool leads, payment records and opt-outs are stored as private files in Vercel Blob storage. - Waitlist entries, briefs and tool leads are copied into a Google Sheet that Belkins controls. Decks are not. - We do not store your IP address. - The site sets no cookies and loads no scripts from other sites. Vercel Web Analytics counts page views without cookies. - The cold email grader runs in your browser; what you paste never leaves it. - Every page is served over HTTPS, with strict transport security and a content security policy. - To report a security problem, write to dylan@meetdylan.ai. ### What is stored These records are stored: briefs, such as the one you send at the last step of "Get my meeting plan"; waitlist entries, with any deck you add; tool leads, when you ask a free tool or the buyer's guide to email you; payment records, when a team we invite pays through Stripe; and opt-outs, when you ask Dylan to stop emailing you. Nothing in the brief is saved until the last step. A waitlist entry is saved from its first step, when you press Join the waitlist, and each later step when you press Save and continue. Each brief, waitlist entry, deck, tool lead, payment record and opt-out is stored as a private file with Vercel, the company that hosts this site, in its Blob storage. A brief holds what you type into it, plus the time and your browser's name. A waitlist entry holds your answers, plus the times you saved each step and your browser's user agent. An opt-out holds the email address or company domain you enter, the time and your browser's user agent. A tool lead is kept only when you ask one of the free tools, or the buyer's guide, to email you: it holds the email address, the numbers or domain you entered and the result, never the text you paste into the cold email grader. A payment record holds Stripe's references for the payment, the amount, the plan and the reference of your waitlist entry, never your card, your name or your address. A deck goes from your browser straight to that private storage. People at Belkins who review waitlist entries open it through a link that stops working after a few days. Example of a stored opt-out: one private file holding its kind, id, time, source, type, the address entered, its domain, the browser's user agent and a status. There is no field for an IP address. Example · What an opt-out looks like when it is saved. A brief is saved the same way, as its own private file. People at Belkins who prepare plans and run Dylan can read briefs and waitlist entries. We do not sell or rent any of it. ### What is never stored We do not store your IP address. It is used for a few minutes, in memory, to stop the forms being flooded, and then forgotten. The site sets no cookies and loads no scripts from other sites. Vercel Web Analytics counts page views from this site's own address, without cookies; each view is sent without anything after a "?" or "#" in its address. Your browser keeps your light or dark theme choice and your Sound switch choice for the example notifications; for the length of your visit, the referral code or campaign tags from your link, the first page you opened and the ways to pay pages you opened; and, if you start the waitlist form, your unsent answers and a key that lets this browser finish your entry, for up to 30 days or until you clear them. They stay on your device and reach us only when you press Join or Save, or inside a brief you send. The example plan you see in steps one to three is built in your browser and is not sent to us. The cold email grader runs in your browser; what you paste never leaves it. The deliverability check does not store the domain you type unless you ask for its report by email. ### How the site is protected Every response from meetdylan.ai carries these headers: | Protection | What it does | | --- | --- | | HTTPS only Strict-Transport-Security | Browsers are told to reach this site, and its subdomains, over HTTPS only. | | Content security policy Content-Security-Policy | Pages load scripts, styles, fonts, images and media from this site only, apart from one inline script the policy names by its hash, inline styles and embedded images. They connect only to this site and, to upload a deck, to Vercel's storage. Forms post only to this site. | | No framing X-Frame-Options | No other site can show these pages inside a frame. | | Device features off Permissions-Policy | Pages cannot use your camera, microphone, location, USB devices or the browser's payment feature. | | Short referrer Referrer-Policy | A link to another site passes on our domain, not the address of the page you were on. | The forms take posts from this site's own pages; a post that a browser sends from another website's page is refused. Each form also has a rate limit: after too many posts from one network address within a few minutes, further posts are refused for a while. ### How long it is kept - Briefs are deleted after 24 months. You can ask us to delete a brief sooner. - Waitlist entries are deleted 24 months after you join, the same as briefs. - Tool leads are deleted 24 months after your last request. - Decks are deleted 12 months after you send them, or sooner if you ask. - The copy in our sheet is deleted with the entry or the brief it copies. - Opt-outs are kept for as long as Dylan sends email, because forgetting them would mean writing to you again. We keep only what we need to recognize the address or the domain. The privacy notice sets this out in full: how long we keep it. ### Who processes it Dylan is an AI agent built by Belkins. These are the services the privacy notice names: | Service | What it does for this site | | --- | --- | | Vercel | Hosts this site, stores each brief, waitlist entry, deck, tool lead and opt-out as a private file in its Blob storage, and counts page views without cookies. | | Google | Holds the Google Sheet, controlled by Belkins in Google Workspace, where each waitlist entry, brief and tool lead is copied without your browser's user agent. Decks are not copied; the sheet holds a link that expires. | | Slack | When a brief, a waitlist entry or an opt-out arrives, our team may get a one-line notice in our internal chat with its reference and the company's domain, never your email address. | | Resend | Sends the same one-line notice by email to our own mailbox, with the reference and the company's domain, never your email address, and sends the result emails you ask the free tools for. | | Stripe | Takes the payments of teams we invite, on its own pages. We keep its references and the amount, never a card. | Where the data is kept, and who can see it, is in the privacy notice: where it is kept. ### Report a security problem If you find a security problem on meetdylan.ai, write to dylan@meetdylan.ai. Tell us what you found and the steps to reproduce it. Please test only with your own data. The same address is in our security.txt file. ### Get on Dylan's calendar. Tell Dylan, our AI agent, who you sell to. A waitlist entry is saved from its first step; a brief is saved only at its last step. Join the waitlist Already know your definition? Send the full brief --- # Page: If Dylan emailed you URL: https://meetdylan.ai/emailed If Dylan emailed you ## Why Dylan wrote to you, and how to stop him. Dylan is an AI agent built by Belkins. He writes on behalf of the company named in his email, and he says so. ### Stop Dylan's emails Reply "stop" to any of his emails and he stops. If you would rather no client of his ever writes to you, leave your address here. ### Why you got this email Dylan finds the people who buy what a company sells, writes to them from his own mailboxes and answers their replies. The company tells him who it wants to meet: functions, titles, company sizes and regions. He wrote to you because your role and your company matched that brief. Here is the shape of a first email from Dylan: Example first email from Dylan to Maya, VP Operations at Nordfeld Logistics. It opens with "Hi Maya, I'm Dylan, an AI agent working with Harrow Line", gives the reason for writing, asks one question and ends with: If not, reply "no" and I won't write again. Example · A first email in the shape Dylan writes. The companies and the person are invented. ### Where your address came from For anything about your data, including where your address came from, write to dylan@meetdylan.ai. We may ask you to confirm it is you. ### Stop in one step Reply "stop" to any of his emails and he stops. The moment a reply is read, every further scheduled email to that person stops, by rule, before any AI sees it. If you would rather no client of his ever writes to you, leave your address in the form at the top of this page. Your request is recorded at once and can take up to 2 business days to reach every campaign. A shared email domain such as gmail.com is never blocked as a whole, because that would stop everyone who uses it. There, only your own address can be stopped. Opt-outs are kept for as long as Dylan sends email, because forgetting them would mean writing to you again. ### Your rights You can ask us for a copy of the personal data we hold about you, and ask us to correct it or delete it. You can always object to direct marketing, and we will stop. Write to dylan@meetdylan.ai. We answer within one month, and we may ask you to confirm it is you. If you are unhappy with our answer, you can complain to a data protection authority. The full list of your rights, and where to complain, is in the privacy notice: your rights. Curious what he would do for your company? Get my meeting plan --- # Page: How Dylan writes URL: https://meetdylan.ai/how-dylan-writes How Dylan writes ## He says he is an AI, first. Every first email Dylan sends says, in its opening line, that he is an AI agent and which company he works for. Short, plain sentences, a specific reason to write, and an obvious way out. Got an email from Dylan? Here is how to stop his emails. A first email ### Five sentences, line by line. Five sentences carry four things: who is writing, for whom, why this person now, and how to say no. A stranger can judge it at a glance. The first email, as Maya sees it · Example From Dylan, AI agent for Harrow Line To Maya, VP Operations, Nordfeld Logistics Subject fuel across your ohio sites Hi Maya, I'm Dylan, an AI agent working with Harrow Line. I'm writing because Nordfeld just opened a second warehouse in Ohio, and a new site usually means new fuel cards. Harrow Line puts every vehicle on one card with its own spend limit. Would a 20-minute review of your fuel spend be useful? If not, reply "no" and I won't write again. Dylan, AI agent for Harrow Line 63 words · lowercase subject · says he is an AI agent in the first line From The From line reads "Dylan, AI agent for" the client's name. Subject Lowercase, the way a person types it. Who is writing, and for whom The disclosure costs nine words, and it sits in the first line, not in small print under the signature. Why this person, now Pretending to be human does nothing for relevance; a specific reason to write does. What the company sells In one line, as your brief puts it. One small ask What the prospect gets comes from your meeting definition. A concrete offer gives the reader a reason to say yes. How to say no Any reply stops every further scheduled email to that person, by rule, before any AI sees it. The companies and the person are invented. How he writes ### Short, plain, and in the first person. Dylan's voice is plain, confident and specific: short sentences, American spelling, no hype. Dylan is he, and he writes in the first person. #### Dylan says he is an AI, first. In the first sentence of every first email, on the page and in replies. Never a fake name, never a fake person. Do · Hi Maya, I'm Dylan, an AI agent working with Harrow Line. Don't · Hi Maya, Sam here from the team. Quick question about your fleet. #### Subject lines are lowercase. The way a person types them. No fake "Re:" pretending to continue a conversation. Do · fuel across your ohio sites Don't · Quick Question About Your Fleet!! #### Times read like a calendar. 24-hour times, the day and the date, the zone wherever a meeting is booked. Do · Booked: Thursday, Oct 22, 10:30 Eastern. Don't · Next Thursday at 10.30am-ish? What is missing matters too: no "just following up on my last note" when there was no last note. Grade your own first email against these rules Cold email templates written by these rules Before anything is sent ### His mailboxes. Your approval. #### From his own domains Dylan writes as an AI agent working for you, from his own warmed domains and mailboxes, with a separate slice for each client. Your domain never sends a cold email. #### You approve the first emails You approve the plan and the first emails of every new angle. Each angle is a new promise in your name: a new claim, a new reason, a new tone. You see every promise once before it is repeated at scale. Replies ### Routine replies he answers. The rest come to you. He answers routine replies himself, such as scheduling or questions your brief answers, and hands you anything about pricing, legal or complaints. When someone replies, every further scheduled email to that person stops the moment the reply is read, by rule, before any AI sees it. Only then does Dylan read it. Example thread: Maya asks what it costs; Dylan hands the pricing question to Harrow Line's team and offers Thursday 10:30 or 14:00 Eastern; Maya picks 10:30; Dylan confirms the booking and says the invite comes from Harrow Line's calendar. ### Got an email from Dylan? Then an AI agent wrote to you on behalf of the company named in the email, and you can end it in one step. Reply "stop" to any of his emails and he stops. If you would rather no client of his ever writes to you, leave your address on our site. Your request is recorded at once and can take up to 2 business days to reach every campaign. Stop his emails ### See the first email he would send for you. Tell Dylan your website and who you want to meet. Your plan shows the first email he would send, and nothing is sent without your approval. Join the waitlist Already know your definition? Send the full brief --- # Page: About URL: https://meetdylan.ai/about About ## Dylan is an AI agent built by Belkins. Dylan finds the people who buy what you sell, writes to them from his own mailboxes, answers their replies and books qualified sales meetings into your calendar. You approve the plan and pay per held meeting, or on a plan we are testing. ### What Dylan does Three steps. You spend a few minutes; Dylan does the rest, from his own infrastructure. 1. A few minutes #### Brief Dylan Your website, who you sell to and who not to contact. 2. Within one business day #### Approve the plan Nothing goes out until you say yes. 3. Week by week #### Take the meetings Dylan writes, follows up, answers replies and books into your calendar. You pay per meeting held. How it works, step by step Built by Belkins ### Built by people who have booked meetings since 2017. Dylan is built by Belkins, a B2B outbound agency. > We have booked meetings for more than 1,000 companies since 2017. We know what a meeting costs when people do every step by hand, and which steps they don't need to. Dylan is that experience as an agent: the judgment of our best SDRs, the rules of our deliverability team, and a price that only counts meetings that happen. Vlad Podoliako · Founder and CEO, Belkins 2017 · Outbound since 1,000+ · Clients 50+ · Industries 4.9 · On Clutch, 230+ reviews $2B+ · Revenue generated for clients Figures as published on belkins.io and clutch.co, October 2026. ### Trusted partners ### From the blog Notes from the team behind Dylan. Written and reviewed by Vlad Podoliako Founder and CEO, Belkins 5 October 2026 · 4 min read #### Agents judge, people approve, code protects: how Dylan is built How Dylan splits the work: AI agents make the judgment calls, people approve what goes out, and plain code enforces the rules that must never bend. 5 October 2026 · 4 min read #### The AI SDR hype is over. Here is what actually survived AI SDRs promised to replace sales teams. Most early rollouts disappointed. What survived: proven playbooks, signals, people at decision points, inbound. 5 October 2026 · 4 min read #### Cold email deliverability in 2026: the rules that matter for B2B Gmail's bulk sender rules get the headlines, but B2B cold email is decided by corporate gateways, Microsoft tenant limits and new-domain checks. All posts ### Get on Dylan's calendar. Tell Dylan, our AI agent, who you sell to. A person at Belkins reads every entry and picks teams by fit. We invite 10 teams every two weeks. You approve the plan and pay per held meeting, or on a plan we are testing. Join the waitlist Already know your definition? Send the full brief --- # Page: Enterprise URL: https://meetdylan.ai/enterprise Enterprise ## Meetings with VP and C-level buyers, priced by quote. For buyers at companies with 1,000+ employees. The price depends on who you want to meet, so on Enterprise it is quoted in your plan: from $900 per held meeting. ### The Enterprise tier Enterprise · from $900 · per held meeting, quoted · VP and C-level · 1,000+ employees · Deposit: three meetings · At the quoted price Beta pricing. All three tiers #### Why it is quoted The effort behind a meeting rises steeply with company size and seniority, and you should not have to estimate it. Enterprise outbound is fishing in a pond, not an ocean. In 2022, only 10,641 companies in the United States had 1,000 or more employees. Read the math on the blog. ### How a quoted plan works Brief Dylan with your website, who you sell to and who not to contact, and choose 1,000+ as the company size. The plan that comes back holds how many companies fit, ten real examples, the first email and the price. A person at Belkins reviews your plan and emails it within one business day. Nothing goes out until you say yes. #### From brief to first meeting 1. Day 0 · You brief Dylan 2. Day 1 · Your plan, reviewed by a person at Belkins 3. Days 2 to 3 · You approve the first emails 4. Week 1 · First emails go out 5. Our target · A first held meeting within 3 weeks #### The deposit To start, you prepay three meetings as credit, at the quoted price. Each held meeting draws it down. No meeting in 60 days? Your deposit comes back. Pause any time; unused credit stays on your account. #### You decide what counts Before anything is sent, you set the meeting definition: the titles, company sizes and regions that count. A meeting is billed only when someone inside it joins the call. - Meetings outside your definition are never billed - No-shows are never billed - Companies on your do-not-contact list are never billed - 72 hours to dispute any meeting Questions before you brief Dylan? Write to dylan@meetdylan.ai. ### See the plan for your company. Tell Dylan, our AI agent, who you sell to. A person at Belkins reads every entry and picks teams by fit. We invite 10 teams every two weeks. You approve the plan and pay per held meeting, or on a plan we are testing. Join the waitlist Already know your definition? Send the full brief --- # Page: Agencies URL: https://meetdylan.ai/agencies Agencies ## Brief Dylan like any company. Dylan is an AI agent built by Belkins, a B2B outbound agency. An agency briefs him the way any company does: on this site, or with one command from a terminal. Built by Belkins - Outbound since 2017 - 1,000+ clients - 50+ industries - 4.9 on Clutch, 230+ reviews - $2B+ revenue generated for clients Figures as published on belkins.io and clutch.co, October 2026. ### Two ways in Both end the same way. A person at Belkins reviews your plan and emails it within one business day. On the site #### The brief Tell Dylan your website and who you want to meet: the functions, titles, company sizes and regions, and any companies he must never contact. Open the brief From a terminal #### One command Send a work email and Dylan stores a short brief. The answer points you to the site to tell him more: buyers, regions, sizes. curl https://meetdylan.ai/join -d you@company.com What it accepts and how it answers ### A wholesale plan, by application For agencies and consultants who sell meetings to their own clients: your name on the meetings, Dylan's engine and rules under them. Dylan still says he is an AI agent in every email. Status: By application · Partners (wholesale) #### Dylan for partners, wholesale A held meeting delivered to one of your clients, under that client's definition, billed to you at a wholesale price set in your partner plan. By application. Not open yet. The terms are set in your partner plan. How the partner plan works · Apply on the waitlist Who it fits - Outbound and appointment-setting agencies - Fractional sales consultants - GTM engineering shops that already sell meetings ### What happens next Three steps. You spend a few minutes; Dylan does the rest, from his own infrastructure. 1. A few minutes #### Brief Dylan Your website, who you sell to and who not to contact. 2. Within one business day #### Approve the plan Nothing goes out until you say yes. 3. Week by week #### Take the meetings Dylan writes, follows up, answers replies and books into your calendar. You pay per meeting held. How it works · Pricing · About Dylan and Belkins ### Get on Dylan's calendar. Tell Dylan, our AI agent, who you sell to. A person at Belkins reads every entry and picks teams by fit. We invite 10 teams every two weeks. You approve the plan and pay per held meeting, or on a plan we are testing. Join the waitlist Already know your definition? Send the full brief --- # Page: Developers URL: https://meetdylan.ai/developers Developers ## What you can reach from a terminal today. One command stores a short brief. The rest is plain files the site serves for feeds, crawlers and language models. POST /join ### The terminal door Send one work email. Dylan stores it as a short brief. A person at Belkins reviews your plan and emails it within one business day. curl https://meetdylan.ai/join -d you@company.com Write https:// in the command: curl does not follow the redirect from plain http on its own. - The body can be the address on its own, an email= form field, or JSON with an email key. - The answer is plain text. Send accept: application/json to get {"ok", "id", "ref"} back instead: the brief's id and your referral code. - Open /join in a browser and it takes you to the brief on this site. - What a brief keeps is in the privacy notice. Example terminal session: curl https://meetdylan.ai/join -d you@company.com answers Saved. Brief BR-7K2M9Q. A person at Belkins reviews your plan and emails it within one business day. Tell us more (buyers, regions, sizes) at https://meetdylan.ai/#plan ### How it answers Errors come back as one plain line with a hint, or, with accept: application/json, as {"error": {"code", "message", "hint"}}. 201 · Saved A short ticket with the brief's id, or JSON when you ask for it. 422 · No address, or not an email Send one work email. 413 · A body over 2 KB The body is larger than 2 KB. 403 · A post from another site's page This endpoint only takes posts from meetdylan.ai. 429 · Too many posts from one address Too many requests from this address. Nothing was saved. 503 · Storage is down We could not save this just now. Nothing was lost on your side. ### Files for machines Plain files at fixed addresses. Questions about any of them: dylan@meetdylan.ai. - /llms.txt · What Dylan is, how pricing works and where the key pages are, in plain Markdown for language models. - /llms-full.txt · The long form of llms.txt. - /rss.xml · The blog as RSS, newest first. - /sitemap-index.xml · The sitemap, for crawlers. - /robots.txt · Crawler rules. Every crawler is allowed. - /.well-known/security.txt · Where to report a security issue. ### Get on Dylan's calendar. Tell Dylan, our AI agent, who you sell to. A person at Belkins reads every entry and picks teams by fit. We invite 10 teams every two weeks. You approve the plan and pay per held meeting, or on a plan we are testing. Join the waitlist Already know your definition? Send the full brief --- # Page: Docs URL: https://meetdylan.ai/docs Docs menu · Overview Docs ## How working with Dylan goes. Dylan is an AI agent built by Belkins who books B2B sales meetings for you, from his own mailboxes. These pages explain each step, what you approve and what you pay for. ### How Dylan works today Dylan works by email today. You brief him with your website and who you want to meet. A person at Belkins reviews your plan and emails it within one business day. Nothing goes out until you say yes. Once you approve, Dylan writes, follows up, answers replies and books meetings into your calendar. You approve the plan and pay per held meeting, or on a plan we are testing. Dylan is new, so we have no results of our own to show yet. These pages describe how he works, not results. ### The first weeks Counted from the day you brief Dylan: From brief to first meeting 1. Day 0 · You brief Dylan 2. Day 1 · Your plan, reviewed by a person at Belkins 3. Days 2 to 3 · You approve the first emails 4. Week 1 · First emails go out 5. Our target · A first held meeting within 3 weeks The last line is our target, not a promise. ### Where to go next New to Dylan? Start with getting started. Each concept page explains one rule. - Start here Getting started The brief, the plan, approvals, your calendar, billing and the deposit, in order. - Concepts All concepts One short page for each rule that pricing and approvals depend on. - Sending and recipients Deliverability His own warmed domains and mailboxes, and why your domain stays out. - Sending and recipients Opt-outs and rights How recipients stop Dylan, and what they can ask of us. The same steps with pictures are on How it works. More on his emails is in How Dylan writes, and what this site keeps is in Security. Got an email from Dylan? If Dylan emailed you explains why, and Opt-outs and rights explains how to stop him. ### Get on Dylan's calendar. Tell Dylan, our AI agent, who you sell to. A person at Belkins reads every entry and picks teams by fit. We invite 10 teams every two weeks. You approve the plan and pay per held meeting, or on a plan we are testing. Join the waitlist Already know your definition? Send the full brief --- # Page: Join the waitlist URL: https://meetdylan.ai/waitlist Waitlist ## Get on Dylan's calendar. Tell Dylan, our AI agent, who you sell to. A person at Belkins reads every entry and picks teams by fit. Five steps. Only the first is needed. 1. 09:00 · You 2. 10:00 · Company 3. 11:00 · Buyers 4. 12:00 · Sales 5. 13:00 · Deck Example: a week on a calendar with an open slot on Thursday at 10:00, an intro with Dylan for your company. 10:00 How picking works ### How we pick who goes first. 1. 10:00 #### A person at Belkins reads every entry. Your answers and your deck are read by a person, who makes every decision. 2. 10:15 #### We invite 10 teams every two weeks. We pick the teams Dylan can help most. Fit comes first, then your place in line. 3. 10:30 #### Each team you bring moves you up 10 places. Share your link. A team counts when it joins with a work email from another company. 11:00 Ways to pay ### Ways to pay, today and in testing. Pay per held meeting is live today. We are testing the others, and partners join by application. Picking one tells us what you prefer; it commits you to nothing, and your plan states the price before anything is sent. Status: Live #### Pay per held meeting A held meeting: someone inside your written definition joins a call Dylan booked, with your meeting owner on it. Lite $250, Standard $500, Enterprise from $900 per held meeting How it works: Pay per held meeting Status: Testing #### Dylan on a monthly plan A monthly fee of $1,500 that covers up to 3 held meetings, then $500 for each held meeting after the 3rd in the same month. Unused included meetings roll over one month. $1,500 a month. Up to 3 held meetings included. Then $500 per held meeting. How it works: Dylan on a monthly plan Status: Testing #### Pay per intent A reply, in the prospect's own words, from a person inside your definition, that asks for a next step. Price set in your plan How it works: Pay per intent Status: Testing #### Pay per signup A new account on your product, created by a person Dylan contacted, inside the attribution window in your plan. Price set in your plan How it works: Pay per signup Status: Testing #### Pay per qualified opportunity A held meeting that your meeting owner confirms as a qualified opportunity, against criteria you wrote before launch. Price set in your plan How it works: Pay per qualified opportunity Status: Testing #### Dylan on your inbound A held meeting that Dylan booked from one of your inbound leads, with a person inside your definition. Price set in your plan How it works: Dylan on your inbound Status: By application #### Dylan for partners, wholesale A held meeting delivered to one of your clients, under that client's definition, billed to you at a wholesale price set in your partner plan. Price set in your partner plan How it works: Dylan for partners, wholesale 12:00 Questions ### Questions about the waitlist. 12:00 · What happens to my deck? It goes from your browser straight to our private storage. Only people at Belkins who review entries can open it, through a link that stops working after a few days. We delete it 12 months after you send it, or sooner if you ask. 12:15 · Will I be charged for joining? No. Joining costs nothing and commits you to nothing. If we invite you, your plan states the price before anything is sent. 12:30 · Can I leave the list? Yes. Write to dylan@meetdylan.ai with your entry id, and we delete your entry and any deck. 12:45 · I already sent a brief. Join here with the same work email. We match your brief and your entry by that address, so your answers stay together. --- # Page: Ways to pay URL: https://meetdylan.ai/ways-to-pay Ways to pay ## One set of rules. Several ways to pay. Today Dylan is paid per held meeting. Next to it are six more ways to pay: five we are testing with a small group and one by application. Each says exactly what it bills, and none bills a no-show. Status: Live · The default ### Pay per held meeting A held meeting: someone inside your written definition joins a call Dylan booked, with your meeting owner on it. Price · Lite $250, Standard $500, Enterprise from $900 per held meeting Who it fits · Everyone: the default offer See the prices and the calculator Status: Testing ### Dylan on a monthly plan What you pay for · A monthly fee of $1,500 that covers up to 3 held meetings, then $500 for each held meeting after the 3rd in the same month. Unused included meetings roll over one month. Price · $1,500 a month. Up to 3 held meetings included. Then $500 per held meeting. Who it fits - Mid-market teams on the Standard definition who budget in fixed monthly lines - Teams already at 3 or more held meetings a month who want one invoice See how it works: Dylan on a monthly plan Status: Testing ### Pay per intent What you pay for · A reply, in the prospect's own words, from a person inside your definition, that asks for a next step. Price · Price set in your plan Who it fits - Markets too small or too senior to produce meetings at a predictable rate - Founders and AEs who want to run the conversation themselves See how it works: Pay per intent Status: Testing ### Pay per signup What you pay for · A new account on your product, created by a person Dylan contacted, inside the attribution window in your plan. Price · Price set in your plan Who it fits - Product-led companies with a self-serve trial or free plan - Developer tools and SMB software where a meeting is the wrong first step See how it works: Pay per signup Status: Testing ### Pay per qualified opportunity What you pay for · A held meeting that your meeting owner confirms as a qualified opportunity, against criteria you wrote before launch. Price · Price set in your plan Who it fits - Mid-market and enterprise teams with CRM stages, longer cycles and higher deal values - RevOps leaders who report on cost per opportunity See how it works: Pay per qualified opportunity Status: Testing ### Dylan on your inbound What you pay for · A held meeting that Dylan booked from one of your inbound leads, with a person inside your definition. Price · Price set in your plan Who it fits - Companies whose inbound leads wait hours or a day for an answer - Mid-market and product companies with real demo volume See how it works: Dylan on your inbound Status: By application ### Dylan for partners, wholesale What you pay for · A held meeting delivered to one of your clients, under that client's definition, billed to you at a wholesale price set in your partner plan. Price · Price set in your partner plan Who it fits - Outbound and appointment-setting agencies - Fractional sales consultants See how it works: Dylan for partners, wholesale ### The same rules on every way to pay. On the ways to pay per event, you prepay credit and unused credit stays on your account. The monthly plan bills its fee at the start of each cycle. One billable event per person per segment: an event billed as an intent is never billed again as a meeting or an opportunity on the same plan. #### Your definition comes first You write the meeting definition before launch: the titles, company sizes and regions that count. #### You approve before anything is sent Nothing is sent before you approve the plan and the first emails. #### What is never billed No-shows, meetings outside your definition, companies on your do-not-contact list and duplicates are never billed. #### 72 hours to dispute 72 hours to dispute any billed event, with fixed reasons. Silence confirms. Disputes come back as credit. #### The stop rule If 1,000 contacts bring no positive reply, Dylan pauses, tells you what he heard and proposes a new angle. #### Your domain stays out of it Dylan says he is an AI agent in the first line of every first email. He sends from his own domains, or from a partner's, never from the domain of the company the meetings are for. ### Pick the way you want to pay. Join the waitlist and pick one. Picking a way to pay tells us what you prefer; it commits you to nothing. Join the waitlist --- # Page: Dylan on a monthly plan URL: https://meetdylan.ai/ways-to-pay/subscription Ways to pay · Monthly plan ## One price a month. Overflow only when Dylan books more. $1,500 a month. Up to 3 held meetings included, then $500 each. You still never pay for a no-show. Status: Testing · What you pay for A monthly fee of $1,500 that covers up to 3 held meetings, then $500 for each held meeting after the 3rd in the same month. Unused included meetings roll over one month. ### Never billed, never counted toward the three - No-shows (Dylan rebooks) - Meetings outside your definition - Companies on your do-not-contact list - Duplicates ### The price Monthly fee $1,500 Billed monthly Included 3 held meetings a month After the 3rd $500 per held meeting Unused included meetings roll over one month. Month to month. Cancel any time before the next billing date. Set in your plan: first-month rule. Status: Testing We are testing monthly plans with a small group. Join the waitlist and pick it; we will confirm the start date with you. One month on the plan · Example Monthly fee, up to three held meetings $1,500 After the 3rd, $500 each 2 × $500 This month, 5 held meetings $2,500 Standard per held meeting, same count · $2,500 At 5 held meetings in a month, both cost $2,500. The plan buys one invoice a month, not a saving. One month on the plan: the first three held meetings are inside the $1,500 fee, each one after is $500, and the dashed line is your cap, where Dylan stops booking. Example figures. How it works ### One fee a month. The same rules as every meeting. The plan changes how you pay, not what counts. A held meeting is the same held meeting, judged against the definition you write. 1. 1 #### You brief Dylan You write the meeting definition: the titles, company sizes and regions that count. 2. 2 #### Your plan, reviewed by a person at Belkins How many companies fit, examples and the first email. 3. 3 #### You approve the first emails Nothing is sent before you approve the plan and the first emails. 4. 4 #### Dylan works the month The $1,500 fee is billed at the start of each monthly cycle. It covers Dylan working your approved plan all month. 5. 5 #### The first three held meetings are inside the fee Each held meeting counts against the three included. No-shows and meetings outside your definition never count. 6. 6 #### After the 3rd, $500 each Each held meeting after the 3rd in the same month is charged once its 72-hour dispute window closes. 7. 7 #### Your cap You can set a monthly cap on held meetings; Dylan stops booking there. What you pay for ### Two charges, and nothing else. #### The monthly fee $1,500 at the start of each monthly cycle. It covers Dylan working your approved plan all month and up to three held meetings. #### After the 3rd $500 per held meeting. Charged after its 72-hour dispute window closes. You can set a monthly cap on held meetings; Dylan stops booking there. #### Who it fits - Mid-market teams on the Standard definition who budget in fixed monthly lines - Teams already at 3 or more held meetings a month who want one invoice Standard definition: Mid-market, directors and VPs, 201 to 1,000 employees. #### Who it does not fit - Lite-market buyers (per held meeting on Lite costs less) - Enterprise definitions (quoted separately) See the prices per held meeting The honest arithmetic ### Below three held meetings, per held meeting costs less. We would rather you see it here than on an invoice. The plan is for teams who want one predictable bill and Dylan working every month. One month, Standard per held meeting next to the monthly plan | Held meetings in a month | Standard, per held meeting | Monthly plan | Costs less | | --- | --- | --- | --- | | 1 held meeting | $500 | $1,500 | Standard, by $1,000 | | 2 held meetings | $1,000 | $1,500 | Standard, by $500 | | 3 held meetings | $1,500 | $1,500 | Same | | 5 held meetings | $2,500 | $2,500 | Same | | 8 held meetings | $4,000 | $4,000 | Same | At three or more held meetings a month, the plan costs the same as Standard per held meeting. Below three, Standard per held meeting costs less. The plan buys one predictable invoice and Dylan working every month, not a saving. ### The same rules on every way to pay. #### Your definition comes first You write the meeting definition before launch: the titles, company sizes and regions that count. #### You approve before anything is sent Nothing is sent before you approve the plan and the first emails. #### What is never billed No-shows, meetings outside your definition, companies on your do-not-contact list and duplicates are never billed. #### 72 hours to dispute 72 hours to dispute any billed event, with fixed reasons. Silence confirms. Disputes come back as credit. #### The stop rule If 1,000 contacts bring no positive reply, Dylan pauses, tells you what he heard and proposes a new angle. #### Your domain stays out of it Dylan says he is an AI agent in the first line of every first email. He sends from his own domains, or from a partner's, never from the domain of the company the meetings are for. Questions ### Questions about the monthly plan. 15:00 · What counts as a held meeting? Someone who matches your brief's meeting definition joins a call Dylan booked, with your meeting owner. No-shows, people on your do-not-contact list, duplicates and anyone outside the definition are not billed. 15:05 · What is never billed? No-shows (Dylan rebooks), meetings outside your definition, companies on your do-not-contact list and duplicates. None of them counts toward the three included meetings either. 15:10 · How do disputes work? You have 72 hours to dispute any meeting, with fixed reasons. Silence confirms. A disputed included meeting returns its slot to the month; a disputed meeting after the three comes back as credit. 15:15 · Which companies is it for? The Standard definition. Mid-market, directors and VPs, 201 to 1,000 employees. Enterprise definitions are quoted. If you sell to companies with 1 to 200 employees, Lite per held meeting costs less. 15:20 · Is it cheaper than paying per held meeting? No. At three or more held meetings a month it costs the same as Standard; below three, Standard per held meeting costs less. The plan buys one invoice a month. 15:25 · Do unused included meetings roll over? Yes, for one month. Unused included meetings roll over one month. 15:30 · How do I cancel? Billed monthly. Month to month. Cancel any time before the next billing date. Any first-month rule is set in your plan. 15:35 · What if it doesn't work? If 1,000 contacts bring no positive reply, Dylan pauses, tells you what he heard and proposes a new angle. 15:40 · Whose name is on the emails? Dylan's. He writes as an AI agent working for you, from his own domains. Your domain never sends a cold email. ### Want to pay this way? We are testing monthly plans with a small group. Join the waitlist and pick it; we will confirm the start date with you. Join the waitlist --- # Page: Pay per intent URL: https://meetdylan.ai/ways-to-pay/per-intent Pay per intent ## Pay for the yes, not the calendar invite. Pay when the right person says yes, in their own words. You read the reply before you pay. Status: Testing · An intent is A reply, in the prospect's own words, from a person inside your definition, that asks for a next step. It is not intent data. A person wrote back, in a thread Dylan started. Example: Dylan's inbox beside the client's week. A reply from Dana, VP Operations at Fenwick Haulage, arrives as a notification: "Happy to talk, what does Thursday look like?" It passes the three tests and is stamped Intent. The thread waits in the Yours to book tray, and Thursday shows a dashed hold, not a booked meeting, because the client books it. Three other replies, an out-of-office, a not now and a request to stop, are marked not billed. You decide what counts ### Pay for the reply, never for the noise. A reply is billed only when it passes all three tests. Everything else costs nothing, and the list comes before the price. #### The three tests Intent They agree to talk, ask for a time, ask about price or terms, or ask you to contact a named colleague inside your definition. Fit The person and the company are inside your meeting definition. A next step A clear action exists: a call, a time, a question for you to answer. One billable event per person per segment: an event billed as an intent is never billed again as a meeting or an opportunity on the same plan. #### Never billed - Auto-replies and out-of-office - Stop, unsubscribe or not interested - Not now with no next step - A request for content alone, unless your plan counts it - A referral to someone outside your definition - Anyone on your do-not-contact list or an existing customer - A second intent from the same person or company in your plan's window - A reply to anything other than the approved offer The price Price set in your plan - Prepaid credit, 72-hour disputes, credit-only refunds. The default offer is pay per held meeting, with its prices on the pricing page. Status: Testing We are testing this way to pay with a small group. The price is set in your plan. Join the waitlist and we will tell you when it opens. How it works ### From the first email to a reply you can use. The plan, the approvals and Dylan's rules are the same as for held meetings. What changes is where Dylan hands over. #### The same plan and approvals You write the meeting definition. A person at Belkins reviews the plan, and you approve the first emails before anything is sent. #### Dylan writes and sends From his own mailboxes, as an AI agent working for you. He follows up, and every further email to a person stops the moment their reply is read. #### The reply is classified Dylan labels each reply against the three tests. During the test, a Belkins operator samples his labels. #### You get the thread An intent comes to you with the prospect's own words and the email headers, so you can read it before you pay. #### You take it from there You run the conversation and book the call. If your plan says so, Dylan books it for you instead. The sorter ### Four replies. One intent. Every reply meets the same three tests. A reply that fails one is never billed, and the card says why. Only the yes goes to you. Example: four replies sorted by the three tests. Riley's out-of-office fails Their own words and A next step: not billed. Noor's "Not now. Maybe next year." fails A next step: not billed. Lena's "Please remove me from your list." fails A next step: not billed, and Dylan stops writing to her. Ines's "Sure, what does a review involve? Thursday works." passes all three: an intent, which waits in the tray for you to book. Riley, Director of IT wrote: "Thanks for your email. I am out of the office until Monday with limited access." - Passes: In your definition - Fails: Their own words - Fails: A next step Not billed: out-of-office Noor, COO wrote: "Not now. Maybe next year." - Passes: In your definition - Passes: Their own words - Fails: A next step Not billed: no next step Lena, VP Finance wrote: "Please remove me from your list." - Passes: In your definition - Passes: Their own words - Fails: A next step Not billed: asked to stop Ines, Head of Fleet wrote: "Sure, what does a review involve? Thursday works." - Passes: In your definition - Passes: Their own words - Passes: A next step Intent Yours to book Ines, Head of Fleet · Intent · the thread is yours, with her words and headers If your plan says so, Dylan books the meeting too. On a hybrid plan the intent is credited against the meeting: you never pay for both. Checked and disputed ### The thread is the evidence. You read the prospect's own words, with the email headers, before you pay. Dylan's classifier labels each reply, and a Belkins operator samples the labels during the test. An intent is charged from your prepaid credit when the thread is handed to you and the 72-hour window closes. Handed to you · Charged from credit Silence confirms. Disputes come back as credit. Fixed reasons to dispute - Outside your definition - Not their own words - No next step - Duplicate - On your do-not-contact list Not a reason: they did not answer my follow-up. After handoff the conversation is yours. ### The same rules on every way to pay. #### Your definition comes first You write the meeting definition before launch: the titles, company sizes and regions that count. #### You approve before anything is sent Nothing is sent before you approve the plan and the first emails. #### What is never billed Only a reply that passes all three tests is billed. Auto-replies, refusals, a not now, existing customers and second intents never are. #### 72 hours to dispute 72 hours to dispute any billed event, with fixed reasons. Silence confirms. Disputes come back as credit. #### The stop rule If 1,000 contacts bring no positive reply, Dylan pauses, tells you what he heard and proposes a new angle. #### Your domain stays out of it Dylan says he is an AI agent in the first line of every first email. He sends from his own domains, or from a partner's, never from the domain of the company the meetings are for. Questions ### Questions about paying per intent. 15:00 · Is this intent data? No. An intent here is a person who wrote back, in a thread Dylan started, in their own words, asking for a next step. 15:05 · Who runs the conversation after the reply? You do. After handoff the conversation is yours. If your plan says so, Dylan books the meeting instead, and the intent is credited against it. 15:10 · What if the reply is an auto-reply? Auto-replies and out-of-office messages are never billed. Neither are stop, unsubscribe or not interested, or a not now with no next step. 15:15 · How long do I have to dispute? 72 hours from handoff, with a fixed reason: outside your definition, not their own words, no next step, a duplicate, or on your do-not-contact list. Silence confirms. Disputes come back as credit. 15:20 · What if nobody replies? If 1,000 contacts bring no positive reply, Dylan pauses, tells you what he heard and proposes a new angle. 15:25 · Does Dylan say he is an AI? Yes, in the first line of every first email. Dylan's. He writes as an AI agent working for you, from his own domains. Your domain never sends a cold email. 15:30 · Do you promise a reply rate? No. For a sense of scale: in Belkins' study of 7.5 million cold emails sent in 2025, the average reply rate was 0.45%. Why we charge per held meeting. ### Want to pay this way? Pick Pay per intent on the waitlist. Picking a way to pay tells us what you prefer; it commits you to nothing. Join the waitlist --- # Page: Pay per signup URL: https://meetdylan.ai/ways-to-pay/per-signup Pay per signup ## For products that sell themselves, pay per signup Dylan started. Some buyers would rather try than talk. Dylan sends them to your signup page, and you pay for the work accounts that arrive from companies he wrote to. Status: Testing · What you pay for A new account on your product, created by a person Dylan contacted, inside the attribution window in your plan. Needs a connection from your signup system before launch. Example: a timeline of two working weeks. Dylan emails Maya, VP Operations at Nordfeld Logistics, on Mon 19. The attribution window, whose length is set in your plan, runs from that day to Tue 27. Maya signs up on Thu 22 with the address Dylan wrote to, inside the window, so the signup counts. You decide what counts ### Pay for the signups Dylan started. A signup is billed only when it meets every part of the matching rule. The list of what is never billed comes before the price. #### The matching rule A new account A trial, a free plan or a demo request on your product, whichever your plan names. Started by Dylan Created by a person Dylan contacted, inside the attribution window your plan sets. A match The signup email is the address Dylan wrote to, or a work email at the contacted company's domain when your plan allows domain matching: one per company, unless your plan says per user. Inside your definition The person is inside your definition's company and title range. A stricter event can be the default in your plan: an activated signup, counted at the first action you name. #### Never billed - Free-mail addresses - People already in your CRM or user base at first contact - Companies Dylan did not contact in the window - Test and duplicate accounts - Accounts deleted within 72 hours The price Price set in your plan - Prepaid credit, 72-hour disputes, credit-only refunds. - Needs a connection from your signup system before launch. The default offer is pay per held meeting, with its prices on the pricing page. Status: Testing We are testing this way to pay with a small group. The price is set in your plan. Join the waitlist and we will tell you when it opens. How it works ### From the first email to a signup on the ledger. The plan, the approvals and Dylan's rules are the same as for held meetings. What changes is the event: an account on your product, not a call. #### The same plan and approvals You write the definition. A person at Belkins reviews the plan, and you approve the first emails before anything is sent. #### Connect your signup system Before launch: a webhook, a Stripe or HubSpot event, a Dylan short link in your form, or a weekly export during the test. You upload your current users, so they are never billed. #### Dylan writes and sends From his own mailboxes, as an AI agent working for you, pointing people who would rather try than talk to your signup page. #### The window runs Each person Dylan contacts opens an attribution window, as long as your plan says. A signup inside it counts, whatever the last click. #### You read the ledger Every match is on the ledger: the email sent, the signup, exact or domain. You have 72 hours to dispute each ledger. The match ledger ### Every signup on one ledger, with the reason. A signup counts only inside the window, from the person or the company Dylan wrote to. Everything else stays on the ledger, marked not billed, so you can see why. Example: Dylan emails Maya, VP Operations at Nordfeld Logistics, on Mon 19. The window runs to Tue 27. Her signup on Thu 22 from the address Dylan wrote to counts. Jon's signup on Thu 29 came after the window: not billed. A signup from a current customer: not billed. Maya, VP Operations · Nordfeld Logistics Example Drag the signup along the days, or focus it and use the arrow keys. Counts - Passes: Dylan wrote to this person - Passes: Signed up inside the window - Passes: A work email that matches - Passes: Not already your customer Match ledger · Example Maya, VP Operations · Email Mon 19 · signup Thu 22 · same address Counts Jon, Head of Data · Email Mon 19 · signup Thu 29 · after the window Not billed Ops lead, Fenwick Haulage · In your user base at first contact Not billed: your customer Checked and disputed ### Matched against your data, written down in advance. This way to pay needs data from your side, so your plan requires it before launch. Dylan matches each signup event against his send log. The attribution rule is written in advance: contacted by Dylan inside the window counts, whatever the last click. Dylan publishes a match ledger, with the email sent, the signup and the kind of match, exact or domain. Ledger published · Charged from credit Silence confirms. Disputes come back as credit. Dispute any match that is - From a company Dylan did not contact - Outside the window - From a free-mail address - Already your customer - A test or duplicate account - Deleted within 72 hours ### The same rules on every way to pay. #### Your definition comes first You write the meeting definition before launch: the titles, company sizes and regions that count. #### You approve before anything is sent Nothing is sent before you approve the plan and the first emails. #### What is never billed Free-mail addresses, people already in your CRM or user base, companies Dylan did not contact in the window, and test or duplicate accounts are never billed. #### 72 hours to dispute 72 hours to dispute any billed event, with fixed reasons. Silence confirms. Disputes come back as credit. #### The stop rule If 1,000 contacts bring no positive reply, Dylan pauses, tells you what he heard and proposes a new angle. #### Your domain stays out of it Dylan says he is an AI agent in the first line of every first email. He sends from his own domains, or from a partner's, never from the domain of the company the meetings are for. Questions ### Questions about paying per signup. 15:00 · Do I need to connect my signup system? Yes, before launch. A webhook, a Stripe or HubSpot event, a Dylan short link in your form, or a weekly export during the test. Without one, this way to pay does not fit. 15:05 · Do free-mail signups count? No. A signup from a free-mail address is never billed, even from a person Dylan wrote to. 15:10 · Do my existing users count? No. The export of your CRM or user base that you upload before launch is the baseline, and anyone on it at first contact is never billed. 15:15 · Does a link in the email track it? A Dylan short link can carry the signup into your form, but matching does not depend on it. A signup counts when the address or the company matches, whatever the last click. 15:20 · How long do I have to dispute? 72 hours from each ledger, with a fixed reason. Silence confirms. Disputes come back as credit. 15:25 · Does Dylan say he is an AI? Yes, in the first line of every first email. Dylan's. He writes as an AI agent working for you, from his own domains. Your domain never sends a cold email. 15:30 · Do you promise a number of signups? No. We are testing this way to pay, and we make no promise about signup volume. ### Want to pay this way? Pick Pay per signup on the waitlist. Picking a way to pay tells us what you prefer; it commits you to nothing. Join the waitlist --- # Page: Pay per qualified opportunity URL: https://meetdylan.ai/ways-to-pay/per-opportunity Pay per qualified opportunity ## Pay for the meetings your team calls real. Your meeting owner confirms each held meeting against criteria you wrote before the first email. Silence confirms. Closing stays with you. Status: Testing · What you pay for A held meeting that your meeting owner confirms as a qualified opportunity, against criteria you wrote before launch. Example: Leo, Head of Fleet at Nordfeld Logistics, held a meeting on Thursday at 15:00. After the call the meeting owner checks it against the plan's written criteria: problem confirmed, budget owner named, next step dated. Confirmed, it is billed as a qualified opportunity. Rejected with one written criterion, it is held and not billed on this plan. With no answer before the confirmation window closes, silence confirms. Thu 15:00 · Leo, Head of Fleet · Held · Nordfeld Logistics Qualified opportunity Confirmed by your meeting owner. Problem confirmed, budget owner named, next step dated. Billed as a qualified opportunity. Thu 16:00 · Sofia, COO · Held · Harrow Line Not billed Held, not billed on this plan. Reason given: no budget owner named, a criterion written into the plan. No answer before the confirmation window in your plan closes? Silence confirms, as it does for held meetings today. After the call ### Qualified opportunity? You are the meeting owner. Leo, Head of Fleet, Nordfeld Logistics Example Each plan writes its own criteria before the first email. These three are examples. Yes needs every criterion the call met checked. Example people and companies. The prepaid deposit stays. 72-hour disputes on the held meeting; the confirmation window is set in your plan. From our post on pricing > A held meeting is the last step we control. Why Dylan charges per held meeting ### Why we go one step past the meeting here We said the held meeting is the last step we control. Some teams asked us to go one step further and be paid only when their own team calls it pipeline. In this test we do, on rules you write before the first email. The criteria judge the prospect's situation on the first call, never your demo or your price. Closing stays your job. Per held meeting stays our default offer, and the argument in the post stands for it. How it works ### The meeting, then one question. Everything up to the held meeting works as it does today. Then your meeting owner answers one question. 1. Before launch #### You write the definition and the criteria The meeting definition, as today, plus the criteria that make a held meeting a qualified opportunity. They judge the prospect: for example, the problem confirmed, the budget owner named, a dated next step. Each plan writes its own. 2. Before sending #### You approve the plan and the first emails Nothing is sent before you approve them. Dylan writes as an AI agent working for you, from his own domains. 3. The call #### The meeting is held Verified as today: the calendar record, then your meeting owner's 72-hour window to dispute the meeting itself. 4. After the call #### One click: qualified opportunity? Your meeting owner answers Yes, or No with one criterion from your written list. Or connect HubSpot or Salesforce, and Dylan reads the stage change instead. 5. Window closes #### Silence confirms No answer by the end of the confirmation window in your plan counts as Yes, the way silence confirms a held meeting today. 6. Throughout #### The integrity rules, in plain words We track how often each client says No. Above the threshold in your plan, the plan goes back to per held meeting pricing. A meeting marked No that your CRM later shows moving forward with the same company, inside the plan's window, is billed. Verdict disputes go to a reviewer at Belkins with the call notes, with fixed reasons only. What you pay for ### A confirmed opportunity. Nothing before it. The billable event A held meeting (the published definition) that your meeting owner confirms as a qualified opportunity against criteria written into your plan before launch, for example: the prospect confirmed the problem you solve, named who owns the budget, and dated a next step. Billed when the owner confirms, or when the confirmation window in your plan closes with no answer: silence confirms. Held meetings that are not confirmed cost nothing on this plan. How it is verified The held meeting as today. Then a one-click check to your meeting owner (Qualified opportunity? Yes / No, and which criterion), or the stage change read from a connected CRM. A No must cite one criterion from the written list; not ready to buy, timing and went with a competitor are not reasons unless written in. Integrity rules: the No rate per client is tracked and a client above the plan's threshold returns to per held meeting pricing; a back-bill clause covers an opportunity marked No that the CRM later shows progressing with the same company inside the plan window; verdict disputes go to a Belkins reviewer with the call notes, fixed reasons only. #### Never billed - A held meeting your meeting owner does not confirm - No-shows (Dylan rebooks) - Meetings outside your definition - Companies on your do-not-contact list - Duplicates Price Price set in your plan - The prepaid deposit stays. 72-hour disputes on the held meeting; the confirmation window is set in your plan. - Single step: nothing is billed for the held meeting itself on this plan. Status: Testing We are testing this way to pay with a small group. The price is set in your plan. Join the waitlist and we will tell you when it opens. #### Who it fits - Mid-market and enterprise teams with CRM stages, longer cycles and higher deal values - RevOps leaders who report on cost per opportunity - Buyers burned by junk meetings #### Who it does not fit - Teams without a CRM or a named meeting owner who will answer the check ### The same rules on every way to pay. #### Your definition comes first You write the meeting definition before launch: the titles, company sizes and regions that count. #### You approve before anything is sent Nothing is sent before you approve the plan and the first emails. #### What is never billed No-shows, meetings outside your definition, companies on your do-not-contact list and duplicates are never billed. #### 72 hours to dispute 72 hours to dispute any billed event, with fixed reasons. Silence confirms. Disputes come back as credit. #### The stop rule If 1,000 contacts bring no positive reply, Dylan pauses, tells you what he heard and proposes a new angle. #### Your domain stays out of it Dylan says he is an AI agent in the first line of every first email. He sends from his own domains, or from a partner's, never from the domain of the company the meetings are for. Questions ### Before you pick this one. Short answers from the rules above. 15:00 · Who decides what counts? Your meeting owner, against the criteria you wrote into your plan before the first email. 15:05 · What if nobody answers the check? Silence confirms. When the confirmation window in your plan closes with no answer, the meeting counts as a qualified opportunity. 15:10 · Can we say "not ready to buy"? Only if it is one of your written criteria. A No must cite one criterion from your list. Not ready to buy, timing and went with a competitor are not reasons unless your plan writes them in. 15:15 · Do you need our CRM? No. The one-click check works without it. If you connect HubSpot or Salesforce, Dylan can read the stage change instead. 15:20 · What does a held meeting cost if it is not confirmed? Nothing on this plan. There is one billable step: the confirmed opportunity. 15:25 · You said you stop at the meeting. Why this? We said the held meeting is the last step we control. Some teams asked us to go one step further and be paid only when their own team calls it pipeline. In this test we do, on rules you write before the first email. The criteria judge the prospect's situation on the first call, never your demo or your price. Closing stays your job. Per held meeting stays our default offer, and the argument in the post stands for it. 15:30 · How do disputes work? You have 72 hours to dispute the held meeting, with fixed reasons, as today. Disputes come back as credit. A disputed verdict goes to a reviewer at Belkins with the call notes. 15:35 · What if it doesn't work? If 1,000 contacts bring no positive reply, Dylan pauses, tells you what he heard and proposes a new angle. 15:40 · Whose name is on the emails? Dylan's. He writes as an AI agent working for you, from his own domains. Your domain never sends a cold email. ### Want to pay this way? We are testing this way to pay with a small group. The price is set in your plan. Join the waitlist and we will tell you when it opens. Join the waitlist --- # Page: Dylan on your inbound URL: https://meetdylan.ai/ways-to-pay/inbound Dylan on your inbound ## The cheapest meeting is the one already asking for you. Dylan answers your inbound leads while they are still looking, says he is an AI, and books the call. You pay only when one becomes a held meeting. Status: Testing · What you pay for A held meeting that Dylan booked from one of your inbound leads, with a person inside your definition. Example: a demo request from Priya, Director of Logistics at Nordfeld Logistics, arrives as a notification. Dylan answers, says he is an AI agent, and books a meeting for today at 11:00; it is billed only once it is held. A request from Leo, an existing customer, is handed to the client's team and never billed. A request from Dev, who had already booked himself, is never billed. A grey block on the next day shows the old next-day handoff, as an illustration, not a statistic. Today 11:00 · Priya, Director of Logistics · Booked from a demo request Booked A new lead. Dylan answers from your approved facts, says he is an AI agent, and books the call. Billed once it is held. Leo, Head of Fleet · Demo request · existing customer Not billed Not billed: your customer. Dylan hands the request to your team. Dev, Fleet Manager · Demo request · booked himself first Not billed Not billed: already booked. He had booked a time before Dylan replied. Example people and times. Leads Dylan answers and disqualifies, or helps without a meeting, cost nothing. Your website ### Request a demo An example form. Pressing send plays one request. Request 2 of 3: from an existing customer. Booked from your inbound. Billed only once the meeting is held. Example people, companies and times. No speed claim: there is no measured number yet. How it works ### Your inbound, answered by Dylan. The inventory is your own inbound, not cold email. If inbound leads wait a day for an answer, fix that first: it is cheaper than any outbound. 1. Setup #### Connect your form, or forward your inbox A webhook from your website form or demo request, or a forwarding address for inbound email. Each request arrives with its time and source. 2. Before launch #### You approve what Dylan may say Your meeting definition, as today, and the facts he may use to answer. He answers from those facts only. 3. A lead arrives #### Dylan answers, and says he is an AI His first line says he is an AI agent working with you. Anything about pricing, legal or complaints he hands to you. 4. The answer #### He qualifies against your definition Leads inside your definition get a time with your meeting owner. Leads he disqualifies, or helps without a meeting, cost nothing. 5. The booking #### He books your meeting owner's calendar The invite goes on your meeting owner's calendar, and the full conversation stays with the meeting. 6. After the call #### Billed once held Attendance comes from the calendar. You have 72 hours to dispute, with fixed reasons, and the inbound source and the full conversation sit on every billed meeting. What you pay for ### A held meeting from your inbound. The billable event A held meeting (the published definition) that Dylan booked from an inbound lead: a website form, a demo request, a chat, or an inbound email forwarded to Dylan. The person must be inside your definition. Leads Dylan answers and disqualifies, or helps without a meeting, cost nothing. How it is verified The form event (webhook or forwarding address) timestamps the request; Dylan's reply and the booking are logged; attendance from the calendar; the same 72-hour window and fixed reasons. The inbound source and the full conversation sit on every billed meeting. #### Never billed - People who had already booked themselves before Dylan replied - Existing customers - Leads your own team answered first - No-shows (Dylan rebooks) - Meetings outside your definition - Companies on your do-not-contact list - Duplicates Price Price set in your plan - Prepaid credit, 72-hour disputes, credit-only refunds. - Needs a form webhook or a forwarding address for your inbound email. Status: Testing We are testing this way to pay with a small group. The price is set in your plan. Join the waitlist and we will tell you when it opens. #### Who it fits - Companies whose inbound leads wait hours or a day for an answer - Mid-market and product companies with real demo volume #### Who it does not fit - Companies with little inbound ### The same rules on every way to pay. #### Your definition comes first You write the meeting definition before launch: the titles, company sizes and regions that count. #### You approve before anything is sent Nothing is sent before you approve the plan and the first emails. #### What is never billed No-shows, meetings outside your definition, companies on your do-not-contact list, duplicates, existing customers, people who had already booked themselves and leads your team answered first are never billed. #### 72 hours to dispute 72 hours to dispute any billed event, with fixed reasons. Silence confirms. Disputes come back as credit. #### Stop any time Pause any time. Unused credit stays on your account. #### Your domain stays out of it On this plan Dylan sends no cold email at all: he answers people who asked you first, and says he is an AI agent in his first line. Questions ### Before you pick this one. Short answers from the rules above. 15:00 · Does Dylan send cold email on this plan? No. On this plan he answers only people who asked you first: your website form, demo requests, chat, or inbound email you forward to him. 15:05 · What if they would have booked anyway? People who had already booked themselves before Dylan replied are never billed. Neither are leads your own team answered first, or existing customers. 15:10 · Does Dylan say he is an AI? Yes, in his first line. 15:15 · What does he know about us? Only the facts you approved. Dylan answers routine ones (scheduling, questions your brief answers) and hands you anything about pricing, legal or complaints. 15:20 · What do we need to connect? A webhook from your form, or a forwarding address for inbound email. 15:25 · How fast does he answer? We do not give a number yet. A speed claim waits until it is measured. 15:30 · What if a lead is not a fit? Leads Dylan answers and disqualifies, or helps without a meeting, cost nothing. 15:35 · What counts as a held meeting? Someone who matches your brief's meeting definition joins a call Dylan booked, with your meeting owner. No-shows, people on your do-not-contact list, duplicates and anyone outside the definition are not billed. 15:40 · How do disputes work? You have 72 hours to dispute any billed meeting, with fixed reasons. Silence confirms. Disputes come back as credit. ### Want to pay this way? We are testing this way to pay with a small group. The price is set in your plan. Join the waitlist and we will tell you when it opens. Join the waitlist --- # Page: Dylan for partners, wholesale URL: https://meetdylan.ai/ways-to-pay/partners Dylan for partners, wholesale ## Your name on the meetings. Dylan's engine under them. Sell meetings under your name. Dylan books them, from your domains, and says he is an AI working with you. Wholesale per held meeting, by application. Status: By application · What a partner pays for A held meeting delivered to one of your clients, under that client's definition, billed to you at a wholesale price set in your partner plan. Example: a partner, Northway Partners, runs three clients through Dylan. Each client has its own week, definition, plan and approvals, and held meetings settle into each. A switch changes the email signature and the calendar invite from "Dylan, AI agent for Client 1" to "Dylan, AI agent working with Northway Partners"; the words "AI agent" stay in both. The partner ledger notes a wholesale charge for each held meeting, at the price set in the partner plan. How Dylan signs Dylan Dylan · AI agent for Client 1 Your brand Dylan · AI agent working with Northway Partners The words "AI agent" never change. White label never hides that Dylan is an AI. How Dylan signs Email signature Dylan · AI agent for Client 1 Calendar invite · From Dylan, AI agent for Client 1 Partner ledger Example partner and clients. Disputes travel from your client to you to Dylan within the same 72 hours. How it would work ### Your clients. Dylan's rules. By application. Not open yet. The terms are set in your partner plan. This is how a partner plan is meant to run. 1. Per client #### You brief Dylan for each client Each of your clients gets its own meeting definition, plan and approvals, and its own do-not-contact list. 2. Before sending #### Your client approves, through you Nothing is sent before the plan and the first emails are approved. 3. Sending #### Dylan books from your domains From your own domains, or from a sending slice reserved for you. Every first email says he is an AI agent working with you. 4. After the call #### Held meetings, client by client The same held-meeting record for each client, and a ledger per client for you. Disputes travel from your client to you to Dylan within the same 72 hours, with fixed reasons. 5. Billing #### You bill your client Dylan bills you a wholesale price per held meeting from a prepaid partner credit pool. You set your own retail price and own the client relationship. What a partner pays for ### A held meeting for one of your clients. The billable event A held meeting delivered to a partner's client, under that client's written definition and the same never-billed list, billed to the partner at a wholesale price set in the partner plan, from a prepaid partner credit pool. The partner sets its own retail price and owns the client relationship. Dylan's AI disclosure stays in every email: white label never hides that he is an AI. How it is verified The same held-meeting record per partner client project; disputes travel client to partner to Dylan within the same 72 hours, fixed reasons; a ledger per client for the partner. #### Never billed - No-shows (Dylan rebooks) - Meetings outside the client's definition - Companies on the client's do-not-contact list - Duplicates Price Price set in your partner plan - No public wholesale price. Your partner plan sets it, and you set your own retail price. Status: By application By application. Not open yet. The terms are set in your partner plan. #### Who it fits - Outbound and appointment-setting agencies - Fractional sales consultants - GTM engineering shops that already sell meetings #### Who it does not fit - Anyone who wants to resell Dylan without carrying the client relationship ### The same rules on every way to pay. #### Your definition comes first You write the meeting definition before launch: the titles, company sizes and regions that count. #### You approve before anything is sent Nothing is sent before you approve the plan and the first emails. #### What is never billed No-shows, meetings outside your client's definition, companies on your client's do-not-contact list and duplicates are never billed. #### 72 hours to dispute 72 hours to dispute any billed event, with fixed reasons. Silence confirms. Disputes come back as credit. #### The stop rule If 1,000 contacts bring no positive reply, Dylan pauses, tells you what he heard and proposes a new angle. #### Your domain stays out of it Dylan sends from your domains or from a sending slice reserved for you, and says he is an AI agent working with you. Your clients' own domains never send a cold email. Questions ### Before you apply. Short answers. The partner plan sets the rest. 15:00 · Is this white label? Your name on the meetings. Dylan still says he is an AI agent in every email: "Dylan, AI agent working with" your company. White label never hides that he is an AI. 15:05 · Whose domains send the email? Yours, or a sending slice reserved for you. Your clients' own domains never send a cold email. 15:10 · When does it open? Not yet. We take applications on the waitlist. 15:15 · Can my client dispute a meeting? Yes, through you, within 72 hours, with fixed reasons. Disputes come back as credit. 15:20 · What is the price? Set in your partner plan. You set your own retail price for your clients. 15:25 · Who is it for? Outbound and appointment-setting agencies, fractional sales consultants, GTM engineering shops that already sell meetings. Not for anyone who wants to resell Dylan without carrying the client relationship. 15:30 · What do my clients get? Each one gets its own meeting definition, plan, approvals and do-not-contact list, and the same never-billed list as every Dylan client. ### Apply for a partner plan. By application. Not open yet. The terms are set in your partner plan. Apply on the waitlist --- # Page: Free tools URL: https://meetdylan.ai/tools Free tools ## Tools for the numbers before the meetings. Each tool uses only what you type. Nothing is saved unless you ask for your result by email. Free tool ### Pipeline calculator Your quota, deal size and win rate in. The held meetings you need each month out, priced in every way to pay. You put in - Your quota or revenue target - Average deal size - Win rate from held first meeting to closed deal You get The held first meetings you need each month, priced in every way to pay for Dylan Open the tool: Pipeline calculator Free tool ### SDR cost calculator Your SDR pay, tools and held meetings in. Your cost per held meeting out, next to Dylan's price. You put in - SDRs on the team - Base salary per SDR - Tools and data per SDR - Held meetings a month, whole team You get Your cost per held meeting, next to Dylan's price per held meeting Open the tool: SDR cost calculator Free tool · Powered by Folderly ### Deliverability check Type a domain. We look up its MX, SPF, DKIM and DMARC records in public DNS, explain each one and show the fix. You put in - Domain - A DKIM selector (optional) You get The domain's MX, SPF, DKIM and DMARC records, each explained in plain words, with the fix Open the tool: Deliverability check Free tool ### Cold email grader Paste a first cold email and see which of Dylan's nine rules it meets, with a fix for each. You put in - Your first email - Who sends it You get A score out of 100 against Dylan's nine rules, with one fix per rule Open the tool: Cold email grader ### Read first - The buyer's guide - Glossary - The blog ### Get on Dylan's calendar. Tell Dylan, our AI agent, who you sell to. A person at Belkins reads every entry and picks teams by fit. We invite 10 teams every two weeks. You approve the plan and pay per held meeting, or on a plan we are testing. Join the waitlist Already know your definition? Send the full brief --- # Page: Pipeline calculator URL: https://meetdylan.ai/tools/pipeline-calculator Free tool ## How many meetings it takes to hit your quota. Put in your quota, your average deal and your own win rate. See the held meetings you need each month, and what they cost in every way to pay for Dylan. ### Your numbers ### Your month Your browser is not running scripts, so the numbers cannot be worked out on this page. The formula below gives the same result. See the formula Your month of held first meetings #### Priced in every way to pay The way to pay you would start with, if you know Lite, per held meeting · Status: Live · Start with this: Lite, per held meeting $250 each Per held meeting. Deposit $750, three meetings of credit. Standard, per held meeting · Status: Live · Start with this: Standard, per held meeting $500 each Per held meeting. Deposit $1,500, three meetings of credit. Enterprise, per held meeting · Status: Live · Start with this: Enterprise, per held meeting Quoted Enterprise is quoted, from $900 per held meeting. The price comes in your plan. Monthly plan · Status: Testing · Start with this: Monthly plan $1,500 a month Standard definition only. Up to three held meetings included, then $500 each. Pay per intent · Status: Testing · Start with this: Pay per intent Price set in your plan A reply, in the prospect's own words, from a person inside your definition, that asks for a next step. Pay per signup · Status: Testing · Start with this: Pay per signup Price set in your plan A new account on your product, created by a person Dylan contacted, inside the attribution window in your plan. Pay per qualified opportunity · Status: Testing · Start with this: Pay per qualified opportunity Price set in your plan A held meeting that your meeting owner confirms as a qualified opportunity, against criteria you wrote before launch. Dylan on your inbound · Status: Testing · Start with this: Dylan on your inbound Price set in your plan A held meeting that Dylan booked from one of your inbound leads, with a person inside your definition. Dylan for partners, wholesale · Status: By application · Start with this: Dylan for partners, wholesale Price set in your partner plan A held meeting delivered to one of your clients, under that client's definition, billed to you at a wholesale price set in your partner plan. Worked out from your numbers only. It is not a forecast of what Dylan will book; your plan from a person at Belkins says what fits. Join the waitlist The formula ### How this is worked out Deals you need = your target, times the part from booked meetings, divided by your average deal. Held meetings you need = deals you need divided by your win rate, rounded up. A month is your target divided by the months in its period. In two steps, the win rate is meeting to opportunity times opportunity to won. Each way to pay is priced at that count of held meetings a month, from the prices on the pricing page. --- # Page: SDR cost calculator URL: https://meetdylan.ai/tools/sdr-cost-calculator Free tool ## What a held meeting costs you with SDRs, next to Dylan. Put in your SDR pay, tools and the meetings your team holds each month. See your cost per held meeting next to Dylan's price. ### Your numbers ### Your cost per held meeting Your browser is not running scripts, so the numbers cannot be worked out on this page. The formula below gives the same result. See the formula #### Your SDR team Pay Tools Total Held meetings Cost per held meeting #### Dylan, per held meeting and on each way to pay The way to pay you would start with, if you know Lite, per held meeting · Status: Live · Start with this: Lite, per held meeting $250 each Per held meeting. Deposit $750, three meetings of credit. Standard, per held meeting · Status: Live · Start with this: Standard, per held meeting $500 each Per held meeting. Deposit $1,500, three meetings of credit. Enterprise, per held meeting · Status: Live · Start with this: Enterprise, per held meeting Quoted Enterprise is quoted, from $900 per held meeting. The price comes in your plan. Monthly plan · Status: Testing · Start with this: Monthly plan $1,500 a month Standard definition only. Up to three held meetings included, then $500 each. Pay per intent · Status: Testing · Start with this: Pay per intent Price set in your plan A reply, in the prospect's own words, from a person inside your definition, that asks for a next step. Pay per signup · Status: Testing · Start with this: Pay per signup Price set in your plan A new account on your product, created by a person Dylan contacted, inside the attribution window in your plan. Pay per qualified opportunity · Status: Testing · Start with this: Pay per qualified opportunity Price set in your plan A held meeting that your meeting owner confirms as a qualified opportunity, against criteria you wrote before launch. Dylan on your inbound · Status: Testing · Start with this: Dylan on your inbound Price set in your plan A held meeting that Dylan booked from one of your inbound leads, with a person inside your definition. Dylan for partners, wholesale · Status: By application · Start with this: Dylan for partners, wholesale Price set in your partner plan A held meeting delivered to one of your clients, under that client's definition, billed to you at a wholesale price set in your partner plan. Your held meetings this month This compares cost at the same number of held meetings. It is not a promise of how many meetings Dylan books, and it leaves out what your SDRs do besides booking meetings. Join the waitlist The formula ### How this is worked out Your monthly cost = SDRs times yearly pay (salary plus commission) divided by 12, plus taxes and benefits as a share of that pay, plus tools for each SDR, plus other costs. Your cost per held meeting = that monthly cost divided by your held meetings. If you only know booked meetings, held meetings are booked meetings times your show rate. Dylan's side is his price per held meeting times the same count, rounded to whole meetings, because he bills whole meetings. --- # Page: Deliverability check URL: https://meetdylan.ai/tools/deliverability-check Free tool ## Check a domain's email setup. Type a domain. We look up its MX, SPF, DKIM and DMARC records in public DNS, explain each one in plain words and show the fix. Works for your domain or for an account you plan to email. Powered by Folderly ### What this check does not tell you - This check reads public DNS records. It does not send an email and cannot see one you sent. - It does not predict inbox placement or spam folder rates. - It does not check sender reputation or blocklists. - It does not see your bounce (Return-Path) domain, so an SPF record there is not checked. - It counts the DNS lookups of a, mx and exists in SPF but does not resolve them. - It finds DKIM keys only at the selectors listed. - Whether a BIMI logo shows is up to each mailbox provider. To test where your emails land, try Folderly's inbox placement test. To check the words in a draft, try Folderly's spam words checker. ### Cold email without risking your domain. Dylan writes from his own warmed domains and mailboxes, with a separate slice for each client. Your domain never sends a cold email. Powered by Folderly Join the waitlist ### How to read this #### MX MX records tell other servers where to deliver mail for a domain. Without them, replies to anyone at the domain can be lost. The host names often show which provider or secure email gateway receives the mail. MX in the glossary #### SPF SPF lists the servers that may send email as a domain. There must be one record, and it may use at most 10 DNS lookups; past 10, SPF fails as an error. SPF in the glossary #### DKIM DKIM is a key in DNS that receivers use to check a message's signature. Keys sit at names called selectors, which cannot be listed from DNS, so we try the common ones and any you add. DKIM in the glossary #### DMARC DMARC tells receivers what to do with mail that fails SPF and DKIM: p=none watches, p=quarantine sends it to spam, p=reject refuses it. Its rua address receives daily reports that show who sends as the domain. DMARC in the glossary --- # Page: Cold email grader URL: https://meetdylan.ai/tools/cold-email-grader Free tool ## Grade a cold email against Dylan's rules. Paste a first email. The grader checks it against the nine rules Dylan writes by and marks every line it finds. It runs in this browser: what you paste is not sent anywhere. Stays on this device ### Your score Your score and the fixes show here. The rubric ### The nine rules it checks. Each rule is one the site already states, quoted from where it says it. The weights add up to 100. #### Rule 1: Who is writing, and for whom, in the first line 20 points “Every first email Dylan sends says, in its opening line, that he is an AI agent and which company he works for.” From an AI agent: the first sentence says it is an AI and names the company. From a person: your name and your company in the first two sentences. Why: How Dylan writes: the voice rules · AI disclosure in cold email #### Rule 2: A reason to write to this person, now 20 points “…a reason that belongs to this person, this month: a new site, a new leader, a new market.” A reason (because, noticed, just opened) next to a detail about this reader in the first three sentences. A line that could go to anyone costs half; an empty merge field costs all of it. Why: What survived the AI SDR hype #### Rule 3: One small ask 15 points “One small ask” Exactly one question or request gets full marks, two get half. Dylan's example first email asks one question. The way-out line never counts as an ask. Why: A first email, line by line #### Rule 4: An obvious way to say no 15 points “Short, plain sentences, a specific reason to write, and an obvious way out.” A line like: If not, reply "no" and I won't write again. An unsubscribe or opt out line counts too. Why: A first email, line by line #### Rule 5: Short enough to judge at a glance 5 points “Five sentences carry four things: who is writing, for whom, why this person now, and how to say no. A stranger can judge it at a glance.” Up to 90 words gets full marks, 91 to 150 half, more none. A sentence over 30 words halves it. The greeting line and the signature are not counted. Why: A first email, line by line #### Rule 6: Plain: no attachments, few links, no images 10 points “Write plain emails: no attachments, few links, no tracking pixels.” 0 or 1 link gets full marks, 2 half, more none. An attachment, an image or a tracking pixel: none. Images and hidden links are seen only when you paste from an email app. Why: Cold email deliverability in 2026 · Powered by Folderly #### Rule 7: A subject line a person would type 5 points “Subject lines are lowercase. The way a person types them. No fake "Re:" pretending to continue a conversation.” Lowercase gets full marks, one or two capitalized words half. Re:, Fwd:, an exclamation mark or Title Case: none. Short acronyms like AI or CRM are fine. No subject: not graded. Why: How Dylan writes: the voice rules #### Rule 8: Plain words, no hype, no guarantees 5 points “When a sentence sells instead of describes, cut it.” The words the site cuts (revolutionary, seamless, AI-powered and the rest) and claims like "guaranteed" or "risk-free". One costs half; two or more cost all of it. Why: The design page: voice #### Rule 9: No fake follow-up 5 points “…no "just following up on my last note" when there was no last note.” Phrases like "just following up", "circling back" or "bumping this" in a first email. One also holds the score at 59. Why: How Dylan writes: the voice rules The weights and the length lines are this grader's own, set from Dylan's example first email (63 words, five sentences). They are not a benchmark. ### What this grader cannot see - Whose domain sends, warm-up, sending caps, send windows, SPF, DKIM and DMARC. They are not in the text of an email. Check a domain's records - Whether a name is real. Dylan's rule is never a fake name, never a fake person. Text cannot show it. - The From line. You paste the body, not the headers. - First person and American spelling. That is Dylan's own voice, not a rule for every writer. - Whether the reason is true, and whether the offer fits. Only the sender can know. - The law. The grader gives no legal verdict on CAN-SPAM or the EU AI Act. The post on AI disclosure covers both, and it is not legal advice either. AI disclosure in cold email ### What it never claims - No reply, open or meeting forecast, and no inbox test. The score says how closely an email follows Dylan's rules, nothing else. - No comparison with other emails. There is no data behind one. - No AI detection. Who sends it is your own answer; the grader never guesses who wrote the text. ### Start from a template Cold email templates written by the same rules, each with an example you can grade here. - Cold email templates - Meeting request template - Follow-up email templates - Cold email subject lines ### Want Dylan to write the first email for you? Tell Dylan your website and who you want to meet. Your plan shows the first email he would send, and nothing is sent without your approval. Join the waitlist Already know your definition? Send the full brief --- # Page: Resources URL: https://meetdylan.ai/resources Resources ## Read, check, then brief Dylan. The posts, the docs and the tools from the team that builds Dylan, in one place. The buyer's guide ### The AI SDR buyer's guide All eight posts in one PDF. 39 pages · PDF, 0.8 MB · Edition of 5 October 2026 Get the guide ### Free tools Free tools, in full #### Pipeline calculator Your quota, deal size and win rate in. The held meetings you need each month out, priced in every way to pay. #### SDR cost calculator Your SDR pay, tools and held meetings in. Your cost per held meeting out, next to Dylan's price. #### Deliverability check Type a domain. We look up its MX, SPF, DKIM and DMARC records in public DNS, explain each one and show the fix. Powered by Folderly #### Cold email grader Paste a first cold email and see which of Dylan's nine rules it meets, with a fix for each. ### From the blog All posts · RSS feed 5 October 2026 · 4 min read #### Agents judge, people approve, code protects: how Dylan is built How Dylan splits the work: AI agents make the judgment calls, people approve what goes out, and plain code enforces the rules that must never bend. 5 October 2026 · 4 min read #### The AI SDR hype is over. Here is what actually survived AI SDRs promised to replace sales teams. Most early rollouts disappointed. What survived: proven playbooks, signals, people at decision points, inbound. 5 October 2026 · 4 min read #### Cold email deliverability in 2026: the rules that matter for B2B Gmail's bulk sender rules get the headlines, but B2B cold email is decided by corporate gateways, Microsoft tenant limits and new-domain checks. ### Docs How working with Dylan goes, one topic at a time. #### Start here - Overview · What Dylan is, how he works today and where each topic lives. - Getting started · The brief, the plan, approvals, your calendar, billing and the deposit, in order. #### Concepts - All concepts · One short page for each rule that pricing and approvals depend on. - Held meetings · What Dylan bills by default, and the definition you write before anything is sent. - Approvals · What waits for your yes, and what Dylan does on his own. - Deposits and credits · Three meetings of credit up front, drawn down by held meetings. - Disputes · The dispute window, what a good dispute points at, and credit. - The stop rule · When the replies do not come, Dylan pauses and proposes a new angle. - Pause and stop · Pausing, what happens to credit, and the stops Dylan makes himself. - Do-not-contact list · The companies Dylan never writes to for you, and when he checks. - AI disclosure · Dylan says he is an AI agent, in the first line of every first email. #### Sending and recipients - Deliverability · His own warmed domains and mailboxes, and why your domain stays out. - Opt-outs and rights · How recipients stop Dylan, and what they can ask of us. ### Words and answers - Glossary · 51 terms · Each term once, in the words the rest of the site uses. Follow a link for the full rule. - FAQ · 11 questions · Short answers before you brief Dylan. The plan itself answers the rest. #### From the glossary - What is an SDR? - What is a BDR? - SDR vs BDR: what is the difference? - What is outbound sales? - What is appointment setting? - What is a sales quota? - What is pipeline coverage? - SQL vs MQL: what is the difference? - What is a held meeting? - What is an ICP in sales? - What is SPF? - What is DKIM? - What is DMARC? - What is email warm-up? - What is CAN-SPAM? ### Watch The 42-second film · Watch Dylan book a meeting ### Changelog What changed on meetdylan.ai · Dated changes you can see on the site, newest first. ### Templates and comparisons - Cold email templates - Compare - Dylan vs hiring an SDR - Dylan vs an agency retainer - Dylan vs AI SDR software ### Get on Dylan's calendar. Tell Dylan, our AI agent, who you sell to. A person at Belkins reads every entry and picks teams by fit. We invite 10 teams every two weeks. You approve the plan and pay per held meeting, or on a plan we are testing. Join the waitlist Already know your definition? Send the full brief --- # Page: The buyer's guide URL: https://meetdylan.ai/resources/buyers-guide Free guide ## The AI SDR buyer's guide Every post from the Dylan blog in one designed PDF: what survived the AI SDR hype, how to brief one, small markets, deliverability, AI disclosure, held meetings and how they are billed. 39 pages · PDF, 0.8 MB · Edition of 5 October 2026 ### Get the PDF. The download starts on this page. We email you the link only if you ask. The first page. Every chapter is also on the blog. Contents ### What is inside #### Chapter 1: The AI SDR hype is over. Here is what actually survived AI SDRs promised to replace sales teams. Most early rollouts disappointed. What survived: proven playbooks, signals, people at decision points, inbound. 4 min read #### Chapter 2: How to brief an AI SDR so it books the right meetings A brief decides who gets emailed, what they read and which meetings count. The seven inputs that matter, and why to edit a draft instead of writing one. 4 min read #### Chapter 3: Enterprise outbound math: your market is a pond, not an ocean Only 1,138 US companies have 10,000+ employees. The outbound math for small markets, why precision beats volume, and what to do when the list runs out. 4 min read #### Chapter 4: Cold email deliverability in 2026: the rules that matter for B2B Gmail's bulk sender rules get the headlines, but B2B cold email is decided by corporate gateways, Microsoft tenant limits and new-domain checks. 4 min read #### Chapter 5: AI disclosure in cold email: why Dylan says he is an AI Every first email from Dylan says he is an AI agent and who he works for. Why we disclose, what the EU AI Act and CAN-SPAM say, and how to stop him. 4 min read #### Chapter 6: What counts as a held meeting, and what never gets billed Booked, held and qualified are three different meetings. How Dylan defines a held meeting, what is never billed, and how disputes and the deposit work. 4 min read #### Chapter 7: Pay per meeting: why Dylan charges only for meetings that happen Retainers, seats and per-lead pricing leave you holding the risk. Why Dylan charges per held meeting instead, and where outcome pricing can go wrong. 5 min read #### Chapter 8: Agents judge, people approve, code protects: how Dylan is built How Dylan splits the work: AI agents make the judgment calls, people approve what goes out, and plain code enforces the rules that must never bend. 4 min read 33 minutes of reading in all, across eight chapters. ### Get on Dylan's calendar. Tell Dylan, our AI agent, who you sell to. A person at Belkins reads every entry and picks teams by fit. We invite 10 teams every two weeks. You approve the plan and pay per held meeting, or on a plan we are testing. Join the waitlist Already know your definition? Send the full brief --- # Page: Glossary URL: https://meetdylan.ai/glossary Glossary ## The words of outbound, defined once. Sales roles, pipeline math, sending and the words Dylan's pricing depends on, each in plain words. The longer terms have a page of their own. 51 terms in 6 topics. ### Sales roles and pipeline 12 terms #### Appointment setting Booking first sales meetings with prospects who fit, so the people who sell spend their time in calls instead of finding them. - Page · Pricing - Blog · What counts as a held meeting, and what never gets billed - Blog · Pay per meeting: why Dylan charges only for meetings that happen - Glossary · Read more about Appointment setting Related: Held meeting, SDR, Outbound sales, No-show #### Average deal size Also: Deal size The average value of a won deal. Your target divided by it gives the number of deals you need. - Free tool · Pipeline calculator Related: Sales quota, Win rate #### BDR Also: Business development representative A business development representative: a seller who starts conversations with companies that have not shown interest yet, and books first meetings. - Page · How it works - Free tool · SDR cost calculator - Blog · Enterprise outbound math: your market is a pond, not an ocean - Glossary · Read more about BDR Related: SDR, SDR vs BDR, Outbound sales, Appointment setting #### MQL Also: Marketing qualified lead Marketing qualified lead: a lead that has shown interest and that marketing judges likely to become a customer, from criteria set in advance, but not ready to buy yet. - Glossary · SQL vs MQL Related: SQL, SQL vs MQL #### Outbound sales Also: Outbound Selling where the seller starts the conversation, usually by cold email or cold call, with companies that did not ask to be contacted. - Page · How it works - Blog · Cold email deliverability in 2026: the rules that matter for B2B - Blog · Enterprise outbound math: your market is a pond, not an ocean - Glossary · Read more about Outbound sales Related: SDR, BDR, Appointment setting, ICP, CAN-SPAM #### Pipeline coverage Also: Pipeline coverage ratio Open pipeline divided by the quota it has to cover in the same period. It tells you whether there is enough in the funnel to hit the number. - Free tool · Pipeline calculator - Blog · Enterprise outbound math: your market is a pond, not an ocean - Glossary · Read more about Pipeline coverage Related: Sales quota, Win rate, SQL vs MQL, Held meeting #### Sales quota Also: Quota A measurable goal a seller or a team is expected to hit in a set period, usually counted in revenue, deals closed or sales activities. - Free tool · Pipeline calculator - Glossary · Read more about Sales quota Related: Pipeline coverage, Win rate, Average deal size, Held meeting #### SDR Also: Sales development representative A sales development representative: the person who finds and qualifies prospects and books first meetings for the people who close deals. - Free tool · SDR cost calculator - Page · How it works - Blog · How to brief an AI SDR so it books the right meetings - Blog · The AI SDR hype is over. Here is what actually survived - Glossary · Read more about SDR Related: BDR, SDR vs BDR, Outbound sales, ICP, Held meeting #### SDR vs BDR Where a company splits the titles, SDRs qualify inbound leads and BDRs create outbound pipeline. Many companies use both titles for the same job. - Free tool · SDR cost calculator - Blog · The AI SDR hype is over. Here is what actually survived - Blog · Pay per meeting: why Dylan charges only for meetings that happen - Glossary · Read more about SDR vs BDR Related: SDR, BDR, Outbound sales, SQL vs MQL #### SQL Also: Sales qualified lead Sales qualified lead: a lead interested enough to move into the sales process and ready to talk to a seller. - Glossary · SQL vs MQL Related: MQL, SQL vs MQL, Qualified opportunity #### SQL vs MQL Also: MQL vs SQL An MQL is a lead marketing judges likely to become a customer. An SQL is a lead ready to move into the sales process and talk to sales. - Ways to pay · Pay per intent - Ways to pay · Pay per qualified opportunity - Blog · The AI SDR hype is over. Here is what actually survived - Glossary · Read more about SQL vs MQL Related: MQL, SQL, Intent, Qualified opportunity, Pipeline coverage #### Win rate The share of your opportunities, or of your first meetings, that end in a won deal. It decides how many meetings and how much pipeline a quota needs. - Free tool · Pipeline calculator Related: Pipeline coverage, Sales quota, Average deal size ### Meetings and billing 12 terms #### Booked meeting A time on a calendar. It becomes a held meeting only when the call takes place with someone inside your definition. - Docs · What counts Related: Held meeting, No-show #### Credit What your deposit becomes. Each held meeting draws it down, disputes come back as credit, and unused credit stays on your account. - Docs · How credit is used Related: Deposit, Dispute window, Pause #### Deposit To start, you prepay three meetings as credit at your tier's price. Each held meeting draws it down. No meeting in 60 days? Your deposit comes back. - Docs · Deposits and credits - Page · Pricing Related: Credit, Stop rule #### Dispute window If you think a billed meeting should not have been, you have 72 hours after it to dispute. Silence confirms. Disputes come back as credit. - Docs · Disputes Related: Held meeting, Credit #### Duplicate The same meeting booked twice. It is never billed twice. - Docs · What is never billed Related: Held meeting, Dispute window #### Held meeting Someone who matches your brief's meeting definition joins a call Dylan booked, with your meeting owner. A held meeting is what Dylan bills by default; the other ways to pay are tests. - Docs · Held meetings - Blog · What counts as a held meeting, and what never gets billed - Blog · Pay per meeting: why Dylan charges only for meetings that happen - Page · Pricing - Glossary · Read more about Held meeting Related: Booked meeting, Qualified meeting, Meeting definition, No-show, Dispute window, Appointment setting #### Meeting definition The titles, company sizes and regions that count, set before anything is sent. It is also the targeting rule: Dylan uses it to decide who to write to. - Docs · Your meeting definition Related: ICP, Held meeting, Meeting owner #### Meeting owner The person whose calendar Dylan books into and who runs the call. - Docs · Meetings on your calendar Related: Meeting definition, Held meeting #### No-show A booked meeting the person does not join. You pay nothing, and Dylan rebooks. - Docs · What is never billed Related: Booked meeting, Held meeting #### Pause Pause any time. Unused credit stays on your account. - Docs · Pause and stop Related: Credit, Stop rule #### Qualified meeting A held call with someone who fits what you agreed to in advance. Dylan's held meeting is the strict version: held and qualified, or not billed at all. - Docs · What counts Related: Held meeting, Qualified opportunity #### Stop rule If 1,000 contacts bring no positive reply, Dylan pauses, tells you what he heard and proposes a new angle. Approve it, or leave with your deposit. - Docs · The stop rule Related: Angle, Deposit ### Ways to pay 6 terms #### Attribution window The time after Dylan contacts someone in which their signup counts. It is written into your plan in advance: contacted by Dylan inside the window counts, whatever the last click. - Ways to pay · Pay per signup Related: Signup #### Intent A reply, in the prospect's own words, from a person inside your definition, that asks for a next step. You read it before you pay. - Ways to pay · Pay per intent Related: Qualified opportunity, Signup #### Monthly plan $1,500 a month, up to 3 held meetings included, then $500 per held meeting. Same held-meeting definition, same 72-hour dispute window. In testing. Unused included meetings roll over one month. - Ways to pay · Dylan on a monthly plan Related: Held meeting, Dispute window #### Partner plan (wholesale) Also: Wholesale A held meeting delivered to one of your clients, under that client's definition, billed to you at a wholesale price set in your partner plan. By application. Not open yet. The terms are set in your partner plan. - Ways to pay · Dylan for partners, wholesale Related: Sending slice, Held meeting #### Qualified opportunity A held meeting that your meeting owner confirms as a qualified opportunity, against criteria you wrote before launch. Silence confirms. - Ways to pay · Pay per qualified opportunity Related: Qualified meeting, Intent #### Signup A new account on your product, created by a person Dylan contacted, inside the attribution window in your plan. - Ways to pay · Pay per signup Related: Attribution window, Intent ### Your brief 7 terms #### Angle A new claim, a new reason or a new tone in the emails. Each angle is a new promise in your name, so you approve its first emails. - Docs · What you approve Related: Approvals, Stop rule #### Approvals Nothing goes out until you say yes. You approve your meeting definition, the plan, the first emails and the first emails of every new angle. - Docs · Approvals Related: Plan, Angle #### Brief What you tell Dylan: your company's website, one line about what you sell, who you want to meet (functions, titles, company sizes and regions) and any companies Dylan must never contact. He drafts the rest; you correct it. - Docs · The brief - Blog · How to brief an AI SDR so it books the right meetings Related: Plan, Meeting definition, ICP, Value proposition, Do-not-contact list #### Do-not-contact list The companies Dylan must never contact for you. He never writes to them, and they are never billed. He checks the list when he builds the plan and again as each email is sent. - Docs · Do-not-contact list Related: Opt-out, Brief #### ICP Also: Ideal customer profile Ideal customer profile: the companies (industry, size, region) and the people (function and seniority) you want to meet. In Dylan's brief it is the "who counts" part of your meeting definition. - Docs · Your meeting definition - Blog · How to brief an AI SDR so it books the right meetings - Page · Join the waitlist - Glossary · Read more about ICP Related: Meeting definition, Brief, SDR, Outbound sales, Held meeting #### Plan How many companies fit, ten real examples, the first email and the price. A person at Belkins reviews your plan and emails it within one business day. - Docs · The plan - Page · Example quote Related: Brief, Approvals #### Value proposition Why customers pick you over the alternative, in one line. - Page · Join the waitlist - Blog · How to brief an AI SDR so it books the right meetings Related: Brief, ICP ### Sending and deliverability 10 terms #### Bulk sender Google's term for anyone who sends "close to 5,000 messages or more to personal Gmail accounts within a 24-hour period". Its rules cover personal Gmail accounts, not Google Workspace. - Blog · Cold email deliverability in 2026: the rules that matter for B2B Related: SPF, DKIM, DMARC #### DKIM A signature on each message that lets the receiver check it came from your domain unchanged. - Free tool · Deliverability check - Blog · Cold email deliverability in 2026: the rules that matter for B2B - Glossary · Read more about DKIM Check your domain · Powered by Folderly Related: SPF, DMARC, MX record #### DMARC Ties SPF and DKIM to your From domain and tells receivers what to do when they fail. - Free tool · Deliverability check - Blog · Cold email deliverability in 2026: the rules that matter for B2B - Glossary · Read more about DMARC Check your domain · Powered by Folderly Related: SPF, DKIM, Bulk sender #### MX record The DNS record that names the servers that receive a domain's email. An MX lookup shows in seconds which gateway a company uses. - Blog · Cold email deliverability in 2026: the rules that matter for B2B Check your domain · Powered by Folderly Related: Secure email gateway, SPF #### Quarantine Where a gateway puts suspicious mail instead of rejecting it. Your sending tool logs a successful delivery, and the recipient never sees the email unless someone in IT releases it. - Blog · Cold email deliverability in 2026: the rules that matter for B2B Related: Secure email gateway, Sender reputation #### Secure email gateway Also: SEG A filter many companies put in front of Microsoft 365 or Google Workspace. It checks the sender's reputation, scans every link, opens attachments in a sandbox and looks for impersonation. - Blog · Cold email deliverability in 2026: the rules that matter for B2B Related: Quarantine, MX record #### Sender reputation How far receivers trust a sending domain or IP. A secure email gateway checks it before a message reaches anyone, and a new domain starts with none. - Blog · Cold email deliverability in 2026: the rules that matter for B2B Related: Warm-up, Secure email gateway, Quarantine #### Sending slice The part of Dylan's own warmed domains and mailboxes kept for one client. Your domain never sends a cold email. - Docs · Deliverability Related: Warm-up, Partner plan (wholesale) #### SPF A DNS record that lists who may send email for your domain. Every gatekeeper checks it. - Free tool · Deliverability check - Blog · Cold email deliverability in 2026: the rules that matter for B2B - Glossary · Read more about SPF Check your domain · Powered by Folderly Related: DKIM, DMARC, MX record, Warm-up #### Warm-up Also: Email warm-up Building a new domain's sending volume slowly, with recipients who engage, before any campaign. Dylan writes from his own warmed domains and mailboxes, so there is no warm-up on your side. - Docs · Deliverability - Blog · Cold email deliverability in 2026: the rules that matter for B2B - Glossary · Read more about Warm-up Related: Sending slice, Bulk sender, SPF, DMARC, Sender reputation ### Recipients and trust 4 terms #### AI disclosure Every first email Dylan sends says, in its opening line, that he is an AI agent and which company he works for. - Docs · AI disclosure - Blog · AI disclosure in cold email: why Dylan says he is an AI Related: Opt-out, Stop on reply #### CAN-SPAM Also: CAN-SPAM Act The US law for commercial email, business-to-business email included: honest headers and subject lines, a postal address, and an opt-out honored within 10 business days. - Docs · Opt-outs and rights - Blog · AI disclosure in cold email: why Dylan says he is an AI - Glossary · Read more about CAN-SPAM Related: Opt-out, AI disclosure, Outbound sales #### Opt-out When someone asks Dylan to stop, the request is honored for every client Dylan works for. It can take up to 2 business days to reach every campaign. - Docs · Opt-outs and rights - Page · If Dylan emailed you Related: Do-not-contact list, Stop on reply #### Stop on reply The moment a reply is read, every further scheduled email to that person stops, by rule, before any AI sees it. - Docs · A reply stops sending to that person Related: Opt-out, AI disclosure ### All terms, A to Z #### A - AI disclosure - Angle - Appointment setting - Approvals - Attribution window - Average deal size #### B - BDR - Booked meeting - Brief - Bulk sender #### C - CAN-SPAM - Credit #### D - Deposit - Dispute window - DKIM - DMARC - Do-not-contact list - Duplicate #### H - Held meeting #### I - ICP - Intent #### M - Meeting definition - Meeting owner - Monthly plan - MQL - MX record #### N - No-show #### O - Opt-out - Outbound sales #### P - Partner plan (wholesale) - Pause - Pipeline coverage - Plan #### Q - Qualified meeting - Qualified opportunity - Quarantine #### S - Sales quota - SDR - SDR vs BDR - Secure email gateway - Sender reputation - Sending slice - Signup - SPF - SQL - SQL vs MQL - Stop on reply - Stop rule #### V - Value proposition #### W - Warm-up - Win rate ### Get on Dylan's calendar. Tell Dylan, our AI agent, who you sell to. A person at Belkins reads every entry and picks teams by fit. We invite 10 teams every two weeks. You approve the plan and pay per held meeting, or on a plan we are testing. Join the waitlist Already know your definition? Send the full brief --- # Page: FAQ URL: https://meetdylan.ai/faq Questions ## Before you brief him. Short answers. The plan itself answers the rest. 15:00 · What counts as a held meeting? Someone who matches your brief's meeting definition joins a call Dylan booked, with your meeting owner. No-shows, people on your do-not-contact list, duplicates and anyone outside the definition are not billed. 15:05 · Whose name is on the emails? Dylan's. He writes as an AI agent working for you, from his own domains. Your domain never sends a cold email. 15:10 · Do I need mailboxes, domains or a sequencer? No. Dylan brings his own, already warm, with a separate slice for each client. 15:15 · What if my market is too small? The plan tells you before you pay. Sometimes the answer is no, and he says so. 15:20 · Can I bring my own leads? Bring target companies. Contact lists are re-verified and may be refused, to protect the shared sending. 15:25 · Which channels and regions? Email, from Dylan's own mailboxes. US targets first. 15:30 · Does Dylan make phone calls? No. Dylan works by email today. If your buyers answer the phone, ask about adding Belkins callers to your plan. 15:35 · What happens with replies? Dylan answers routine ones (scheduling, questions your brief answers) and hands you anything about pricing, legal or complaints. 15:40 · What if it doesn't work? If 1,000 contacts bring no positive reply, Dylan pauses, tells you what he heard and proposes a new angle. Approve it, or leave with your deposit. And if no meeting is held in 60 days, the deposit comes back. 15:45 · Can I stop? Pause any time. Unused credit stays on your account. 15:50 · Is there a monthly plan? We are testing one with a small group: $1,500 a month, up to 3 held meetings included, then $500 per held meeting. Unused included meetings roll over one month. Month to month. Cancel any time before the next billing date. ### Get on Dylan's calendar. Tell Dylan, our AI agent, who you sell to. A person at Belkins reads every entry and picks teams by fit. We invite 10 teams every two weeks. You approve the plan and pay per held meeting, or on a plan we are testing. Join the waitlist Already know your definition? Send the full brief --- # Page: Trusted partners URL: https://meetdylan.ai/partners Trusted partners ## Who stands behind Dylan. Dylan is an AI agent built by Belkins. His deliverability is powered by Folderly. Builds Dylan ### Belkins The B2B lead generation agency behind Dylan. Outbound since 2017. #### What Belkins does for Dylan - A person at Belkins reviews your plan and emails it within one business day. - Dylan works by email today. If your buyers answer the phone, ask about adding Belkins callers to your plan. - Belkins in figures, with their sources: About. Visit belkins.io Powers Dylan's deliverability ### Folderly AI and email deliverability tools for B2B teams. #### What Folderly does for Dylan - Powered by Folderly: the deliverability check and the rules Dylan sends by. Visit folderly.com ### Looking for the partner plan for agencies? That is a way to pay: Dylan for partners, wholesale. By application. ### Get on Dylan's calendar. Tell Dylan, our AI agent, who you sell to. A person at Belkins reads every entry and picks teams by fit. We invite 10 teams every two weeks. You approve the plan and pay per held meeting, or on a plan we are testing. Join the waitlist Already know your definition? Send the full brief --- # Page: Pay per meeting URL: https://meetdylan.ai/pay-per-meeting Pay per meeting ## Pay per meeting, billed only when the meeting is held. Pay per meeting means you pay for each sales meeting a vendor books, not for its hours, seats or emails. At Dylan it is stricter: you pay only for a held meeting, a call that took place with someone inside the definition you wrote, with your meeting owner on it. No-shows are never billed. ### The short version - You pay per held meeting. A held meeting: someone inside your written definition joins a call Dylan booked, with your meeting owner on it. - Beta prices per held meeting: $250 on Lite, $500 on Standard and from $900 on Enterprise. - Never billed: no-shows (Dylan rebooks), meetings outside your definition, companies on your do-not-contact list and duplicates. - 72 hours to dispute any meeting. Disputes come back as credit. - No meeting in 60 days? Your deposit comes back. ### What does pay per meeting mean? Pay per meeting is a way to buy B2B lead generation: the vendor is paid for each sales meeting it books for you. You may also see it called pay per appointment. You do not pay for the research, the writing or the emails it takes to get there. The catch is the word meeting. In its 2026 guide to appointment setting prices, OutboundPros, an outbound agency, notes that some vendors charge on booked meetings and others only on held ones. Billed on booking, you pay for the calendar invite, whether or not anyone joins. Dylan bills the strict version: a held meeting inside the definition you wrote. The argument for it is in why Dylan charges only for meetings that happen. ### Booked, held or qualified: which meeting do you pay for? Three words get mixed up, and the gap between them is where budgets go. | Meeting | What it is | What Dylan bills | | --- | --- | --- | | Booked meeting | A time on a calendar. | Nothing. A booking alone is never billed. | | Held meeting | A call that took place. | Billed only when the person is inside your definition and your meeting owner is on the call. | | Qualified meeting | A held call with someone who fits what you agreed to in advance. | Billed. Dylan's held meeting is this strict version: held and qualified, or not billed at all. | | Qualified opportunity | A held meeting your meeting owner confirms against criteria you wrote before launch. | Billed only on pay per qualified opportunity, a way to pay we are testing. | No-shows are the main gap between booked and held. OutboundPros puts no-show rates anywhere from 10% to 35%, depending on segment, seniority and booking flow. The full rulebook is in what counts as a held meeting. ### What counts as a held meeting at Dylan? A held meeting: someone inside your written definition joins a call Dylan booked, with your meeting owner on it. You write the meeting definition before anything is sent. A good one has three parts: - Who counts. The companies (industry, size, region) and the people (function and seniority) you want to meet. - Who takes it on your side. Your meeting owner: the person whose calendar Dylan books into and who runs the call. - What the prospect gets. The reason they agreed to meet, in one line. How it is checked: the calendar record plus your meeting owner's 72-hour dispute window; silence confirms. The definition is also the targeting rule, so a loose one fills your calendar with the wrong calls. The held meeting, in the docs. ### What is never billed? - No-shows (Dylan rebooks) - Meetings outside your definition - Companies on your do-not-contact list - Duplicates If the person does not join, you pay nothing, and Dylan rebooks. A meeting with the wrong person is not a held meeting, however pleasant the call. ### How much does a held meeting cost? The price per held meeting is set by who you want to meet, not by how many emails it takes. These are the beta prices: - Lite · Small companies, founder-led buyers, 1 to 200 employees · $250 · Per held meeting. Deposit $750, three meetings of credit. - Standard · Mid-market, directors and VPs, 201 to 1,000 employees · $500 · Per held meeting. Deposit $1,500, three meetings of credit. - Enterprise · VP and C-level, 1,000+ employees · from $900 · Per held meeting, quoted. Deposit: three meetings, at the quoted price. No seats, no price per email. We are also testing a monthly plan with a small group: $1,500 a month. Up to 3 held meetings included. Then $500 per held meeting. See pricing, with a calculator for both. ### How do the deposit and disputes work? To start, you prepay three meetings as credit. Each held meeting draws it down. It is not a fee. No meeting in 60 days? Your deposit comes back. If you think a billed meeting should not have been, you have 72 hours after it to dispute it, and disputes come back as credit. Pause any time; unused credit stays on your account. Deposits and credits has the details. ### How is pay per meeting different from pay per lead? Pay per lead bills for a name: a contact, a form fill or a lead recommended for outreach, depending on the vendor. Between a name and a meeting sits everything hard: finding the right person, writing something worth answering, landing in the inbox, handling the reply and finding a time. Per lead, you pay for every name and carry the misses. Per held meeting, the misses are ours. ### When is pay per meeting the wrong choice? - Your market is very small. If your whole market is a few dozen accounts, you need a relationship plan, not a meeting machine. Dylan's plan tells you before you pay, and sometimes the answer is no. Your market is a pond, not an ocean walks through the math. - You would rather run the first conversation yourself. Then pay for the reply, not the meeting: pay per intent is a way to pay we are testing. - Your inbound leads wait a day for an answer. Fix that first. It is cheaper than any outbound, ours included. ### What other ways to pay is Dylan testing? Pay per held meeting is live and the default. We are testing the others with a small group; see every way to pay. - Dylan on a monthly plan (testing). A monthly fee of $1,500 that covers up to 3 held meetings, then $500 for each held meeting after the 3rd in the same month. Unused included meetings roll over one month. - Pay per intent (testing). A reply, in the prospect's own words, from a person inside your definition, that asks for a next step. - Pay per signup (testing). A new account on your product, created by a person Dylan contacted, inside the attribution window in your plan. - Pay per qualified opportunity (testing). A held meeting that your meeting owner confirms as a qualified opportunity, against criteria you wrote before launch. - Dylan on your inbound (testing). A held meeting that Dylan booked from one of your inbound leads, with a person inside your definition. - Dylan for partners, wholesale (by application). A held meeting delivered to one of your clients, under that client's definition, billed to you at a wholesale price set in your partner plan. Not sure how many held meetings you need? Work it out with the pipeline calculator, or compare your SDR cost per meeting. How the meetings get booked is on AI appointment setter and what an AI SDR does. ### Sources 1. B2B Appointment Setting Pricing in 2026 (OutboundPros, August 2026) outboundpros.io ### Get on Dylan's calendar. Tell Dylan, our AI agent, who you sell to. A person at Belkins reads every entry and picks teams by fit. We invite 10 teams every two weeks. You approve the plan and pay per held meeting, or on a plan we are testing. Join the waitlist Already know your definition? Send the full brief --- # Page: AI SDR URL: https://meetdylan.ai/ai-sdr AI SDR ## What is an AI SDR? An AI SDR, short for AI sales development representative and also called an AI BDR, is AI software that does the outbound part of a sales development rep's job: it finds the right people, writes and sends cold emails, follows up and answers replies to book sales meetings. Dylan is an AI SDR billed per held meeting. ### The short version - An AI SDR does outbound prospecting: finding people, first emails, follow-ups, replies and booking. - It scales what already works. It does not fix a weak offer or a vague list. - Dylan is an AI SDR built by Belkins. He sends from his own mailboxes, says he is an AI in every first email, and sends nothing before you approve. - You pay per held meeting, from $250 on Lite during the beta. No-shows are never billed. ### What does an AI SDR do? The same work a sales development rep does before a meeting, in order: 1. Find the right people. Companies and people who match who you sell to. Dylan's plan shows how many companies fit and ten real examples. 2. Write the first email and the follow-ups. One reason to talk, one small ask and a clear way out. See how Dylan writes. 3. Send them. Paced, from mailboxes and domains that can carry cold email without hurting yours. 4. Answer replies. Routine ones, such as scheduling or questions your brief answers. Anything about pricing, legal or complaints goes to a person. 5. Book the meeting. Into the calendar of the person on your side who takes the call. That part is the job of an AI appointment setter. How Dylan runs each step, and when, is on how it works. ### Is an AI SDR the same as an AI BDR? On this page, yes. It treats AI SDR and AI BDR as one job: outbound prospecting that ends in a booked meeting. With people, some sales teams give SDRs and BDRs different jobs, and others use the two titles as synonyms. This page says AI SDR throughout. ### What does an AI SDR not do? - Run your sales call. The meeting, and everything after it, is yours. A held meeting is the last step Dylan controls. - Answer what a person should. Dylan hands you anything about pricing, legal questions or complaints. - Make phone calls. Dylan works by email today. If your buyers answer the phone, ask about adding Belkins callers to your plan. - Fix what is broken. SaaStr's first lesson after six months of running its own was that AI SDRs "scale what's already working" and cannot fix what is broken. If outbound did not work when people did it, an agent does the wrong thing faster. ### Where did the first AI SDRs go wrong? The first wave sold replacement: software instead of a sales development team, sending without limit and running on its own. Most of it disappointed. - In a SaaStr reader survey in November 2024, 83% said they had not gotten anything from AI SDRs yet, and 3% had generated real revenue from them. - A year later, SaaStr reported 15 to 20 hours a week of people's time managing its five AI SDRs, and wrote that "this is not set-and-forget technology." - It started its agents in draft mode, where the agent suggests and a person approves, and six months in still kept some there for high-value prospects. Each failure treated outbound as a production problem, more emails with fewer people, when it is mostly judgment: who to write to, why now and what to say when they answer. The longer story is in the AI SDR hype is over: what actually survived. ### How is Dylan different from other AI SDRs? - His own mailboxes. Dylan brings his own mailboxes and domains, already warm, with a separate slice for each client. Your domain never sends a cold email. - People approve. You approve the plan and the first emails of every new angle. A person at Belkins reviews your plan and emails it within one business day. - He says he is an AI. Every first email says, in its opening line, that he is an AI agent and which company he works for. See why Dylan says he is an AI. - Replies stop the sequence. The moment a reply is read, every further scheduled email to that person stops, by rule, before any AI sees it. - Paid per held meeting. No seats, no price per email. No meeting in 60 days? Your deposit comes back. See pay per meeting. The rule underneath all five: agents judge, people approve, code protects. How Dylan is built explains it. ### How does Dylan compare with AI SDR software? | Question | Dylan | AI SDR software | | --- | --- | --- | | You pay for | Meetings that happen | Seats, contacts or credits | | Mailboxes and domains | Dylan's own, already warm | You buy and warm them | | If no meetings come | Deposit back after 60 days | You still pay | | Before anything is sent | You approve | Often automatic | | Setup on your side | A few minutes | Integrations and setup | Hiring an SDR and an agency retainer are in the same table on the home page. To put a number on your own team, try the SDR cost calculator. ### What should you ask any AI SDR vendor? 1. Who approves the plan and the first emails before anything is sent? If nobody does, your brand is the test environment. 2. What happens, mechanically, when someone replies "stop"? Listen for a rule in the system, not an instruction to the model. 3. Whose domain sends the emails? If it is yours, a bad month lands on the address your customers and invoices come from. 4. What do you pay if no meetings come? That tells you who carries the risk. 5. Does the agent say it is an AI, and who it works for? If not, ask what happens to your name when a prospect finds out. Before you ask, write down who you want to meet. How to brief an AI SDR lists the inputs that matter, and the buyer's guide has every post in one PDF. ### Sources 1. 83% of You Haven't Gotten AI SDRs to Work Yet (SaaStr, November 2024) saastr.com 2. 6 Months of AI SDRs: What's Worked (SaaStr, November 2025) saastr.com ### Get on Dylan's calendar. Tell Dylan, our AI agent, who you sell to. A person at Belkins reads every entry and picks teams by fit. We invite 10 teams every two weeks. You approve the plan and pay per held meeting, or on a plan we are testing. Join the waitlist Already know your definition? Send the full brief --- # Page: AI appointment setter URL: https://meetdylan.ai/ai-appointment-setter AI appointment setter ## From an interested reply to a held meeting. An AI appointment setter is an AI agent that turns interested replies into booked sales meetings. It answers routine questions, offers times, books the call into your calendar and hands anything sensitive to a person. Dylan does this by email for B2B teams, and by default you pay only when the meeting is held. Replies ### Routine replies he answers. The rest come to you. He answers routine replies himself, such as scheduling or questions your brief answers, and hands you anything about pricing, legal or complaints. When someone replies, every further scheduled email to that person stops the moment the reply is read, by rule, before any AI sees it. Only then does Dylan read it. Example thread: Maya asks what it costs; Dylan hands the pricing question to Harrow Line's team and offers Thursday 10:30 or 14:00 Eastern; Maya picks 10:30; Dylan confirms the booking and says the invite comes from Harrow Line's calendar. ### What does an AI appointment setter do? AI appointment setting is the step between "maybe" and a call on the calendar. With Dylan it goes like this: 1. Reads the reply. The moment a reply is read, every further scheduled email to that person stops, by rule, before any AI sees it. 2. Answers what it may. Routine replies, such as scheduling or questions your brief answers. 3. Hands over what it should not answer. Pricing, legal questions and complaints go to you. 4. Offers times and books. Into the calendar of your meeting owner, the person who takes the call. 5. Counts only what happened. The meeting is billed only once it is held, with someone inside your definition. Finding the people and writing the first emails comes before this. That is the rest of an AI SDR's job, and the whole sequence is on how it works. ### Which replies does Dylan answer, and which come to you? | The reply | Who handles it | | --- | --- | | Yes, or a request for a time | Dylan offers times and books the call with your meeting owner. | | A question your brief answers | Dylan answers it. | | A question about pricing | Handed to you. | | A legal question | Handed to you. | | A complaint | Handed to you. | | Stop, or unsubscribe | Honored for every client Dylan works for. | A stop request can take up to 2 business days to reach every campaign. People who got an email from Dylan can also stop him on if Dylan emailed you. ### How does the booking reach my calendar? Meetings go to your meeting owner: the person whose calendar Dylan books into and who runs the call. You name them in your brief. Connect your meeting owner's real calendar and block the hours they protect. A meeting your own side reschedules is a poor first impression. Meetings on your calendar, in the docs. ### What counts as a held meeting? Someone who matches your brief's meeting definition joins a call Dylan booked, with your meeting owner. You write the definition before anything is sent: the titles, company sizes and regions that count. A booked meeting is a time on a calendar; a held meeting is a call that took place. Dylan bills held meetings only. The held meeting has the rules, and pay per meeting has the prices. ### What happens when someone does not show up? You pay nothing, and Dylan rebooks. No-shows are never billed, and neither are duplicates, meetings outside your definition or companies on your do-not-contact list. If a billed meeting should not have been, you have 72 hours after it to dispute it, and disputes come back as credit. ### Does an AI appointment setter make phone calls? Dylan does not. He works by email today, from his own mailboxes. If your buyers answer the phone, ask about adding Belkins callers to your plan. Belkins, the agency that built Dylan, also runs appointment setting with people. ### Can Dylan book meetings from my inbound leads? We are testing it with a small group: Dylan on your inbound. A held meeting that Dylan booked from one of your inbound leads, with a person inside your definition. Leads he answers and disqualifies, or helps without a meeting, cost nothing. The steps ### What happens, and when. 1. Day 0 #### Brief Dylan Your website, who you sell to and who not to contact. He drafts the rest; you correct it. 2. Day 1 #### Get your plan How many companies fit, ten real examples, the first email and the price. 3. Days 2 to 3 #### Approve the first emails You approve the first emails or ask for changes. Nothing is sent without your approval. 4. Week 1 #### First emails go out Dylan writes, follows up and answers replies. 5. Week by week #### Take the meetings Dylan books meetings into your calendar. You pay per meeting held. ### Get on Dylan's calendar. Tell Dylan who you want to meet and who takes the calls. Nothing is sent without your approval. You approve the plan and pay per held meeting, or on a plan we are testing. Join the waitlist Already know your definition? Send the full brief --- # Page: Cold email templates URL: https://meetdylan.ai/resources/cold-email-templates Cold email templates ## Cold email templates, written by Dylan's rules. A good B2B cold email template says who is writing and for whom, gives one reason to write to this person now, makes one small ask and offers an easy way to say no. Below are six templates in that shape, each with a filled-in example, why it works and what to avoid. Follow-up email templates · Meeting request template · Cold email subject lines · Grade your own email ### Which cold email template should you use? | Your situation | Template | | --- | --- | | You write to someone for the first time, and you have a real reason to write to them now. | The first cold email | | An AI agent writes for your company. The first sentence says so, and names the company. | The first email from an AI agent | | You know this is the right person and the reason is strong, so you ask for a meeting at two real times. | Asking for a meeting | | Your first email got no reply, and you have one new fact worth a second email. | The second email: one new thing | | You have written twice with no reply. This email says it is the last, and it is. | The last email: close the loop | | You have a reason to write to the company, but you are not sure who owns the topic. | Finding the right person | | You need a subject line for any of them. | Cold email subject lines | ### The templates Copy one, fill in every field, and read it once as the person who gets it. Each one opens a filled-in example; the companies and the people in the examples are invented. #### The first cold email When to use it · You write to someone for the first time, and you have a real reason to write to them now. ##### Why it works - The first line says who is writing and for which company, so a stranger can judge the email at a glance. - The reason belongs to this person, this month. It is the one line a merge field cannot fake. - One small ask, so a reply takes one word. - The last line is an obvious way out, and you keep the promise it makes. ##### What not to do - Opening with "I hope this email finds you well" or "I wanted to reach out". Those lines could go to anyone. - Sending it with the reason field empty or vague. Without a reason, it is a mass email with a first name. - Adding a second question, a deck or a row of links. Grade the example Template Subject {{topic}} at {{company}} Hi {{firstName}}, I'm {{yourName}} at {{yourCompany}}. I'm writing because {{reason}}. {{yourCompany}} {{offer}}. Would a short call next week be useful? If not, reply "no" and I won't write again. Best, {{yourName}} See it filled in · Example The first cold email, filled in · Example To Maya, Nordfeld Subject fuel cards at nordfeld Hi Maya, I'm Alex at Harrow Line. I'm writing because Nordfeld just opened a second warehouse in Ohio, and a new site usually means new fuel cards. Harrow Line puts every vehicle on one card with its own spend limit. Would a short call next week be useful? If not, reply "no" and I won't write again. Best, Alex The companies and the people are invented. #### The first email from an AI agent When to use it · An AI agent writes for your company. The first sentence says so, and names the company. ##### Why it works - The disclosure sits in the first line, not in small print under the signature. A disclosure nobody reads is not a disclosure. - It names the company the agent works for, so the reader knows whose brand is on the email. - The rest has the shape of any good first email: a reason, one ask, a way out. ##### What not to do - A human first name and no mention of AI. A disguise fails twice: once for the email, and again for the company named in it. - Putting the disclosure in the signature, where nobody reads it. - A way out that depends on the agent reading the reply correctly. Any reply should stop the next email, by rule. Grade the example Template Subject {{topic}} across your {{place}} From The AI agent, for {{yourCompany}} Hi {{firstName}}, I'm {{yourName}}, an AI agent working with {{yourCompany}}. I'm writing because {{reason}}. {{yourCompany}} {{offer}}. Would a 20-minute review be useful? If not, reply "no" and I won't write again. See it filled in · Example The first email from an AI agent, filled in · Example From Dylan, AI agent for Harrow Line To Maya, Nordfeld Subject fuel across your ohio sites Hi Maya, I'm Dylan, an AI agent working with Harrow Line. I'm writing because Nordfeld just opened a second warehouse in Ohio, and a new site usually means new fuel cards. Harrow Line puts every vehicle on one card with its own spend limit. Would a 20-minute review of your fuel spend be useful? If not, reply "no" and I won't write again. The companies and the people are invented. #### Asking for a meeting When to use it · You know this is the right person and the reason is strong, so you ask for a meeting at two real times. ##### Why it works - Two real times, written the way a calendar shows them: the day, the date, the time and the zone. Saying yes takes one word. - The ask is small and exact: 20 minutes at a named time, not "some time to connect". - The reason comes before the ask, so the meeting has a purpose the reader can see. - It still offers a way to say no. A meeting request without one reads like pressure. ##### What not to do - "Next Thursday at 10.30am-ish?" A loose time makes the reader do the work. - Asking for a meeting and a referral and a reply to a question, all in one email. - Attaching a deck. Plain emails carry no attachments, and a first email should not need one. Grade the example · More on this template Template Subject 20 minutes on {{topic}} Hi {{firstName}}, I'm {{yourName}} at {{yourCompany}}. I'm writing because {{reason}}. {{yourCompany}} {{offer}}. Would {{time1}} or {{time2}} work for 20 minutes? If not, reply "no" and I won't write again. Best, {{yourName}} See it filled in · Example Asking for a meeting, filled in · Example To Maya, Nordfeld Subject 20 minutes on fuel cards Hi Maya, I'm Alex at Harrow Line. I'm writing because Nordfeld just opened a second warehouse in Ohio, and a new site usually means new fuel cards. Harrow Line puts every vehicle on one card with its own spend limit. Would Thursday, Oct 22, 10:30 Eastern or Friday, Oct 23, 14:00 Eastern work for 20 minutes? If not, reply "no" and I won't write again. Best, Alex The companies and the people are invented. #### The second email: one new thing When to use it · Your first email got no reply, and you have one new fact worth a second email. ##### Why it works - It sits in the same thread as your first email, so the reader sees what came before. That is a real follow-up, not a fake Re: on a first email. - It adds one new thing instead of repeating the first email, so there is something new to answer. - It says again who is writing and keeps the way out, because the reader may never have opened the first email. - One question, with an easy answer either way. ##### What not to do - "Just following up" or "circling back" with nothing new to say. - A new subject line that hides that this is the same pitch. - Guilt lines such as "I guess you're busy". Grade the example · More on this template Template Subject {{topic}} at {{company}} Hi {{firstName}}, it's {{yourName}} at {{yourCompany}} again. I'm writing once more because {{reason}}. One thing I left out: {{detail}}. Is this worth a short call, or is the timing wrong? If not, reply "no" and I won't write again. Best, {{yourName}} Send it as a reply to your first email, so the subject and the thread stay the same. See it filled in · Example The second email: one new thing, filled in · Example To Maya, Nordfeld Subject fuel cards at nordfeld Hi Maya, it's Alex at Harrow Line again. I'm writing once more because Nordfeld's Ohio site opens soon, and fuel cards are easier to set up before the first trucks arrive. One thing I left out: each card can be limited to fuel only, so a lost card buys nothing else. Is this worth a short call, or is the timing wrong? If not, reply "no" and I won't write again. Best, Alex The companies and the people are invented. #### The last email: close the loop When to use it · You have written twice with no reply. This email says it is the last, and it is. ##### Why it works - It says this is the last email, and then it is. A promise to stop only counts if you keep it. - It leaves a door open for later instead of pushing for now. - It restates the reason in one line, for a reader who never opened the first two. ##### What not to do - Calling it the last email and then sending another one. - A "breakup" line meant to sting, such as "I'll assume this isn't a priority". - Writing again after a no, from another address or another colleague. Grade the example · More on this template Template Subject {{topic}} at {{company}} Hi {{firstName}}, it's {{yourName}} at {{yourCompany}}, with my last note on this. I wrote because {{reason}}, and I don't want to fill your inbox. Would it be fine if I wrote again in {{month}}? If you'd rather I didn't, reply "no" and I won't write again. Best, {{yourName}} Send it in the same thread as the first two emails. See it filled in · Example The last email: close the loop, filled in · Example To Maya, Nordfeld Subject fuel cards at nordfeld Hi Maya, it's Alex at Harrow Line, with my last note on this. I wrote because Nordfeld just opened a second warehouse in Ohio, and I don't want to fill your inbox. Would it be fine if I wrote again in March? If you'd rather I didn't, reply "no" and I won't write again. Best, Alex The companies and the people are invented. #### Finding the right person When to use it · You have a reason to write to the company, but you are not sure who owns the topic. ##### Why it works - It asks for a name, not a meeting. That is a smaller ask, and it is easy to answer. - It still gives the reason, so whoever it is forwarded to knows why you wrote. - One question and one way out. ##### What not to do - Writing to five people at the same company on the same day. - Pretending someone referred you when nobody did. Grade the example Template Subject who looks after {{topic}}? Hi {{firstName}}, I'm {{yourName}} at {{yourCompany}}. I'm writing because {{reason}}, and I'm not sure who at {{company}} looks after {{topic}}. Is that you, or is there someone better to write to? If not, reply "no" and I won't write again. Best, {{yourName}} See it filled in · Example Finding the right person, filled in · Example To Maya, Nordfeld Subject who looks after fuel cards? Hi Maya, I'm Alex at Harrow Line. I'm writing because Nordfeld just opened a second warehouse in Ohio, and I'm not sure who at Nordfeld looks after fuel cards. Is that you, or is there someone better to write to? If not, reply "no" and I won't write again. Best, Alex The companies and the people are invented. ### What goes in the fields? Fill in every one before you send. An empty field is the first thing a reader sees, and the grader marks it. {{firstName}} Their first name. {{company}} Their company. {{yourName}} Your name, or the AI agent's name if an agent sends it. {{yourCompany}} Your company. {{reason}} Why you write to this person now: a new site, a new leader, a new market. Something true about them. {{offer}} What your company does, in one line and in their terms. {{topic}} What the email is about, in two or three lowercase words. {{detail}} One fact the first email left out. {{time1}} A real time you can meet: the day, the date, the time and the zone. {{time2}} A second real time, on another day. {{month}} When you could write again, if they would like that. {{event}} What just happened at their company, in a few words. {{place}} Where what you sell applies to them: their sites, their region, their team. ### What makes a cold email template work? Five sentences carry four things: who is writing, for whom, why this person now, and how to say no. Every template here keeps that shape: - Who is writing, and for whom, in the first line. From an AI agent, the first sentence says it is an AI. - A reason that belongs to this person, this month: a new site, a new leader, a new market. - One small ask. Two asks make the reader choose; one lets them answer. - An obvious way to say no, and you keep the promise it makes. The rest is restraint: short sentences, a lowercase subject, no hype words, no attachments and few links. How Dylan writes shows one first email line by line. ### What should a cold email never do? - Fake a conversation. No "Re:" on a first email, and no "just following up on my last note" when there was no last note. - Hide who is writing. An AI agent says it is one, in the first line. Why Dylan says he is an AI. - Sell instead of describe. Words like revolutionary, seamless or game-changer, and promises like "guaranteed", get cut. - Carry a payload. Plain emails have no attachments, few links and no tracking pixels. Cold email deliverability in 2026. - Ignore a no. In the United States the FTC's CAN-SPAM guide says subject lines must not deceive and opt-outs must be honored within 10 business days, and the law makes no exception for business-to-business email. This is not legal advice. ### Do these templates come with reply rates? No. We publish no reply rate for any template on this page: we have no data on them, and a template is only as good as the reason you put in it. For numbers on whole sequences, Belkins' 2026 follow-up study reports its own clients' campaigns. Belkins builds Dylan. The cold email grader checks an email against the rules these templates follow. The score is how closely your email follows the rules Dylan writes by. It is not a prediction of replies. ### Sources 1. Sales follow-up statistics in B2B: Belkins' 2026 study (updated 2026-06-26) belkins.io 2. CAN-SPAM Act: A Compliance Guide for Business (FTC) ftc.gov ### Want Dylan to write the first email for you? Tell Dylan your website and who you want to meet. Your plan shows the first email he would send, and nothing is sent without your approval. Join the waitlist Already know your definition? Send the full brief --- # Page: Compare URL: https://meetdylan.ai/compare Compare ## How does Dylan compare with an SDR, an agency or AI SDR software? Most teams get B2B sales meetings one of three ways: they hire an SDR, pay an agency a monthly retainer, or buy AI SDR software. All three bill for effort, so you pay in a month with no meetings. Dylan bills per held meeting. Each page below also says when the other option is the better choice. Side by side ### What do you actually pay for? | Question | Dylan | Hiring an SDR | Agency retainer | AI SDR software | | --- | --- | --- | --- | --- | | You pay for | Meetings that happen | Salary, tools and ramp time | A monthly retainer | Seats, contacts or credits | | Mailboxes and domains | Dylan's own, already warm | You buy and warm them | Often yours | You buy and warm them | | If no meetings come | Deposit back after 60 days | You still pay | You still pay | You still pay | | Before anything is sent | You approve | Depends on the rep | Depends on the agency | Often automatic | | Setup on your side | A few minutes | Hiring and training | Onboarding calls | Integrations and setup | Dylan's column is his beta offer, as the pricing page states it. The other columns are the usual setup in each category, not any one company's. ### Which comparison do you need? - Dylan vs hiring an SDR · Salary, tools and ramp time next to a price per held meeting, and when a person on your team is the better call. - Dylan vs an agency retainer · A monthly fee for a team's time next to a price per held meeting, and when an agency's people and channels fit better. - Dylan vs AI SDR software · A platform your team runs next to an agent you pay per held meeting, and when owning the software fits better. ### Why no pages about named companies? We compare categories, not companies. Vendors change their prices and features faster than a page can keep up, and we would rather not guess at theirs. Any figure on these pages links the public source it comes from. Before you sign with any vendor, including us, ask the five questions at the end of The AI SDR hype is over. ### Get on Dylan's calendar. Tell Dylan, our AI agent, who you sell to. A person at Belkins reads every entry and picks teams by fit. We invite 10 teams every two weeks. You approve the plan and pay per held meeting, or on a plan we are testing. Join the waitlist Already know your definition? Send the full brief --- # Page: Dylan vs hiring an SDR URL: https://meetdylan.ai/compare/hiring-an-sdr Compare · Hiring an SDR ## Should you hire an SDR or brief Dylan? Hire an SDR when you need a person on the phone, at events and inside your team for the long run. Choose Dylan when you want held meetings by email without hiring: he sends from his own warm mailboxes, you approve the plan and the first emails, and you pay per held meeting instead of a salary. Side by side ### How does hiring an SDR compare with Dylan? | Question | Dylan | Hiring an SDR | | --- | --- | --- | | You pay for | Meetings that happen | Salary, tools and ramp time | | Mailboxes and domains | Dylan's own, already warm | You buy and warm them | | If no meetings come | Deposit back after 60 days | You still pay | | Before anything is sent | You approve | Depends on the rep | | Setup on your side | A few minutes | Hiring and training | | Price | $250, $500 or from $900 per held meeting | Your pay and overhead: work it out in the calculator below | | Phone calls and events | No. Email only today | Yes, if you hire for it | | Regions | US targets first | Wherever you hire | | After the first meeting | Your team runs the deal | A rep who can grow into closing | Dylan's column is his beta offer, as the pricing page states it. The SDR column is the usual setup, not any one company's. Calculator ### What does your SDR team cost per held meeting? ### Your numbers ### Your cost per held meeting Your browser is not running scripts, so the numbers cannot be worked out on this page. The formula on the calculator page gives the same result. See the formula #### Your SDR team Pay Tools Total Held meetings Cost per held meeting #### Dylan, per held meeting and on each way to pay The way to pay you would start with, if you know Lite, per held meeting · Status: Live · Start with this: Lite, per held meeting $250 each Per held meeting. Deposit $750, three meetings of credit. Standard, per held meeting · Status: Live · Start with this: Standard, per held meeting $500 each Per held meeting. Deposit $1,500, three meetings of credit. Enterprise, per held meeting · Status: Live · Start with this: Enterprise, per held meeting Quoted Enterprise is quoted, from $900 per held meeting. The price comes in your plan. Monthly plan · Status: Testing · Start with this: Monthly plan $1,500 a month Standard definition only. Up to three held meetings included, then $500 each. Pay per intent · Status: Testing · Start with this: Pay per intent Price set in your plan A reply, in the prospect's own words, from a person inside your definition, that asks for a next step. Pay per signup · Status: Testing · Start with this: Pay per signup Price set in your plan A new account on your product, created by a person Dylan contacted, inside the attribution window in your plan. Pay per qualified opportunity · Status: Testing · Start with this: Pay per qualified opportunity Price set in your plan A held meeting that your meeting owner confirms as a qualified opportunity, against criteria you wrote before launch. Dylan on your inbound · Status: Testing · Start with this: Dylan on your inbound Price set in your plan A held meeting that Dylan booked from one of your inbound leads, with a person inside your definition. Dylan for partners, wholesale · Status: By application · Start with this: Dylan for partners, wholesale Price set in your partner plan A held meeting delivered to one of your clients, under that client's definition, billed to you at a wholesale price set in your partner plan. Your held meetings this month This compares cost at the same number of held meetings. It is not a promise of how many meetings Dylan books, and it leaves out what your SDRs do besides booking meetings. Join the waitlist ### What does an SDR cost? More than the salary. The monthly cost of one SDR usually includes: - Base pay and commission. - Payroll taxes and benefits. - Tools and data: a sequencer, a contact database and the seats that go with them. - Mailboxes and domains for cold email, which need warming before they send. - A manager's time to hire, train and review the work. - The ramp: the time before a new rep books meetings at full pace. You pay all of it in a month with no meetings too. We do not print a salary figure here. Pay depends on the city, the seniority and the commission plan, and your own numbers beat any average. Put them in the calculator above: your pay, tools and held meetings a month give your cost per held meeting, next to Dylan's price. It also has its own page, the SDR cost calculator, with the formula it uses. ### What does Dylan cost instead? Dylan bills per held meeting, at a price set by who you want to meet: - Lite: $250 per held meeting. Small companies, founder-led buyers, 1 to 200 employees. Deposit $750. - Standard: $500 per held meeting. Mid-market, directors and VPs, 201 to 1,000 employees. Deposit $1,500. - Enterprise: from $900 per held meeting, quoted. VP and C-level, 1,000+ employees. Deposit: three meetings. The deposit is credit for your first meetings. No meeting in 60 days? Your deposit comes back. The prices are for the beta; the full terms are on the pricing page. ### When is hiring an SDR the better choice? - Your buyers answer the phone or meet you at events. Dylan works by email today. If you want calls next to his emails, ask about adding Belkins callers to your plan. - Most of your buyers are outside the US. Dylan writes to US targets first. - You are building a sales team. An SDR learns your product, sits in your deal reviews and can grow into a closing role. Dylan books the first meeting and hands it to your team. - Your whole market is a few dozen named accounts. A person who researches each one by hand may suit it better. Dylan's plan tells you if your market is too small before you pay, and sometimes the answer is no. ### When is Dylan the better choice? - You want meetings without a hiring process. The brief takes a few minutes. A person at Belkins reviews your plan and emails it within one business day. The first emails go out in week 1. - You do not want to buy and warm mailboxes. Dylan sends from his own domains, already warm. Your domain never sends a cold email. - You want the seller to carry the misses. You pay per held meeting. Never billed: meetings outside your definition, no-shows, companies on your do-not-contact list. - You want to see every new angle first. Nothing is sent before you approve the plan and the first emails. ### Can you use both? Yes. Keep your SDRs on the calls and the accounts that need a person, and brief Dylan on a segment they do not reach. Put the accounts your SDRs own on Dylan's do-not-contact list: he checks it when he builds the plan and again as each email is sent. Not sure what counts as a held meeting? Read what counts as a held meeting, then why Dylan charges per held meeting. ### The other comparisons All three side by side - Dylan vs an agency retainer · A monthly fee for a team's time next to a price per held meeting, and when an agency's people and channels fit better. - Dylan vs AI SDR software · A platform your team runs next to an agent you pay per held meeting, and when owning the software fits better. ### Get on Dylan's calendar. Tell Dylan, our AI agent, who you sell to. A person at Belkins reads every entry and picks teams by fit. We invite 10 teams every two weeks. You approve the plan and pay per held meeting, or on a plan we are testing. Join the waitlist Already know your definition? Send the full brief --- # Page: Dylan vs an agency retainer URL: https://meetdylan.ai/compare/agency-retainer Compare · Agency retainer ## Should you pay an agency retainer or per held meeting? Pay an agency retainer when you want a team of people running outbound across email, LinkedIn and the phone, and you can carry a monthly fee while it ramps. Choose Dylan when email is enough and you would rather pay per held meeting, with a deposit that comes back if no meeting is held in 60 days. Side by side ### How does an agency retainer compare with Dylan? | Question | Dylan | Agency retainer | | --- | --- | --- | | You pay for | Meetings that happen | A monthly retainer | | Mailboxes and domains | Dylan's own, already warm | Often yours | | If no meetings come | Deposit back after 60 days | You still pay | | Before anything is sent | You approve | Depends on the agency | | Setup on your side | A few minutes | Onboarding calls | | Price | $250, $500 or from $900 per held meeting | $3,000 to $15,000+ a month, in one agency's 2026 guide | | Channels | Email, from his own mailboxes | Often email, LinkedIn and phone | | Who does the work | An AI agent; a person at Belkins reviews your plan | A team of people | | Stopping | Pause any time; unused credit stays yours | Set by the contract | Dylan's column is his beta offer, as the pricing page states it. The agency column is the usual retainer, not any one agency's; the price range is one agency's own, linked. ### What does an agency retainer cost? One agency's 2026 pricing guide puts monthly retainers at $3,000 to $15,000+, per-meeting fees at $250 to $1,500+, and hybrid models that combine a retainer with a fee per meeting (OutboundPros, August 2026). The same guide tells buyers who choose a retainer to expect a 60- to 90-day ramp. These are one agency's ranges, not a market survey. Ask every agency you talk to for its own terms in writing, and ask what counts as a meeting. A retainer pays for a team's time. In the guide's list, that covers ICP and segmentation work, data sourcing, copywriting, sending setup and deliverability monitoring, testing and reporting. You pay for that time in a month with no meetings too. ### What does Dylan cost instead? Dylan does the email part of that work himself and bills only for held meetings, at a price set by who you want to meet: - Lite: $250 per held meeting. Small companies, founder-led buyers, 1 to 200 employees. Deposit $750. - Standard: $500 per held meeting. Mid-market, directors and VPs, 201 to 1,000 employees. Deposit $1,500. - Enterprise: from $900 per held meeting, quoted. VP and C-level, 1,000+ employees. Deposit: three meetings. The deposit is credit for your first meetings. No meeting in 60 days? Your deposit comes back. The prices are for the beta; the full terms are on the pricing page. ### When is an agency the better choice? - You need more channels than email. Agencies often run LinkedIn and calls as well. Dylan works by email today. - Your market is tiny or your offer needs explaining. In the guide's words, per-meeting pricing "works worst when your ICP is tiny, your offer needs education, or your sales cycle is highly consultative." There, a retainer can be the honest deal. - You want an outbound team, not a meeting supplier. The guide says retainers make sense "when you want a team acting like an outsourced outbound function rather than a meeting vendor." - Most of your buyers are outside the US. Dylan writes to US targets first. ### When is Dylan the better choice? - You would rather pay for meetings than for months. Dylan bills per held meeting, and you have 72 hours to dispute any meeting. Never billed: meetings outside your definition, no-shows, companies on your do-not-contact list. - You want the deposit back if nothing happens. If no meeting is held in 60 days, the deposit comes back. - You want your own domain kept out of it. The guide tells buyers to ask who owns inbox setup, domains and deliverability. With Dylan, his own warm domains send, and yours never sends a cold email. - You want to approve before anything is sent. Dylan sends nothing until you approve the plan and the first emails. ### Where does Belkins fit? Belkins, the B2B lead generation agency behind Dylan, runs outbound with people across email, LinkedIn and cold calling (belkins.io). Dylan is Belkins' AI agent. - If you want a team of people and more channels, talk to Belkins. - If you want held meetings by email, billed per meeting, brief Dylan. - If you want Dylan and your buyers answer the phone, ask about adding Belkins callers to your plan. More on how the two work together on Dylan's trusted partners page. Why a held meeting is the unit: why Dylan charges per held meeting. ### Sources 1. B2B Appointment Setting Pricing in 2026: Per Meeting, Retainer, Hybrid, and What "Qualified" Really Costs (OutboundPros, August 2026) outboundpros.io 2. Lead generation and appointment setting services (Belkins) belkins.io ### The other comparisons All three side by side - Dylan vs hiring an SDR · Salary, tools and ramp time next to a price per held meeting, and when a person on your team is the better call. - Dylan vs AI SDR software · A platform your team runs next to an agent you pay per held meeting, and when owning the software fits better. ### Get on Dylan's calendar. Tell Dylan, our AI agent, who you sell to. A person at Belkins reads every entry and picks teams by fit. We invite 10 teams every two weeks. You approve the plan and pay per held meeting, or on a plan we are testing. Join the waitlist Already know your definition? Send the full brief --- # Page: Dylan vs AI SDR software URL: https://meetdylan.ai/compare/ai-sdr-software Compare · AI SDR software ## Should you buy AI SDR software or pay per held meeting? Buy AI SDR software when your team wants to run its own outbound: you pay for the platform, connect your tools, warm your own mailboxes and steer the agent every week. Choose Dylan when you want the outcome instead: he sends from his own mailboxes, you approve the plan and the first emails, and you pay per held meeting. Side by side ### How does AI SDR software compare with Dylan? | Question | Dylan | AI SDR software | | --- | --- | --- | | You pay for | Meetings that happen | Seats, contacts or credits | | Mailboxes and domains | Dylan's own, already warm | You buy and warm them | | If no meetings come | Deposit back after 60 days | You still pay | | Before anything is sent | You approve | Often automatic | | Setup on your side | A few minutes | Integrations and setup | | Price | $250, $500 or from $900 per held meeting | $50,000 to $100,000+ a year per platform, in SaaStr's account | | Your team's time | Approve the plan and the first emails | 15 to 20 hours a week for five agents, at SaaStr | | Who runs it | Dylan; a person at Belkins reviews your plan | Your team | | Control of the settings | You approve; Dylan runs the work | Yours, all of them | | Says it is an AI | In the first line of every first email | Depends on the tool and your settings | Dylan's column is his beta offer, as the pricing page states it. The software column is the usual setup, not any one vendor's; the figures are SaaStr's own, linked. ### What does AI SDR software cost? SaaStr, which runs five AI SDRs of its own, puts effective AI SDRs at $50,000 to $100,000+ a year per specialized platform: typically $60,000 to $70,000 for the annual subscription and $20,000 to $30,000 for training and onboarding (SaaStr). It also notes that some vendors are launching cheaper self-serve versions, so ask each vendor for its own price. The bigger cost is time. SaaStr's team spends 15 to 20 hours a week managing its five agents, and it says so plainly: "This is not set-and-forget technology." Software bills for seats, contacts or credits, and you buy and warm the mailboxes it sends from. You pay in a month with no meetings too. ### What does Dylan cost instead? Dylan is an AI agent too, but you do not run him: you brief him, approve the plan and the first emails, and pay per held meeting, at a price set by who you want to meet: - Lite: $250 per held meeting. Small companies, founder-led buyers, 1 to 200 employees. Deposit $750. - Standard: $500 per held meeting. Mid-market, directors and VPs, 201 to 1,000 employees. Deposit $1,500. - Enterprise: from $900 per held meeting, quoted. VP and C-level, 1,000+ employees. Deposit: three meetings. The deposit is credit for your first meetings. No meeting in 60 days? Your deposit comes back. The prices are for the beta; the full terms are on the pricing page. ### How did the first AI SDRs do? In a SaaStr reader survey in November 2024, 83% said they had not gotten anything from AI SDRs yet, and 3% said they had generated real revenue. What survived since, and why, is in The AI SDR hype is over. ### When is AI SDR software the better choice? - You have someone with hours a week to run it. In SaaStr's words, "Performance ebbs and flows directly with human attention." - Your contacts are already yours. SaaStr runs separate agents for cold outbound, lapsed customers, active nurture, inbound qualification and ghosted leads. Software that works your own database and CRM fits that well. - Your inbound leads wait for an answer. SaaStr says its inbound agent books meetings instantly, where the old handoff could take up to 24 hours. Fix that before you buy outbound from anyone, including us. - You want every setting in your own hands. Software gives your team the controls. Dylan gives you approvals. ### When is Dylan the better choice? - Nobody on your team has the hours to steer an agent. A person at Belkins reviews your plan and emails it within one business day. After that, your part is approving. - You want to pay for meetings, not seats. Never billed: meetings outside your definition, no-shows, companies on your do-not-contact list. If no meeting is held in 60 days, the deposit comes back. - You want your own domain kept out of cold email. Dylan sends from his own warm domains, with a separate slice for each client. - You want stopping to be a rule, not a setting. The moment a reply is read, every further scheduled email to that person stops, before any AI sees it. ### What should you ask any AI SDR vendor? Before you sign with anyone, including us, ask who approves the first emails, what happens when someone replies "stop", whose domain sends, what you pay if no meetings come, and whether the agent says it is an AI. The five questions, and why each one matters, are at the end of The AI SDR hype is over. How Dylan answers them: how it works and how Dylan writes. ### Sources 1. 6 Months of AI SDRs: What's Worked, How They Brought In $1M+ in 90 Days, and the Real Data Everyone's Asking For (SaaStr) saastr.com 2. 83% of You Haven't Gotten AI SDRs to Work Yet (SaaStr, November 2024) saastr.com ### The other comparisons All three side by side - Dylan vs hiring an SDR · Salary, tools and ramp time next to a price per held meeting, and when a person on your team is the better call. - Dylan vs an agency retainer · A monthly fee for a team's time next to a price per held meeting, and when an agency's people and channels fit better. ### Get on Dylan's calendar. Tell Dylan, our AI agent, who you sell to. A person at Belkins reads every entry and picks teams by fit. We invite 10 teams every two weeks. You approve the plan and pay per held meeting, or on a plan we are testing. Join the waitlist Already know your definition? Send the full brief --- # Page: The film URL: https://meetdylan.ai/film The film ## Watch Dylan book a meeting. Forty-two seconds, from a website to a held meeting: the whole job, step by step. Example data throughout. Download the 4:5 cut for LinkedIn · MP4, 1080 by 1350, 42 seconds, 3.3 MB. Silent; the captions are in the picture. Every step in words ### What happens in the film. The film has no sound and its captions are part of the picture, so here is each chapter in words. Chapter 1, Brief · 0:02 to 0:07 #### Brief Dylan in a few minutes The “Brief Dylan” form fills in for Harrow Line, an example company: the website harrowline.com and the line “Fleet fuel cards with per-vehicle limits” are typed in, then Operations and a company size of 201 to 1,000 employees are picked. The “Your brief so far” panel on the right updates with each answer. The “Get my meeting plan” button is clicked and changes to “Building your plan”. Chapter 2, Plan · 0:07 to 0:13 #### Get a plan with real numbers The example meeting plan builds on screen: the counters run up to 1,810 companies that fit, 4,420 people to contact, 6 to 13 held meetings per pass and $500 per held meeting. Ten sample companies rise into a list, each with a reason to write now, such as Nordfeld Logistics opening a second warehouse in Ohio. A forecast for the next three weeks fills with likely meeting slots, and the terms appear under the list: a $1,500 deposit, no-shows not billed and $500 only when a meeting is held. Chapter 3, Approve · 0:13 to 0:19 #### Nothing goes out until you approve In Approvals, the first email of a new angle waits for sign-off: Dylan, writing as an AI agent for Harrow Line, tells Maya, VP Operations at Nordfeld Logistics (both example companies), that a new Ohio warehouse usually means new fuel cards. The view zooms in, the sentence where Dylan says he is an AI agent is highlighted, and Approve is clicked, so an “Approved by you” stamp lands on the email. A toast at the bottom says sending starts in 60 seconds and offers Undo, with a countdown ring. Chapter 4, Send · 0:19 to 0:25 #### He writes from his own mailboxes On the Today screen, Dylan’s 12 warm mailboxes for the example client Harrow Line send the first pass: each mailbox lights up as it sends, and a live log lists who was just written to. The counters climb to 148 sent, 4 replies and 2 meetings. Beside them, the client’s own domain, harrowline.com, stays at 0 cold emails. Chapter 5, Reply · 0:25 to 0:32 #### He answers replies and books In this example thread, a “New reply” toast from Maya is clicked and her conversation opens in the Inbox, where she asks “Maybe. What does it cost?” Dylan replies that Harrow Line’s team will cover pricing in the meeting and offers Thursday at 10:30 or 14:00 Eastern, and a note marks the pricing question as handed to you. Maya answers “10:30 works.” and Dylan confirms the booking for Thursday, Oct 22 at 10:30 Eastern, with the invite coming from Harrow Line’s calendar. Chapter 6, Booked · 0:32 to 0:37 #### The meeting lands in your calendar The Calendar opens on the example week of Oct 19 to 23, 2026, then Maya’s meeting lands on Thursday at 10:30 with a “Meeting booked” toast, and the toolbar count moves to 4 booked. The side panel switches to her meeting brief: Thursday, Oct 22, 10:30 to 11:00 EDT, why now, what she expects, and that Dylan booked it for Sam at Harrow Line. Chapter 7, Held · 0:37 to 0:40 #### You pay only when it happens Time moves on to Thursday at 11:05, just after the meeting, and Maya’s block turns solid green with a check mark as the toolbar updates to 3 held. A Billing card lists the example week: $500 for each held meeting, a no-show marked not billed and rebooked, and Maya’s meeting added at $500. The total billed this week rises from $1,000 to $1,500. The chapters as clips ### One step at a time. Each chapter on its own, a few seconds long. Tap one to play it. Brief · Brief Dylan in a few minutes Plan · Get a plan with real numbers Approve · Nothing goes out until you approve Send · He writes from his own mailboxes Reply · He answers replies and books Booked · The meeting lands in your calendar Held · You pay only when it happens ### Get on Dylan's calendar. Tell Dylan, our AI agent, who you sell to. A person at Belkins reads every entry and picks teams by fit. We invite 10 teams every two weeks. Join the waitlist Already know your definition? Send the full brief --- # Page: Privacy notice URL: https://meetdylan.ai/privacy Privacy notice ## What we keep, and why. Last updated 9 October 2026. This notice covers the brief you send from meetdylan.ai, the waitlist you join (with your answers and any deck you add), the free tools and the buyer's guide, payments by teams we invite, and the form for people who want Dylan to stop emailing them. ### The short version - We keep what you type into the brief, or the address you ask us to stop emailing, plus the time and your browser's name. - We use it to prepare your meeting plan, hold your place, and keep Dylan away from anyone who said stop. - If you join the waitlist, we keep your answers and any deck you add, so we can decide whom to invite first. - If you ask one of our free tools to email you a result, or get the buyer's guide, we keep your email address with the result in our lead list. - We copy waitlist entries, briefs and that lead list into a Google Sheet that Belkins controls. Google stores it for us. - It is stored privately with Vercel, our host, in the EU and the US. We do not sell it. - We count page views with Vercel Web Analytics, which sets no cookies. - Briefs, waitlist entries and tool leads are deleted after 24 months. Opt-outs are kept so we can keep honoring them. - Ask for a copy, a correction or deletion at dylan@meetdylan.ai. ### Who is responsible Dylan is an AI agent built by Belkins. Belkins is the controller of the personal data described here: it decides why and how it is used, and it is the one to contact about it. Write to dylan@meetdylan.ai. ### What we collect #### When you brief Dylan ("Get my meeting plan") Only the last step of the brief is saved. It holds: - your company's website and one line about what you sell; - who you want to meet: functions, any titles you add, company sizes and regions; - your work email address, and whether it is a free email service such as Gmail; - any companies Dylan must never contact, as you typed them; - the referral code, if you came from someone's referral link, and campaign tags in the link you followed (utm_source and the like); - your browser's name and version (its user agent), and the time you sent the brief. The example plan you see in steps one to three is built in your browser and is not sent to us. #### When you join the waitlist Your place is saved when you press Join the waitlist. Each later step is saved when you press Save and continue. An entry holds: - from the first step: your work email, your name, your company's website and the way to pay you are most interested in; - about your company: its name, your role, its size and where it is based, what you sell and why customers choose you; - the buyers you want to meet: functions, titles, industries, company sizes, regions, and any companies Dylan must never contact; - how you sell today: deal size, sales cycle, current outbound, how many people take meetings, how many meetings a month you want, and when you want to start; - any notes, and your deck or a link to it; - the referral code and campaign tags from the link you followed, the page you first opened on this site, the ways to pay pages you opened on this site during the visit, your browser's user agent, and when you joined and last saved a step. If you tick the box to hear about Dylan's launch and pricing tests, we keep the time you ticked it. #### Your deck If you add a deck, it goes from your browser straight to our private storage with Vercel. People at Belkins who review waitlist entries can open it, through a link that stops working after a few days. We do not share it outside Belkins. We delete it 12 months after you send it, or sooner if you ask. #### When you join from a terminal curl https://meetdylan.ai/join -d you@company.com saves the email address you send, the time and your client's user agent, as a short brief. #### When you use a free tool The pipeline calculator, the SDR cost calculator and the cold email grader work in your browser. What you type is not sent to us unless you ask for your result by email, or join the waitlist with a calculator's numbers (they are then saved with your entry). The cold email grader works the same way: what you paste is checked in your browser and is not sent to us. If you use the deliverability check, the domain you type is looked up in public DNS through the public resolvers of Cloudflare and Google, and we may request that domain's MTA-STS policy file. We do not store the domain. #### When you ask a tool to email you a result If you ask us to email you a result from one of our tools (a calculator, the deliverability check, the email grader or the buyer's guide): your email address, the numbers or domain you entered, and the result. We do not keep an email you paste into the grader; it is graded and dropped. From the grader, only which of its rules your email met, whether a person or an AI sends it, its word, sentence and link counts and any style notes it did not score reach us, never the text; we work the score out from those. With it we keep whether the address is a free email service, the time of each request, which tools you used, the page you first opened on this site and campaign tags in the link you followed. If you tick the box to hear about Dylan's launch and pricing tests, we keep the time you ticked it. #### When you get the buyer's guide Your work email address, whether it is a free email service, and the time you asked, with the page you first opened on this site and campaign tags in the link you followed. It is the same lead record as a tool's result email, marked as the guide. We email you the download link only if you tick "Email me the link as well", and we email you about Dylan only if you tick that box too. #### When a team we invited pays Payments go through Stripe, on Stripe's own pages. Stripe collects your card and billing details. We keep Stripe's references for the payment, the amount, the plan and the reference of your waitlist entry, never your card, your name or your address. #### When you ask Dylan to stop The email address or company domain you enter, the time and your browser's user agent. #### What we do not collect We do not store your IP address. It is used for a few minutes, in memory, to stop the forms being flooded, and then forgotten. The site sets no cookies and loads no scripts from other sites. Your browser keeps your light or dark theme choice and your Sound switch choice for the example notifications; for the length of your visit, the referral code, campaign tags, the first page you opened and the ways to pay pages you opened; and, if you start the waitlist form, your unsent answers and a key that lets this browser finish your entry, for up to 30 days or until you clear them; and, if you come to the waitlist from one of our tools, that tool's numbers until you join or leave them out. They stay on your device and reach us only when you press Join or Save, or inside a brief you send. #### How we count page views We count page views with Vercel Web Analytics. It runs from this site's own address and sets no cookies. For each view it records the time, the page's address without anything after a "?" or "#", the site that linked you here, your approximate location (country, region and city), and your browser, operating system and device type. Vercel tells visits apart by a code made from the request, which it discards after 24 hours; the views are not tied to you or to your IP address. ### Why we use it - To prepare and send your meeting plan, and to talk to you about it. These are steps you ask for before any contract, and our legitimate interest in answering you. - To hold your place on the waitlist and tell you when your wave opens: our legitimate interest in opening Dylan in an orderly way. - To decide whom to invite first. We give each entry a score from your answers to sort the list, and a person at Belkins reads entries and makes every decision; nothing is decided by the score alone. This is our legitimate interest in opening Dylan to the teams he can help, and a step you ask for before any contract. - To email you about Dylan's launch and pricing tests, only if you ticked that box. You can stop these at any time. - To send the result email you asked for, once, and to keep you in our lead list so Belkins can see who is interested in Dylan. We email you again only if you tick the box. This is a step you ask for, and our legitimate interest in knowing who is interested in Dylan. - To take a payment that a team we invited makes through Stripe: to perform our contract with that team. - To count page views, so we know which pages people read: our legitimate interest. - To keep your do-not-contact list, so Dylan never writes to those companies for you. - To honor a request to stop emails, for every client Dylan works for: your right to object to direct marketing, which we must respect, and our legitimate interest in keeping an accurate suppression list. - To learn which links bring briefs (referral codes and campaign tags), and to keep the forms safe from abuse (the user agent and the short-lived IP check): our legitimate interests. We do not sell or rent any of it. ### Where it is kept, and who sees it Each brief and each opt-out is stored as a private file with Vercel, the company that hosts this site, in its Blob storage. Vercel may process data in the European Union and in the United States. Where personal data leaves the UK or the EU, the transfer relies on the safeguards the law provides, such as standard contractual clauses or an adequacy decision. Security explains how the site protects these records, and how to report a security problem. Waitlist entries and decks are stored the same way, as private files with Vercel. We also copy each waitlist entry and brief, and the people who ask for a result email, without your browser's user agent, into a Google Sheet that Belkins controls in Google Workspace; Google processes it for us as our service provider. Decks stay with Vercel and are not copied into the sheet; the sheet holds a link that expires. People at Belkins who prepare plans and run Dylan can read briefs and waitlist entries. When a brief, a waitlist entry or an opt-out arrives, our team may get a one-line notice in our internal chat (Slack), or by email to our own mailbox sent through Resend, with its reference and the company's domain, never your email address. Resend also sends the result emails you ask for. The deliverability check asks the public DNS resolvers of Cloudflare and Google about the domain you type. Payments go through Stripe, which processes them for us. Page views are counted by Vercel, our host. ### How long we keep it - Briefs, including the waitlist place they hold: 24 months from when you send them, then deleted. If you become a client, your agreement with Belkins sets what happens next. You can ask us to delete a brief sooner. - Waitlist entries: 24 months from when you join, then deleted, the same as briefs. - Tool results and the address they went to (the buyer's guide included): 24 months from your last request, then deleted, the same as waitlist entries. To stop abuse we keep a coded form of the address, which cannot be read back, for 30 days. - Decks: 12 months after you send them, then deleted, or sooner if you ask. - The copy in our sheet is deleted with the entry or the brief it copies. - Opt-outs: kept for as long as Dylan sends email, because forgetting them would mean writing to you again. We keep only what we need to recognize the address or the domain. ### Your rights Under the UK GDPR and the EU GDPR you can ask us: - for a copy of the personal data we hold about you; - to correct it, or to delete it; - to restrict how we use it, or to send it to you in a portable format; - to stop using it where we rely on our legitimate interests. You can always object to direct marketing, and we will stop. Write to dylan@meetdylan.ai. We answer within one month, and we may ask you to confirm it is you. If you are unhappy with our answer, you can complain to a data protection authority: in the UK the Information Commissioner's Office (ico.org.uk), in the EU the authority where you live or work. ### If Dylan emailed you Dylan is an AI agent. He writes on behalf of the company named in his email, and he says so. To stop him, reply "stop" to any of his emails, leave your address on the page for people Dylan emailed, or leave your address or your company's domain in the form on our home page. Your request is recorded at once and can take up to 2 business days to reach every campaign. For anything else about your data, including where your address came from, write to dylan@meetdylan.ai. ### Changes to this notice If we change what we collect or how we use it, we update this page and the date at the top first. --- # Questions URL: https://meetdylan.ai/faq ## What counts as a held meeting? Someone who matches your brief's meeting definition joins a call Dylan booked, with your meeting owner. No-shows, people on your do-not-contact list, duplicates and anyone outside the definition are not billed. ## Whose name is on the emails? Dylan's. He writes as an AI agent working for you, from his own domains. Your domain never sends a cold email. ## Do I need mailboxes, domains or a sequencer? No. Dylan brings his own, already warm, with a separate slice for each client. ## What if my market is too small? The plan tells you before you pay. Sometimes the answer is no, and he says so. ## Can I bring my own leads? Bring target companies. Contact lists are re-verified and may be refused, to protect the shared sending. ## Which channels and regions? Email, from Dylan's own mailboxes. US targets first. ## Does Dylan make phone calls? No. Dylan works by email today. If your buyers answer the phone, ask about adding Belkins callers to your plan. ## What happens with replies? Dylan answers routine ones (scheduling, questions your brief answers) and hands you anything about pricing, legal or complaints. ## What if it doesn't work? If 1,000 contacts bring no positive reply, Dylan pauses, tells you what he heard and proposes a new angle. Approve it, or leave with your deposit. And if no meeting is held in 60 days, the deposit comes back. ## Can I stop? Pause any time. Unused credit stays on your account. ## Is there a monthly plan? We are testing one with a small group: $1,500 a month, up to 3 held meetings included, then $500 per held meeting. Unused included meetings roll over one month. Month to month. Cancel any time before the next billing date. --- # Glossary URL: https://meetdylan.ai/glossary ## SDR URL: https://meetdylan.ai/glossary/sdr A sales development representative: the person who finds and qualifies prospects and books first meetings for the people who close deals. ### What is an SDR? An SDR, or sales development representative, works the first part of the sales process. SDRs research prospects, reach out by email and phone, answer early questions, check whether a prospect fits and book a first meeting for an account executive, who runs the deal from there. The role has traditionally been seen as entry level. #### What does an SDR do? Salesforce describes the SDR as a sales professional who "manages all top-of-the-funnel activities in the sales cycle": everything that happens before a prospect is ready to buy. In practice that is four jobs. - **Prospecting.** Building the list of companies and people who fit your [ideal customer profile](/glossary/icp). - **Outreach.** Writing to and calling people who did not ask to hear from you, and following up. - **Qualifying.** Checking that the person has the problem, the role and the timing to be worth a meeting. - **Booking.** Putting a first meeting on the calendar of the account executive who will run the deal. Salesforce adds that SDRs "often function as a bridge between the sales and marketing departments, doing a mix of inbound and outbound presales work." #### Is an SDR the same as a BDR? Often, in practice. Many companies use the two titles for one job. Where they split them, the SDR follows up on inbound leads and the BDR starts outbound conversations. [SDR vs BDR](/glossary/sdr-vs-bdr) sets the two side by side. #### How do you measure an SDR? An SDR's output is a first meeting, so count meetings. Count held meetings, not booked ones: a booked meeting is a time on a calendar, and a [held meeting](/glossary/held-meeting) is a call that took place. To see what one held meeting costs you with an in-house SDR, use the [SDR cost calculator](/tools/sdr-cost-calculator). #### Where does Dylan fit? Dylan is an AI agent built by Belkins that does the email side of the job. He writes from his own mailboxes, follows up, answers routine replies and books meetings into your calendar. Pricing, legal questions and complaints go to your team, and you pay per held meeting. He does not make phone calls. Sources: - What is a Sales Development Representative (SDR)? (Salesforce): https://www.salesforce.com/blog/sales/sales-development-representative/ - SDR vs. BDR: Key Differences, Roles, and When to Hire (ZoomInfo): https://pipeline.zoominfo.com/sales/sdr-vs-bdr-difference ## BDR URL: https://meetdylan.ai/glossary/bdr A business development representative: a seller who starts conversations with companies that have not shown interest yet, and books first meetings. ### What is a BDR? A BDR, or business development representative, opens conversations with companies that have not asked to hear from you. BDRs research target accounts, write cold emails, make cold calls and reach out on LinkedIn, then book a first meeting for an account executive. Where a company splits the titles, the BDR works outbound and the SDR works inbound. #### What does a BDR do? ZoomInfo describes a BDR as someone who "proactively reaches out to prospects who haven't engaged with your company yet." The work is outbound from start to finish. - **Research.** Choosing the accounts that fit and the people worth writing to at each. - **Cold outreach.** Emails, calls and LinkedIn messages to people who are not expecting them. - **Follow-up.** A short, polite sequence after the first message, stopped at the first reply. - **Booking.** A first meeting with an account executive, who takes the deal from there. #### How is a BDR different from an SDR? In ZoomInfo's words: "SDRs qualify inbound demand; BDRs create outbound pipeline." The same article warns that "definitions vary by company and job posting," so read the job description, not the title. [SDR vs BDR](/glossary/sdr-vs-bdr) has the full comparison. #### When does a company need a BDR? When buyers will not come to you on their own: a new market, a new product, or a short list of large accounts that marketing does not reach. ZoomInfo puts it this way: "When inbound volume is low or the growth strategy requires breaking into new logos, BDRs are the motion that fills the gap." That work is [outbound sales](/glossary/outbound-sales). #### Where does Dylan fit? Dylan does the email part of a BDR's job, under your approval. You approve the plan and the first emails before anything goes out, and every first email says he is an AI agent and which company he works for. He works by email only, from his own mailboxes, so your domain never sends a cold email. Sources: - SDR vs. BDR: Key Differences, Roles, and When to Hire (ZoomInfo): https://pipeline.zoominfo.com/sales/sdr-vs-bdr-difference - What Is Outbound Sales? Strategies and Tips (Salesforce): https://www.salesforce.com/sales/outbound-sales/ ## SDR vs BDR URL: https://meetdylan.ai/glossary/sdr-vs-bdr Where a company splits the titles, SDRs qualify inbound leads and BDRs create outbound pipeline. Many companies use both titles for the same job. ### SDR vs BDR: what is the difference? The difference is the direction of the work. Where a company splits the titles, an SDR follows up on inbound leads, people who already showed interest, and a BDR starts conversations with companies that have not. Both qualify prospects and book first meetings for an account executive, and many companies use the two titles for one job. #### SDR and BDR side by side In short, following ZoomInfo's description of the two roles: | Compared | SDR | BDR | | --- | --- | --- | | Starts from | Demo requests, downloads, signups | Accounts that have not engaged | | Main channels | Fast replies to inbound | Cold email, cold calls, LinkedIn | | Hands off to | An account executive | An account executive | ZoomInfo also notes that "definitions vary by company and job posting, some organizations invert these roles entirely, and many use both titles interchangeably." #### Is one more senior than the other? No. In ZoomInfo's words, "Neither role is higher in seniority," and both "commonly progress to Account Executive (AE)." Salesforce describes SDRs as doing "a mix of inbound and outbound presales work," which is one reason the titles blur. #### Which one do you need? If leads already come in and wait too long for an answer, the inbound job comes first. If they do not come in, someone has to start conversations, and that is the outbound job. Before you hire, write down the work instead of the title: who the person writes to, how they qualify, and what counts as a meeting. That last part is your [held meeting](/glossary/held-meeting) definition. #### What does each one cost? That depends on your pay, tools and results. The [SDR cost calculator](/tools/sdr-cost-calculator) takes your SDR pay, tools and held meetings and gives your cost per held meeting, next to Dylan's price. Sources: - SDR vs. BDR: Key Differences, Roles, and When to Hire (ZoomInfo): https://pipeline.zoominfo.com/sales/sdr-vs-bdr-difference - What is a Sales Development Representative (SDR)? (Salesforce): https://www.salesforce.com/blog/sales/sales-development-representative/ ## Outbound sales URL: https://meetdylan.ai/glossary/outbound-sales Selling where the seller starts the conversation, usually by cold email or cold call, with companies that did not ask to be contacted. ### What is outbound sales? Outbound sales is selling where the seller starts the conversation. Instead of waiting for buyers to fill in a form, the seller picks the companies that fit, finds the right people and writes or calls first, usually by cold email or phone. Inbound is the opposite: the buyer finds you through marketing and gets in touch. #### Outbound vs inbound Salesforce puts it simply: "The biggest difference between outbound and inbound sales is who initiates the outreach." | Compared | Outbound | Inbound | | --- | --- | --- | | Who starts | The seller | The buyer | | Who it reaches | Companies you chose | People already looking | | How it starts | Cold email, cold call | Marketing and advertising | #### The steps of an outbound program 1. Decide who counts: your [ICP](/glossary/icp) and the meeting you want. 2. Build the list of companies and the people worth writing to at each. 3. Write a short first email with a real reason to talk, and a polite follow-up. 4. Send from domains set up for it, with [SPF](/glossary/spf), [DKIM](/glossary/dkim) and [DMARC](/glossary/dmarc) in place, at a pace receivers accept. 5. Stop on the first reply, and honor every opt-out. 6. Book the meeting, and make sure it is held. #### Is outbound email legal? In the United States, commercial email falls under [CAN-SPAM](/glossary/can-spam), and the FTC says plainly: "The law makes no exception for business-to-business email." Honest headers, a postal address and a working opt-out are the floor. #### How Dylan does outbound Dylan runs the email side. He writes from his own warmed domains and mailboxes, with a separate slice for each client, so your domain never sends a cold email. He says he is an AI agent in every first email, and nothing goes out until you approve the plan and the first emails. Sources: - What Is Outbound Sales? Strategies and Tips (Salesforce): https://www.salesforce.com/sales/outbound-sales/ - CAN-SPAM Act: A Compliance Guide for Business (FTC): https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business ## Appointment setting URL: https://meetdylan.ai/glossary/appointment-setting Booking first sales meetings with prospects who fit, so the people who sell spend their time in calls instead of finding them. ### What is appointment setting? Appointment setting is the work of booking first sales meetings with prospects who fit. Someone finds the right people, reaches out, answers early questions and puts a call on the calendar of the person who will sell. It can be done by an in-house SDR team, by an agency, or by an AI agent like Dylan. #### What does appointment setting include? - **Choosing who to meet.** Your [ICP](/glossary/icp) and the meeting definition: the titles, company sizes and regions that count. - **Outreach and follow-up.** By email, phone or LinkedIn. - **Handling replies.** Questions, scheduling, and the people who say no. - **Booking the call.** On the calendar of the person who will run it. - **Getting it held.** A [no-show](/glossary#no-show) is not a meeting, so it gets rebooked. #### Booked, held and qualified meetings Appointment setting has a vocabulary problem. A booked meeting is a time on a calendar. A held meeting is a call that took place. A qualified meeting is a held call with someone who fits what you agreed to in advance. The gap costs buyers money. OutboundPros, an outbound agency, gives an example: if an agency celebrates 20 booked meetings but 6 no-show and 5 are outside the target profile, "you did not buy 20 meetings. You bought 9 usable conversations." #### How is appointment setting paid for? Ask any provider what exactly you are paying for: a team's time, a booked meeting or a held one. The difference decides who pays for no-shows and wrong-fit calls. Dylan bills per [held meeting](/glossary/held-meeting) by default: no-shows, people outside your definition, duplicates and companies on your do-not-contact list are never billed. #### Agency, in-house or AI agent? Belkins, the team behind Dylan, runs [appointment setting as an agency service](https://belkins.io/appointment-setting). Dylan is the AI agent version: email only, from his own mailboxes, paid per held meeting. To compare with an in-house team, the [SDR cost calculator](/tools/sdr-cost-calculator) works out your cost per held meeting. Sources: - B2B Appointment Setting Pricing in 2026 (OutboundPros): https://outboundpros.io/blog/b2b-appointment-setting-pricing-2026 - What is a Sales Development Representative (SDR)? (Salesforce): https://www.salesforce.com/blog/sales/sales-development-representative/ - B2B Appointment Setting Services (Belkins): https://belkins.io/appointment-setting ## Sales quota URL: https://meetdylan.ai/glossary/sales-quota A measurable goal a seller or a team is expected to hit in a set period, usually counted in revenue, deals closed or sales activities. ### What is a sales quota? A sales quota is a measurable goal a seller or a team must hit in a set period, such as a month, a quarter or a year. Most quotas count revenue or deals closed; some count activities such as calls and meetings. Managers usually set them so that, if every seller hits theirs, the company hits its sales target. #### What types of sales quota are there? Salesforce lists five. - **Activity quota.** The number of actions, such as cold calls, emails sent and meetings scheduled. - **Profit quota.** Profit, meaning sales revenue after selling expenses. - **Forecast quota.** Set from past sales and market conditions. - **Volume quota.** The total number of units a seller sells. - **Combination quota.** More than one of the above at once. #### How do you turn a quota into a plan? Work backward from the number. 1. Deals you need = your quota divided by your [average deal size](/glossary#deal-size). 2. Held meetings you need = deals you need divided by your [win rate](/glossary#win-rate) from first meeting to won deal. 3. Meetings a month = that number divided by the months in the period. Example: an annual quota of $600,000 with an average deal of $20,000 needs 30 deals. At a win rate of 25% from held meeting to won deal, that is 120 held meetings, or 10 a month. The [pipeline calculator](/tools/pipeline-calculator) does this math with your own numbers. #### Quota vs pipeline coverage The quota is the target. [Pipeline coverage](/glossary/pipeline-coverage) tells you whether the deals you are working today are enough to reach it. Sources: - What Are Sales Quotas? Types, Examples and Tips (Salesforce): https://www.salesforce.com/sales/sales-quotas/ ## Pipeline coverage URL: https://meetdylan.ai/glossary/pipeline-coverage Open pipeline divided by the quota it has to cover in the same period. It tells you whether there is enough in the funnel to hit the number. ### What is pipeline coverage? Pipeline coverage is the value of your open pipeline divided by the quota it has to cover in the same period. If the deals you are working add up to three times the quarter's target, coverage is 3x. The coverage you need depends on your win rate: the fewer deals you win, the more pipeline you need. #### How do you calculate pipeline coverage? Pipeline coverage = open pipeline value ÷ quota for the period. Count only deals that can close in that period. Metabase separates two versions: - **Raw coverage.** Open pipeline value divided by quota. Simple, but an early deal counts as much as one about to sign. - **Weighted coverage.** Each deal's value times its stage probability, added up, then divided by quota. #### What pipeline coverage ratio do you need? A common rule of thumb is 3x to 4x, but Metabase calls the "3× pipeline" rule "a heuristic, not a law." The target that follows from your own numbers is one divided by your win rate. Metabase's examples: a 33% win rate implies roughly 3x, 25% roughly 4x, and 50% roughly 2x. #### A worked example Example: a team has a quarterly quota of $300,000 and $900,000 in open pipeline, so coverage is 3x. If it wins 25% of its deals, that pipeline should close about $225,000. That is short of the quota, so the team needs more pipeline, a better win rate or bigger deals. #### Where does new pipeline come from? From first meetings. Work backward: the deals you need, divided by your win rate, give the meetings you need. The [pipeline calculator](/tools/pipeline-calculator) does that math from your quota, average deal size and win rate, and shows the held meetings you need each month. If your market is small, count it first: [your market is a pond, not an ocean](/blog/enterprise-market-is-a-pond). Sources: - Pipeline Coverage: Definition, Formula and How to Track It (Metabase): https://www.metabase.com/metrics/pipeline-coverage ## Win rate URL: https://meetdylan.ai/glossary#win-rate The share of your opportunities, or of your first meetings, that end in a won deal. It decides how many meetings and how much pipeline a quota needs. ## Average deal size URL: https://meetdylan.ai/glossary#deal-size The average value of a won deal. Your target divided by it gives the number of deals you need. ## SQL vs MQL URL: https://meetdylan.ai/glossary/sql-vs-mql An MQL is a lead marketing judges likely to become a customer. An SQL is a lead ready to move into the sales process and talk to sales. ### SQL vs MQL: what is the difference? An MQL, or marketing qualified lead, has shown interest and fits criteria marketing set in advance, but is not ready to buy. An SQL, or sales qualified lead, is ready to move into the sales process and talk to a seller. The difference is readiness, and the handoff from one to the other decides which leads sales works. #### MQL and SQL side by side As Salesforce defines them: | Compared | MQL | SQL | | --- | --- | --- | | What it has done | Engaged with marketing or visited the site a few times | Shown it is serious about buying | | What it needs | More information before a decision | A conversation with sales | | Who works it next | Marketing | Sales | An MQL is a lead "that marketing has deemed likely to become a customer based on preset criteria, like product-need fit and budget." An SQL is one that is "ready to move into your sales process." #### Why does the difference matter? Because leads get lost between the two teams. Salesforce warns that if the handoff goes wrong, "the lead can slip right through your fingers and you lose the deal." Write down the criteria for each stage, and who follows up and how fast. #### Where do outbound leads fit? Outbound skips the MQL stage. An outbound prospect never filled in a form, so the first sign of interest is a reply. Pay per intent, one of Dylan's ways to pay (a way to pay we are testing), bills that moment: A reply, in the prospect's own words, from a person inside your definition, that asks for a next step. Pay per qualified opportunity (a way to pay we are testing) sits further down the funnel: A held meeting that your meeting owner confirms as a qualified opportunity, against criteria you wrote before launch. Sources: - MQL vs. SQL: What's The Difference? (Salesforce): https://www.salesforce.com/blog/sales/mql-vs-sql/ ## MQL URL: https://meetdylan.ai/glossary#mql Marketing qualified lead: a lead that has shown interest and that marketing judges likely to become a customer, from criteria set in advance, but not ready to buy yet. ## SQL URL: https://meetdylan.ai/glossary#sql Sales qualified lead: a lead interested enough to move into the sales process and ready to talk to a seller. ## Held meeting URL: https://meetdylan.ai/glossary/held-meeting Someone who matches your brief's meeting definition joins a call Dylan booked, with your meeting owner. A held meeting is what Dylan bills by default; the other ways to pay are tests. ### What is a held meeting? A held meeting is a sales call that actually took place. Someone who matches your brief's meeting definition joins a call Dylan booked, with your meeting owner. It is not the same as a booked meeting, which is only a time on a calendar. A held meeting is what Dylan bills by default; the other ways to pay are tests. #### Booked, held and qualified Three words get mixed up. A booked meeting is a time on a calendar. A held meeting is a call that took place. A qualified meeting is a held call with someone who fits what you agreed to in advance. Dylan's held meeting is the strict version: held and qualified, or not billed at all. #### What is never billed? - **No-shows.** If the person does not join, you pay nothing, and Dylan rebooks. - **People on your do-not-contact list.** They should never have been contacted, so you never pay for meeting them. - **Duplicates.** The same meeting is never billed twice. - **Anyone outside your definition.** A meeting with the wrong person is not a held meeting. #### Who decides what counts? You do, before anything is sent. Your meeting definition sets the titles, company sizes and regions that count, who takes the call on your side, and what the prospect gets. It is also the targeting rule: Dylan uses it to decide who to write to. The definition starts from your [ICP](/glossary/icp). Settle the awkward cases in advance: if the VP you targeted sends a director, does that count, and if your meeting owner is away, may a colleague take the call? Write the answers into the definition. #### What if you disagree with a billed meeting? If you think a billed meeting should not have been, you have 72 hours after it to dispute. Silence confirms. Disputes come back as credit. #### Why count held meetings at all? Because a held meeting is the first thing in outbound you would happily buy on its own. If you run outbound in-house, the [SDR cost calculator](/tools/sdr-cost-calculator) shows what one held meeting costs you today, and the [pipeline calculator](/tools/pipeline-calculator) shows how many you need for your quota. ## Booked meeting URL: https://meetdylan.ai/glossary#booked-meeting A time on a calendar. It becomes a held meeting only when the call takes place with someone inside your definition. ## Qualified meeting URL: https://meetdylan.ai/glossary#qualified-meeting A held call with someone who fits what you agreed to in advance. Dylan's held meeting is the strict version: held and qualified, or not billed at all. ## No-show URL: https://meetdylan.ai/glossary#no-show A booked meeting the person does not join. You pay nothing, and Dylan rebooks. ## Meeting definition URL: https://meetdylan.ai/glossary#meeting-definition The titles, company sizes and regions that count, set before anything is sent. It is also the targeting rule: Dylan uses it to decide who to write to. ## Meeting owner URL: https://meetdylan.ai/glossary#meeting-owner The person whose calendar Dylan books into and who runs the call. ## Duplicate URL: https://meetdylan.ai/glossary#duplicate The same meeting booked twice. It is never billed twice. ## Deposit URL: https://meetdylan.ai/glossary#deposit To start, you prepay three meetings as credit at your tier's price. Each held meeting draws it down. No meeting in 60 days? Your deposit comes back. ## Credit URL: https://meetdylan.ai/glossary#credit What your deposit becomes. Each held meeting draws it down, disputes come back as credit, and unused credit stays on your account. ## Dispute window URL: https://meetdylan.ai/glossary#dispute-window If you think a billed meeting should not have been, you have 72 hours after it to dispute. Silence confirms. Disputes come back as credit. ## Stop rule URL: https://meetdylan.ai/glossary#stop-rule If 1,000 contacts bring no positive reply, Dylan pauses, tells you what he heard and proposes a new angle. Approve it, or leave with your deposit. ## Pause URL: https://meetdylan.ai/glossary#pause Pause any time. Unused credit stays on your account. ## Intent URL: https://meetdylan.ai/glossary#intent A reply, in the prospect's own words, from a person inside your definition, that asks for a next step. You read it before you pay. ## Signup URL: https://meetdylan.ai/glossary#signup A new account on your product, created by a person Dylan contacted, inside the attribution window in your plan. ## Qualified opportunity URL: https://meetdylan.ai/glossary#qualified-opportunity A held meeting that your meeting owner confirms as a qualified opportunity, against criteria you wrote before launch. Silence confirms. ## Attribution window URL: https://meetdylan.ai/glossary#attribution-window The time after Dylan contacts someone in which their signup counts. It is written into your plan in advance: contacted by Dylan inside the window counts, whatever the last click. ## Monthly plan URL: https://meetdylan.ai/glossary#monthly-plan $1,500 a month, up to 3 held meetings included, then $500 per held meeting. Same held-meeting definition, same 72-hour dispute window. In testing. Unused included meetings roll over one month. ## Partner plan (wholesale) URL: https://meetdylan.ai/glossary#partner-plan A held meeting delivered to one of your clients, under that client's definition, billed to you at a wholesale price set in your partner plan. By application. Not open yet. The terms are set in your partner plan. ## Brief URL: https://meetdylan.ai/glossary#brief What you tell Dylan: your company's website, one line about what you sell, who you want to meet (functions, titles, company sizes and regions) and any companies Dylan must never contact. He drafts the rest; you correct it. ## Plan URL: https://meetdylan.ai/glossary#plan How many companies fit, ten real examples, the first email and the price. A person at Belkins reviews your plan and emails it within one business day. ## ICP URL: https://meetdylan.ai/glossary/icp Ideal customer profile: the companies (industry, size, region) and the people (function and seniority) you want to meet. In Dylan's brief it is the "who counts" part of your meeting definition. ### What is an ICP in sales? In sales, ICP stands for ideal customer profile: a description of the companies that get the most from what you sell and the people inside them you want to meet. It names the industry, company size and region, and the function and seniority of the buyer. Sales teams use it to decide who to write to first. #### What goes into an ICP? Two layers, and the exceptions. - **The company.** Industry, size, region, and anything else that predicts fit, such as a recent change in the business. - **The person.** The function and seniority of the people who feel the problem and can say yes. - **The exceptions.** Companies that look right and are not: current customers, open deals, partners, and customers who churned. The best ICPs come with examples. SaaStr lists a "Detailed ICP definition with examples and non-examples" among the training that makes AI SDRs work. #### How is an ICP different from a buyer persona? An ICP describes the account. A persona describes one person at that account: their job, their problems and how they buy. Start with the ICP, because it decides which personas are worth writing to. #### How do you write a good ICP? Start from your ten best customers, not from a blank page. For each, write one line on why they bought and what was happening at the time; the trigger matters more than the logo. Then add three non-examples: customers who looked right and churned, or deals you wish you had walked away from. [How to brief an AI SDR](/blog/how-to-brief-an-ai-sdr) walks through it. #### How does Dylan use your ICP? In Dylan's brief, the ICP is the "who counts" part of your [held meeting](/glossary/held-meeting) definition: the companies (industry, size, region) and the people (function and seniority) you want to meet. The definition is also the targeting rule, so Dylan uses it to decide who to write to. The plan then shows how many companies fit and ten real examples, so you can correct the ICP before anything is sent. Sources: - 6 Months of AI SDRs: What's Worked (SaaStr): https://www.saastr.com/6-months-of-ai-sdrs-whats-worked ## Value proposition URL: https://meetdylan.ai/glossary#value-proposition Why customers pick you over the alternative, in one line. ## Do-not-contact list URL: https://meetdylan.ai/glossary#do-not-contact-list The companies Dylan must never contact for you. He never writes to them, and they are never billed. He checks the list when he builds the plan and again as each email is sent. ## Approvals URL: https://meetdylan.ai/glossary#approvals Nothing goes out until you say yes. You approve your meeting definition, the plan, the first emails and the first emails of every new angle. ## Angle URL: https://meetdylan.ai/glossary#angle A new claim, a new reason or a new tone in the emails. Each angle is a new promise in your name, so you approve its first emails. ## SPF URL: https://meetdylan.ai/glossary/spf A DNS record that lists who may send email for your domain. Every gatekeeper checks it. ### What is SPF? SPF, or Sender Policy Framework, is a DNS record that lists the servers allowed to send email for your domain. A receiving server reads it and checks whether a message came from one of them. With DKIM and DMARC, it is one of the three checks receivers use to decide whether mail that claims to be from you is real. #### How does SPF work? SPF is defined in RFC 7208. The RFC starts from a plain problem: existing protocols "place no restriction on what a sending host can use as the 'MAIL FROM' of a message." SPF lets a domain's owner "explicitly authorize the hosts that are allowed to use their domain names," and a receiving host "can check such authorization." In practice it is one TXT record on your domain. It starts with `v=spf1`, lists the services allowed to send for you, and ends with a rule for everything else. An example for the placeholder domain example.com: `v=spf1 include:_spf.example.com -all` Here `-all` asks receivers to fail mail from any server not listed. #### What does SPF not do? SPF checks the envelope sender, the address servers use to route and bounce mail, not the From address a person sees. That is why [DMARC](/glossary/dmarc) exists: it ties the result to your From domain. And SPF says nothing about whether the message was changed on the way; that is [DKIM](/glossary/dkim). #### Do you need SPF for cold email? Yes. Google's sender guidelines tell every sender to Gmail accounts to "Set up SPF or DKIM email authentication for your sending domains," and require SPF, DKIM and DMARC from senders of more than 5,000 messages a day. Those rules cover personal Gmail accounts, but in B2B every gatekeeper checks the same records. They are the price of entry, not an advantage. #### Check your domain The free [deliverability check](/tools/deliverability-check) looks up a domain's MX, SPF, DKIM and DMARC records in public DNS and explains each one. Dylan's deliverability is powered by [Folderly](https://folderly.com). Sources: - RFC 7208: Sender Policy Framework (SPF) for Authorizing Use of Domains in Email (IETF): https://www.rfc-editor.org/rfc/rfc7208 - Email sender guidelines (Google): https://support.google.com/mail/answer/81126?hl=en ## DKIM URL: https://meetdylan.ai/glossary/dkim A signature on each message that lets the receiver check it came from your domain unchanged. ### What is DKIM? DKIM, or DomainKeys Identified Mail, adds a cryptographic signature to the email you send. The receiving server looks up a public key in your domain's DNS and checks the signature. If it matches, a server your domain trusts signed the message and the signed parts were not changed on the way. DKIM works alongside SPF and DMARC. #### How does DKIM work? DKIM is defined in RFC 6376. It lets the owner of a domain "claim some responsibility for a message by associating the domain with the message," and that claim "is validated through a cryptographic signature and by querying the Signer's domain directly to retrieve the appropriate public key." 1. Your mail server signs the message's body and chosen headers with a private key. 2. It adds a DKIM-Signature header that names your domain (the `d=` tag) and a selector (the `s=` tag). 3. The receiver fetches the public key from DNS, under the selector in your domain's `_domainkey` subdomain, and checks the signature. #### How is DKIM different from SPF? | Compared | SPF | DKIM | | --- | --- | --- | | What it checks | The server that sent the message | A signature on the message | | Where it lives | One TXT record on your domain | A public key per selector | Neither one checks the From address a person sees. [DMARC](/glossary/dmarc) does that, using the results of both. #### Do you need DKIM for cold email? Yes. Google tells every sender to Gmail accounts to "Set up SPF or DKIM email authentication for your sending domains," and requires both, plus DMARC, from senders of more than 5,000 messages a day. Every service that sends as your domain, from your mailbox provider to your CRM, should sign with its own DKIM key. #### Check your domain The free [deliverability check](/tools/deliverability-check) looks up a domain's MX, SPF, DKIM and DMARC records in public DNS and explains each one. Dylan's deliverability is powered by [Folderly](https://folderly.com). Sources: - RFC 6376: DomainKeys Identified Mail (DKIM) Signatures (IETF): https://www.rfc-editor.org/rfc/rfc6376 - Email sender guidelines (Google): https://support.google.com/mail/answer/81126?hl=en ## DMARC URL: https://meetdylan.ai/glossary/dmarc Ties SPF and DKIM to your From domain and tells receivers what to do when they fail. ### What is DMARC? DMARC is a DNS record that ties SPF and DKIM to the domain in your From address. It tells receivers what you want done with mail that fails those checks, and asks them to send you reports about mail that uses your domain. The name stands for Domain-based Message Authentication, Reporting, and Conformance. #### What do the DMARC policies mean? The `p` tag in the record sets the policy. RFC 9989, the current DMARC standard (May 2026), defines three values: | Policy | What it tells receivers | | --- | --- | | `p=none` | "The Domain Owner offers no expression of preference." | | `p=quarantine` | "The Domain Owner considers such mail to be suspicious." | | `p=reject` | Every failure is "a clear indication that the use of the domain name is not valid." | A record with no `p` tag is treated as `p=none`. Receivers still decide: the RFC says they "SHOULD NOT reject messages solely because of a published policy of 'reject'." #### Where should you start? At `p=none`, with reports switched on. In the RFC's words, "Domain Owners usually start with 'p=none'," so the reports can show any server or outside sender missed in the SPF and DKIM setup. Fix what they show before you move to a stricter policy. #### What is alignment? DMARC passes when SPF or DKIM passes for a domain that matches the one in the From address. The RFC allows two modes, "relaxed" and "strict": relaxed accepts a domain from the same organization, such as a subdomain, and strict needs the exact domain. #### Do you need DMARC for cold email? Google requires DMARC from senders of more than 5,000 messages a day to Gmail accounts, and says the policy "can be set to none." For B2B, set it up anyway, aligned with your From domain: gateways check it too. #### Check your domain The free [deliverability check](/tools/deliverability-check) looks up a domain's MX, SPF, DKIM and DMARC records in public DNS and explains each one. Dylan's deliverability is powered by [Folderly](https://folderly.com). Sources: - RFC 9989: Domain-Based Message Authentication, Reporting, and Conformance (DMARC) (IETF): https://www.rfc-editor.org/rfc/rfc9989 - Email sender guidelines (Google): https://support.google.com/mail/answer/81126?hl=en ## MX record URL: https://meetdylan.ai/glossary#mx The DNS record that names the servers that receive a domain's email. An MX lookup shows in seconds which gateway a company uses. ## Warm-up URL: https://meetdylan.ai/glossary/warm-up Building a new domain's sending volume slowly, with recipients who engage, before any campaign. Dylan writes from his own warmed domains and mailboxes, so there is no warm-up on your side. ### What is email warm-up? Email warm-up is building a new domain's or mailbox's sending volume slowly, with recipients who engage, before any campaign. New domains start with no reputation, and a domain that sends a lot in its first weeks looks like the throwaway domains spammers buy in bulk. Warm-up gives the domain a history before it has to carry volume. #### Why do new domains need warm-up? Because reputation is built on history, and a new domain has none. Spamhaus notes that "for the first 30 days after initial registration, most companies specializing in threat intelligence will flag a newly registered domain" and watch it for mass sending. Its advice is direct: "Don't send a bulk email run with your newly acquired domain name." #### How does warm-up work? - **Authenticate first.** [SPF](/glossary/spf), [DKIM](/glossary/dkim) and [DMARC](/glossary/dmarc) in place before the first email. - **Start with people who engage.** Spamhaus recommends "a set of highly engaged recipients for the initial mailings." - **Raise volume step by step.** Slowly, watching replies and bounces. - **Show who owns the domain.** Do not hide it behind privacy masking, and connect it visibly to your brand. #### Do new Microsoft tenants have limits too? Yes. emailexpert reports that from September 14, 2026, Microsoft is rolling out lower limits for new Exchange Online tenants: 10% of the standard external-recipient quota for tenants less than 31 days old, and 25% from day 31 to day 60. The limit covers the whole tenant, not one mailbox, so cold email from your main tenant can hold up ordinary mail. #### Do you need warm-up with Dylan? No. Dylan writes from his own warmed domains and mailboxes, with a separate slice for each client, and your domain never sends a cold email. No DNS, no warm-up, nothing on your side to set up or burn. Sources: - Best practice for owners of a newly registered domain, part 3 (Spamhaus): https://www.spamhaus.org/resource-hub/domain-reputation/best-practice-for-owners-of-a-newly-registered-domain-part-3/ - Microsoft puts new Exchange Online tenants on 60-day sending probation (emailexpert): https://emailexpert.com/microsoft-puts-new-exchange-online-tenants-on-60-day-sending-probation/ ## Secure email gateway URL: https://meetdylan.ai/glossary#secure-email-gateway A filter many companies put in front of Microsoft 365 or Google Workspace. It checks the sender's reputation, scans every link, opens attachments in a sandbox and looks for impersonation. ## Quarantine URL: https://meetdylan.ai/glossary#quarantine Where a gateway puts suspicious mail instead of rejecting it. Your sending tool logs a successful delivery, and the recipient never sees the email unless someone in IT releases it. ## Sender reputation URL: https://meetdylan.ai/glossary#sender-reputation How far receivers trust a sending domain or IP. A secure email gateway checks it before a message reaches anyone, and a new domain starts with none. ## Bulk sender URL: https://meetdylan.ai/glossary#bulk-sender Google's term for anyone who sends "close to 5,000 messages or more to personal Gmail accounts within a 24-hour period". Its rules cover personal Gmail accounts, not Google Workspace. ## Sending slice URL: https://meetdylan.ai/glossary#sending-slice The part of Dylan's own warmed domains and mailboxes kept for one client. Your domain never sends a cold email. ## AI disclosure URL: https://meetdylan.ai/glossary#ai-disclosure Every first email Dylan sends says, in its opening line, that he is an AI agent and which company he works for. ## Opt-out URL: https://meetdylan.ai/glossary#opt-out When someone asks Dylan to stop, the request is honored for every client Dylan works for. It can take up to 2 business days to reach every campaign. ## Stop on reply URL: https://meetdylan.ai/glossary#stop-on-reply The moment a reply is read, every further scheduled email to that person stops, by rule, before any AI sees it. ## CAN-SPAM URL: https://meetdylan.ai/glossary/can-spam The US law for commercial email, business-to-business email included: honest headers and subject lines, a postal address, and an opt-out honored within 10 business days. ### What is CAN-SPAM? CAN-SPAM is the United States law that sets the rules for commercial email. Every message must carry honest header information and an honest subject line, say clearly that it is an ad or a solicitation, include a valid postal address and offer a clear way to opt out. It covers business-to-business email too. This page explains the law in plain words. It is not legal advice. #### What does CAN-SPAM require? The FTC's compliance guide sets out the main rules: 1. Don't use false or misleading header information. 2. Don't use deceptive subject lines. 3. Identify the message as an ad. 4. Tell recipients where you're located, with "a valid physical postal address". 5. Tell recipients how to opt out of future marketing email from you. 6. Honor opt-out requests promptly: within 10 business days. 7. Monitor what others are doing on your behalf. #### Does CAN-SPAM apply to B2B email? Yes. The FTC is direct: "The law makes no exception for business-to-business email." And "Despite its name, the CAN-SPAM Act doesn't apply just to bulk email." A single cold email to a prospect counts. #### Who is responsible when someone sends for you? Both of you. The FTC says that "even if you hire another company to handle your email marketing, you can't contract away your legal responsibility," and that both the company whose product is promoted and the company that sends the message "may be held legally responsible." #### How does Dylan handle it? Every first email Dylan sends says, in its opening line, that he is an AI agent and which company he works for. When someone asks Dylan to stop, the request is honored for every client Dylan works for, and it can take up to 2 business days to reach every campaign. The reasons are in [why Dylan says he is an AI](/blog/why-dylan-says-hes-an-ai), and the [opt-out](/docs/opt-outs) docs explain how stopping works. Sources: - CAN-SPAM Act: A Compliance Guide for Business (FTC): https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business - 15 U.S. Code § 7704: Other protection for users of commercial electronic mail (Cornell LII): https://www.law.cornell.edu/uscode/text/15/7704 --- # Page: Follow-up email templates URL: https://meetdylan.ai/resources/cold-email-templates/follow-up ## How to follow up when a cold email gets no reply. A follow up email after no response should add one new thing, not repeat the first email. Send it as a reply in the same thread, say again who you are, ask one easy question and keep the way out. Then stop: a last email that closes the loop, and nothing after a no. ### Should you follow up on a cold email? Yes, when the first email had a real reason to write. In [Belkins' 2026 follow-up study](https://belkins.io/blog/sales-follow-up-statistics) of 7,530,489 emails sent in Belkins' managed outreach in 2025, the follow-ups (steps 2 to 6 of a sequence) brought 58.6% of all replies, and the first email brought 41.4%. Belkins calls 3 to 5 steps the practical sweet spot for most B2B email sequences. Those are Belkins' own campaigns, not these templates. Belkins builds Dylan. We publish no reply rate for the templates on this page. ### Template: the second email Send it when the first email got no reply and you have one new fact. Not a reminder: a reason to read again. Subject: {{topic}} at {{company}} (Send it as a reply to your first email, so the subject and the thread stay the same.) Hi {{firstName}}, it's {{yourName}} at {{yourCompany}} again. I'm writing once more because {{reason}}. One thing I left out: {{detail}}. Is this worth a short call, or is the timing wrong? If not, reply "no" and I won't write again. Best, {{yourName}} Example, filled in (invented companies and people). Subject: fuel cards at nordfeld Hi Maya, it's Alex at Harrow Line again. I'm writing once more because Nordfeld's Ohio site opens soon, and fuel cards are easier to set up before the first trucks arrive. One thing I left out: each card can be limited to fuel only, so a lost card buys nothing else. Is this worth a short call, or is the timing wrong? If not, reply "no" and I won't write again. Best, Alex ### Template: the last email The third email in this shape is the last. It says so, leaves a door open for later and keeps the way out. Subject: {{topic}} at {{company}} (Send it in the same thread as the first two emails.) Hi {{firstName}}, it's {{yourName}} at {{yourCompany}}, with my last note on this. I wrote because {{reason}}, and I don't want to fill your inbox. Would it be fine if I wrote again in {{month}}? If you'd rather I didn't, reply "no" and I won't write again. Best, {{yourName}} Example, filled in (invented companies and people). Subject: fuel cards at nordfeld Hi Maya, it's Alex at Harrow Line, with my last note on this. I wrote because Nordfeld just opened a second warehouse in Ohio, and I don't want to fill your inbox. Would it be fine if I wrote again in March? If you'd rather I didn't, reply "no" and I won't write again. Best, Alex ### What should a follow-up never say? - **"Just following up on my last note"** when there was no last note. A follow-up is a reply to an email you really sent. - **"Just following up", "circling back" or "bumping this"** with nothing new. If you have nothing to add, the follow-up is noise. - **A fake "Re:" or "Fwd:"** on a first email. A real reply in a real thread is fine; a pretend one is a disguise. - **Guilt or pressure**, such as "I guess you're busy" or "last chance". - **More than the first email had**: more links, an attachment, a second ask. ### When should you stop following up? - **On the first reply.** Any reply, even "not now", stops every scheduled email to that person. Dylan does this by rule: the next email stops the moment the reply is read, before any AI sees it. - **On a no, and on every opt-out.** The [FTC's CAN-SPAM guide](https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business) says opt-outs must be honored within 10 business days, and the law makes no exception for business-to-business email. - **After the last email.** If you said it was the last, it is. - **When a whole company goes quiet.** Pause there instead of writing harder. [Cold email deliverability in 2026](https://meetdylan.ai/blog/cold-email-deliverability-2026) explains why. ### When should you send a follow-up? In the recipient's morning. In [Belkins' data](https://belkins.io/blog/cold-email-response-rates), emails sent between 8 AM and noon had the best reply rate, 0.54%. We do not set a fixed number of days between emails here: give each email its own reason, and send it when the reason is true. ### How does Dylan follow up? Dylan writes, follows up and answers replies from his own mailboxes, in the shape of the templates above. You approve the first emails of every new angle before anything is sent. Read [how Dylan writes](https://meetdylan.ai/how-dylan-writes), or grade your own follow-up with the [cold email grader](https://meetdylan.ai/tools/cold-email-grader). If an AI agent sends any of these, change the first line so it says so and names the company: "I'm Dylan, an AI agent working with Harrow Line." Every first email Dylan sends opens that way. [Why Dylan says he is an AI](https://meetdylan.ai/blog/why-dylan-says-hes-an-ai). Sources: - Sales follow-up statistics in B2B: Belkins' 2026 study (updated 2026-06-26): https://belkins.io/blog/sales-follow-up-statistics - What are B2B cold email response rates? Belkins' 2026 study: https://belkins.io/blog/cold-email-response-rates - CAN-SPAM Act: A Compliance Guide for Business (FTC): https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business --- # Page: Meeting request template URL: https://meetdylan.ai/resources/cold-email-templates/meeting-request ## A cold email template for asking for a meeting. A cold email asking for a meeting works when the reason comes first and the ask is small and exact. Say who you are, why this person and why now, then offer two real times with the day, the date and the zone. End with an easy way to say no. ### The meeting request template Subject: 20 minutes on {{topic}} Hi {{firstName}}, I'm {{yourName}} at {{yourCompany}}. I'm writing because {{reason}}. {{yourCompany}} {{offer}}. Would {{time1}} or {{time2}} work for 20 minutes? If not, reply "no" and I won't write again. Best, {{yourName}} Example, filled in (invented companies and people). Subject: 20 minutes on fuel cards Hi Maya, I'm Alex at Harrow Line. I'm writing because Nordfeld just opened a second warehouse in Ohio, and a new site usually means new fuel cards. Harrow Line puts every vehicle on one card with its own spend limit. Would Thursday, Oct 22, 10:30 Eastern or Friday, Oct 23, 14:00 Eastern work for 20 minutes? If not, reply "no" and I won't write again. Best, Alex ### When should you ask for a meeting in the first email? When you are fairly sure this is the person who decides, and the reason to write is strong and specific. If you are not sure who owns the topic, ask for a name first with the [right-person template](https://meetdylan.ai/resources/cold-email-templates#right-person). If the reason is weak, no template saves the email. ### How do you suggest a time in a cold email? Write times the way a calendar shows them: the day, the date, the time and the zone. | Write this | Not this | | --- | --- | | Thursday, Oct 22, 10:30 Eastern | Next Thursday at 10.30am-ish? | | Friday, Oct 23, 14:00 Eastern | Sometime later this week | | One booking link, if you use one | A booking link, a deck and three case studies | Two times give the reader a choice without a back-and-forth. A booking link counts as a link: plain emails carry few links, no attachments and no tracking pixels. ### What should a meeting request not do? - Ask for "a quick call" with no reason and no time. - Make several asks at once: a meeting, a referral and a question. - Open with "I hope this email finds you well". - Promise results you cannot show, or use words like "guaranteed" and "risk-free". - Invent urgency the reader does not have. ### What happens when they say yes? Send the calendar invite at once, for the time they picked, with one line on what the 20 minutes will cover. When Dylan books for you, the meeting goes into your calendar, and you pay only when someone inside your meeting definition joins the call. [What counts as a held meeting](https://meetdylan.ai/blog/what-counts-as-a-held-meeting). If an AI agent sends any of these, change the first line so it says so and names the company: "I'm Dylan, an AI agent working with Harrow Line." Every first email Dylan sends opens that way. [Why Dylan says he is an AI](https://meetdylan.ai/blog/why-dylan-says-hes-an-ai). --- # Page: Cold email subject lines URL: https://meetdylan.ai/resources/cold-email-templates/subject-lines ## Cold email subject lines a person would type. A good cold email subject line is a few lowercase words that say what the email is about, the way a person would type them. It matches the email, names something true about the reader and never pretends to be a reply. Below are six patterns with examples, and the lines to avoid. ### Six subject line patterns Each pattern names what the email is about, in the reader's terms. The examples use invented companies. - What and for whom: {{topic}} at {{company}} (example: fuel cards at nordfeld). Most first emails. - Their news: your {{event}} (example: your second ohio warehouse). The reason to write is something that just happened at their company. - Where it applies: {{topic}} across your {{place}} (example: fuel across your ohio sites). What you sell depends on where they work. - Their own question: {{topic}} for the {{event}}? (example: fuel cards for the new site?). The reader would ask the question themselves. - The meeting: 20 minutes on {{topic}} (example: 20 minutes on fuel cards). With the meeting request template. - The right person: who looks after {{topic}}? (example: who looks after fuel cards?). With the right-person template. ### Should cold email subject lines be lowercase? Yes. Dylan writes every subject line in lowercase, the way a person types it. Short acronyms such as AI or CRM are fine. Title Case, capital letters for emphasis and exclamation marks read like a campaign, and the [cold email grader](https://meetdylan.ai/tools/cold-email-grader) marks them. ### Can you use Re: or Fwd: in a cold email subject line? Not on a first email. A fake "Re:" pretends to continue a conversation that never happened, and the [FTC's CAN-SPAM guide](https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business) says subject lines must not deceive. A follow-up sent as a real reply in the thread of your first email is different: that Re: is true. ### How long should a cold email subject line be? A few words. We publish no ideal length: we have no data of our own on subject lines, and a length rule matters less than a subject that matches the email. If the subject would make sense on any email to anyone, it is too vague. ### What to write, and what not to ### What subject line should a follow-up use? The first email's, by replying in the same thread. The reader sees what came before, and nobody is misled. [Follow-up email templates](https://meetdylan.ai/resources/cold-email-templates/follow-up). ### Grade a subject line The [cold email grader](https://meetdylan.ai/tools/cold-email-grader) checks the subject line with the rest of a first email: lowercase gets full marks, a fake Re: or Fwd:, an exclamation mark or Title Case gets none. It runs in your browser. If an AI agent sends any of these, change the first line so it says so and names the company: "I'm Dylan, an AI agent working with Harrow Line." Every first email Dylan sends opens that way. [Why Dylan says he is an AI](https://meetdylan.ai/blog/why-dylan-says-hes-an-ai). Sources: - CAN-SPAM Act: A Compliance Guide for Business (FTC): https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business --- # Cold email templates, in full URL: https://meetdylan.ai/resources/cold-email-templates ## The first cold email URL: https://meetdylan.ai/resources/cold-email-templates#first-email When to use it: You write to someone for the first time, and you have a real reason to write to them now. Subject: {{topic}} at {{company}} Hi {{firstName}}, I'm {{yourName}} at {{yourCompany}}. I'm writing because {{reason}}. {{yourCompany}} {{offer}}. Would a short call next week be useful? If not, reply "no" and I won't write again. Best, {{yourName}} Example, filled in (invented companies and people). Subject: fuel cards at nordfeld Hi Maya, I'm Alex at Harrow Line. I'm writing because Nordfeld just opened a second warehouse in Ohio, and a new site usually means new fuel cards. Harrow Line puts every vehicle on one card with its own spend limit. Would a short call next week be useful? If not, reply "no" and I won't write again. Best, Alex Why it works: - The first line says who is writing and for which company, so a stranger can judge the email at a glance. - The reason belongs to this person, this month. It is the one line a merge field cannot fake. - One small ask, so a reply takes one word. - The last line is an obvious way out, and you keep the promise it makes. What not to do: - Opening with "I hope this email finds you well" or "I wanted to reach out". Those lines could go to anyone. - Sending it with the reason field empty or vague. Without a reason, it is a mass email with a first name. - Adding a second question, a deck or a row of links. ## The first email from an AI agent URL: https://meetdylan.ai/resources/cold-email-templates#ai-first-email When to use it: An AI agent writes for your company. The first sentence says so, and names the company. Subject: {{topic}} across your {{place}} Hi {{firstName}}, I'm {{yourName}}, an AI agent working with {{yourCompany}}. I'm writing because {{reason}}. {{yourCompany}} {{offer}}. Would a 20-minute review be useful? If not, reply "no" and I won't write again. Example, filled in (invented companies and people). Subject: fuel across your ohio sites Hi Maya, I'm Dylan, an AI agent working with Harrow Line. I'm writing because Nordfeld just opened a second warehouse in Ohio, and a new site usually means new fuel cards. Harrow Line puts every vehicle on one card with its own spend limit. Would a 20-minute review of your fuel spend be useful? If not, reply "no" and I won't write again. Why it works: - The disclosure sits in the first line, not in small print under the signature. A disclosure nobody reads is not a disclosure. - It names the company the agent works for, so the reader knows whose brand is on the email. - The rest has the shape of any good first email: a reason, one ask, a way out. What not to do: - A human first name and no mention of AI. A disguise fails twice: once for the email, and again for the company named in it. - Putting the disclosure in the signature, where nobody reads it. - A way out that depends on the agent reading the reply correctly. Any reply should stop the next email, by rule. ## Asking for a meeting URL: https://meetdylan.ai/resources/cold-email-templates#meeting-request When to use it: You know this is the right person and the reason is strong, so you ask for a meeting at two real times. Subject: 20 minutes on {{topic}} Hi {{firstName}}, I'm {{yourName}} at {{yourCompany}}. I'm writing because {{reason}}. {{yourCompany}} {{offer}}. Would {{time1}} or {{time2}} work for 20 minutes? If not, reply "no" and I won't write again. Best, {{yourName}} Example, filled in (invented companies and people). Subject: 20 minutes on fuel cards Hi Maya, I'm Alex at Harrow Line. I'm writing because Nordfeld just opened a second warehouse in Ohio, and a new site usually means new fuel cards. Harrow Line puts every vehicle on one card with its own spend limit. Would Thursday, Oct 22, 10:30 Eastern or Friday, Oct 23, 14:00 Eastern work for 20 minutes? If not, reply "no" and I won't write again. Best, Alex Why it works: - Two real times, written the way a calendar shows them: the day, the date, the time and the zone. Saying yes takes one word. - The ask is small and exact: 20 minutes at a named time, not "some time to connect". - The reason comes before the ask, so the meeting has a purpose the reader can see. - It still offers a way to say no. A meeting request without one reads like pressure. What not to do: - "Next Thursday at 10.30am-ish?" A loose time makes the reader do the work. - Asking for a meeting and a referral and a reply to a question, all in one email. - Attaching a deck. Plain emails carry no attachments, and a first email should not need one. ## The second email: one new thing URL: https://meetdylan.ai/resources/cold-email-templates#follow-up-second When to use it: Your first email got no reply, and you have one new fact worth a second email. Subject: {{topic}} at {{company}} (Send it as a reply to your first email, so the subject and the thread stay the same.) Hi {{firstName}}, it's {{yourName}} at {{yourCompany}} again. I'm writing once more because {{reason}}. One thing I left out: {{detail}}. Is this worth a short call, or is the timing wrong? If not, reply "no" and I won't write again. Best, {{yourName}} Example, filled in (invented companies and people). Subject: fuel cards at nordfeld Hi Maya, it's Alex at Harrow Line again. I'm writing once more because Nordfeld's Ohio site opens soon, and fuel cards are easier to set up before the first trucks arrive. One thing I left out: each card can be limited to fuel only, so a lost card buys nothing else. Is this worth a short call, or is the timing wrong? If not, reply "no" and I won't write again. Best, Alex Why it works: - It sits in the same thread as your first email, so the reader sees what came before. That is a real follow-up, not a fake Re: on a first email. - It adds one new thing instead of repeating the first email, so there is something new to answer. - It says again who is writing and keeps the way out, because the reader may never have opened the first email. - One question, with an easy answer either way. What not to do: - "Just following up" or "circling back" with nothing new to say. - A new subject line that hides that this is the same pitch. - Guilt lines such as "I guess you're busy". ## The last email: close the loop URL: https://meetdylan.ai/resources/cold-email-templates#follow-up-last When to use it: You have written twice with no reply. This email says it is the last, and it is. Subject: {{topic}} at {{company}} (Send it in the same thread as the first two emails.) Hi {{firstName}}, it's {{yourName}} at {{yourCompany}}, with my last note on this. I wrote because {{reason}}, and I don't want to fill your inbox. Would it be fine if I wrote again in {{month}}? If you'd rather I didn't, reply "no" and I won't write again. Best, {{yourName}} Example, filled in (invented companies and people). Subject: fuel cards at nordfeld Hi Maya, it's Alex at Harrow Line, with my last note on this. I wrote because Nordfeld just opened a second warehouse in Ohio, and I don't want to fill your inbox. Would it be fine if I wrote again in March? If you'd rather I didn't, reply "no" and I won't write again. Best, Alex Why it works: - It says this is the last email, and then it is. A promise to stop only counts if you keep it. - It leaves a door open for later instead of pushing for now. - It restates the reason in one line, for a reader who never opened the first two. What not to do: - Calling it the last email and then sending another one. - A "breakup" line meant to sting, such as "I'll assume this isn't a priority". - Writing again after a no, from another address or another colleague. ## Finding the right person URL: https://meetdylan.ai/resources/cold-email-templates#right-person When to use it: You have a reason to write to the company, but you are not sure who owns the topic. Subject: who looks after {{topic}}? Hi {{firstName}}, I'm {{yourName}} at {{yourCompany}}. I'm writing because {{reason}}, and I'm not sure who at {{company}} looks after {{topic}}. Is that you, or is there someone better to write to? If not, reply "no" and I won't write again. Best, {{yourName}} Example, filled in (invented companies and people). Subject: who looks after fuel cards? Hi Maya, I'm Alex at Harrow Line. I'm writing because Nordfeld just opened a second warehouse in Ohio, and I'm not sure who at Nordfeld looks after fuel cards. Is that you, or is there someone better to write to? If not, reply "no" and I won't write again. Best, Alex Why it works: - It asks for a name, not a meeting. That is a smaller ask, and it is easy to answer. - It still gives the reason, so whoever it is forwarded to knows why you wrote. - One question and one way out. What not to do: - Writing to five people at the same company on the same day. - Pretending someone referred you when nobody did. --- # Changelog URL: https://meetdylan.ai/changelog ## 2026-10-09: The pipeline calculator - A free tool at /tools/pipeline-calculator: put in your quota, average deal size and win rate, and see the held first meetings you need each month. - It prices that number in every way to pay for Dylan, from the prices on the pricing page. - Fill in an example shows round values marked Example, not a benchmark. You can email yourself the result, or join the waitlist with these numbers. ## 2026-10-09: The SDR cost calculator - A free tool at /tools/sdr-cost-calculator: put in your SDR pay, tools and held meetings, and see your cost per held meeting next to Dylan's price. - Fill in an example shows round values marked Example, not a benchmark. You can email yourself the result. ## 2026-10-09: The deliverability check - A free tool at /tools/deliverability-check: type a domain and see its MX, SPF, DKIM and DMARC records in public DNS, each explained, with the fix. - It reports only what it measured, with no score. A lookup that gets no answer reads Could not check. - Powered by Folderly. You can email yourself the report. ## 2026-10-09: The cold email grader - A free tool at /tools/cold-email-grader: paste a first cold email and see which of Dylan's nine rules it meets, with one fix per rule. - It grades in your browser. What you paste is not sent to us. ## 2026-10-09: Free tools - A new page, Free tools, at /tools, lists every tool with what you put in and what you get back. ## 2026-10-09: Resources - A new page, Resources, at /resources, ties the blog, the docs, the free tools, the buyer's guide, the glossary, the FAQ, the film and the changelog together. ## 2026-10-09: The AI SDR buyer's guide - Every post from the blog in one PDF at /resources/buyers-guide, free for your email. - The download link works for 7 days. We email it to you only if you tick the box. - Each post and the blog page link to it. ## 2026-10-09: The glossary - A new page, Glossary, at /glossary: each term once, in the words the rest of the site uses, grouped by topic. - The docs search finds glossary terms too. ## 2026-10-09: The FAQ has its own page - Every question from the home page now has its own page at /faq, with a link to each answer. - A new question says how the monthly plan works: unused included meetings roll over one month, and it is month to month. ## 2026-10-09: Trusted partners - A new page, Trusted partners, at /partners: Belkins builds Dylan, and his deliverability is powered by Folderly. - The About page shows both. ## 2026-10-09: New menus, invitations and privacy - The header groups its links into Product, Tools, Resources and Company menus. On a phone, Menu opens them on one sheet. - The footer has five groups, with every free tool and resource. - Wherever the site says how invitations work, it now says: We invite 10 teams every two weeks. - The monthly plan: unused included meetings roll over one month, and you can cancel any time before the next billing date. - Your waitlist ticket can email you your place and link. - The privacy notice explains the free tools, the result emails, the buyer's guide, payments and how we count page views. We count them with Vercel Web Analytics, which sets no cookies. ## 2026-10-08: The waitlist and the ways to pay we are testing - A new page, Join the waitlist, in five short steps: you, your company, your buyers, your sales and your deck. The first step saves your entry. - You can add your sales deck as a file or paste a link to it. The privacy notice says how long a deck is kept. - Ways to pay: an overview and one page for each way to pay we are testing: a monthly plan, pay per intent, pay per signup, pay per qualified opportunity, Dylan on your inbound, and Dylan for partners, by application. - Pricing shows the monthly plan next to the prices per held meeting, and the calculator compares the two. - The button in the header is now Join the waitlist, on every page. The full brief stays on the home page under Send the full brief. - In the home page's example calendar, each booked meeting arrives as a notification in a stack. A Sound switch plays a soft chime; it is off until you turn it on. ## 2026-10-06: The blog names its author - Every post and the blog page show who wrote and reviewed it: Vlad Podoliako, Founder and CEO, Belkins. - His name links to his page on belkins.io, and each post's social image carries it too. - The RSS feed names him as the author of each post. - The reading time on each blog card now matches the time on the post itself. ## 2026-10-06: One contact address - The footer, the privacy notice, the stop pages and llms.txt now all give one address: dylan@meetdylan.ai. ## 2026-10-06: Accessibility fixes - Errors in the brief are read out by screen readers, and focus goes back to the form when a save fails. - Text that fell short of WCAG AA contrast was fixed, in light and dark. - The copy buttons on the design system page are named by their visible text. - The small icons in the example product pictures are no longer links: they are pictures of an app, not navigation. ## 2026-10-06: Launch hardening - The stop form explains that a shared email domain such as gmail.com cannot be stopped as a whole, and asks for the full address instead. - The example product screens match the film. - The founder's name and the Folderly mention link to their sources. - The font files are smaller, cut down to what the site uses, and the film's poster on phones is a smaller file. - The site is written in US English, and blog titles are under 60 characters. ## 2026-10-06: The site is built - The home page, with a live calendar, the dated ramp and the brief behind Get my meeting plan. - The 42-second film, with every chapter described in words. - The blog, with eight posts and an RSS feed. - The design system, The Meeting. - The privacy notice, and a form on the home page to stop Dylan's emails. - A door for the terminal: curl https://meetdylan.ai/join with a work email stores a short brief. --- # Post: Agents judge, people approve, code protects: how Dylan is built URL: https://meetdylan.ai/blog/agents-judge-people-approve-code-protects Published: 2026-10-05 By Vlad Podoliako, Founder and CEO, Belkins > How Dylan splits the work: AI agents make the judgment calls, people approve what goes out, and plain code enforces the rules that must never bend. Dylan is built on one rule: agents judge, people approve, code protects. Each kind of decision goes to whoever is best and safest at it. From the buyer's side of the table, that is what good AI agent guardrails look like, and it is why the protections are never left to the AI. ## A bank, not a chatbot Think of a well-run bank. A loan officer judges the application, a manager signs off on anything above a limit, and the core system will not pay out more than the account holds, however persuasive the request. The officer can use judgment freely precisely because the worst outcomes are impossible. Dylan works the same way: an agent with room to think, a person with the pen, and rules underneath that nobody talks their way past. ## Agents judge The work that needs judgment goes to AI agents: researching the companies in your market, deciding who fits your brief and why now, writing each email, reading replies, answering the routine ones and finding a time. No rule can be written for these in advance; they need reading, weighing and writing at a scale no team can staff. For example, a company that opened a second warehouse last month may be a perfect reason to write, or irrelevant to what you sell; only reading tells you which. A reply that says "not me, try Priya in finance" is not a no but a referral, and a rule that sorted replies by keyword would throw it away. ## People approve Some decisions should never be automatic, because they carry your name or your money. You approve: - the plan: who Dylan will write to, why, and the forecast; - the first emails of every new angle; - any new segment or new spend. Why every new angle, and not just the first email ever? Because each angle is a new promise in your name: a new claim, a new reason, a new tone. You should see every promise once before it is repeated at scale. Before the plan reaches you, a person at Belkins reviews it. [Belkins](https://belkins.io/), the B2B lead generation agency behind Dylan, has run outbound since 2017 for 1,000+ clients across 50+ industries and holds a [4.9 rating on Clutch from 230+ reviews](https://clutch.co/profile/belkins). Once Dylan is running, he answers routine replies himself and hands you anything about pricing, legal matters or complaints. On his own, he acts for only two reasons: to protect you (pacing, pausing, keeping your do-not-contact list), or to carry out what you already approved. [SaaStr](https://www.saastr.com/6-months-of-ai-sdrs-whats-worked), which runs several AI SDRs, advises starting agents in "draft mode," where the agent suggests and a person approves, and six months in it still kept its high-value prospects there. Human in the loop is not a phase you grow out of. It is where you put people on purpose. ## Code protects The rules that must never bend are plain, deterministic code: same input, same result, whatever any model thinks. Everything the agents never decide lives here. - **A reply stops sending to that person.** The moment a reply is read, every further scheduled email to that person stops, by rule, before any AI sees it. If an AI misread "please stop" as interest, the mistake could not be taken back, so the stop does not depend on reading at all. - **The do-not-contact list is checked again at send time**, not only when the list is built. A company you add this morning will not receive an email scheduled last week. - **Per-company caps.** No company gets flooded, however many good contacts it has. - **Send windows in the recipient's time zone.** Emails go out at hours that make sense where the recipient is, not at three in the morning their time. - **A 60-second undo** on every launch and every approved reply, because second thoughts are normal. - **A record of who did what.** Every action records who took it: you, a person at Belkins, an agent or the system itself. Think of a smoke detector: it does not weigh whether a fire is interesting; it goes off. That is the property you want from anything whose job is to prevent the one mistake you cannot undo. And if a prospect ever asks your CEO why they were contacted, the record can answer in minutes: which plan, who approved it, which email went out and when. "The AI decided" is not an answer anyone should have to give. ## Why AI agent guardrails belong in code, not in prompts An instruction in a prompt is a promise. A rule in code is a guarantee. Most of the time the two look identical; the difference shows on the day something goes wrong. In September 2026, [404 Media reported](https://www.404media.co/ai-agent-platform-reinvents-spam-floods-inboxes-worldwide/) on agents from the iLands platform that told recipients they would not follow up unless someone responded, then "messaged us multiple times with the same pitch." The founder's response was a list of controls being added after the fact: an unsubscribe option, "cross-agent deduplication, rate limits, and stop-contact controls." None of those should depend on an agent remembering its instructions. They belong underneath the agent, where no amount of clever reasoning can route around them. That is the whole design: let the model be smart where smart helps, and make it irrelevant where smart is a risk. ## What to do next For you, the split means an agent's speed without handing it your name. An agent can be wrong about a sentence, and you catch that at approval; it is built so it cannot keep writing to someone who replied, or email a company you told us to avoid. It is also why Dylan can [say plainly that he is an AI](https://meetdylan.ai/blog/why-dylan-says-hes-an-ai), and why we accept being paid only when [a meeting actually happens](https://meetdylan.ai/blog/what-counts-as-a-held-meeting). When you evaluate any AI agent that writes in your name, ask three questions: which decisions does the AI make, which do you approve, and which are enforced in code no matter what the AI says? If the third list is empty, the first one is too long. Sources: - Belkins, B2B lead generation agency: https://belkins.io/ - Belkins reviews on Clutch: https://clutch.co/profile/belkins - 6 Months of AI SDRs: What's Worked (SaaStr): https://www.saastr.com/6-months-of-ai-sdrs-whats-worked - AI Agent Platform Reinvents Spam, Floods Inboxes Worldwide (404 Media): https://www.404media.co/ai-agent-platform-reinvents-spam-floods-inboxes-worldwide/ --- # Post: The AI SDR hype is over. Here is what actually survived URL: https://meetdylan.ai/blog/ai-sdr-hype-what-survived Published: 2026-10-05 By Vlad Podoliako, Founder and CEO, Belkins > AI SDRs promised to replace sales teams. Most early rollouts disappointed. What survived: proven playbooks, signals, people at decision points, inbound. The first wave of AI SDRs sold a simple idea: replace your sales development team with software that never sleeps. That idea mostly failed. What survived is narrower and more useful: agents doing the work that scales, and people making the calls that carry risk. ## What the AI SDR wave promised, and what broke The pitch had three parts: replace the team, send without limit, and run on its own once set up. Each part broke on contact with real buyers. **Replacement.** In an informal [SaaStr reader survey](https://www.saastr.com/83-percent-of-you-havent-gotten-ai-sdrs-to-work-yet) in late 2024, 83% said they had gotten nothing from AI SDRs yet, and only 3% reported real revenue. The best-known story is 11x, an AI SDR startup backed by Andreessen Horowitz and Benchmark. In March 2025, [TechCrunch reported](https://techcrunch.com/2025/03/24/a16z-and-benchmark-backed-11x-has-been-claiming-customers-it-doesnt-have/) that 11x had shown logos of companies that said they were not customers, and that most early customers used break clauses, typically at three months, to leave. A former employee said some customers had hoped to replace "an entire outbound sales team." 11x disputed parts of the reporting, said its retention was 79%, and said performance "ultimately relies on the quality of user input." Remember that last line. **Volume.** Cheap writing made cheap sending, and buyers noticed. In [Gartner's survey](https://www.gartner.com/en/newsroom/press-releases/2025-06-25-gartner-sales-survey-finds-61-percent-of-b2b-buyers-prefer-a-rep-free-buying-experience) of 632 B2B buyers, 73% said they actively avoid suppliers who send irrelevant outreach. [Belkins' study of 7.5 million cold emails](https://belkins.io/blog/cold-email-response-rates) shows the crowding: reply rates fell from 0.50% in the first half of 2025 to 0.40% in the second, a 20% drop within one year, which the study blames on saturation, stricter filtering and finite attention. **Set and forget.** SaaStr [reports](https://www.saastr.com/6-months-of-ai-sdrs-whats-worked) 15 to 20 hours a week of human oversight for its own AI SDRs, and says it bluntly: "This is not set-and-forget technology." Notice what the three failures share: each treated outbound as a production problem (more emails, fewer people) when it is mostly a judgment problem (who to write to, why now, and what to say when they answer). Software made production nearly free. It did not make judgment free, and that is where everything that survived lives. ## Survivor one: proven playbooks and real data SaaStr's first lesson is that AI SDRs "scale what's already working" and cannot fix what is broken. If outbound did not work when people did it, an agent will not rescue it. It will do the wrong thing faster, in more inboxes. Most readers skip one detail: SaaStr's outbound agents mostly wrote to people already in its own database ("About 90% of contacts are ours"). Strong numbers on warm contacts say little about cold outreach, so before you benchmark against any case study, ask how cold the list really was. That is what "the quality of user input" means in practice. An agent is only as good as what it is told about the market, the offer and the buyer. That input is a playbook, and someone has to have proven it first. ## Survivor two: a reason to write now The emails that still work carry a reason that belongs to this person, this month: a new site, a new leader, a new market. A signal answers the question every recipient asks before replying: why me, and why now? The Belkins study ends on the same note: "relevant message, right person, right moment." Compare two openings to the same operations leader, both invented for this example: "I help logistics companies cut costs," and "You opened a second warehouse in Ohio in May, and a new site usually means a new set of fuel cards." Only the second gives the reader something to answer, and only the second could not have been sent to everyone else on the list. ## Survivor three: people at the decision points The setups that hold up put people exactly where a mistake would be expensive. SaaStr advises starting agents in "draft mode," where the agent suggests and a person approves, and six months in it still kept high-value prospects there. Buyers want the same thing. In [Gartner's 2026 survey](https://www.gartner.com/en/newsroom/press-releases/2026-05-20-gartner-survey-finds-sixty-nine-percent-of-b-two-b-buyers-turn-to-sales-reps-to-validate-ai-generated-insights) of 645 B2B buyers, 69% said they prefer to validate AI-generated insights with sales reps. An agent can open the conversation, but a person still has to be reachable when it matters. ## Survivor four: inbound first The biggest win in SaaStr's account was not cold outbound at all. It was an inbound agent that answers website visitors and books them in seconds to minutes, where the old handoff took one to three days. In October, according to SaaStr, 70% of its closed revenue came through that agent. The honest lesson for anyone shopping for outbound, including from us: if inbound leads wait a day for a reply, fix that first. People who already raised their hand are the cheapest meetings you will ever book. ## What to do next: five questions for any AI SDR Before you sign with any AI SDR vendor, ask these and get the answers in writing: 1. **Who approves the plan and the first emails before anything is sent?** If nobody does, your brand is the test environment. 2. **What happens, mechanically, when someone replies "stop"?** Listen for a rule in the system, not an instruction to the model. 3. **Whose domain sends the emails?** If it is yours, a bad month lands on the address your customers and invoices come from. 4. **What do you pay if no meetings come?** That tells you who carries the risk, whatever the brochure says. 5. **Does the agent say it is an AI, and who it works for?** If not, ask what happens to your name when a prospect finds out. A vendor who answers all five clearly has learned from the first wave. Our answers are in [how Dylan is built](https://meetdylan.ai/blog/agents-judge-people-approve-code-protects) and [why he charges per held meeting](https://meetdylan.ai/blog/why-dylan-charges-per-held-meeting). To weigh the options side by side, see [Dylan next to AI SDR software](https://meetdylan.ai/compare/ai-sdr-software). Sources: - 83% of You Haven't Gotten AI SDRs to Work Yet (SaaStr, November 2024): https://www.saastr.com/83-percent-of-you-havent-gotten-ai-sdrs-to-work-yet - a16z- and Benchmark-backed 11x has been claiming customers it doesn't have (TechCrunch, March 2025): https://techcrunch.com/2025/03/24/a16z-and-benchmark-backed-11x-has-been-claiming-customers-it-doesnt-have/ - Gartner Sales Survey Finds 61% of B2B Buyers Prefer a Rep-Free Buying Experience (June 2025): https://www.gartner.com/en/newsroom/press-releases/2025-06-25-gartner-sales-survey-finds-61-percent-of-b2b-buyers-prefer-a-rep-free-buying-experience - What are B2B cold email response rates? Belkins' 2026 study: https://belkins.io/blog/cold-email-response-rates - 6 Months of AI SDRs: What's Worked (SaaStr): https://www.saastr.com/6-months-of-ai-sdrs-whats-worked - Gartner Survey Finds 69% of B2B Buyers Turn to Sales Reps to Validate AI-Generated Insights (May 2026): https://www.gartner.com/en/newsroom/press-releases/2026-05-20-gartner-survey-finds-sixty-nine-percent-of-b-two-b-buyers-turn-to-sales-reps-to-validate-ai-generated-insights --- # Post: Cold email deliverability in 2026: the rules that matter for B2B URL: https://meetdylan.ai/blog/cold-email-deliverability-2026 Published: 2026-10-05 By Vlad Podoliako, Founder and CEO, Belkins > Gmail's bulk sender rules get the headlines, but B2B cold email is decided by corporate gateways, Microsoft tenant limits and new-domain checks. Most cold email deliverability advice is written around Gmail's consumer rules. If you sell to businesses, the rules that decide whether you land are set elsewhere: in the security gateways in front of corporate mailboxes, in Microsoft's new limits for fresh tenants, and in the suspicion every new domain starts with. Meanwhile, the numbers you used to steer by are going dark. ## The famous rules are about consumer inboxes Google defines a bulk sender as anyone who sends "close to 5,000 messages or more to personal Gmail accounts within a 24-hour period," and its [FAQ](https://support.google.com/mail/answer/14229414?hl=en) is explicit about scope: "Sender requirements and Google enforcement apply only when sending email to personal Gmail accounts," not Google Workspace accounts. Microsoft's equivalent, enforced since May 2025, covers [senders of 5,000 or more emails a day](https://dmarcian.com/microsoft-enforces-spf-dkim-dmarc/) to its consumer addresses at outlook.com, hotmail.com and live.com. That does not make business inboxes easier. It means the gatekeepers are different, and less forgiving. Set up SPF, DKIM and DMARC anyway. SPF lists who may send for your domain, DKIM signs each message, and DMARC ties both to your From domain and tells receivers what to do when they fail. Every gatekeeper below checks them; they are the price of entry, not an advantage. ## B2B mail meets a gateway first Many companies route incoming mail through a secure email gateway before it reaches Microsoft 365 or Google Workspace, and Proofpoint and Mimecast are the names [you will see most in B2B bounce messages](https://willitinbox.com/blog/corporate-email-filters-proofpoint-mimecast). Think of a corporate mailroom with a security scanner: every envelope is opened and checked before it reaches anyone. The gateway checks the sender's reputation, scans every link, opens attachments in a sandbox and looks for impersonation. Two of its habits matter most for cold email: - **It quarantines quietly.** The default for suspicious mail is quarantine, not rejection. Your sending tool logs a successful delivery, and the recipient never sees the email unless someone in IT releases it. - **It clicks your links.** Gateways rewrite and scan links, and those automated fetches register as opens and clicks. Your most engaged account may be a sandbox. Few teams check which gateway their targets use, though an MX lookup shows it in seconds. And because a quarantine looks like a delivery, the warning signs are indirect: a company that used to answer goes silent, or a contact says they never got your email. ## New domains and new tenants start on probation [Spamhaus](https://www.spamhaus.org/resource-hub/domain-reputation/best-practice-for-owners-of-a-newly-registered-domain-part-3/) notes that for roughly the first 30 days after registration, most threat-intelligence companies flag a new domain and watch it for mass sending. Criminals buy domains in bulk and burn them, so a domain with no history looks like one of theirs. Spamhaus's advice: "Don't send a bulk email run with your newly acquired domain name." Show who owns the domain instead of hiding it behind privacy masking, connect it visibly to your brand, and build volume slowly with recipients who engage. Microsoft has added a probation of its own. From mid-September 2026, new Exchange Online tenants get [10% of their normal external-recipient quota](https://emailexpert.com/microsoft-puts-new-exchange-online-tenants-on-60-day-sending-probation/) in their first 30 days and 25% until day 60, and trial tenants drop from 5,000 external recipients a day to 500. The detail most teams miss is that this limit covers the whole tenant, not one mailbox. As emailexpert puts it, "a sales team using Exchange Online for outreach could therefore prevent the rest of the business from sending ordinary external email." An aggressive campaign from your main tenant can stop your finance team sending invoices. ## The telemetry is disappearing Four numbers outbound teams relied on are fading: - **Opens.** [Belkins disabled open tracking](https://belkins.io/blog/cold-email-response-rates) for its whole 2025 study because the tracking pixel "was hurting deliverability throughout the industry in 2024." - **Clicks.** Gateway scanners click links automatically, so click data from corporate domains is polluted. - **Reputation.** Google says the domain and IP reputation dashboards in Postmaster Tools [will be retired](https://support.google.com/mail/answer/16594218?hl=en), because "reputation data is not easily actionable for most senders." - **"Delivered."** A quarantined email counts as delivered. What is left is what a person does: replies and meetings. Belkins now measures reply rate against every email sent rather than against opens, a stricter number and the only honest denominator left. ## Eight cold email deliverability rules for 2026 1. Keep cold email off your main domain and your main Microsoft tenant. 2. Authenticate with SPF, DKIM and DMARC, aligned with your From domain. 3. Give new domains time before volume; the first month is when they are watched hardest. 4. Write plain emails: no attachments, few links, no tracking pixels. 5. Cap how much any one company receives per day, and spread volume across mailboxes. 6. Send in the recipient's morning. In Belkins' data, emails sent between 8 AM and noon had the best reply rate, 0.54%. 7. Stop on the first reply, and honor every opt-out. 8. When one company goes quiet, pause there instead of retrying harder. In WillItInbox's words, "volume against a suspicious gateway confirms its judgment." Rule 5 matters twice in enterprise markets, where an account you annoy may not come back: [your market is a pond, not an ocean](https://meetdylan.ai/blog/enterprise-market-is-a-pond). ## How Dylan sends Dylan writes from his own warm domains and mailboxes, with a separate slice for each client. Your domain never sends a cold email, so your tenant, your brand domain and your invoices stay out of it. He caps sends per company, sends within set windows in the recipient's time zone, and stops writing to a person the moment their reply is read, by rule, before any AI sees it. Deliverability comes from the team behind [Folderly](https://folderly.com). The full set of protections is in [how Dylan is built](https://meetdylan.ai/blog/agents-judge-people-approve-code-protects). ## What to do next Run an MX lookup on your top 50 accounts this week. If your team sends cold email from your main domain or tenant, move it before your next campaign. And take open rate off your dashboard: put replies per email sent in its place. Sources: - Email sender guidelines FAQ (Google): https://support.google.com/mail/answer/14229414?hl=en - Microsoft Enforces SPF, DKIM, DMARC for High-Volume Senders (dmarcian): https://dmarcian.com/microsoft-enforces-spf-dkim-dmarc/ - Why Corporate Domains Eat Your Emails: Proofpoint, Mimecast, and the SEG (WillItInbox): https://willitinbox.com/blog/corporate-email-filters-proofpoint-mimecast - Best practice for owners of a newly registered domain, part 3 (Spamhaus): https://www.spamhaus.org/resource-hub/domain-reputation/best-practice-for-owners-of-a-newly-registered-domain-part-3/ - Microsoft puts new Exchange Online tenants on 60-day sending probation (emailexpert): https://emailexpert.com/microsoft-puts-new-exchange-online-tenants-on-60-day-sending-probation/ - Learn about the deprecation of the old Postmaster Tools interface (Google): https://support.google.com/mail/answer/16594218?hl=en - What are B2B cold email response rates? Belkins' 2026 study: https://belkins.io/blog/cold-email-response-rates --- # Post: Enterprise outbound math: your market is a pond, not an ocean URL: https://meetdylan.ai/blog/enterprise-market-is-a-pond Published: 2026-10-05 By Vlad Podoliako, Founder and CEO, Belkins > Only 1,138 US companies have 10,000+ employees. The outbound math for small markets, why precision beats volume, and what to do when the list runs out. Enterprise outbound is fishing in a pond, not an ocean. In 2022 there were 1,138 companies in the United States with 10,000 or more employees, and at the reply rates those companies show, one careless pass can use up most of your chances. The arithmetic says precision beats volume, and it says it loudly. ## How small the enterprise pond is The [US Census Bureau](https://www.census.gov/data/tables/2022/econ/susb/2022-susb-annual.html) counted about 6.4 million employer firms in the United States in 2022. Only 10,641 had 1,000 or more employees, and only 1,138 had 10,000 or more. Narrow that by industry, region and fit, and a product that suits one in four of the largest companies has a few hundred accounts: a list you could print on a few pages. Even the 1,000+ band is spread across every industry; narrow it to yours and you are back to a pond. Then add the second problem: big companies reply less. In [Belkins' study of 7.5 million cold emails](https://belkins.io/blog/cold-email-response-rates) sent in 2025, reply rates fell steadily with company size, from 0.72% at companies with up to 10 employees to 0.22% at 10,000 or more. The study blames structure: several people per company get similar outreach, the right person is harder to find, and decisions move slowly. ## The arithmetic of one pass Here is one pass through a pond that size. Only the first and last numbers are measured; the steps in between are round examples to replace with your own. | Step | Count | Where the number comes from | | --- | --- | --- | | US companies with 10,000+ employees | 1,138 | US Census, 2022 | | Companies that fit your offer (example: one in four) | 285 | Illustration | | People worth writing to at each (example: four) | 1,140 | Illustration | | Emails, at four per person | 4,560 | Illustration | | Replies at 0.22% per email | About 10 | Belkins study | About ten replies, and the study counts every reply, including "not interested." For a sense of how far replies sit from meetings: across all of Belkins' 2025 campaigns, 7.5 million emails booked over 1,200 appointments. At that average, these 4,560 emails would book less than one meeting. That is a whole market, worked once. Send the same thing again next month and you are writing to the same people, who now remember your name. Two of the example numbers drain the pond faster as they grow: people per company and emails per person. Only the reply rate per email can grow without draining it, and it depends on who you pick and what you say. Ponds refill, but slowly: people change jobs, companies open sites, budgets reset. The refill rate, not your sending capacity, sets how fast enterprise outbound can grow, so ask anyone promising a steady stream from a few hundred accounts where the water comes from. ## Why precision beats volume in enterprise outbound In an ocean, a bad cast costs one cast; in a pond, it scares the fish. In [Gartner's survey of 632 B2B buyers](https://www.gartner.com/en/newsroom/press-releases/2025-06-25-gartner-sales-survey-finds-61-percent-of-b2b-buyers-prefer-a-rep-free-buying-experience), 73% said they actively avoid suppliers who send irrelevant outreach. A careless email to a small market does not just fail; it can close the account to you. The good news is that averages hide an enormous spread. In the Belkins data, the gap between the best and worst industries is almost tenfold, and founders and owners reply at 0.57% while VPs reply at 0.32%. Who you write to, and why, moves the number far more than how many you write to. For large companies the study recommends multi-threaded outreach, account-level personalization and longer nurture, and says plainly: "Lower send volumes produce higher reply rates." In practice, precision comes down to three habits: - **The right person, not the highest title.** The buyer who owns the problem often sits a level or two below the top of the chart. - **A reason that belongs to this company this month.** A new site, a new leader or a new market gives a reply something to attach to. - **A pace that never floods an account.** Several people at one company should never get the same email in the same week. ## When the list runs out Every enterprise program reaches the end of its list, usually sooner than planned. The moves that work, roughly in order: 1. **Rest, don't repeat.** Leave people alone after a sequence ends; a second identical pass just asks the same question twice. 2. **Wait for signals.** A new executive, a new site or an acquisition refills the pond one event at a time. Write when there is a reason. 3. **Go wider inside the account.** Other departments and the people around the buyer each have their own reason to care. 4. **Move one size band down.** In the same study, companies with 1,001 to 5,000 employees replied at 0.27%, and the Census counts about 8,400 US firms with 1,000 to 4,999 employees. 5. **Change the channel.** Events, partners and introductions reach people that email cannot. 6. **Let inbound do its share.** Accounts that already know your name answer differently, so make sure the ones who come to you hear back fast. ## What to do next Count your pond before you buy anything: the companies that truly fit (not a database filter), times the people worth writing to at each, times the emails one careful sequence takes, times a reply rate you trust for that company size. If the answer is a few hundred companies and a few dozen replies, choose a partner who thinks in accounts, not volume, and brief them precisely; [how to brief an AI SDR](https://meetdylan.ai/blog/how-to-brief-an-ai-sdr) covers what to include. Dylan's plan does this count before anything is sent, and if your market is too small, it says so before you pay. Because a pond punishes stubbornness, he also has a stop rule: if 1,000 contacts bring no positive reply, he pauses, tells you what he heard and proposes a new angle instead of draining the rest. Sources: - 2022 SUSB Annual Data Tables by Establishment Industry (US Census Bureau): https://www.census.gov/data/tables/2022/econ/susb/2022-susb-annual.html - What are B2B cold email response rates? Belkins' 2026 study: https://belkins.io/blog/cold-email-response-rates - Gartner Sales Survey Finds 61% of B2B Buyers Prefer a Rep-Free Buying Experience (June 2025): https://www.gartner.com/en/newsroom/press-releases/2025-06-25-gartner-sales-survey-finds-61-percent-of-b2b-buyers-prefer-a-rep-free-buying-experience --- # Post: How to brief an AI SDR so it books the right meetings URL: https://meetdylan.ai/blog/how-to-brief-an-ai-sdr Published: 2026-10-05 By Vlad Podoliako, Founder and CEO, Belkins > A brief decides who gets emailed, what they read and which meetings count. The seven inputs that matter, and why to edit a draft instead of writing one. When you brief an AI SDR, you decide who gets written to, what they read and which meetings count, so the brief shapes your results more than the model behind it does. Most briefs fail for a simple reason: they ask busy people to write. The better way is to let the agent draft and to spend your time editing. ## Don't make them write, make them edit Ask a founder to describe the ideal customer on a blank page and you will get "mid-market companies that value efficiency." Show the same founder ten companies the agent thinks fit, and within a minute they will cross some out and tell you exactly why. That "why" is the brief. [SaaStr](https://www.saastr.com/6-months-of-ai-sdrs-whats-worked) lists generic training among the mistakes that sink AI SDR rollouts: "Here's our website, here are some email templates, go!" produces mediocre results. What works is specific: proof points from real conversations, the objections you actually hear, clear rules for when to bring in a person, an ICP with "examples and non-examples," and a voice that matches yours. A blank form rarely produces any of that; a draft you can mark up does, because reacting is faster than recalling. Architects know this: nobody can describe a dream house from scratch, but anyone can point at a floor plan and say the kitchen is in the wrong place. That is how Dylan's brief works: he reads your website and drafts the rest, and you correct it. ## The seven inputs of an AI SDR brief | Input | Why it matters | What people forget | | --- | --- | --- | | Your website | Every claim the agent makes must match it | The pages that are out of date | | Ten best customers | The pattern the agent looks for | Why they bought, and what triggered it | | Who to meet | Sets targeting and the meeting definition | Who not to meet | | Do-not-contact list | Protects relationships you already have | Open deals, partners and investors | | Meeting definition | Decides what counts and what is billed | Who on your side takes the call | | Calendar | Where meetings land | Real availability and buffers | | Voice and no-go topics | Keeps your name safe | Claims you cannot make | ## Your website and your ten best customers Buyers check your website against what they are told. In [Gartner's survey of 632 B2B buyers](https://www.gartner.com/en/newsroom/press-releases/2025-06-25-gartner-sales-survey-finds-61-percent-of-b2b-buyers-prefer-a-rep-free-buying-experience), 69% reported inconsistencies between a company's website and what its sellers said. An agent can repeat one inconsistency to every prospect it writes to, so fix the stale page or tell the agent which parts to ignore. Then name your ten best customers and, for each, write one line on why they bought and what was happening at the time. The trigger matters more than the logo. "They opened a second site and their old process broke" teaches an agent what a reason to write looks like, in a way "logistics, 500 employees" never will. Add three non-examples: customers who looked right and churned, or deals you wish you had walked away from. Telling an agent what not to chase is often worth more than another good example. ## Who to meet, and who never Name the functions, seniority and company sizes, and be accurate about size, since with Dylan it also sets the price per meeting. Do not default to the highest title either. In [Belkins' study of 7.5 million cold emails](https://belkins.io/blog/cold-email-response-rates), founders and owners replied at 0.57% and VPs at 0.32%, and the study warns against reflexively aiming at the C-suite "when a Director or Owner will engage at nearly twice the rate." The do-not-contact list is the most underrated part of any brief. List by domain, not by name, since people change jobs: current customers, open opportunities, partners, investors, companies in a dispute with you, and anyone a colleague is already talking to. Dylan checks the list when he builds the plan and again as each email is sent, so a company you add today is protected today. ## The meeting definition, the calendar and the voice The meeting definition tells the agent who to book and decides what counts: who qualifies, who takes the meeting on your side, and what the prospect gets, such as "a 20-minute review of your fuel spend." That last line is your offer, and a concrete one gives the reader a reason to say yes. The details are in [what counts as a held meeting](https://meetdylan.ai/blog/what-counts-as-a-held-meeting). For the calendar, connect your meeting owner's real calendar and block the hours they protect; a meeting your own side reschedules is a poor first impression. Finally, tell the agent how you sound and where it must stop: words you never use, claims you cannot make (customer names, figures, guarantees), competitors you never mention, topics that go to a person. "We never promise savings in the first email" beats a paragraph about being "friendly but professional." Dylan hands pricing, legal matters and complaints to your team; add anything else that needs a human. ## After the brief: edit the plan like a hiring manager The plan that comes back is the brief's second draft; give it the attention you would give a shortlist of candidates. Would you be glad to meet each sample company next week? Read the first emails as the recipient would, on a phone between two meetings: is the reason real, is the ask small, is the way out obvious? Once replies arrive, feed the objections back in, because an agent learns your market the way a new hire does, from corrections. ## What to do next Before you brief any agent, spend half an hour collecting four things: your ten best customers with one line each, three non-examples, your do-not-contact domains, and the name of the person who will take the meetings. If your market is only a few hundred companies, read [why an enterprise market is a pond](https://meetdylan.ai/blog/enterprise-market-is-a-pond) before you write the targeting section. Sources: - 6 Months of AI SDRs: What's Worked (SaaStr): https://www.saastr.com/6-months-of-ai-sdrs-whats-worked - Gartner Sales Survey Finds 61% of B2B Buyers Prefer a Rep-Free Buying Experience (June 2025): https://www.gartner.com/en/newsroom/press-releases/2025-06-25-gartner-sales-survey-finds-61-percent-of-b2b-buyers-prefer-a-rep-free-buying-experience - What are B2B cold email response rates? Belkins' 2026 study: https://belkins.io/blog/cold-email-response-rates --- # Post: What counts as a held meeting, and what never gets billed URL: https://meetdylan.ai/blog/what-counts-as-a-held-meeting Published: 2026-10-05 By Vlad Podoliako, Founder and CEO, Belkins > Booked, held and qualified are three different meetings. How Dylan defines a held meeting, what is never billed, and how disputes and the deposit work. A held meeting is a call that actually happened, with someone who matches the definition you wrote, and your own meeting owner on the line. It is what Dylan bills by default, and you decide what it means before a single email goes out. ## Booked, held, qualified: three different meetings Appointment setting has a vocabulary problem, and it costs buyers money. A booked meeting is a time on a calendar; a held meeting is a call that took place; a qualified meeting is a held call with someone who fits what you agreed to in advance. The gap between those words is where budgets disappear. [OutboundPros](https://outboundpros.io/blog/b2b-appointment-setting-pricing-2026), an outbound agency, gives a blunt example: when an agency celebrates 20 booked meetings, 6 people never show and 5 sit outside the target profile, "you did not buy 20 meetings. You bought 9 usable conversations." Dylan's held meeting is the strict version: held and qualified, or not billed at all. ## The held meeting definition you write Every Dylan brief includes one, and a good one has three parts: - **Who counts.** The companies (industry, size, region) and the people (function and seniority) you want to meet. "Decision-makers" is not a definition. - **Who takes it on your side.** Your meeting owner: the person whose calendar Dylan books into and who runs the call. - **What the prospect gets.** The reason they agreed to meet, in one line. A meeting booked on a vague promise rarely goes anywhere. Here is a complete one (an example; the company and the person are invented): > **Who counts:** VP Operations, Head of Fleet or Fleet Manager at US trucking and logistics companies with 201 to 1,000 employees. **Meeting owner:** Sam, Head of Sales. **What the prospect gets:** a 20-minute review of their fleet's fuel spend. What most buyers overlook is that the definition is also the targeting rule. Dylan uses it to decide who to write to, so a loose one fills your calendar with the wrong calls. And an unbilled meeting is still not free: your meeting owner prepares for it, takes it and follows up, all on a senior person's time. Settle the awkward cases now, while nobody has an opinion about a specific meeting: if the VP you targeted sends a director, does that count, and if your meeting owner is away, may a colleague take the call? Write the answers into the definition. Every rule decided in advance is an argument you never have. ## What never gets billed Four things are never billed, whatever else happens: - **No-shows.** If the person does not join, you pay nothing, and Dylan rebooks. - **People on your do-not-contact list.** They should never have been contacted, so you never pay for meeting them. - **Duplicates.** The same meeting is never billed twice. - **Anyone outside your definition.** A meeting with the wrong person is not a held meeting, however pleasant the call. The same OutboundPros piece puts no-show rates anywhere from 10% to 35%, depending on segment, seniority and booking flow, and under booked pricing each one is a meeting you paid for and did not get. We bill no-shows at zero because getting the right person to show up is part of our job, not yours. ## Disputes, the deposit and the stop-loss If you think a billed meeting should not have been, you have 72 hours after it to dispute, and disputes come back as credit. Seventy-two hours is long enough to check the facts and short enough that they are still facts; a window measured in months turns every invoice into a draft. A good dispute points at the definition, not at the mood of the call. "The person who joined was an analyst, and our definition says director and above" is a dispute; "they were not ready to buy" is not, because readiness was never in the definition. If it should be, add it, and accept that Dylan will then book fewer meetings. To start, you prepay three meetings as credit: $750 on Lite, $1,500 on Standard, and three meetings at the quoted price on Enterprise. Each held meeting draws it down. If no meeting is held within 60 days, the deposit comes back, and if you pause, unused credit stays on your account. So the worst case is easy to state: a few minutes on a brief, some time approving a plan and a handful of emails, and your deposit back after 60 days. Sixty days is the whole bet, and it is more ours than yours. Traders use a stop-loss order for a simple reason: the moment a trade goes wrong is the worst moment to decide when to get out, so they decide before they go in. Dylan has one too. If 1,000 contacts bring no positive reply, he pauses, tells you what he heard and proposes a new angle, and you approve it or leave with your deposit. > The exit is decided before the first email, not after a quarter of hoping. That is why we keep our own rules strict. If we could bill for no-shows or loose fits, we would be paid for activity, which is exactly what [pay per meeting](https://meetdylan.ai/blog/why-dylan-charges-per-held-meeting) was meant to end. ## What to do next Write your meeting definition before you talk to any vendor, us included. Three lines are enough: who counts, who takes the meeting on your side, and what the prospect gets from the call. Then list the companies that must never hear from you: current customers, open deals, partners and anyone a colleague is already talking to. Take both to every vendor you consider and ask them to show you, in writing, what they bill and what they never bill. For the rest of the brief, see [how to brief an AI SDR](https://meetdylan.ai/blog/how-to-brief-an-ai-sdr). Sources: - B2B Appointment Setting Pricing in 2026 (OutboundPros): https://outboundpros.io/blog/b2b-appointment-setting-pricing-2026 --- # Post: Pay per meeting: why Dylan charges only for meetings that happen URL: https://meetdylan.ai/blog/why-dylan-charges-per-held-meeting Published: 2026-10-05 By Vlad Podoliako, Founder and CEO, Belkins > Retainers, seats and per-lead pricing leave you holding the risk. Why Dylan charges per held meeting instead, and where outcome pricing can go wrong. Dylan charges per held meeting, and nothing for the research, the writing and the thousands of emails it takes to get one. We chose pay per meeting because a held meeting is the first thing in outbound you would happily buy on its own. Everything before it is the cost of making one, and the people doing the making should carry that cost. The price depends on who you want to meet. During the beta it is $250 for founder-led buyers at small companies, $500 for directors and VPs in the mid-market, and from $900, quoted, for VP and C-level buyers at companies with 1,000 or more employees. ## Every pricing model answers one question: who pays for the misses? Outbound is mostly misses. In [Belkins' study of 7.5 million cold emails sent in 2025](https://belkins.io/blog/cold-email-response-rates), the average reply rate was 0.45%, and all those emails together booked over 1,200 appointments. That is roughly one booked meeting for every 6,000 emails. So the useful question about any proposal is not the price. It is who pays for the emails that never became a meeting. | Model | What you pay for | Who carries the misses | | --- | --- | --- | | Hiring an SDR | Salary, tools and ramp time | You | | Agency retainer, [$3,000 to $15,000+ a month](https://outboundpros.io/blog/b2b-appointment-setting-pricing-2026) | The team's time | You | | AI SDR software, [$50,000 to $100,000+ a year per platform](https://www.saastr.com/6-months-of-ai-sdrs-whats-worked) | Seats, contacts or credits | You | | Per lead, [$1 a lead](https://www.cmswire.com/customer-experience/hubspot-shifts-breeze-ai-agents-to-pay-per-result-pricing/) | Names to contact | You, one name at a time | | Per meeting, billed when booked | A calendar invite | You, for every no-show | | Per held meeting (Dylan) | A call that happened | Us | Pricing per held meeting makes us the underwriter. Like an insurer, we survive only by pricing risk well, which means being honest about which markets we can serve. That is why Dylan's plan sometimes says no before you pay. Some costs never reach an invoice: a tool that sends from your domains can damage the domain your invoices come from, and someone has to run it (SaaStr reports 15 to 20 hours a week overseeing its five AI SDRs). Dylan sends from his own mailboxes, and your domain never sends a cold email. ## A dollar a lead is an input price In April 2026, [HubSpot moved two of its Breeze agents](https://www.cmswire.com/customer-experience/hubspot-shifts-breeze-ai-agents-to-pay-per-result-pricing/) to paying for results. Its customer agent went from $1.00 per conversation to $0.50 per resolved conversation, and its prospecting agent from a monthly charge per enrolled contact to $1 per lead recommended for outreach. It is a good move, but look at what counts as the result. A lead recommended for outreach is a name, and between a name and a meeting sits everything hard: finding the right person, writing something worth answering, landing in the inbox, handling the reply and finding a time. Paying per lead is like paying a recruiter per CV. CVs are cheap. You wanted a hire. ## Why the price follows the buyer, not the effort The effort behind a meeting rises steeply with company size and seniority, and you should not have to estimate it. The Belkins study shows the slope: reply rates fall from 0.72% at companies with up to 10 employees to 0.22% at 10,000 or more, and founders and owners reply at 0.57% against 0.32% for VPs. A meeting with a VP at a 5,000-person company takes more research, patience and email than one with the founder of a 30-person firm. Price per email and you pay for that slope. Price per held meeting and we absorb it, with every reason to get better at climbing it. ## Why we bill held meetings, not booked ones In [one agency's 2026 survey of appointment-setting prices](https://outboundpros.io/blog/b2b-appointment-setting-pricing-2026), per-meeting fees run from $250 to $1,500+, but vendors split on what they count: some charge on booking, others only when the meeting is held. The difference is the empty chair, and the survey puts no-show rates anywhere from 10% to 35%, depending on segment, seniority and booking flow. Pay per meeting also has a known flaw. In the survey's words, if the vendor only gets paid on meeting count, "quality pressure can slip unless qualification rules are brutally clear." A vendor paid per meeting is tempted to book anyone who will take a call. We close that gap in four places: - **You write the meeting definition** before anything is sent: which companies, which people, and who takes the call on your side. - **Anything outside the definition is not billed**, and neither are no-shows, duplicates or anyone on your do-not-contact list. - **You have 72 hours to dispute a meeting**, and disputes come back as credit. - **You approve the plan and the first emails**, so nothing goes out that you have not seen. The full rulebook is in [what counts as a held meeting](https://meetdylan.ai/blog/what-counts-as-a-held-meeting). ## Why we stop at the meeting, and why there is a deposit Why not charge on pipeline or revenue? Because a held meeting is the last step we control: after it, the result depends on your demo, your price and your timing, which we should neither bill for nor be blamed for. A held meeting is the cleanest line between our work and yours, and both sides can see it. **Update, October 8, 2026:** some teams asked us to go one step further and be paid only when their own team calls a meeting pipeline. We are testing that with a small group as [pay per qualified opportunity](https://meetdylan.ai/ways-to-pay/per-opportunity): your meeting owner confirms each held meeting against criteria you write before the first email, and the criteria judge the prospect's situation on the call, never your demo or your price. Per held meeting stays our default, and the argument above stands for it. To start, you prepay three meetings as credit: $750 on Lite, $1,500 on Standard, and three meetings at the quoted price on Enterprise. The plan, the research, the first emails and the sending all come before any meeting can, so the deposit commits both sides first. It is not a fee. If no meeting is held within 60 days, the deposit comes back. If you pause, unused credit stays on your account. ## When pay per meeting is the wrong choice This model is not for everyone. The same survey notes that per-meeting pricing "works worst when your ICP is tiny, your offer needs education, or your sales cycle is highly consultative." If your whole market is, say, 80 accounts, you need a relationship plan, not a meeting machine; [an enterprise market is a pond](https://meetdylan.ai/blog/enterprise-market-is-a-pond) walks through the math. And if inbound leads wait a day for an answer, fix that first. It is cheaper than any outbound, ours included. ## What to do next Work out what a held meeting costs you today. Add up a month of outbound spend (salaries or retainers, tools, data, domains and your team's hours) and divide it by the held meetings that matched your definition. Not booked: held. The survey's own example shows why. At $450 per booked meeting, 20 bookings became 14 held meetings and 8 qualified ones, a real cost of $1,125 each. Once you know your number, compare it with ours. Sources: - What are B2B cold email response rates? Belkins' 2026 study: https://belkins.io/blog/cold-email-response-rates - B2B Appointment Setting Pricing in 2026 (OutboundPros): https://outboundpros.io/blog/b2b-appointment-setting-pricing-2026 - HubSpot Shifts Breeze AI Agents to Pay-per-Result Pricing (CMSWire): https://www.cmswire.com/customer-experience/hubspot-shifts-breeze-ai-agents-to-pay-per-result-pricing/ - 6 Months of AI SDRs: What's Worked (SaaStr): https://www.saastr.com/6-months-of-ai-sdrs-whats-worked --- # Post: AI disclosure in cold email: why Dylan says he is an AI URL: https://meetdylan.ai/blog/why-dylan-says-hes-an-ai Published: 2026-10-05 By Vlad Podoliako, Founder and CEO, Belkins > Every first email from Dylan says he is an AI agent and who he works for. Why we disclose, what the EU AI Act and CAN-SPAM say, and how to stop him. Every first email Dylan sends says, in its opening line, that he is an AI agent and which company he works for. We made AI disclosure a rule rather than a setting for three reasons: it is honest, the law is moving the same way, and the company named in the email has the most to lose from a disguise. ## What a recipient sees The From line reads "Dylan, AI agent for" the client's name. Here is a first email in the shape Dylan writes (an example; the companies and the person are invented): > Hi Maya, I'm Dylan, an AI agent working with Harrow Line. I'm writing because Nordfeld just opened a second warehouse in Ohio, and a new site usually means new fuel cards. Harrow Line puts every vehicle on one card with its own spend limit. Would a 20-minute review of your fuel spend be useful? If not, reply "no" and I won't write again. Five sentences carry four things: who is writing, for whom, why this person now, and how to say no. The disclosure costs nine words, and it sits in the first line, not in small print under the signature. A disclosure nobody reads is not a disclosure. What is missing matters too: no fake first name, no "just following up on my last note" when there was no last note, no fake "Re:" in the subject line pretending to continue a conversation. A stranger can judge it at a glance, which is the respectful thing to offer. ## Why AI disclosure comes first A disguised agent works until someone notices, and then it fails twice: once for the email, and again for the company named in it. The prospect who learns that the "rep" they traded emails with for a week does not exist will not blame the software vendor. They will blame the brand on the email. People say plainly that they want to know. In [Salesforce's 2024 survey of 15,015 consumers](https://www.salesforce.com/news/stories/ai-customer-research/), nearly 75% said they want to know if they are communicating with an AI agent. That survey asked consumers, not business buyers, but your buyers are the same people at work. Will some people refuse to reply to an AI? Yes, and Dylan is new, so we have no results of our own to show yet. But honesty is not what costs replies; irrelevance is. In [Gartner's survey of 632 B2B buyers](https://www.gartner.com/en/newsroom/press-releases/2025-06-25-gartner-sales-survey-finds-61-percent-of-b2b-buyers-prefer-a-rep-free-buying-experience), 73% said they actively avoid suppliers who send irrelevant outreach. Pretending to be human does nothing for relevance; a specific reason to write does. And a meeting that starts with a discovered lie rarely gets a second one. ## What the law says This is not legal advice; ask your own counsel about your situation. But the direction of travel is clear on both sides of the Atlantic. **The EU AI Act.** The transparency obligations in [Article 50 began to apply on 2 August 2026](https://www.morganlewis.com/blogs/sourcingatmorganlewis/2026/08/eu-ai-acts-transparency-rules-what-went-into-effect-on-2-august). In Morgan Lewis's summary, providers of AI systems meant to interact directly with people "must ensure that individuals are appropriately informed that they are interacting with such a system, unless this would already be obvious." [The Article itself](https://artificialintelligenceact.eu/article/50/) sets the timing: "at the latest at the time of the first interaction or exposure." Who carries which duty depends on whether a company is the provider or the deployer of the system, a question for counsel. **CAN-SPAM in the United States.** The [FTC's guide](https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business) is direct: "The law makes no exception for business-to-business email." Header information must identify who initiated the message, subject lines must not deceive, commercial email needs a valid postal address and a clear way to opt out, and opt-outs must be honored within 10 business days. Penalties run up to $53,088 per email in violation. And for anyone who hires a sender: both the company whose product is promoted and the company that sends the message "may be held legally responsible." Outsourcing the sending does not outsource the risk. Neither law asks for clever wording. Both reward the same habit: say plainly who is writing, for whom, and how to make it stop. ## Disclosure needs a real off switch Saying "I'm an AI" means little if the AI keeps writing. In September 2026, [404 Media described](https://www.404media.co/ai-agent-platform-reinvents-spam-floods-inboxes-worldwide/) agents on the iLands platform that told recipients they would not follow up unless someone responded, then "messaged us multiple times with the same pitch." A stop should never depend on an AI reading a reply correctly. When someone replies to Dylan, every further scheduled email to that person stops the moment the reply is read, by rule, before any AI sees it. Only then does Dylan read it: he answers routine questions, such as scheduling or anything the client's brief already covers, and hands pricing, legal matters and complaints to the client's own team. ## Got an email from Dylan? Then an AI agent wrote to you on behalf of the company named in the email, and you can end it in one step. Reply "stop" to any of his emails and he stops. If you would rather no client of his ever writes to you, leave your address on our site. ## What to do next If you are evaluating any AI SDR, read its first email the way a recipient would. Does it say what it is and who it works for, in the opening lines? Is there a plain way to make it stop, and what happens inside the system when someone uses it? If the answer starts with "we instruct the model to," ask what happens when the model gets it wrong. Our answer is in [how Dylan is built](https://meetdylan.ai/blog/agents-judge-people-approve-code-protects). Sources: - EU AI Act's Transparency Rules: What Went Into Effect on 2 August? (Morgan Lewis): https://www.morganlewis.com/blogs/sourcingatmorganlewis/2026/08/eu-ai-acts-transparency-rules-what-went-into-effect-on-2-august - Article 50: Transparency Obligations for Providers and Deployers of Certain AI Systems (EU AI Act): https://artificialintelligenceact.eu/article/50/ - CAN-SPAM Act: A Compliance Guide for Business (FTC): https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business - Salesforce releases AI Connected Customer research (October 2024): https://www.salesforce.com/news/stories/ai-customer-research/ - Gartner Sales Survey Finds 61% of B2B Buyers Prefer a Rep-Free Buying Experience (June 2025): https://www.gartner.com/en/newsroom/press-releases/2025-06-25-gartner-sales-survey-finds-61-percent-of-b2b-buyers-prefer-a-rep-free-buying-experience - AI Agent Platform Reinvents Spam, Floods Inboxes Worldwide (404 Media): https://www.404media.co/ai-agent-platform-reinvents-spam-floods-inboxes-worldwide/ --- # Contact - Privacy and data requests: dylan@meetdylan.ai - LinkedIn: https://www.linkedin.com/company/145296276/