Outbound appointment setting · updated 19 September 2026
Appointment setting service: the work that decides a booked meeting
The short answer: an appointment-setting service is not judged by the appointments printed in a report, it is judged by one number — meetings that hold, per hundred contacts that were verified. Everything before that (list size, touches per prospect, mailboxes rented) is an input. This page is written from the list this kind of work runs on: 6 604 company domains collected from 44 public sources, of which 1 040 publish an address of their own. Below are the four checks a row has to pass before it is sent, where the domains actually came from, how much volume is needed before a meeting number is worth reading, and the three fixed scopes — $900 Sprint, $1,900/month Engine, $2,900 Full Build.
Four things decide the meeting before the first send
The domain comes from the post, not from the text
On job feeds the employer’s domain sits inside body copy, and roughly half of what gets extracted turns out to be the board itself, an ATS (greenhouse.io, lever.co, ashbyhq.com), a link inside the ad, or the same company under two ccTLDs. When the domain is taken from a structured field or from the post URL — Show HN, package registries, dev.to canonicals — the reject rate drops from about 50% to 5–12%. That is why this file counts 44 sources and not 4,000 scraped pages.
A domain is not a company until it answers
Every host is requested live before it enters the file, and only pages that look like a product (pricing, sign-up, demo, integrations) are kept. Skip it and the list fills with university course pages, documentation sites and personal blogs: on the first pass of this campaign 21 candidates produced 10 usable rows.
A published address is not a verified address
Of 6 604 rows, 1 040 expose an address at all — the rest are companies without a public mailbox, and guessing the pattern produces the bounce. In the agency pull two of 35 addresses were placeholder text (hello@world.com) and three belonged to a different domain than the page they sat on; all five would have gone out as working data without a domain match.
The mailbox is checked where it will be used
The address is SMTP-checked, role addresses are separated from personal ones, and bounces leave the queue instead of being re-guessed. Deliverability is a separate job that runs before volume goes up: the same checks are public as a tool page, cold email domain warm-up, and as a verifier API. Skip any of the four checks and the failure shows up as a bounce or a no-show in the same week the appointment was promised.
Where the 6 604 domains actually came from
Appointment setting needs a list, and a list is only as good as the source it was taken from. Every row carries the source it came from and the domain it was checked against; the numbers below are counted from the file itself, one row at a time.
| Source family | Domains | Published an address | Yield |
|---|---|---|---|
| Hacker News “Who is hiring?” threads (2024 → Sep 2026) | 2 792 | 304 | 11% |
| Y Combinator open hiring catalog | 736 | 0 | 0% |
| remoteintech/remote-jobs public catalog | 531 | 0 | 0% |
| Agency directories | 525 | 522 | 99% |
| GitHub repositories and organisations (website field) | 466 | 33 | 7% |
| Show HN launches — domain taken from the post URL | 407 | 44 | 11% |
| WordPress plugin catalog (homepage field) | 350 | 9 | 3% |
| dev.to posts whose canonical is a company domain | 220 | 40 | 18% |
| Package registries (npm PyPI crates.io) | 190 | 0 | 0% |
| Hacker News other threads | 106 | 22 | 21% |
| Job feeds (WeWorkRemotely Jobicy Arbeitnow RemoteOK Remotive LaunchingNext Working Nomads) | 182 | 62 | 34% |
| Reddit and Mastodon threads | 58 | 0 | 0% |
| Product Hunt launches | 37 | 4 | 11% |
| Applicant tracking systems | 4 | 0 | 0% |
| Total in the file | 6 604 | 1 040 | 16% |
Two readings matter more than the total. First, 42% of the domains come from one family (hiring threads), and that family publishes almost no mailboxes — 304 addresses out of 2 792 rows, because a hiring post gives you the company, not the contact. Second, the only family with near-total contact data is agency directories: 522 of 525 rows carry an address, because agencies publish one on purpose. A list built only from job feeds is a list of companies; a list built only from directories is a list of competitors. An appointment-setting offer built on one of the two is either a cold guess or a re-send.
How much volume before a meeting rate means anything
A strict two-variant test needs 13 914 contacts per arm — 56 days at 500 contacts a day. Below that volume the honest output of outbound is not a conversion rate, it is a reading list: which segment answers, which sentence earns a reply, which objection comes back first. That is why the first test here is 100 verified contacts: it decides the segment and the sentence on evidence rather than on a spreadsheet, and it costs the price of one Sprint rather than a quarter.
Anyone quoting appointments per month before the segment has been read is quoting the report, not the meetings. Set the number after the first hundred replies are in, and write it with the volume in the same sentence.
What the engagement is
Segment and definition, the contact list with addresses checked, the first touches sent, and the measurement that says what the channel owns. Ends with the reading list and the number for the next volume.
The loop keeps running: list refreshed, sends going out, replies worked to a booked conversation, a read-out each cycle, the stop rule written down. This is the monthly version of appointment setting.
Offer, landing page, a free tool, distribution and measurement — the same work that produced this page and the artifacts behind it.
Three kinds of buyer get the most out of it: SaaS and seed-stage teams that have a product and no pipeline, agencies that want the list and the sending run white-label under their own brand, and local and regional B2B where the list is small enough to be checked by hand: for SaaS, for agencies (white-label), for local B2B. Data and mailbox costs are never inside the fee, and the same list is not resold.
What you can open before paying
The proof page carries the third-party artifacts that were accepted by other people’s repositories, the machine-readable offer carries the same scopes for agents rather than people, and pricing keeps the three numbers in one place without a form. The list work itself is written up with the full source table on B2B lead list building.
See the engagement Write on Telegram
Where this argument was published
Same numbers, written for a developer audience, with the filter pipeline left in: I ran 521 Show HN launch URLs through a lead filter: 86 companies survived (dev.to, 19 September 2026). The page you are reading is the canonical version.
Questions asked before hiring for appointment setting
- What is an appointment-setting service?
- Someone else owns the outbound: the list is built and checked, the first touches go out, replies are worked until a meeting is on a calendar. It is bought as work, not as a spreadsheet, because the list is only the input — the sentence and the reading of replies are what produce the meeting.
- How many appointments per month will outbound produce?
- No honest number exists before the segment is read. A strict two-variant test needs 13 914 contacts per arm; below that volume the output is a reading list, not a rate. The first test here is 100 verified contacts, and the send volume is set from what that test returns — not from a promise made before it ran.
- Where does the contact list come from?
- Public sources only, 44 of them in the file described above, with the source column kept in every row: hiring threads, Show HN launch URLs, package registries, agency directories, dev.to canonicals, public catalogs. The domain is taken from the post or from a structured field, then the host is requested live and the published address is matched to the domain it sits on and SMTP-checked.
- What does it cost?
- Three fixed scopes: $900 for the Sprint (segment, checked list, first touches, measurement), $1,900/month for the Engine (the same loop kept running, replies worked to a booked conversation), $2,900 for the Full Build. There is no per-1,000-records price, because the list is the input, not the product. Data and mailbox costs stay outside the fee.
- What do you need from me to start?
- Three things: what you sell, who buys it, and the volume you want tested. The Telegram link above opens with those three fields already in the message. Everything else — segment definitions, sending domains, the stop rule — is decided in the first day and written down.
Related: B2B data enrichment — the same rows after enrichment: what happens when they are used for their outcome rather than their fields.