Bitscale: Fill CRM Gaps with Waterfall Data

A row can sit in the system of record for years with an empty phone field and an email that has not worked since the account was created. Reps then copy that row into a spreadsheet, rent another data vendor, and paste the result into a sequencer. Each hop is a chance to overwrite a good value with a stale one. A hiring change or a tech-stack shift shows up in one product and never reaches the person who was supposed to call.

Bitscale

Bitscale is a go-to-market (GTM) data layer for revenue operations (RevOps) teams. It sits on a customer relationship management (CRM) system, builds account and contact lists in spreadsheet-like grids, and enriches them through a waterfall of providers and artificial intelligence (AI).

Native CRM connections include HubSpot and Salesforce. Lists can also start from a file, a search, or a webhook, and finished rows can go back to the CRM or out to a sequencer.

Fewer Empty Fields, Fewer Bounces

The useful case is the list you already have. A waterfall column asks contact-data providers in order and keeps the first valid email or phone. Validation can be required before writing that value to the row. In Bitscale, credits are spent only when a provider returns a valid result. Failed lookups, formula columns, and CRM syncs do not spend credits.

That design is what makes a thin CRM usable for outbound. Work-email and phone coverage are sold as a sequence, not as a single vendor’s database. A separate waterfall handles personal email. Company and people search draws on a monthly search allowance counted separately from enrichment credits.

One customer described what that coverage looked like against a European ideal customer profile (ICP).

Our email and phone waterfall hits 92% coverage on European ICP. Nothing else we tested came close.

Shannon Jhanji, Sales at Guidebook

The public pricing page lists four plans. Annual billing saves 10 percent. The Free plan does not require a credit card.

On Bitscale, Growth adds the wider source catalog, credit rollover up to three times the plan amount, and two-way HubSpot. Booster adds Salesforce and a private Slack channel. Enterprise is scoped on a call. Search for companies and people uses a separate monthly allowance, so those lookups don’t consume the enrichment credits in the table.

What You Can Run in a Grid

The grid is the workspace. Each row is a company or a person, and each column is an input, an enrichment, a piece of AI, or a formula. These are the pieces a revenue team actually turns on.

• AI research and copy: BitAgent can read a live website. ChatGPT and Claude can draft copy in the grid. Perplexity is available as a research action.
• Buying signals: Columns for an executive hire, a tech-stack change, or a funding event, so the list moves when the account moves.
• Grids and workbooks: A grid is one dataset. A workbook groups related grids. A run condition can hold a step until the row is ready, which keeps an expensive lookup off records that will never be contacted.
• Integrations: Native connections include HubSpot, Salesforce, Attio, Instantly, Smartlead, Lemlist, Amplemarket, Outreach, and Slack. A webhook or custom application programming interface (API) supports tools not on that list.
• Playbooks: Ready workflows for prospecting, outbound, champion tracking, and hiring, so the first grid does not have to be designed from a blank sheet.
• Sales Navigator and local sources: Paste a Sales Navigator search URL, pull people who reacted to a post, or start from Google Maps or a Google Sheet.
• Security controls: The homepage displays Service Organization Control (SOC) 2 Type II, California Consumer Privacy Act (CCPA), and General Data Protection Regulation (GDPR) marks, plus role-based access. Enterprise adds single sign-on (SSO).
• Tech-stack enrichment: BuiltWith can mark which products an account already runs, which helps when the offer fits only a certain stack.
• Waterfall contact data: Work email and phone run through a sequence of providers, including Apollo, and stop at the first valid result. Personal email is a separate waterfall with its own provider set.

Bitscale keeps that work in one grid: find the account, fill the contact, check the trigger, and send the row to the system that will work it. The still-empty field and the bounced address are the problems the waterfall is there to shrink.

How to Build a Grid

Bitscale describes the workflow as generate, enrich, then outreach. The Free plan is enough to build the first grid and see which columns return a valid contact.

1. Open a Bitscale account on the Free plan. No credit card is required.
2. Create a grid and choose a source. Options include Find Companies or Find People, a comma-separated values (CSV) file or a spreadsheet, a HubSpot list, a Salesforce report, a Sales Navigator URL, Google Maps, or a Google Sheet.
3. Add a waterfall column for work email or phone. Providers run in sequence and stop at the first valid result.
4. Add an AI column for a researched line or a short outreach note, and gate it so it runs only when the email is already valid.
5. Export the grid, or push the rows to the CRM, a sequencer, or Slack.

You finish with a list you can work from, with the original CRM row still in place for the values you didn’t mean to replace. Use playbooks when the first grid should follow a pattern someone else already designed.

Start a Bitscale Grid