Practices/ Customer Tech/CRM & Marketing Automation
Customer Tech01 / 03

CRM & Marketing Automation

Automation amplifies whatever you give it, including the confusion.

A CRM nobody trusts and automation nobody understands are worse than no system at all. Whichever platform you run, we define how your revenue actually works first, then build the system around it, and stay accountable for whether people use it after launch.

SAME SOFTWARE, TWO OUTCOMESCLEAR PROCESSAUTOMATIONGROWTH ATSPEEDUNCLEARPROCESSAUTOMATIONCONFUSION ATSCALE
SAME SOFTWARE, TWO OUTCOMESCLEAR PROCESSAUTOMATIONGROWTH AT SPEEDUNCLEAR PROCESSAUTOMATIONCONFUSION AT SCALE

The input decides the output. So the process comes first.

01 · The idea

What This Practice Is

A CRM is the system of record for every account, contact, deal and customer. Marketing automation is the set of rules that act on that record: routing a lead, scoring it, moving it between stages, sending the next message. CRM implementation is making both of them run the way your revenue actually works.

The software is the easy part. The hard part is the model underneath it: what counts as a qualified lead, what each pipeline stage means, who owns an account at each handoff, and which numbers leadership will trust. Get those wrong and the best-configured system in the world produces reports nobody believes.

That is why this sits with an executive rather than an administrator. We own the business outcome of the system, not just the build, and we stay until your team prefers it to a spreadsheet.

02 · The problem

Why Systems Get Routed Around

One

The tool arrived before the process

A platform is bought to fix unclear ownership and inconsistent stages. It cannot, so the unclear process gets formalized in software and runs faster.

Two

Every team has its own definitions

Marketing calls a form fill qualified. Sales requires a verified buying process. The reports can never agree, and every pipeline review becomes an argument about data.

Three

More tools, more places to break

Systems that do not talk to each other, data kept in several places, and each new tool adding another definition of the same thing.

Four

Nobody owns it after launch

The implementation partner leaves, fields drift, and within two quarters the team is back in spreadsheets with a CRM they still pay for.

03 · The practice

One Revenue Language

Before anything is configured, sales, marketing and customer success agree the definitions the system will enforce. This is the step most implementations skip, and the reason most of them are routed around.

Lifecycle stagesWhat moves a contact from lead to customer, and who decides.
QualificationThe evidence a lead needs before sales accepts it.
Pipeline stagesExit criteria based on what the buyer did, not what the rep felt.
Forecast categoriesWhat commit, best case and pipeline actually mean here.
HandoffsWho owns the next action, and what must be on the record when they take it.
Churn and expansionDefined once, so retention numbers mean the same in every room.
04 · The method

How the Work Runs

Ninety days to a working operating rhythm, with automation deliberately last. The first thirty days build nothing at all.

THE PROCESS FIRST, THEN THE BUILDBASELINEFOUNDATIONSCADENCENEXT PHASEDAY 1DAY 30DAY 60DAY 9001 · BASELINEDAYS 1 TO 30WHAT IS TRUENOWRevenue goals andfunnel performanceProcess gaps andhow reliable thesystems areOwnership, and thegap in forecastaccuracy02 · FOUNDATIONSDAYS 31 TO 60FIX WHAT HURTSMOSTPipeline stagesstandardizedQualificationdefined, criticalfields repairedLead routing andhandoff ruleswritten down03 · CADENCEDAYS 61 TO 90RUN IT, THENCHECKManagement rhythmput into practiceAdoption measured,not assumedWhether thereporting istrusted yet04 · NEXT PHASEAFTER DAY 90BUILT ONEVIDENCEAdvancedautomation, only ifadoption holdsOr frontlineadoption beforemore complexityChosen on what days61 to 90 showed
THE PROCESS FIRST, THEN THE BUILDBASELINEFOUNDATIONSCADENCENEXT PHASEDAY 1DAY 30DAY 60DAY 9001 · BASELINE · DAYS 1 TO 30WHAT IS TRUE NOWRevenue goals and funnel performanceProcess gaps and how reliable the systems areOwnership, and the gap in forecast accuracy02 · FOUNDATIONS · DAYS 31 TO 60FIX WHAT HURTS MOSTPipeline stages standardizedQualification defined, critical fields repairedLead routing and handoff rules written down03 · CADENCE · DAYS 61 TO 90RUN IT, THEN CHECKManagement rhythm put into practiceAdoption measured, not assumedWhether the reporting is trusted yet04 · NEXT PHASE · AFTER DAY 90BUILT ON EVIDENCEAdvanced automation, only if adoption holdsOr frontline adoption before more complexityChosen on what days 61 to 90 showed

AUTOMATION COMES LASTAutomation should amplify a clear process, not formalize confusion. Until the process is proven, nothing gets built on top of it.

Fix the highest-friction point first. For one company that is pipeline stages, for another it is lead routing or customer handoffs.

Quick wins in days 31 to 60 matter because they prove the new discipline improves performance without slowing the business down.
05 · The fit

Where You Are Now

Most companies move through four stages. Maturity is not tool count and it is not effort. It is whether revenue strategy turns into repeatable execution.

Reactive

Manual reporting, definitions that vary by team, and pipeline reviews spent arguing about the data.

Emerging

Core systems in place and a RevOps owner, still spending too much time cleaning data and answering ad hoc asks.

Integrated

Agreed cross-functional metrics, consistent stages, and planning connected to execution and reporting.

Optimized

Scenario-based planning, with capacity, coverage and conversion modeled with discipline.

How to assess it honestly, and how we measure the work.

  • Can leadership explain the forecast gap
  • Are stage definitions objective and enforced
  • Do handoffs happen without friction
  • Can problems be acted on this quarter
  • Do managers actually use the definitions
  • Is the reporting trusted in the room

Forecast accuracy is the first of these we look at. If nobody can explain the gap between forecast and actual with confidence, the system is less mature than the tool list suggests.

06 · The stack

The Platforms We Work In

We work inside most major CRM and marketing automation platforms, and we do not sell you a new one to make the engagement easier. If the system you already pay for can run your revenue model, we make it do that. If it cannot, we will say so plainly.

CRM
  • Gold partnerHubSpotHubSpot
  • SalesforceSalesforce
  • Microsoft Dynamics 365Microsoft Dynamics 365
  • Zoho CRMZoho CRM
  • PipedrivePipedrive
  • Oracle NetSuiteOracle NetSuite
Marketing automation
  • Gold partnerHubSpot Marketing HubHubSpot Marketing Hub
  • Salesforce Account EngagementSalesforce Account Engagement
  • Adobe Marketo EngageAdobe Marketo Engage
  • ActiveCampaignActiveCampaign
  • MailchimpMailchimp
HubSpot Gold Solutions Partner badge

On HubSpot, we go further. Mahdlo is a HubSpot Solutions Provider at the Gold tier, listed in the HubSpot Solutions Directory, and we run our own business on the same platform. The six workstreams and four hubs we implement are set out on our HubSpot partner page.

Everywhere else, the method is the same: one revenue language, the process before the build, and ownership after launch. None of that depends on whose logo is on the login screen.

07 · The answers

Questions We Get

What is CRM implementation?

CRM implementation is setting up a customer relationship management system so it reflects how a company actually sells and serves customers: lifecycle and pipeline stages, qualification rules, data fields, routing, automation and reporting. A good implementation starts with agreed definitions and ends with the team using the system, not just with the software configured.

What is the difference between a CRM and marketing automation?

A CRM is the system of record for accounts, contacts, deals and customers. Marketing automation is the set of rules that act on that record, such as scoring and routing leads, moving contacts between stages, and sending the right message at the right time. Automation is only as good as the CRM data and the process underneath it.

Which CRMs do you work with?

Most major platforms, including Salesforce, HubSpot, Microsoft Dynamics 365, Zoho CRM, Pipedrive and NetSuite, and marketing automation in HubSpot, Salesforce Account Engagement, Marketo, ActiveCampaign and Mailchimp. We are a Gold tier HubSpot Solutions Provider, and the method, agreed definitions first and automation last, is the same on every platform.

Should we choose HubSpot or Salesforce?

We work in both, so this is a fit question rather than a sales one. Salesforce tends to suit larger organizations that need deep customization and have the administrators to maintain it. HubSpot tends to suit small and mid-sized companies that value ease of use and fast adoption. The better question is which one your team will actually use, because a platform people route around costs more than either license.

Do we have to switch CRMs to work with you?

No. Most engagements work inside the system you already have. Replacing a CRM is expensive and disruptive, so we only recommend it when the platform genuinely cannot run your revenue model, and we will show you why before anyone signs a new contract.

We already own HubSpot and nobody uses it. Can you fix that?

Usually, and it is one of the most common engagements. It starts with the baseline, not a rebuild, because an unused system is almost always a definitions and ownership problem before it is a configuration problem.

How long does it take?

About ninety days to a working operating rhythm: thirty to establish the baseline, thirty to fix the highest-friction foundations, and thirty to run the management cadence and measure adoption. Advanced automation comes after that, if the evidence supports it.

What does it cost?

Cost scales with the state of the current system and how much of the revenue model needs defining before anything is built. Thirty minutes on a call is usually enough to size it.

Ready to talk?

Thirty minutes is usually enough to know whether this is the right practice for you.

Schedule a conversation

Not ready to talk? Start with the Growth Engine Diagnostic: give us your website and see where your revenue engine works, where it leaks and where we would start.