Most UK SMEs I meet don’t have a “Salesforce problem.”

They have an implementation problem.

They’re paying for licences, but:

  • Pipeline lives in spreadsheets
  • Quotes and contracts are built manually in Word
  • Leaders don’t fully trust the reports, so they double‑check everything outside the system

Salesforce becomes a very expensive address book.

My whole job at Redigitised is taking businesses in that exact spot and turning Salesforce into what it should have been from day one: a resilient operating system that runs the business, not just reports on it.

Below is how I think about that, and how we fix it in a focused 4‑week sprint.

Why your team really avoids Salesforce

If reps hate using Salesforce, it’s rarely because they’re “lazy” or “don’t like change.”

It’s usually three things:

  1. Every update feels like admin work
    Too many fields, too many required picklists, too many clicks.
    So the real work happens in email and Excel, and Salesforce gets updated “later” (read: never).
  2. Salesforce doesn’t drive the process
    Stages exist, but nothing changes when you move from one to the next.
    No prompts, no tasks, no templates.
    It’s a scoreboard for work done elsewhere.
  3. Documents still live outside Salesforce
    Quotes, proposals and contracts are built manually in Word / Excel.
    That’s where you quietly lose hours a day per salesperson.

A recent project: 2 hours per rep, per day, back

On a recent engagement, a UK client came to me with:

  • Deals managed in spreadsheets
  • Quotes built from scratch in Word
  • Contracts retyped each time

They already had Salesforce. It just wasn’t running the show.

In 4 weeks we:

  • Mapped their real‑world sales process and rebuilt it inside Salesforce
  • Captured the right data at the right moment (no 27‑field forms “just in case”)
  • Hooked up quote and document generation directly from Salesforce
  • Added guardrails so reps couldn’t “go rogue” and break the process

Result: each salesperson got around 2 hours a day back to sell instead of formatting documents.

Same people. Same licences. Different design.

The 5‑lens Salesforce Health Check

When I run a Blueprint / Health Check, I look at your org through five lenses:

  1. Process fit
    • Does your actual sales / service process live in Salesforce?
    • Do stages trigger clear next actions, owners and due dates?
  2. Data quality
    • Are reps entering the minimum viable data to move a deal?
    • Can leadership pull a trusted pipeline view without “fixing” reports?
  3. Adoption & effort
    • How many clicks to update a deal, log activity or raise a quote?
    • If it’s more than a few seconds, adoption will always lag.
  4. Automation & documents
    • Do tasks, follow‑ups and handoffs get triggered by the system?
    • Are quotes / docs generated from Salesforce, or manually assembled?
  5. Visibility for leadership
    • Can you answer “What’s closing this month?” from one dashboard you trust?
    • Or are you cross‑referencing exports and gut feel?

Most “broken” orgs fall down on at least two of these.

Why the second implementation is always more expensive

By the time many SMEs call me, they’re on round two.

The first implementation usually:

  • Was sold as a generic “quick start”
  • Followed menus and standard objects, not your process
  • Got “patched” internally into a Frankenstein org

On paper, that first build looked cheap. In reality it cost you:

  • Adoption (people went back to spreadsheets)
  • Trust (leaders stopped believing the numbers)
  • Agility (every small change felt risky)

The second implementation has to:

  1. Unwind the bad decisions
  2. Redesign from the business backwards
  3. Make Salesforce the operating system, not a side tool

That’s why it feels more expensive. You’re paying to fix the past as well as design the future.

Before you spend another £1 on Salesforce, ask this

If you’re about to start or restart a project, answer:

  1. What problem are we actually trying to solve, in one sentence?
  2. Where will our single source of truth live: Salesforce or spreadsheets?
  3. What would make this project a failure in 6–12 months?
  4. Who owns Salesforce internally and cares about the outcome?
  5. What’s the smallest 4‑week win we can ship that gives the team time or trust back?

If you can’t answer those clearly, that’s your risk. The tech isn’t the constraint. The thinking is.

Want a blunt assessment of your org?

If you’re a UK business with Salesforce that currently feels like a chore, I offer a short Salesforce Blueprint call.

In 15 minutes we will:

  • Score your org on the five lenses above
  • Pinpoint the biggest leaks in time, trust or adoption
  • Outline what a focused 4‑week fix could look like

Use the contact form / booking link on this page to request a Salesforce Blueprint call, and include “BLUEPRINT” in your message.

No fluff, no slides. Just a clear view of whether your Salesforce is salvageable, and how to turn it into the operating system it should have been from day one.