Choose the sales motion before the channel
The SaaS label does not tell you how people should buy. Choose the next action that helps a suitable buyer evaluate the product. A demo is useful when a conversation resolves something the buyer cannot reasonably work out alone.
All situations, messages and reporting figures below are original fictional teaching examples. They contain no client or prospect records and are not Beespoke results.
Self-serve
When buyers can reach useful value themselves and the customer contribution is small, improve discovery, onboarding and activation first. High-touch outbound can cost more than the account supports. A trial sign-up is not a sales-qualified lead.
Sales-assisted
Product usage may reveal an account worth helping, but check company fit, the user's role and the unresolved need. An active free user is not automatically a budget owner. Coordinate the product and sales history before contacting them.
Sales-led or enterprise
A workflow change, integration, security review or buying committee may justify a tailored demo. Target a defined account problem and involve the right product expert. Do not force every visitor into a call.
Define a segment you can actually research
Specify the workflow, company context, market, product prerequisites and people affected. Separate accounts you can serve today from an attractive market your product cannot yet support. Use your own customer learning with permission; do not treat a database category as proof of need.
| Illustrative segment | Reason to investigate | Exclusion or unanswered question |
|---|---|---|
| Multi-site operators evaluating scheduling software | A public operations discussion describes coordinating local teams | Can the product support their locations, permissions and existing systems? Exclude unsupported requirements. |
| Software teams evaluating developer tooling | A technical post describes a workflow the product genuinely addresses | Is the author a user, evaluator or sponsor? Public code or a job advert does not prove a procurement project. |
| Small teams using a self-serve productivity tool | Users can experience the core task without a sales process | If low contribution cannot fund personal prospecting, prioritize self-serve acquisition rather than selling a costly demo campaign. |
Check readiness without inventing an intent score
Keep the original eight readiness considerations, but use them to make a decision. Eight ticks cannot certify demand.
- Can we explain and support the offer?
- A narrow use case; relevant, authorized proof; an offer with paying customers. If these are missing, use founder-led learning and product work before commissioning a scaled campaign.
- Can we reach a defensible market?
- A sufficiently large account universe; mapped economic and technical buyers; written exclusions. If only a few suitable accounts remain, use individual account planning instead of increasing send volume.
- Can we afford and handle the result?
- Customer contribution that can support human acquisition; a sales owner able to respond and run discovery. If either is unknown, model the cost and ownership before approving the test.
Map the people and the questions they need answered
A job title is a starting point. Ask who experiences the problem, who can approve a change and who must validate it. One person can play several roles; do not contact an entire department simply because the account is attractive.
| Role | Question to resolve | Useful next evidence |
|---|---|---|
| User or operational owner | What task is difficult, and what would change in daily work? | A realistic workflow demonstration and adoption requirements |
| Champion or economic sponsor | Why consider a change, who owns the decision and what would justify the effort? | A bounded value explanation using the buyer's own assumptions |
| Technical, security or integration evaluator | What requirements must the product satisfy? | Current product documentation and answers from an authorized technical owner |
| Finance, legal or procurement | What approval, supplier and commercial steps apply? | The client's actual terms and review process; never an outreach agent's invented assurance |
Keep the public fact separate from the hypothesis
Funding, hiring, a new market, product usage or a technology change can prompt research. None proves approved budget, dissatisfaction or permission to contact someone. Use only information and contact routes appropriate to the campaign.
- Observed
- A fictional operations leader publicly describes the difficulty of coordinating several locations. Record the source and date.
- Hypothesized
- Scheduling software might help. You still do not know their current system, constraints, timing or interest in changing.
- Confirmed
- The responsible person explains the actual workflow and agrees a relevant next step. Record their words accurately, including what remains unknown.
Personal context can also supply the reason to write: a relevant public post, a professional interest, an event or a genuine shared location. Connect it to the discussion naturally. Shared geography or a friendly reply is not evidence of a buying project.
Use channels for different jobs
Coordinate outreach, product activity, useful content and referrals around the same account history. You do not need every channel at once.
| Route | Useful job | Condition or limit |
|---|---|---|
| Cold email or LinkedIn | Start a specific conversation with a suitable person you can identify | Choose the channel where they are active or sensibly reachable. Check research and contact permissions; avoid simultaneous duplicate sequences. |
| Product-led or sales-assisted | Help suitable users evaluate a workflow or a larger deployment | Agree product signals, account ownership and appropriate contact rules. Usage alone does not establish budget or intent. |
| Search content and demonstrations | Answer a real evaluation, integration or use-case question | Match the next action to the question. A guide view or download is not a qualified demo. |
| Partners, referrals and communities | Reach a relevant audience through genuine expertise or an appropriate introduction | Respect the relationship and community rules. Do not exchange private customer lists or use communities as a message-scraping shortcut. |
| Paid acquisition, events or calling | Test a defined audience and offer where economics and capacity support it | Keep costs and outcome definitions explicit. Calling is a separate scope, not automatically part of an email/LinkedIn campaign. |
Prepare the evidence and the people behind the campaign
Buyers need enough substance to judge the software. A relevant demonstration is more useful than unsupported growth language. Before launch, agree who can answer each kind of question.
- Prepare a short workflow demo, current prerequisites, implementation responsibilities and known product limits.
- Use authorized proof with its starting situation, contribution, period and limits. If proof is confidential, use a clearly fictional demonstration rather than recognizable details with names removed.
- Name the product or technical owner for integrations, security, data handling and roadmap questions. Do not promise an unverified feature or certification.
- Approve target-account fit, exclusions, sender identity, messaging permissions and access boundaries. Assign the owner of contact-data checks and suppression records.
- Agree who configures and checks the sending infrastructure, handles failures and monitors account health. Automation does not guarantee inbox placement or remove platform constraints.
- Check existing customers, active opportunities, partners and previous declines before enrollment. Keep one contact history across channels.
Work through one account before scaling the list
Consider a fictional scheduling-software provider selling to multi-site service businesses. Its product supports a defined set of workflows and integrations; that boundary matters more than the size of a prospect's brand.
- Research
- An operations leader has published a post about arranging cover between locations. The account appears to fit the supported market. Save that evidence; do not invent staff numbers, software spend or frustration.
- Decision
- Check whether the problem is within the product's documented capabilities. If a required integration is unsupported, park the account or ask the product owner before making a claim.
- Conversation
- Ask how the workflow is handled and whether a short, relevant example would be useful. Do not announce a transformation or an assumed saving.
- Handoff
- If the person confirms a relevant need and wants to evaluate it, agree who should join the demonstration. Carry the unresolved technical questions into the client's calendar and CRM.
Write to the person and the situation
The sender in these fictional examples represents the software provider. These are alternative approaches, not messages to send to the same person at the same time. Replace every premise with something true.
Email: explain the reason and one useful next step
Hi [first name],
Your post about arranging cover between locations raised a practical question: does each site still have to find cover separately, or is there one place the operations team can see the gaps?
We make scheduling software for teams with several locations. One workflow we can show is how an operations lead reviews an uncovered shift before asking another site for help. Whether it fits would depend on your current setup and the systems it needs to connect to.
Would a short walkthrough of that workflow be useful, or is this already covered?
The public point creates a specific question. The sender states the commercial purpose openly, describes an actual capability and leaves room for a non-fit answer. There is no invented pain, saving or claim to know the buyer's systems.
A brief second email
Hi [first name], would that walkthrough be useful, or is this already handled in your current system?
A short follow-up around four days later is an example of Beespoke's usual two-message approach, not a universal timetable. A reply, decline or contact preference overrides the sequence.
LinkedIn: an alternative when the person is active there
Hi [first name], your point about letting each location solve cover locally was interesting. How does the operations team keep sight of gaps that need help from another site? We build scheduling software for that sort of workflow. Happy to send a short example if useful.
The message joins an actual discussion and explains the product connection. A genuine shared event or relevant personal interest could also be the starting point; it must not be a fabricated familiarity tactic.
Read the message aloud and remove empty praise, generic growth promises and interchangeable observations. AI can help draft, but a person must verify the facts and meaning. Phrases such as “I saw” are not reliable AI detectors; specificity and accuracy matter more than banning a particular word.
Let the reply change the plan
Choose the first channel from the person's activity and reachability. If email gets no response, reassess whether LinkedIn or a separately scoped call makes sense; do not automatically restart the same pitch everywhere. Keep the history and stop instructions shared.
- “Send the example.”
- Send the promised workflow and one useful question. An information request is not acceptance of a meeting or a sales opportunity.
- “Does it connect to our system?”
- Route the exact question to the product owner. Answer from current documentation; do not convert uncertainty into a promise.
- “Not until our current review is finished.”
- Ask whether a later check-in is welcome. Record the agreed timing and remove the person from immediate follow-ups.
- “We have this covered.”
- Respect that answer. Explore another need only if the person invites it; otherwise close the loop.
- “No”, an unsupported requirement or a stop request
- Stop or disqualify the affected route and keep the reason. Do not approach colleagues to circumvent a decline.
Agree what makes a demo qualified
Use written acceptance criteria before launch. A booked slot, a product-qualified lead (PQL) and a sales-qualified lead (SQL) describe different things. Define those labels for your business instead of relying on a provider's score.
- Account: the company fits the agreed market, exclusions and product prerequisites.
- Person: the attendee has a relevant role; record whether they are a user, evaluator, sponsor or an introducer.
- Need: a relevant workflow or evaluation question is confirmed. Keep unknown budget, authority and timing marked unknown.
- Interest: the person understands what the conversation is about and agrees to it; a guide download or trial registration alone is insufficient.
- Practical fit: record requirements that could block the sale and the expert needed to answer them.
- Outcome: distinguish booked, held, held and qualified, and sales-accepted opportunity. A no-show cannot count as a held demo.
Pass context into the client's calendar and CRM
- Use the client's approved calendar link and confirm the agreed purpose and attendees. A calendar click is not a completed booking.
- Keep the original booking/event ID and creation time. Link reschedules and cancellations to the original event rather than counting them as new demand.
- Pass the account reason, source of interest, role, relevant conversation, unanswered questions and next owner through approved access only.
- Have the client's sales owner record whether the call was held, qualified and accepted as an opportunity, with a reason for rejection or recycling.
- Keep product discovery, tailored demos, proposals and closing with the client. Feed the agreed outcome back into targeting and messages; request only the access needed.
Measure the same accounts through the same funnel
This fictional cohort has had enough time for every listed outcome to be checked. It is an arithmetic illustration, not a benchmark or forecast. Count unique accounts and people separately; do not mix several contacts at one account into a new-customer total.
| Stage | Fictional count | What the count establishes |
|---|---|---|
| Approved accounts contacted | 120 | Accounts meeting the research criteria; not 120 interested buyers |
| Original demo bookings | 15 | Deduplicated booking IDs; reschedules are linked, not new bookings |
| Held demos | 10 | Five bookings did not become held demos in this reconciled cohort |
| Held and qualified demos | 8 | Two held conversations failed the written qualification criteria |
| Sales-accepted opportunities | 5 | The client's sales owner accepted a defined next step |
| New paying customers | 3 | Three verified customer outcomes, not three predicted closes |
Held-to-qualified is 8 ÷ 10 = 80% in this fictional cohort; booked-to-held is 10 ÷ 15, about 67%. Neither is an expected conversion rate. Trial sign-ups and activated product accounts belong in their own defined funnel before joining an account-level report.
For real reporting, show cohort entry dates, observation cutoff, sales-cycle maturity and any unknown outcomes. Period activity can legitimately differ from cohort conversion: a customer closing this month may come from an earlier campaign.
Keep original acquisition source, observed website landing page, later visits and the buyer's own explanation separate. Outreach that leads to a website booking is not automatically organic search. Preserve unknown attribution; exclude audit visits and never treat a click, tool use or reschedule as a new lead.
Use contribution and complete costs to set the limit
ACV, ARR, retention and customer acquisition cost (CAC) are useful only with explicit definitions. Revenue is not gross profit, and a campaign invoice is not fully loaded CAC.
- Illustrative inputs
- A fictional cohort costs 12,000 currency units in acquisition, including the agreed allocation of properly costed team time, tools, data and sales work. It produces three new paying customers and eight held, qualified demos.
- Arithmetic
- 12,000 ÷ 8 = 1,500 per held, qualified demo. 12,000 ÷ 3 = 4,000 per new customer. If each customer's first-year revenue is 9,000 and the assumed gross margin is 80%, first-year gross profit is 7,200 before acquisition and other overhead.
- Decision and limits
- At 600 of assumed gross profit per month, recovering 4,000 would take about 6.7 months under flat revenue and margin assumptions. That is not a cash-flow, retention or payback forecast. Early churn, implementation costs, discounts and payment timing can change the decision. If costs or customer outcomes are incomplete, label the result incomplete.
Use one currency and a consistent cohort. Do not borrow another company's LTV:CAC target or reply rate to justify your budget. A profitable-looking unit calculation does not prove enough suitable accounts exist.
Optional: check acquisition cost per outcome
Use complete acquisition costs in one currency and verified outcomes from the same sufficiently mature cohort. Leave an unknown count blank; enter zero only when zero is confirmed. Nothing entered here is sent or saved.
Use a small test to find the actual bottleneck
Agree one segment, offer, owner, review window and decision rule before launch. Allow for your sales cycle; early replies do not establish customer acquisition economics. Pause on product, permission or account-health problems rather than trying to solve them with more contacts.
| Observed problem | Investigate first | A sensible next change |
|---|---|---|
| Accounts do not fit | Research criteria and exclusions | Narrow or correct the segment before rewriting messages |
| Messages fail or reach the wrong person | Contact accuracy, sending setup and role ownership | Repair the verified cause; more volume is not a remedy |
| Relevant replies do not become useful demos | Question asked, qualification, availability and handoff | Clarify the next step and unresolved requirement |
| Qualified demos do not progress | Discovery notes, product fit, proof, decision process and sales ownership | Review with the client; change the actual constraint and keep cohort outcomes open |
Ask an agency to show the operating plan
Ask for a sample account rationale, a message review, qualification rules and a handoff record. A long software list or a promised demo total cannot replace those artifacts.
Open the SaaS campaign brief
Read the questions here or download the same static CSV. No email address is required. The optional cost check runs only in this page; its inputs are not saved or sent. The CSV contains planning questions, not your entered figures.
- Sales motion
- Which next action should the buyer take, and why?
- Segment
- Which workflow, company context and market can we support?
- Evidence and exclusions
- What proves relevance, what is unknown and what disqualifies the account?
- Buying group
- Who uses, sponsors, validates and approves the change?
- Product proof
- Which demonstration, documents and authorized outcomes can we show?
- Execution
- Who approves the list, sender, access and message permissions?
- Replies and stop rules
- Who handles technical questions, timing requests, declines and suppression?
- Qualified demo
- What exact account, person, need, interest and fit criteria apply?
- Handoff and measurement
- Which calendar, event ID, CRM owner, cohort and source fields will reconcile outcomes?
- Economics and review
- Which complete costs, customer contribution, observation cutoff and test decision will we use?
Where Beespoke fits
Beespoke runs founder-led managed cold-email and/or LinkedIn campaigns for suitable B2B offers. We research accounts and people, write individual messages, execute with authorization, handle replies, qualify interest and facilitate bookings against agreed criteria. Your team approves target fit and supplies the product truth; it retains technical discovery, demos, proposals and closing.
We choose the first channel from the person's activity and reachability, usually use an opening and a brief follow-up, and coordinate subsequent contact rather than running competing sequences. Required software, data and third-party costs are separate unless included in written scope. Calling is separately quoted by market; the base service does not include a dedicated full-time SDR or a guaranteed meeting volume.
The founder supports delivery in English, Spanish, Catalan and French. That does not mean an unlimited native calling team or that every third-party tool has all four interfaces. A fit call should establish the offer, constraints, evidence and smallest defensible test.
Questions about B2B SaaS lead generation
Should every SaaS company use outbound?
No. It fits best when you can identify suitable accounts, explain a credible reason to evaluate the product and support human acquisition with customer contribution and sales capacity. A low-contribution self-serve offer or an unvalidated product may need a different next step.
Is a trial user a qualified sales lead?
Not automatically. Product use may help identify an account worth assisting, but company fit, role, relevant need and interest still matter. Define PQL and SQL criteria for your business and keep trial, demo and opportunity counts separate.
What makes a SaaS demo qualified?
Written criteria should cover the account, attendee role, relevant need, interest and product prerequisites, with unknowns kept visible. Report booked, held, held and qualified, and sales-accepted opportunity as separate stages.
How long does it take to judge a campaign?
There is no universal timetable. Set a review window around your account universe, reply handling and sales cycle. Early engagement can diagnose targeting or messaging; customer economics require complete costs and sufficiently mature outcomes.
Does Beespoke run product demonstrations and close deals?
Beespoke handles approved prospect research, messaging, reply handling, qualification and booking facilitation. The client's experts retain product and technical discovery, demonstrations, proposals and closing. Agree the exact handoff and feedback loop before launch.
Will a campaign brief or calculator prove buying intent?
No. They help structure a decision. A download, completed checklist or calculated ratio does not establish a prospect's need, budget or willingness to meet. This page's optional cost check is local and does not send or save entered figures.
Sources and methodology
Reviewed November 9, 2026. These strategy articles and service pages informed the comparison. Their advertised results, prices, conversion rates and timelines are not used as benchmarks. The worked examples and decision tools are original illustrations; a tool result does not establish buying intent.
- Saleshandy — saleshandy.com/blog/lead-generation-for-b2b-saas/
- SalesRoads — salesroads.com/tactics/saas-lead-generation-strategies/
- Mouseflow — mouseflow.com/blog/saas-lead-generation-strategies/
- Oppora — oppora.ai/blog/lead-generation-for-b2b-saas/
- Artisan — artisan.co/blog/b2b-saas-lead-generation
- Overloop — overloop.com/blog/lead-generation-strategies-every-saas-business-should-try-today
- AI bees — ai-bees.io/post/b2b-saas-lead-generation
- PayPro Global — payproglobal.com/answers/what-is-saas-lead-generation/
- Ironpaper — ironpaper.com/lead-generation-for-saas
- Lead Express — leadgeneration.com.au/industry-specific-solutions/lead-generation-for-saas-companies/
- LevelUp Leads — levelupleads.io/industries-served/software-saas/
- Zaphyre — zaphyrpro.com/b2b-saas-companies
- Sopro — sopro.io/solutions/lead-generation-for-saas-services/