Systems & How-To

The Close CRM Configuration I Deploy Before Any Team Goes Live

By Felix Maru · November 10, 2026 · 7 min read

I have set up Close CRM for a handful of different teams over the past few years, and every time I open a fresh instance the experience is the same: the defaults are technically functional, but practically wrong. Generic lead statuses that don't map to how anyone sells. No smart views. Sequence templates written for a hypothetical prospect who doesn't exist. Reps land in the tool, poke around for a week, and start building workarounds instead of pipelines. By month two, the CRM is a mess and nobody trusts the data.

The fix is not complicated. It's a one-afternoon configuration pass before anyone else logs in. Here is exactly what I do.

Start With Lead Statuses

Close ships with statuses like "Potential," "Open," "Contacting," "Unqualified," "Interested," and a handful of others. These are fine as concepts, but they describe an abstract pipeline, not an actual sales motion. The first thing I do is rewrite them to match what the team actually does.

For a typical outbound SDR setup, I replace the defaults with:

The logic here matters as much as the labels. Status is the rep's answer to "where is this lead in my pipeline?" If the statuses don't match the actual stages of your process, every pipeline review becomes a conversation about what a word means rather than what a deal needs. Get it wrong once and you will spend months trying to retroactively clean it up.

Close lets you define statuses per pipeline. If the team runs both outbound and inbound motions, build separate pipelines with separate status sets rather than trying to squeeze both into one.

Build Three Smart Views Before the First Rep Logs In

Smart views are saved searches that update in real time as records change. They are the best feature in Close and the one most teams underuse. The three I always build first:

1. No Touch in 3 Days. Filter: leads in "Active Cadence" status where the last activity date is more than 3 days ago. This surfaces sequences that have quietly stalled. Without this view, a rep can easily have 15 leads sitting in "Active Cadence" with nothing actually running. The view makes the problem visible in one click.

2. Qualified, No Next Step. Filter: leads in "Qualified" status with no open task and no upcoming event. These are the deals most likely to slip. Someone had a good conversation, marked the lead qualified, and then didn't book the next action. This view is the safety net for that moment.

3. My Open Tasks Today. Filter: tasks assigned to current user, due today or overdue. Pin this to the sidebar as the rep's default landing view. It replaces the habit of checking email to figure out what to do next. Everything that needs attention is in one place.

Name them clearly, pin them to the sidebar in the right order (Today's Tasks first, then No Touch, then Qualified No Next Step), and walk through how to use them in the team onboarding session. A view nobody knows about is just a view that doesn't exist.

Set Up One Starter Sequence

Most reps run email sequences manually because the built-in defaults don't match how they talk. Rather than leaving them to build from scratch, I drop in one opinionated starter sequence before go-live. The goal is not perfection. It is giving people a starting point they can customize instead of a blank screen that paralyzes them.

The structure I use:

Everything in this sequence is a template, not a script. Flag it clearly in the template name ("Starter Outbound v1 - customize before using") so reps understand it's a scaffold, not a finished product.

Add Four Custom Fields

Close lets you add custom fields to contacts, leads, and opportunities. The defaults give you name, company, email, phone. That is not enough to run a real pipeline review. The four I always add:

Four fields. Add more and they stop getting filled in. The discipline is to only add a field if someone will actually update it and someone will actually use it in a decision.

Configure Activity Notifications (Then Turn the Rest Off)

Close has a broad notification system that most teams leave at the defaults, which means everyone is getting alerts for everything and ignoring most of them. The ones worth keeping on:

Everything else: off by default. Notifications about lead status changes, sequence completions, and activity updates are useful when they're actionable. When they're background noise, reps tune out the whole notification channel, including the ones that matter.

Every notification that isn't directly tied to a next action is training your team to ignore all of them. Default to off and add back only what someone will act on.

The Whole Pass Takes One Afternoon

Rewriting statuses takes about 30 minutes, including testing them in a sample pipeline. Building the three smart views takes another 20. Setting up the starter sequence, with the email copy drafted properly rather than placeholder text, runs about 90 minutes if you're being honest about the writing. Custom fields are 15 minutes. Notification settings are 10. You're done in under four hours, usually less.

What you get on the other side is a CRM your reps can actually navigate. Status labels that match how they think about the pipeline. Views that surface what needs attention without manual searching. A sequence they can personalize rather than build from scratch. Fields that make pipeline reviews a conversation about deals instead of a conversation about what fields mean.

If you're inheriting a Close instance that's already a mess rather than setting up a fresh one, the approach is the same but slower. Fix the statuses first (data cleanup is impossible without consistent statuses). Then build the smart views, which start returning value immediately. Then audit the sequences and kill any that haven't been touched in 60 days. Work through it over a few weeks rather than trying to do it all at once.

The CRM that never got properly set up is the one everyone stops trusting. That trust, once lost, is very hard to rebuild.

If you're in the middle of a Close setup or a messy CRM cleanup and want to compare notes, reach out here. Happy to look at what you're working with.

Share 𝕏 in ✉

Comments