[ Prospecting ]

Build a SaaS prospect list with enrichment and AI outreach

Source SaaS companies, enrich them with pricing and traffic context, then generate personalized cold-email drafts in the same Cockpit spreadsheet.

Use this playbook

Overview

Build a SaaS prospect list with enrichment and AI outreach by keeping sourcing, qualification, and message generation in one spreadsheet workflow. This playbook is useful when you do not just need more rows. You need a tighter list of companies, enough context to decide whether they fit your offer, and a first draft of outreach that already references what you learned from enrichment.

Source SaaS companies, enrich them with pricing and traffic context, then generate personalized cold-email drafts in the same Cockpit spreadsheet.

How it works

Filter a SaaS company source

Target company rows imported into Cockpit

Enrich pricing and traffic context

Qualification signals added per row

Generate personalized cold emails

Row-specific outreach drafts ready

Review the best-fit accounts

Approved prospects ready for handoff

Step-by-step process

1
Build the starting SaaS company list
The first decision is not which prompt to use. It is which companies should enter the sheet in the first place. In the walkthrough, the operator starts from a company database source instead of a static CSV so the segment can be defined before any enrichment credits are spent.
The example target is US SaaS companies with fewer than 100 employees, plus keywords such as software, SaaS, and mobile apps. Before importing the final batch, the operator previews the source to check whether the companies actually resemble the intended market, then caps the example run at 50 rows to keep the first pass inspectable.
A good result at this stage is a sheet full of plausible accounts, not just a high row count. If the preview looks noisy, tighten geography, headcount, or keyword logic before moving forward.
2
Enrich each company with pricing and ICP context
Once the rows land in Cockpit, the workflow shifts from sourcing to qualification. The video adds company-level research focused on pricing and ICP context because the example offer is pricing consulting for SaaS companies.
This step matters because the best prospect list is not always the biggest one. It is the one where each row contains enough commercial context to judge whether outreach makes sense. Pricing information, company positioning, and fit clues do more work here than generic firmographics alone.
If the output comes back thin or inconsistent, that is useful signal. You may need tighter source filters, a different provider, or different research fields before AI generation is worth running.
3
Layer in Similarweb traffic signals
After the pricing pass, the walkthrough adds Similarweb traffic data. This gives the sheet a second layer of account quality before any message is drafted.
The operator specifically reviews traffic volume, traffic trend, top countries, and traffic sources. Those fields help answer practical questions such as whether the business shows visible traction and whether the account looks broad enough to prioritize for outreach.
You do not need perfect certainty here. You need enough signal to prioritize rows and enough context for the later AI step to say something concrete. If the traffic fields look wrong or empty, verify the company mapping before trusting the output.
4
Generate personalized cold emails from attached columns
With sourcing and qualification in place, the workflow moves into AI generation. The operator creates an AI email column, writes a concise prompt, and attaches the fields the model should use as context.
In the demo, the offer is pricing consulting services. The attached context includes LinkedIn JSON, pricing findings, the exact search context, and Similarweb traffic signals. That pattern is important: the model is not asked to invent personalization from scratch. It is asked to synthesize the evidence already present in the sheet.
A strong result is a concise message that reflects real company signals without sounding bloated. If the draft feels generic, the fix is usually better attached columns or a tighter prompt rather than more AI verbosity.
5
Run all rows and review the resulting drafts
The last step is review. After choosing the model, the operator runs the AI step across the selected rows and inspects the output inside the spreadsheet instead of exporting immediately.
That matters because the final output is more than a lead list. It is a working outbound batch with source logic, qualification context, and first-draft copy visible together. From here you can filter weak accounts, rerun only the rows that need work, or hand off the best prospects to your next tool.
Before moving on, check whether the rows you would actually contact are the same rows the workflow now prioritizes. If they are not, use the run as a calibration pass and revise the earlier steps.

Key outputs

Pricing and ICP context

Enrichment

Company-level context gathered during the first enrichment pass so the operator can quickly judge fit and message relevance.

Pricing notes
ICP clues
Company context

Traffic signal columns

Similarweb

Website traction fields used to sharpen prioritization and give the AI more concrete inputs for personalization.

Traffic volume
Traffic trend
Top countries

Personalized cold email

The generated outreach draft for each company, written from the attached pricing, LinkedIn, and traffic signals and left in the sheet for review.

Personalized opener
Offer angle
Concise CTA

How to build a better SaaS prospect list

A SaaS prospect list is only useful if the rows are specific enough to act on. A generic list of software companies usually creates more work later: someone still has to check whether the companies fit the offer, look for signs of traction, and write outreach that does not sound like it was sent to every company in the category.

The workflow shown here starts earlier than a normal enrichment pass. It begins with the source itself: choosing a market, company size, and keywords before the rows enter the sheet. That makes the first import a controlled batch instead of a dumping ground.

Use company filters before importing rows.
Keep the first run small enough to inspect manually.
Only enrich fields that help qualification or outreach.

Once the companies are in Cockpit, the goal is not to add data for its own sake. Pricing context helps judge whether the account looks like a real fit. Similarweb traffic adds another layer of qualification by showing whether the company has visible traction, which countries drive demand, and how people reach the site. Those signals make the list easier to prioritize and give the AI column better material to work with.

Signal	Why it matters
Pricing context	Shows whether the company is likely to fit the offer.
Traffic data	Helps prioritize accounts with visible traction.
AI draft	Turns research into a first message a human can review.

This is also a useful playbook when you are trying to replace a manual prospecting routine. Many teams still export a large list, open several tabs per company, copy notes into a spreadsheet, and switch to a separate AI tool for message drafts. Keeping sourcing, enrichment, and AI output in the same sheet makes it easier to understand why a company was included and what informed the final outreach angle.

It is not the right workflow for every outbound task. If you already have a clean contact list and only need copy, an AI-only workflow may be faster. If you only need verified company or contact data, a pure enrichment workflow may be enough. This page is most useful when you need targeting, qualification, and first-draft outreach to happen together.

A practical way to judge the output is to ask three questions after the run:

Are the imported companies actually inside the segment you meant to target?
Do the enrichment columns explain why a row is worth pursuing?
Would a rep realistically want to edit and send the generated draft?

If one of those answers is no, that still gives you a useful diagnosis. Bad source filters create noisy rows. Thin research creates weak qualification. Weak context creates generic AI drafts. The value of this workflow is that the whole chain stays visible in one place, which makes it easier to improve the next batch.

The final step is turning the enriched rows into first-draft outreach. Because the AI prompt can reference the source data, pricing research, and traffic signals, each draft has a better chance of mentioning something concrete about the company. The output still needs human review, but the sheet now contains the full path from targeting to qualification to message draft, which is what makes it useful for a repeatable outbound workflow.

To get started

Choose the company segment and filters you want to source
Decide which enrichment fields should inform qualification and outreach
Write an AI prompt that tells Cockpit how to use the attached company signals

When to use this

You want to build a targeted outbound list from company criteria instead of importing a static CSV
Prospecting quality depends on pricing, ICP, or traffic context before outreach starts
You want list building and first-pass email generation to happen in the same reviewable sheet

Integrations

Similarweb

AI columns

CSV export

What you can swap

This playbook follows the workflow shown in the video, but the exact source, enrichment, prompt, and handoff can be changed to match your team.

Source filters and row limits
Company enrichment fields
Traffic provider or signal set
AI model, prompt, and export destination

Common questions

Is this workflow only for SaaS companies?

No. The demo uses SaaS filters, but the same pattern works for any segment where company-level enrichment and personalized outreach matter. You would just change the source filters, research fields, and message angle.

Why enrich traffic before generating the email?

The walkthrough uses Similarweb data as additional evidence about the company. That gives the AI more concrete material to reference and helps the operator prioritize which rows deserve follow-up first.

Do I need to send the emails from Cockpit?

No. This playbook focuses on sourcing, enrichment, and draft generation inside the spreadsheet. Once the rows are reviewed, you can export or hand them off to the outbound tool your team already uses.

What should I do if the first imported list looks noisy?

Use the preview and the first small batch as a filtering checkpoint. Tighten the geography, headcount range, or keyword set before running more enrichment. The workflow works best when the first imported rows already resemble the companies you would genuinely want to contact.

Can I swap Similarweb for another signal source?

Yes. Similarweb is the traffic layer shown in the walkthrough, but the broader idea is to add one more company-level signal before AI generation. Any provider that gives reliable traction or company-context data can fill that role.

How many rows should I run on the first pass?

The example trims the batch to 50 rows so the operator can inspect the results without spending too many credits. That is a good default pattern: start small, validate the segment and the prompt, then scale after the workflow looks right.

More Prospecting playbooks

Import and enrich CSV leads

Upload a trade show list, map names and domains, enrich missing emails and company fields, then export the approved rows.

Use your LinkedIn network for prospecting

Export your LinkedIn connections, import the file into Cockpit, shortlist the people who fit your offer, then draft messages or build a sequence from the strongest warm-path rows.