Searchbase for SaaS sales teams: account lists and buying signals in one prompt

Quick answer: SaaS sales teams use Searchbase to build account lists a contact database cannot produce, companies hiring for a specific role, running ads on a specific keyword, or naming a specific tool on their own site, with the evidence attached to each row. Describe your ideal customer. Searchbase finds them across Europe in one prompt, with the source on every cell. A first list of a hundred accounts with signals takes minutes and a few hundred credits, and the free plan renews 150 credits a month so you can test the motion before paying anything.

What SaaS sales teams ask for

The prompts that work are the ones a junior rep could execute by hand if they had a month. Real examples:

• "Companies in Amsterdam with 50 to 200 employees hiring a Head of Revenue Operations, with the job post link and the careers page."
• "SaaS companies in Berlin running Google Ads on 'customer data platform', with the ad text and the landing page they point to."
• "Fintech companies in Paris that mention Snowflake or dbt anywhere on their engineering blog, with the page where they say it."
• "Companies in Stockholm that announced a new office in Milan or Madrid in the last twelve months, with the press source."
• "Digital agencies in Lisbon that list HubSpot as a partner on their site, with the partner page and a contact email."
• "Companies in Dublin advertising HR software on TikTok, with the creative and the advertiser page."

The pattern is a segment, a signal, and the proof you want next to it. Vague prompts like "SaaS companies in Europe" return a large and useless table. A signal turns the same table into a call list, because every row already contains the reason to reach out.

What comes back

A spreadsheet that streams in while the agent works. For a SaaS account list the usual columns are company name, domain, country and city, employee range where the company states it, the signal itself in full, and the page it came from.

The signal column is the one that matters. For a hiring prompt it holds the job title and the date the post appeared. For an ad prompt it holds the creative text and the platform. For a technology prompt it holds the sentence on the page, not an inference about it. Every cell carries a link back to the page it was read from, a freshness badge with when it was collected, and the extraction method. If a value cannot be verified, the cell stays n/a. Searchbase does not guess an employee count or a budget it did not read somewhere public.

Contact columns appear when the contact is public: a role inbox on the site, a form URL, a named person on a team page. Direct dials and personal mailboxes are what contact databases sell, and today teams use Apollo for exactly that. Searchbase is the layer that tells you which accounts are worth looking up.

Sources that matter for SaaS sales

Nine job boards carry most of the weight, because a job post is the cheapest honest signal a company emits about its next twelve months. A company hiring its first RevOps lead is buying tooling. A company hiring three implementation consultants has customers to onboard.

Company pages come second, and they are underused. Pricing pages, changelogs, engineering blogs, partner directories and integration pages state, in the company's own words, what stack they run and who they sell to. That is a page read, and a page read costs about one credit.

Three ad libraries, Meta, Google and TikTok, answer the question a database never can: who is spending money on this category right now, and what are they saying. Press coverage catches funding rounds and market entries. Twelve social platforms are where the people behind the account live once you know which account to care about. Directories help in categories that are well indexed and add little where they are not.

A worked example

Prompt: "Companies in Amsterdam with 50 to 200 employees hiring a Head of Revenue Operations, with the job post link and the careers page."

The agent plans first, and you watch it plan. It decides to search the job boards for the role across the Amsterdam metro area, then to open each hiring company's own careers page to confirm the post is live and not a syndicated copy, then to read the company site for size and category.

Then it searches, opens roughly a hundred and twenty pages, and extracts as it goes. Rows appear in the table before the run ends, so you can stop it if the segment is wrong. At about one credit per page read, a run like this costs a couple of hundred credits. Adding the hiring manager from a social profile costs about three credits per profile. If you then want a full brief on the ten best accounts, Deep Research costs 20 to 40 credits per report and returns a cited write-up rather than a row.

What comes out is roughly forty companies, each with a live job post, a date, a careers URL and a domain. Today teams assemble the same list with LinkedIn Sales Navigator and a lot of tab switching, then lose the evidence when they paste it into the CRM.

From the table to the first message

Once the table exists, the agent drafts outreach for the people in it. It writes email and LinkedIn sequences that reference the actual signal, the specific role being hired, the specific ad, the specific line on the pricing page, because that is the only part of the row a prospect cares about.

Every draft goes through a review step. You read the sequence, edit what sounds wrong, and nothing leaves without your approval. Sending from the campaign wizard is still rolling out, so the practical workflow today is: review the drafts, export, and send from the tool your team already uses. Export is JSON on every plan, CSV from Starter, an API from Pro and webhooks on Business, so the list can land in your CRM without a copy and paste.

Pricing for a SaaS sales team

Free costs nothing and renews 150 credits a month, enough to run one real segment end to end and see whether the signal you picked actually predicts a reply.

Starter at €29 a month gives 1,000 credits and CSV export. That is roughly one solid list a week for a single rep working one territory.

Pro at €79 a month gives 4,000 credits and API access, which is where most SaaS teams land. Four thousand credits covers weekly refreshes of several segments, and the API means the table becomes a job that runs on Monday morning instead of a task someone remembers to do.

Business at €199 a month gives 12,000 credits and webhooks, so a new match on a saved segment can push straight into the CRM as a task. Prices are in euros, the company is European, and the product works in English and Italian.

Frequently asked questions

Does Searchbase replace our contact database? No. A database is better at direct dials and verified personal emails at scale. Searchbase is better at deciding which accounts belong on the list in the first place, and at finding the ones no database has indexed yet.

How current are the signals? Every cell carries the date it was collected. A job post read this morning says so. Nothing in the table is older than the run that produced it, and you can rerun a saved prompt whenever you want fresh rows.

Can I see why a company is in the list? Yes, that is the point. Click the cell and you land on the page the value came from. If a value could not be verified on a public page, it is n/a rather than a plausible number.

Does it send the emails? The agent drafts the sequences and you approve them. Launching from the campaign wizard is being switched on progressively, so today most teams review and export.

How many credits does a typical account list cost? Reading a page is about one credit, a social profile about three, a Deep Research report 20 to 40. A hundred-account list with one signal per account usually lands between 150 and 300 credits.

Does it work outside Europe? It reads any public page, so yes. Coverage, languages and pricing are tuned for European teams, which is where it is strongest.

Prices checked on 2026-09-08 on searchbase.org.