DATA INFRASTRUCTURE · SEGMENTATION

Data Infrastructure for Segmentation

ICP criteria applied to every account you own or could own, fit scored with reasons, segments cut by industry, size, stack, signal and stage, and each one delivered as a list, a chart and a report the team can act on. The infrastructure under segmentation, run by autonomous AI agents.

FIT SCORED WITH REASONSSEGMENTS THAT REFRESHCHARTS AND REPORTS INCLUDED
20+
segmentation fields

Firmographics, technographics, funding, hiring, intent, geography and CRM stage, on every row before a filter runs.

1
score per row, explained

Fit against the ICP with the reasons listed, so a segment boundary is an argument you can read.

segments per list

Cut the same enriched list as many ways as the team needs; each segment is its own refreshable list.

0
credits for scoring

Scoring, filtering, charts and reports are free; only the enrichment that fills the fields bills.

⟨ THE JOB TODAY ⟩

Where the week actually goes.

01 /

Segments are built on fields nobody trusts

The CRM says "Mid-Market" because a rep picked it from a dropdown in 2022. Headcount is blank on a third of accounts, industry is free text, and every segmentation exercise starts by cleaning the fields it depends on.

02 /

The ICP lives in a slide

Everyone agrees on the ideal customer in the kickoff and nobody can apply it to a list. Turning "B2B SaaS, 50 to 500 people, runs a modern CRM, hiring in ops" into a filter needs data the filter tool does not have.

03 /

The report is a one-off

The analysis that produced the tiers was a spreadsheet exported on a Tuesday. Accounts moved, raised and hired since, and the tiers did not.

SEGMENT REPORTACCOUNTS · 4,120
WITH ASTROFABRIC

What changes when agents carry the work.

The ICP as executable criteria

Industries, size bands, geographies, technologies, funding stages, hiring patterns and intent topics held as a profile the agents apply, with weights you can adjust and a plain-language override for one-off cuts.

icp_profile · list_score

Every row enriched before it is filtered

Firmographics, technographics, funding, hiring and intent filled through a waterfall of licensed sources, so a segment on headcount or stack is cut on complete fields with a source on each.

list_enrich · tech_stack · hiring_signals

Fit scored with reasons

Each account scored against the profile with the reasons listed: the criteria it meets, the ones it misses and the signal that moved it. Tiers are cut on the score, and the boundary is inspectable.

list_score · list_get

Segments as lists, charts and reports

Each segment saved as a refreshable list, charted by size, industry, stack or signal, and summarized in a written report delivered to Slack, a sheet or the CRM as a property.

render_chart · list_export · list_push
HOW IT WORKS

From objective to delivered rows.

  1. 01 · UNIVERSE

    Choose the universe

    A CRM export, a saved list, a CSV or a discovery mission that builds the universe first. Suppression applies before anything is scored.

  2. 02 · ENRICH

    Enrich

    Every account filled with the fields the ICP needs: size, industry, geography, stack, funding, hiring and intent, with a source on each value.

  3. 03 · SCORE

    Score

    Fit against the workspace ICP or a one-off profile, with reasons per row and adjustable weights.

  4. 04 · SEGMENT

    Cut segments

    Tiers and segments by score, industry, size band, stack, signal or CRM stage, each saved as its own list with a name and an owner.

  5. 05 · REPORT

    Chart and report

    Distribution charts and a written summary: what each segment looks like, how many accounts, which signals cluster there and what to do first.

  6. 06 · DELIVER

    Deliver and refresh

    Segment membership written to the CRM as a property after approval, the report posted to Slack, and the whole cut re-run on a schedule.

⟨ THE DATA ON EVERY ROW ⟩
IndustrySub-industryHeadcount bandHeadcount growthRevenue rangeHeadquarters country and regionFunding stageMonths since last roundTechnologies in useTechnology category coverageOpen roles by functionBuying-intent topicsCRM stage and ownerCustomer, prospect or churnedFit score and reasonsSegment and tier
USE CASES

The jobs this page was written for.

Tier the CRM

Every account in the CRM enriched and scored against the ICP, cut into three tiers with reasons, membership written back as a property so routing, SLAs and sequences key off it.

A tiered book of business the whole team can see the logic of.

Territory design on evidence

A target universe segmented by region, size band and stack, charted so territories balance on scored accounts instead of raw counts, exported per rep as a list.

Territories that carry equal opportunity, on the numbers.

Segment by stack

Accounts grouped by the CRM, data warehouse or marketing platform they run, so each segment gets messaging and playbooks that match its integrations.

Stack-specific segments with the count and the names.

Find the segment that converts

Closed-won and closed-lost enriched and compared: which industries, sizes, stacks and signals cluster in wins, charted, and the ICP updated with what the data shows.

An ICP grounded in your own outcomes.
BEFORE AND AFTER

Segmentation, before and after

By handWith AstroFabric
FieldsDropdowns and free text from years agoEnriched through a waterfall, sourced and dated
ICPA slide everyone agrees withExecutable criteria the agents apply to any list
ScoringA formula in a spreadsheetFit with reasons on every row, weights you set
SegmentsA one-off exportNamed lists that refresh on a schedule
ReportingCharts built by hand each quarterCharts and a written report on every run
DeliveryEmailed spreadsheetCRM property after approval, report in Slack
MISSIONS YOU WOULD RUN

Described in plain language. Delivered end to end.

SCORING & VERIFICATION

Tier the whole CRM

Every account enriched, scored against the ICP with reasons and cut into tiers, membership staged as a CRM property with the distribution charted.

EnrichmentScoringChartsHubSpot
ONE MISSION · EVIDENCE ATTACHED
SCORING & VERIFICATION

Win-loss segment analysis

Closed-won and closed-lost enriched and compared by industry, size, stack and signal, charted, with a written recommendation for the ICP.

FirmographicsTechnographicsChartsGoogle Sheets
ONE MISSION · EVIDENCE ATTACHED
SCORING & VERIFICATION

Stack-based segments

A target list grouped by the platforms each company runs, one list per segment, counts and names reported to Slack for messaging and playbook design.

TechnographicsListsScoringSlack
ONE MISSION · EVIDENCE ATTACHED

Three of a hundred. The full playbook library ships in every workspace, and anything you can describe becomes a mission.

GOVERNED AUTONOMY

Safe enough to actually turn on.

⟨ CONTROL PLANE ⟩ENFORCED AT RUNTIME · NOT ADVISORY

Scoring is free and explainable

Fit scores, filters, charts and reports never bill credits, and every score lists the criteria behind it so a segment boundary can be challenged.

CRM properties wait for approval

Writing a tier or segment onto CRM records is staged as a batch that shows every account and the value it would receive before a person approves.

Suppression before scoring

Customers, competitors and the workspace suppression list are separated before a universe is scored, so segments describe opportunity accurately.

Licensed data only

Every enrichment field comes from licensed providers with its source recorded. The agents never scrape member networks.

FAQ

Questions, answered.

What does data infrastructure for segmentation mean?

The layer that makes segments possible on real data: every account enriched with the fields the ICP needs, scored for fit with reasons, cut into named segments that live as refreshable lists, charted and reported, and written to the CRM as a property after approval. Autonomous agents run each step.

How is the ICP defined?

Onboarding drafts a profile from your website and you confirm or edit it in Settings: industries, size bands, geographies, technologies, funding stages, hiring patterns and intent topics, each with a weight. A mission can override any field in plain language for a one-off cut.

What can segments be cut on?

Any enriched field or signal: industry and sub-industry, headcount band and growth, revenue range, region, funding stage and recency, technologies and categories, open roles by function, intent topics, CRM stage, customer status and the fit score itself. Segments combine criteria freely.

Do segments update?

Yes. Each segment is a list with its criteria attached, so a scheduled run re-enriches the universe, re-scores it and moves accounts between segments, reporting what changed. The CRM property updates after the batch is approved, and every run posts what moved to Slack.

What does the report contain?

Segment sizes and medians, distribution charts by industry, size, stack and signal, the accounts that moved since the last run, the signals that cluster in each segment and a short recommendation on where to start. It posts to Slack, a doc or a sheet.

Can I segment my CRM directly?

Yes. Connect HubSpot, Pipedrive, Attio or Zoho CRM, choose the objects and filters, and the agents enrich, score and segment the records, then stage the tier or segment as a property for approval. Nothing is written until a person approves the batch.

What does segmentation cost?

Scoring, filtering, charts and reports are free. The only billable step is enrichment, a few credits per company row, shown before the run and skipped for rows already complete. Every rate is shown in the console before the work runs, and plans start at $49 per month.

⟨ DEPLOY ASTROFABRIC ⟩

Give segmentation its infrastructure.

Point it at the CRM or a list. Enriched, scored segments come back as lists, charts and a report, and they refresh themselves.