How to Do Customer Segmentation Step by Step

A RevOps lead at a 40-person SaaS company opens HubSpot and tries to build a segment: "Pro plan customers with 3+ support tickets this month." She can filter by lifecycle stage. She can filter by deal value. But plan tier lives in Stripe, support tickets live in Intercom, and neither field exists in HubSpot. Every guide on how to do customer segmentation starts at step 4: "build your segments." Nobody explains step 1 through 3, which is where the actual work happens: getting the data from your tools into one place.

For the full breakdown of customer segmentation types and methods, we covered that in our pillar guide. This guide picks up where that one stops. You already know what customer segmentation is. Now you want to do it, this afternoon, with the tools you already run.

Why most customer segmentation projects fail before they start

Customer segmentation projects fail for one reason: the data is scattered. Not missing. Scattered.

Your billing tool knows which plan each customer is on, when they subscribed, and whether they paid last month. Your support platform knows how many tickets each customer filed, how long resolution took, and whether they escalated. Your product database knows how often each customer logs in, which features they use, and when they last created a record. Your CRM knows lifecycle stage, deal value, and last sales touchpoint.

Each tool has a piece of the customer profile. No tool has the full picture. And you cannot segment on data you cannot access in one place.

Every competitor guide on market segmentation analysis follows the same pattern: define your ICP, list segmentation types, build personas, analyze gaps, optimize. That methodology works if you already have unified data. For a team of 40 people without a data engineer, it skips the hardest part. You don't need a framework for customer segmentation step by step. You need your Stripe data in your CRM.

Step 1: Map the customer data you already have for customer segmentation

Before syncing anything, audit what data exists in each tool. Open a spreadsheet and create four columns: tool name, record type, useful fields, and overlap with other tools.

Most teams discover they have 15-20 useful segmentation fields scattered across 4-5 tools. The fields that matter most for customer segmentation are the ones that differ between tools. Lifecycle stage already exists in your CRM. Plan tier exists only in Stripe. That is the field worth syncing.

Pick 5-8 fields that would change how your team operates if they appeared on every CRM contact record. For most SaaS teams, this list looks like: plan name, MRR, subscription status, support ticket count (last 30 days), last login date, and features used count.

Step 2: Choose your customer segmentation dimensions

Segmentation dimensions are the axes you segment on. Most guides list a dozen types of market segmentation analysis. For a practical implementation, you need three to five dimensions that map directly to business decisions.

The key insight: each dimension requires data from a specific source tool. If the data stays in that source tool, you cannot segment on it in your CRM. The segmentation analysis marketing teams want to run is only possible when the underlying data is accessible.

Avoid the temptation to pick 15 dimensions. Start with three: one from billing (plan tier), one from engagement (last login), and one from support (ticket count). Three dimensions produce eight possible segments. That is more than enough to start making different decisions for different customer groups.

Step 3: Sync data between tools for customer segmentation step by step

This is the step that every customer segmentation guide skips. Getting billing data, support data, and product usage data into your CRM so you can segment on all of it.

Connect Stripe to your CRM. In Oneprofile, add Stripe as a source and HubSpot (or your CRM) as the destination. Authenticate with API keys. Select Stripe Customers and map them to CRM Contacts using email as the matching key. Map the fields you chose in Step 2:

Use "Update or Create" sync mode. Set a 15-minute schedule.

Connect Intercom to your CRM. Same process. Map Intercom Contacts to CRM Contacts on email. Sync the fields that drive your support health dimension:

Connect your product database. If your app writes to Postgres, connect it as a source. Map your users table to CRM Contacts. Sync last login, features used, and records created. These fields power your engagement and adoption dimensions.

After all three syncs run, every CRM contact record has billing data, support data, and product usage data. You now have the foundation for customer segmentation that actually works.

Step 4: Build customer segments in your CRM and activate them across workflows

With synced data in your CRM, building segments takes minutes. Use your CRM's native list builder (HubSpot Active Lists, Salesforce Reports, Attio Lists) to create saved segments from the synced fields.

Five starter segments that cover the most common business decisions:

Each segment triggers a specific action. A segment without an action is a vanity metric. Connect segments to CRM workflows: when a contact enters the "Churn risk" segment, auto-assign a task to the account owner. When a contact enters "Upgrade candidate," enroll them in an email sequence that highlights the paid features they haven't tried.

This is how to segment customers without a CDP, a warehouse, or a data engineer. The CRM's native filters do the segmentation work. The data sync layer does the data unification work. Together, they replace the bottom 80% of what an enterprise segmentation platform provides.

What changes after customer segmentation is live

The Monday morning CSV export disappears. When a customer downgrades in Stripe, their CRM segment changes within 15 minutes. When they file three support tickets in a week, they move into the churn risk segment automatically. Your success team gets a Slack notification instead of discovering the problem during a quarterly review.

The first week, spot-check 20 records per segment. Verify that the filter criteria produce the right contacts. Adjust thresholds if needed: maybe "14 days since last login" is too aggressive for your product and 21 days is the real risk signal. The data is live, so adjusting criteria takes seconds.

The second week, add more dimensions. Sync additional fields from Stripe (cancellation date, coupon code) or from your product database (specific feature flags, API call counts). Each new field unlocks more granular segments without adding complexity to the sync setup.

By month two, your CRM is the segmentation engine your team has been asking for. Every contact record reflects current billing status, recent support interactions, and real product engagement. Marketing sends campaigns to segments defined by actual behavior. Sales prioritizes accounts by revenue and engagement, not gut feel. Support sees the full customer context before answering the first ticket.

Oneprofile handles the data flow that makes this possible. Connect Stripe, Intercom, your product database, and your CRM. Map the fields you care about. Set a schedule. Every contact record stays current, and your CRM's native filters become your customer segmentation engine. No CDP, no warehouse, no data engineer. Free to start.