Field report — home

We build CRMs the way a reporter files a story:
from the field notes,
not the brochure.

RSM is a HubSpot consulting practice. We design, build, and migrate CRMs for companies that need the system to work the first time — not the third. We're opinionated about how, and quiet about how loudly. Everything on this page is proof in the open: what we actually believe, what we actually ship, and an honest place we hold for the work we're proud of — told plainly when clients say the word.

Signed by the people doing the work

Field notes Written from the work — no invented numbers

Editorial illustration of a route toward go-live looping back on itself at month two

Fig. 01 — Where a build stalls

Migration & build

Why a CRM build stalls in month two

The first month is all momentum. The second is where the gap between the demo and the daily habit shows up. The cause is almost never the software.

The demo worked, the portal is standing up, everyone's optimistic — and then the rework loop opens. A field doesn't match the name the team actually uses. A stage doesn't fit the deal they sell a dozen times a week. So the workaround quietly re-enters. Nobody announces the stall; the system just starts being updated on Fridays, then not at all.

The fix isn't a louder poster or another training day. It's building to the work people already do — which is exactly what the diagnostic is for. We build to the field notes, not to the brochure.

Read the note →

Editorial survey map with a route and a crosshair on where the real work happens

Fig. 02 — The field map

Diagnostic

The diagnostic is the deliverable

Before we build anything, we ride along. We watch how the team actually sells — the words they use, the handoffs that work, the data they trust. The map we make of that is the most useful thing we ship, because it's the spec the build is held to.

Read the note →

Editorial illustration of a rigid grid of instructions dissolving into one continuous habit-line

Fig. 03 — The habit line

Adoption

Adoption is designed, not encouraged

A poster that says "use the CRM" changes nothing. Adoption is the result of a system that slots into the work instead of interrupting it. We design for the habit first — then the habit shows up on its own.

Read the note →

The work in context Case studies — a framework, not a claim

A place we reserve for the work, told honestly.

We don't publish case studies we can't stand behind. None are published yet. This is the shell they'll live in — the story structure we hold every engagement to, so that when a client approves a write-up it lands in the same honest shape. No invented clients, no invented numbers, no borrowed logos.