Early stage B2B outbound, before product-market fit, is not a volume game. It is a way to learn. Your first campaign should tell you who answers, who says no, and what they say when they do. Pipeline is a bonus at this stage.
That changes how you run it. You send small batches. You write down who you think buys and why, before the first email goes out. You read every reply yourself. You also keep the setup boring: warmed mailboxes, checked DNS, and a person who approves what goes out.
This guide walks through that, in order.
Who buys
No outside source can tell you who buys your product. Your own deals can. Everything below starts from that.
If you have past deals, use them. Outlevo can import won and lost deals from a CSV or a CRM and return a win/loss analysis that proposes ICP hypotheses [[1]](#sources). A CSV import takes up to 200,000 rows. It maps your columns to domain, name, country, size, industry and deal fields such as stage, amount, outcome and loss reason. Importing uses no credits [[2]](#sources).
Pay attention to how the analysis counts. It counts companies, not deals, and it labels small samples. Fewer than 10 won companies is labeled very low confidence [[3]](#sources). If you have fewer than 10 won companies, treat every segment as a guess you are testing. Do not treat it as a finding.
If you have no deals yet, start from your website. The free assessment reads up to 5 public pages of a site. It returns facts labeled as verified observations or AI inferences, and up to 5 experimental segment hypotheses [[4]](#sources). AI-proposed ICP segments stay labeled experimental until a person approves them [[3]](#sources).
One more point on markets. Outlevo asks which countries you sell into and never proposes markets [[3]](#sources). You decide that. This guide will not tell you where to sell.
Roles to reach
Pick roles from your won deals, not from a template. If a buyer title appears in your closed-won records, that is your first role to test. If it appears only in your hopes, mark it as a hypothesis.
Two facts help with the mechanics:
- If you use HubSpot, Outlevo can read contacts with email, name, job title and email opt-out. That happens only after an admin turns contact import on with a stated purpose [[5]](#sources).
- Finding contacts at a qualified account costs credits. Contact discovery costs 4 credits, volume contact discovery costs 2, and email verification costs 1 [[6]](#sources).
Keep the first batch narrow: one role in one segment. When replies come back, you will know which of the two moved the result. If you test three roles across four segments, you will learn nothing from a small batch.
For a worked example of a single role in a single segment, see the playbook on outbound to RevOps leaders at SaaS companies.
Triggers to watch
A trigger is a reason to write to this company this week. At your stage, a short list of triggers beats a long list of accounts.
What Outlevo can show you:
- Readiness Cards. Each qualified account gets a Readiness Card with fit, intent and data quality scores. A card needs at least three observations, each with a source and a date. Guesses are labeled as hypotheses, never presented as findings [[7]](#sources). Facts read from a website are kept only when their quote is found on the page [[7]](#sources).
- Website visitors. One script on your site shows which companies visit, which pages they read and whether they fit your ICP. It never identifies a person [[8]](#sources). It costs 1 credit per company identified per day, however many pages it reads [[8]](#sources).
- Competitor tracking. Outlevo offers quoted facts from competitors' public pages, changes, win/loss by competitor and competitor signals on accounts [[9]](#sources).
Use triggers to decide who goes in the batch. Then use them in the first line of the email, with the source and date written down so you can show where it came from. If you cannot name the observation, do not mention it.
Write the ICP down before you send
A written ICP is a short document. It does not have to be polished. It needs four parts:
- Segment. The kind of company you think buys, in a sentence.
- Role. The person you will write to.
- Reason. The evidence for the first two. A won deal, a visit, a quoted fact from their site.
- Disconfirmer. What would make you drop the segment. For example: no replies from the role, or the same objection every time.
The disconfirmer is the part teams skip. Without it, every reply looks like encouragement.
Keep the document in a shared doc or version control. If you use HubSpot, the sync writes the ICP version to each company record [[5]](#sources). The point is that when you change your mind, you can see what you changed and why.
If your data lives in a CRM, connect it so the analysis reads real outcomes. HubSpot is read for companies, deals and owners, and Outlevo writes its status, fit score and next step to fields it owns [[5]](#sources). It never edits your standard HubSpot fields, and nothing is written until an owner or admin approves the field mapping [[5]](#sources). Salesforce is a pilot: the connection needs the Outlevo package in your org, which Outlevo installs with you, and there is no AppExchange listing [[10]](#sources). See the Salesforce integration page for the details. Connecting and syncing a CRM uses no credits [[5]](#sources).
Start small and keep it small
Do not pick a batch size from a benchmark. Use this rule instead: send no more than you can follow up by hand, and no more than you will read every reply to.
Why that rule works:
- Every reply is data at this stage, including the short and rude ones.
- A small batch lets you change the email after ten minutes of reading replies. A large batch has already gone out.
- A small batch limits the damage if the list was wrong.
If you want to build the whole flow before anything is sent, use test keys. They run against a sandbox with 100 fake companies, so you can build without sending anything or spending credits [[11]](#sources). The developer hub also states that test keys are not charged [[12]](#sources). This is useful if you have a developer on the team and want to wire replies into your own tools first.
Set up sending properly
Mailbox setup is slow. Plan for it.
Outlevo has two rules here. Before a campaign sends through Smartlead, every mailbox must be connected and warmed up, and its domain must have SPF, DKIM and DMARC checked in the last 7 days [[13]](#sources). If you use managed mailboxes, a new mailbox sends nothing until it is warm: at least 14 days, usually about 3 weeks [[14]](#sources).
So the first campaign cannot start the day you sign up. Set up sending first, write the ICP while the mailboxes warm up, and send when they are ready.
Some details on the setup:
- With managed mailboxes, Outlevo buys sending domains, creates the mailboxes through Zapmail, sets up DNS and warms them up, so you never touch your main domain [[14]](#sources). You choose the domains Outlevo proposes and the sender names [[14]](#sources).
- Builder includes 1 domain and 2 mailboxes. Growth includes 2 domains and 4 mailboxes [[14]](#sources).
- With Smartlead, Outlevo builds each campaign there, and Smartlead sends from the mailboxes in your Smartlead account [[13]](#sources). Campaign leads are pushed in batches of 100 [[13]](#sources). Sent, reply, bounce, unsubscribe and category changes come back to Outlevo by webhook [[13]](#sources).
- Sending, follow-ups and the mailboxes your plan includes use no credits [[13]](#sources).
For what a sequence is and how follow-ups fit into it, see the glossary.
Keep a person in the loop
At this stage, you want to read what goes out. Outlevo's approach is that nothing is sent outside a policy that a person approved. Policies set who can be contacted, on which channels, how often and with what budget [[15]](#sources). Every external action is checked against the approved policy before it runs, and recorded in a ledger [[15]](#sources). Kill switches pause a campaign, a channel or the whole workspace at once [[15]](#sources).
Outlevo is not the only tool that offers a review step. Reply.io describes it as "Approve each message before it goes out, or let it run on autopilot" [[16]](#sources). 11x says "Every message can be reviewed, edited or overridden before it goes out, or it runs on autopilot" [[17]](#sources). For the full comparison of approach, read autonomous SDR vs approval-first outbound.
For a first campaign, choose review. Autopilot is for when you already know what a good email looks like. You do not yet. Reading the drafts is how you find out.
For more on writing the first line, see cold email personalization by hand vs policy.
LinkedIn, if you use it
LinkedIn can sit next to email. Outlevo sends a connection invitation with a note of at most 300 characters, then one message after the person accepts. A reply stops that lead's emails [[18]](#sources). Each person connects their own account [[18]](#sources).
Automatic sending comes with Growth and Managed, or with a LinkedIn seat on Builder. Otherwise the invitations and messages are drafted for you to send by hand [[18]](#sources).
Read LinkedIn's own terms before you turn it on. Its User Agreement prohibits using "bots or other unauthorized automated methods to access the Services, add or download contacts, send or redirect messages" [[19]](#sources). That is your decision to make, with the terms in front of you. If you want the lower-risk route, send the drafted messages by hand.
Rules to know before the first send
Three public rules come up often. This is not legal advice. Read them and ask a lawyer about your case.
- The FTC says of CAN-SPAM: "The law makes no exception for business-to-business email." [[20]](#sources)
- GDPR Article 6(1)(f) refers to "processing is necessary for the purposes of the legitimate interests pursued by the controller or by a third party". [[21]](#sources)
- The ICO says under PECR: "You can email or text any corporate body (a company, Scottish partnership, limited liability partnership or government body)." [[22]](#sources)
They are different rules for different places. Which ones apply depends on where you and your recipients are, and that follows from the markets you chose to sell into.
Sample first email (example)
Example only: written for this playbook, not sent to anyone.
Subject: {{specific thing on their site}}
Hi {{first name}},
I read {{the page you read}} and saw {{one observation, with the date you read it}}.
We build {{one plain sentence on what your product does}}. I am writing because {{the reason this company, this week}}.
Are you the right person to ask about {{the problem}}? If someone else owns it, a name is enough.
If this is not relevant, reply "no" and I will not write again.
{{your name}}
{{your role, company}}
Notes on the email:
- It names one observation you can point to. If you cannot, cut the line.
- It asks one question. It does not ask for a call.
- It makes no claim about results. At this stage you have none to cite, and a claim you cannot source will cost you the reply.
- It gives a way out. That is a courtesy, and it also keeps the replies you read clean.
Read every reply
This is the research part. Reading replies is what your first campaign is for.
Sort replies into groups: interested, wrong person, wrong timing, not for us, unsubscribe. Then write down the reason in the customer's own words. Do this by hand for the first batches.
Some tools that help:
- Smartlead sends reply, bounce and unsubscribe events back to Outlevo [[13]](#sources).
- If you connect Calendly, Outlevo answers interested replies with your booking link, with their name and email filled in. On autopilot the answer goes at once. Otherwise it waits in Replies for you to send [[23]](#sources).
After each batch, ask three questions. Did the role answer? Did the segment answer? Did the reason you gave match the reason they gave? Then change one thing and send the next small batch.
If a segment gets no replies from the right role across a few batches, check your disconfirmer. Dropping a segment is a result. It is cheaper to learn that now than after hiring an SDR.
What it costs
Plans, as listed on pricing: Free is USD 0 a month. Builder is USD 29 a month with 320 credits. Growth is USD 149 a month with 1650 credits. Managed starts from USD 999 a month, on a contract [[6]](#sources).
Credit costs for the research steps in this guide: light qualification costs 1, qualification costs 3, contact discovery costs 4, email verification costs 1 and deep research costs 30. A signal check costs 1 and a person signal costs 1 [[6]](#sources).
Deep research is the one to ration. Use it on accounts that already look like a fit, not on the whole list. Sending, follow-ups, LinkedIn sending and CRM syncing do not use credits [[13]](#sources) [[18]](#sources) [[5]](#sources).
If you build against the API, metered calls quote their credit cost first and run only when confirmed [[11]](#sources). Reads are free [[11]](#sources).
Comparing data tools to feed the list? See data and enrichment tools: pricing compared and Outlevo vs Clay.
A checklist for the first campaign
- Write the ICP: segment, role, reason, disconfirmer.
- Import past deals if you have them, and note how many won companies you have; under 10 is very low confidence [[1]](#sources) [[3]](#sources).
- Tell Outlevo which countries you sell into [[3]](#sources).
- Set up mailboxes and start warm-up. Allow for at least 14 days [[14]](#sources).
- Check SPF, DKIM and DMARC on the sending domain, within 7 days of the send [[13]](#sources).
- Build a small batch: one role, one segment.
- Review every email before it goes out.
- Read every reply and write down the reason.
- Change one thing. Send the next batch.
Next step
Start with the part that costs nothing: the free ICP assessment. It reads up to 5 public pages of your website and returns facts labeled as verified observations or AI inferences, plus up to 5 experimental segment hypotheses [[4]](#sources). Take those hypotheses, check them against your own deals, and write the ICP down before you send anything.
Sources
- Release 2026-10-19
- CSV and Excel integration
- ICP from evidence
- Free ICP assessment
- HubSpot integration
- Outlevo pricing
- Readiness Cards
- Website visitors integration
- Release 2026-10-19
- Salesforce integration
- REST API and SDK integration
- Developer hub
- Smartlead integration
- Managed mailboxes integration
- How Outlevo works
- Reply.io Jason AI
- 11x AI personalization
- LinkedIn integration
- LinkedIn User Agreement (section 8.2, Don’ts)
- FTC: CAN-SPAM Act compliance guide for business
- GDPR Article 6(1)(f): lawfulness of processing
- ICO: Electronic mail marketing (PECR)
- Calendly integration