Brief · CRMbyRSM · A new theme built off Obsidian's ideas

Three directions for a CRM site that doesn't look like every other CRM site.

Same content. Same dark + green spine. Same movement vocabulary (hover, ambient, scroll-fill, no glow/shimmer). Three different visual languages sitting between technical and premium consulting.

Each direction shows snippets of Home, Services, Blog, and a self-service tool so you can judge them across the page types you'll actually ship. Every block is structured as a HubSpot module — see the build map at the bottom.

01
Blueprint
Technical. Engineered. Mono labels, grid undertones, corner-draw hovers. Electric green.
Space Grotesk · JetBrains Mono
02
Ledger
Editorial. Documentation feel. Serif display, hairlines that fill on scroll. Sage green.
Newsreader · Onest
03
Atrium
Premium consulting. Generous whitespace, all-sans, drifting gradient field. Deep emerald.
Hanken Grotesk · DM Mono
Direction 01
Blueprint

For the technical side of your audience. Feels like a system that's documented, not a brochure that's decorated.

Display
Space Grotesk
Mono
JetBrains Mono
Accent
#4FE39A
SYS / RSM / HUBSPOT STATUS: OPERATIONAL v.2026.05

CRM that your
team will actually use.

We design, build, and migrate HubSpot for companies that need the system to work the first time — not the third.

// SERVICES.LIST()

Four practices, one operating model.

Each engagement starts with the same diagnostic. From there we plug in the practice — or stack — your situation needs.

S.01

HubSpot Implementation

Sales, Service, Marketing, Operations, Content. Stood up properly — the first time.

S.02

CRM Migration

Salesforce, Pipedrive, Zoho, spreadsheets. We move records without losing the history they depend on.

S.03

Sales Process Design

Pipelines, stages, exit criteria, forecast logic. A process the team will follow because it matches how they actually sell.

S.04

Integration & Automation

Quote-to-cash, finance sync, support handoffs. Custom workflows that don't break when HubSpot ships an update.

Field notes from inside the system.

All entries →
0001 2026 · 05 · 02

Why your CRM migration stalls in month two.

MIGRATION
0002 2026 · 04 · 18

The hidden cost of unused HubSpot seats.

FINOPS
0003 2026 · 04 · 03

Mapping a sales process your team will actually follow.

PROCESS
0004 2026 · 03 · 21

Quote-to-cash without a custom dev team.

AUTOMATION
// SELF_SERVICE / DIAGNOSTIC

What's your CRM costing you?

Three sliders. One number. A starting point for the conversation — not a sales trick.

ANNUAL DRAG / EST. $0
Direction 02
Ledger

For the side of your audience that reads. Feels considered, written, edited — closer to a publication than a product page.

Display
Newsreader
Body
Onest
Accent
#B8D49A
RSM Consulting · Established 2014 Vol. 12 · Issue 05 · May 2026

A CRM that matches how your
team actually sells.

Most CRM problems aren't software problems. They're decisions the system was never told about — written down nowhere, surviving only in the memory of three salespeople and a spreadsheet.

What we do — and how.

§ I — IV
§ I

HubSpot Implementation

From a blank portal to a system your team logs into without being asked. We configure all five hubs against your real sales motion, not a textbook one.

Typical engagement8–14 weeks
§ II

CRM Migration

Salesforce, Pipedrive, Zoho, spreadsheets. The records arrive intact — and so does the history your reps and managers depend on.

Volumes handledUp to 12M records
§ III

Sales Process Design

Stages, exit criteria, forecast logic, dashboards. The process you have on paper, but actually written into the system that runs your week.

Where we startPipeline diagnostic
§ IV

Integration & Automation

Quote-to-cash, finance sync, support handoffs, lifecycle automation. Custom workflows that survive HubSpot's quarterly updates.

Tools we connect40+ integrations

From the writing.

Read all entries →
FEATURE· May 2 · 9 min read

Why your CRM migration stalls in month two.

The pattern repeats: kick-off feels great, the first sprint ships, then something goes quiet around week six. It's almost always the same root cause — and it isn't the software.

Read the piece
FinOps · Apr 18 · 4 min

The hidden cost of unused HubSpot seats.

Most clients are paying for ~30% more seats than they're actively using. Here's how to find them.

Process · Apr 3 · 7 min

Mapping a sales process your team will actually follow.

Stop modelling what management wants to see. Model what reps already do — then tighten.

Automation · Mar 21 · 5 min

Quote-to-cash without a custom dev team.

What you can do with native HubSpot, what you need integrations for, and where to draw the line.

Adoption · Mar 8 · 6 min

The first 90 days after go-live.

The hardest part of an implementation isn't the implementation. Here's the playbook we run after launch.

A short diagnostic

What is your CRM costing you?

Three honest answers. One rough number. It won't be precise, but it usually surprises people in the right way.

14
6
$75
Estimated annual dragWhat you're leaving on the table
$0
Direction 03
Atrium

For the executive side of your audience. Reads as a premium consulting firm — confident, spacious, deliberate.

Display
Hanken Grotesk
Mono
DM Mono
Accent
#2EC09A
Now booking · Q3 2026 engagements

The CRM your team actually wants to use.

We are a HubSpot consulting practice for companies that need their CRM to work — quietly, accurately, the first time. Sales, Service, Marketing, Operations, Content. All five hubs.

Implementations
142
since 2014
Adoption / 90d
86%
team-wide average
Records migrated
8.4M
across 120+ portals
Time to live
11wk
median engagement

Four practices.
One operating model.

Every engagement starts with the same diagnostic. From there we plug in the practice — or the stack — your situation calls for.

01 / 04

HubSpot Implementation

From blank portal to system your team logs into without being asked. All five hubs, configured against your real motion.

Read more
02 / 04

CRM Migration

Salesforce, Pipedrive, Zoho, spreadsheets. Records arrive intact — and so does the history your reps depend on.

Read more
03 / 04

Sales Process Design

Pipelines, stages, exit criteria, forecast logic. A process your team will follow because it matches how they actually sell.

Read more
04 / 04

Integration & Automation

Quote-to-cash, finance sync, support handoffs. Workflows that don't break when HubSpot ships an update.

Read more

Notes from the practice.

All writing
Feature · Migration
May 2 · 20269 min read

Why your CRM migration stalls in month two.

The kick-off feels great, the first sprint ships, then something goes quiet around week six. The pattern repeats — and it isn't the software.

Read the piece
FinOps
Apr 184 min

The hidden cost of unused HubSpot seats.

Most clients pay for ~30% more seats than they actively use. Here's how to find them.

Read
Process
Apr 37 min

Mapping a sales process your team will follow.

Stop modelling what management wants to see. Model what reps already do — then tighten.

Read
Diagnostic · 30 seconds

What is your CRM costing you, right now?

Three honest inputs, one number. A starting point for a real conversation — not a sales trick.

CRM Drag Calculator
Estimated annual dragWhat you're leaving on the table
$0
HubSpot build map · How this becomes a real theme

Every block above is a module.

Naming, structure, and content are all written as if these were already HubSpot modules. Below: the proposed module list per direction, the theme fields that drive the look, and the motion approach — all of which fit a marketplace-clean theme on top of the Obsidian baseline.

Modules per page
Home · hero-{dir}, services-{dir}, blog-listing-{dir}, diagnostic-{dir}, cta-block
Services · hero-secondary, services-grid, process-steps, case-study-strip, faq, cta-block
Blog · hero-listing, blog-featured, blog-list (reuses listing module), newsletter-cta
Self-service · hero-secondary, diagnostic-{dir}, results-panel, cta-block
Theme fields (extending Obsidian)
theme.colors.* → bg, surface, card, accent, accent_warm, text, text_sub, text_muted
theme.typography.* → heading, body, mono (new), display (new, optional serif)
theme.motion.* → reveal_distance, reveal_duration, ambient (on/off), cursor_glow (on/off)
theme.direction → blueprint | ledger | atrium (sets all the above to a preset)
Motion (replaces glow/shimmer)
Scroll reveals · IntersectionObserver in /js/motion.js adds .is-in. Modules style themselves.
Timeline fill · scroll-driven rail height on .tl-rail elements (services + process).
Ambient · CSS-only background drift per direction (grid / grain / blob).
Hover · per-module CSS — corner-draw, side-rail, lift, cursor-tracked light. No glow.
What changes vs. current Obsidian
Kill · button shimmer, box-shadow glow on hover, the nth-child fade-slide on .dnd-section
Keep · the field schema, the grid system, the responsive breakpoints, the HubL contracts
Add · direction presets, scroll-driven rails, ambient layers, cursor-tracked highlights
Rewrite · main.css motion block, hero modules, services + blog listing modules
Next decisions
Pick a direction (or mix — e.g. Atrium type with Blueprint hovers). I'll then build out the full page-level mocks for Home / Services / Blog / Self-service in that direction, plus a style tile with the complete color/type/component system, ready to hand to a HubSpot dev to turn into modules.