Revlyn
Revlyn/Partners/Bitscale in Action

Live plays · Bitscale on top of HubSpot

A CRM that goes
looking for revenue.

Bitscale is the layer we bolt onto HubSpot so your pipeline stops waiting for reps to type names into a form. It watches the internet, enriches what it finds, and drops usable records right where your team already works. We install the plays. We run them. We kill the ones that stop earning.

signal_ledger.log
live · last 4 h
utcsource · signal → actionscore
  • 14:02
    LinkedIn Careers
    3 new AE roles posted, 30d window
    → create task · SDR outbound
    92/100
  • 13:47
    BuiltWith
    Segment tag deployed on pricing page
    → enrich company · notify AE
    78/100
  • 12:31
    Crunchbase
    Series B close, $22M, 2 days ago
    → upsert deal · lifecycle: MQL
    88/100
  • 11:15
    GitHub
    Public repo migrated off HubSpot API v1
    → flag risk · CS owner
    64/100
  • 09:58
    G2 Reviews
    Competitor review left last night
    → draft opener · queue for review
    71/100
routed → HubSpot5 / 142 today
outbound nurture internal

Sample ledger from a live install. Sources are public.
Scores are the operator's, not the model's.

01
What Bitscale is

An AI data + workflow platform for GTM teams. Think enrichment + agent workflows + outbound intelligence, in one workspace.

02
Where it sits

Between the open internet and your CRM. It fetches, cleans, scores, then hands rows to HubSpot.

03
What Revlyn does

We design the plays, wire them to your HubSpot properties, write the prompts, and keep them tuned every week.

The catalog · Ten plays we install

What we actually build
on top of Bitscale.

You do not need all ten. Most teams start with three, get them humming for two months, then add the next three. Everything below is a real thing we have shipped, not a slide.

Play · P01

Sourcing on a live ICP

The ICP is a query, not a spreadsheet you re-buy every quarter.

142 MATCHES

We translate your ICP into a Bitscale query: firmographics, tech stack, hiring signals, geography. Bitscale re-runs it on a schedule. New matches drop into HubSpot as companies with the right owner and lifecycle stage.

Company recordsOwner routingLifecycle: Lead
Play · P02

Enrichment for the records that matter

Not every field on every row. The fields your workflows actually read.

employeesstackfundingintenthiring

We pick the ~15 fields your reps and workflows consume, then let Bitscale keep them fresh. Firmographics, technographics, funding, employee count deltas, primary contact roles. Old records get a one-time backfill.

15 HubSpot propertiesBackfill runWeekly refresh
Play · P03

Intent + trigger monitoring

The world is noisy. We tell it what counts.

JOBFUNDSTACKNEWS

Job posts for roles that predict a purchase. Funding rounds in your ICP. Tech installs (Segment, Snowflake, Salesforce). Press mentions of a competitor. Each fires a HubSpot task with the reason attached, so the rep opens their inbox with context, not a name.

Trigger libraryReason stringsTask auto-create
Play · P04

Contact discovery + waterfall

Who actually makes the call. Not a director of interns.

CEO / FounderVP RevenueHead of RevOpsMarketing Ops

For each qualified company, Bitscale runs a waterfall to find the buying committee. Titles are mapped to your persona list. Emails are verified. Slack alerts fire in your rep channel with a 90-second brief.

Persona mapVerified emailsSlack brief
Play · P05

Agent-drafted outreach that sounds like you

The email arrives with a reason for existing.

SUBJECT · Segment install last Tuesday?Saw you shipped Segment on the pricing page.Usually means an attribution rewrite is coming.We rebuilt Datapel's HubSpot in two weeks: 19% → 68% MoM lead → SAL.Worth 20 min?

We build the prompt library: tone, structure, forbidden phrases, proof snippets. Bitscale agents draft opener + one follow-up per trigger. Everything routes through a HubSpot approval queue for the first two weeks, then to reps with review gates.

Prompt libraryApproval queueReply routing
Play · P06

Account research briefs

One page. Everything a rep needs before the call.

GTM MOTIONRECENT MOVES

Bitscale composes a live brief per account: what they sell, who runs GTM, funding, hiring, tech stack, recent moves, competitors. Pinned to the HubSpot company record. Refreshed the morning of any scheduled meeting.

One-page briefPre-meeting refreshCompany timeline
Play · P07

Deal signal monitoring

Open deals aren't sleeping. Bitscale watches them for you.

For every open opportunity, we set up a watch: leadership changes, funding, layoffs, new integrations. Fires a HubSpot task on the deal owner with the change and a suggested next step. Stale deals get automatic reactivation prompts.

Open-deal watchlistReactivation promptsDeal notes
Play · P08

ABM tier + territory build

Named accounts, tiered by value, mapped to a rep.

T124accountsT286accountsT3312accounts

We segment your target list into Tier 1/2/3, define the play per tier (multi-thread, sequence, nurture), and hand each tier to Bitscale for signal watch. Territory changes ripple back into HubSpot ownership automatically.

Tier definitionsTerritory rulesPlay-per-tier
Play · P09

CRM hygiene, on a schedule

The dirtiest CRM is the one nobody fixes.

dedupe running…

Dedupe, standardise, retire dead records, correct titles, fix domains, patch missing owners. Bitscale runs the checks nightly. We approve the diffs weekly. Reps stop yelling at Salesforce, sorry, HubSpot.

Nightly dedupeWeekly diff reportRetire rules
Play · P10

Reporting that a founder can read

One dashboard. Live. No screenshotting from four tabs.

We wire Bitscale outputs into a single HubSpot dashboard: sources fired, triggers routed, accounts touched, meetings held, pipeline created. Weekly note goes to founders in plain English. No screenshotted charts, ever.

HubSpot dashboardWeekly noteSource-of-truth metrics

One workflow, end to end

Signal walks in.
A qualified meeting walks out.

Runs on
A schedule you set. Hourly, daily, weekly, per source.
Owned by
One senior Revlyn operator. Not a shared queue.
Measured by
Meetings held, not emails sent.

Playbooks · Written, not verbal

Every play ships
with a paper trail.

Because when a rep leaves, the play should not leave with them. Each playbook lives in your Notion or Google Drive and gets versioned.

Playbook · 016pp
Outbound
Outbound: hiring-signal opener
Trigger
Company posts 3+ AE roles in 30 days
What runs
  1. 01Bitscale detects the hiring signal on LinkedIn + careers page
  2. 02Enrichment: pull ICP fit score, tech stack, funding stage
  3. 03AI drafts opener referencing the specific roles hired
  4. 04Task auto-created in HubSpot for the owning AE
  5. 053-touch cadence: email → LinkedIn → email
ObservedReply rate 11.4%
Playbook · 029pp
ABM
ABM Tier-1 multi-thread cadence
Trigger
Named account enters active buying window
What runs
  1. 01Map 5 personas per account: Champion, EB, Users, Finance, IT
  2. 02Bitscale enriches each with intent + engagement history
  3. 03Sequenced touches staggered across 21 days
  4. 04Rep gets a HubSpot task with a written next-best-action
  5. 05Meetings booked route to the correct AE by territory
Observed1.8 meetings per account
Playbook · 034pp
Deals
Reactivation for stalled deals >45d
Trigger
Deal untouched for 45 days in stage 3+
What runs
  1. 01Bitscale scans for a fresh signal (news, hire, product launch)
  2. 02If signal found, generate a specific re-open message
  3. 03If no signal, generate a graceful close-lost with a return path
  4. 04Update HubSpot deal stage + note the reason
Observed22% reopen rate
Playbook · 045pp
Expansion
Expansion play on new integration
Trigger
Customer connects a new integration in-product
What runs
  1. 01Product event lands in HubSpot via webhook
  2. 02Bitscale enriches the account with usage depth
  3. 03CSM gets a task with a written expansion angle
  4. 04Auto-drafted email tied to the integration adopted
Observed1.4x net revenue retention lift
Playbook · 058pp
Ops
Enrichment field spec
Trigger
New company or contact created in HubSpot
What runs
  1. 0118 fields enriched on Company: size, stage, tech, funding
  2. 029 fields enriched on Contact: seniority, function, tenure
  3. 03Dedupe against existing records before write
  4. 04Ownership routing runs on the enriched record
Observed94% record completeness
Playbook · 0612pp
AI
Prompt library · brand voice
Trigger
Any AI-generated message before send
What runs
  1. 01System prompt encodes your voice, tone, banned phrases
  2. 02Persona-specific prompts for CEO, VP Sales, IC
  3. 03Fact-check step: no invented case studies or claims
  4. 04Human approval queue for the first 30 days
Observed0 hallucinated claims shipped

Deliverables · What lands

You leave with a system,
not a slide deck.

Everything below is yours the day the engagement starts. Nothing is locked behind our seat.

Bitscale workspace
Configured against your HubSpot pipelines, lifecycle stages, and property schema.
Signal library
8–12 curated triggers with reason strings your reps understand.
Prompt library
Written, versioned, brand-safe. No hallucinated case studies.
HubSpot wiring
Two-way sync, dedupe, ownership rules, task auto-create, approval queues.
Playbooks
One document per play. What runs, when, why, what a rep does next.
Dashboard
A single HubSpot report. Sources, triggers, meetings, pipeline created.
Weekly note
Plain English. Sent Friday. Read by founders on Saturday morning coffee.

Timeline · From zero to signal

Four weeks. Then it runs.

Week 1
Wire it in
HubSpot audit for the fields Bitscale needs. Workspace configured. First two plays scoped.
01
Week 2
First plays live
Sourcing + enrichment + one trigger running through the approval queue. Reps trained in 30 minutes.
02
Week 3
Loosen the reins
Approval queue moves to spot-check. Reason strings tuned. Prompt library edits based on reply quality.
03
Week 4
Meetings show up
First meetings booked from Bitscale-sourced signal. Dashboard live. Weekly note begins.
04

Ways to work together

Three ways in.

Mode · 01
One-time install

You have a Bitscale seat. You want it wired properly. We come in, install the plays, hand over playbooks and dashboards.

Best if you already run outbound in-house.
Mode · 02
Embedded in HubSpot as a Service

The default. Bitscale is one lane inside a full HubSpot operating engagement. Same senior operator runs both.

Best if your CRM and Bitscale should think as one system.
Mode · 03
Signal-only retainer

You do the outreach yourselves. We keep Bitscale sourcing, enriching, and routing signal into HubSpot every week.

Best for teams with a strong AE bench.

Common questions

Things founders ask us
before signing.

01Do we need a Bitscale seat before we start?+

No. We help you decide the right seat size after the first walkthrough. Most teams start on a smaller plan than they think.

02What if we already have Clay or Apollo?+

Bitscale plays nicely alongside both. Sometimes we replace, sometimes we co-exist. We tell you honestly on the first call.

03Who writes the prompts?+

A senior operator on our side, with your product marketer in the room. Never an intern, never fully agent-generated.

04Does the agent send emails on its own?+

Only after two weeks of approval-queue review and only through your reps' inboxes with review gates. Reply handling is human.

05What happens if a play stops working?+

We kill it. Every play has a kill criterion written in advance. No sunk-cost automations left running for months.

Talk to the operator, not a form

Bring us the ICP.
We will show you what
Bitscale actually finds.

Read the partnership termsinfo@revlyn.io