Mayberry Advisory

Deals slow down in the gaps between your tools.

Your revenue team runs a pile of tools and dashboards that do not share data. Leads wait. Handoffs break. The forecast drifts. I find where, rank the gaps by dollars, and design the workflow that fixes them.

From lead to buyer Illustrative Research CRM Quoting Contracts ! Handoff breaks here Every broken handoff is a place a deal waits.
120%+
lifetime quota attainment
277%
of plan at my peak
$5M+
pipelines I have managed
$500k+
multiple net-new wins at that size
The gap analysis

A sample stack, with the handoffs that break.

This is a typical large revenue stack. Each tool does its job. The trouble sits in the links between them. Red dashed lines are handoffs where data stops, gets re-keyed, or lands too late.

HUNT CONVERT CLOSE RETAIN Account research Marketing automation CRM Quoting and pricing Contracts and e-sign Billing Customer success Forecast dashboard 1 2 3 4 Data moves on its own Handoff breaks Sample stack. Illustrative, not a client.
  1. Research to CRMSignals about an account sit in a research tool. The rep who owns the account never sees them, and works a stale list.
  2. CRM to quotingPricing and scope change in email. The quote no longer matches the plan, and late-stage deals wait on approvals.
  3. Contracts to billingSigned terms are typed again by hand. Start dates and amounts drift from what the buyer agreed to.
  4. Customer success to CRMRisk on an account shows up late. The renewal is close before anyone with the relationship hears about it.

Reps feel it too. In Salesforce's fifth State of Sales report, reps said they spend 28% of the week selling, and 66% said they are overwhelmed by the number of tools. Source: Salesforce

The method

Seven steps, in plain order.

I start with a real deal, not a tool list. I follow it through every system it touches and mark each handoff clean, manual, or broken.

  1. Step 1

    Inventory

    List every tool, who owns it, who uses it, and what data goes in and out.

  2. Step 2

    Map to the buyer journey

    Lay the tools over the path a buyer takes, from first trigger to renewal.

  3. Step 3

    Find the broken handoffs

    Trace real deals. Mark where data stops, repeats, or arrives late.

  4. Step 4

    Measure the cost

    Count delay in days, deals touched, and revenue waiting at each gap. Time to buyer is the days from the first qualified signal to the first meeting with the person who owns budget.

  5. Step 5

    Rank by dollars

    Order the gaps by what they cost. Fix the top ones first. Leave the rest alone.

  6. Step 6

    Design the target workflow

    Draw the flow that should exist. Name the data fields, the rules, and the owner of each handoff.

  7. Step 7

    Roll out in 30, 60 and 90 days

    Ship the highest-value fixes first. Check each one against the pipeline.

What you receive

Three deliverables.

Stack map

One picture of how your revenue tools connect today.

  • Every tool, its owner, and its users
  • Data in and out of each tool
  • Each handoff marked clean, manual, or broken

Gap report

A ranked list of what is slowing deals, with evidence.

  • Each broken handoff, shown on a real deal
  • The delay and the dollars at stake
  • A rank, an owner, and a recommended fix

Workflow blueprint

The repeatable system that closes the gaps.

  • The target flow, drawn end to end
  • Data fields, rules, and who does what
  • A 30, 60 and 90 day rollout and the numbers to track

Then a monthly stack review

After the 90 days, a monthly review keeps the gains. It shows the scorecard, what closed, new findings, decisions for your executive sponsor, and the next 30 days.

Every sample uses a made-up client and illustrative figures. They show the format. They are not results.

Why me

Most firms audit and build. I have also closed.

Three things set this work apart. Each one comes with proof.

I have sat on the closing side.

I have carried quota on large enterprise deals and managed the accounts after the sale. I know where a stack hurts a deal in real life, because I have lost time to it.

Proof: over 120% lifetime attainment, 277% of plan at my peak, and multiple retention wins on contracts above $500k a year.

I design systems that repeat.

A fix that depends on one person is not a fix. I write the rules, the templates, and the numbers so a team can run the system without me.

Proof: I built a retention department from zero at a real estate CRM startup. A team of five, a template library, and a blueprint other managers adopted. Average annual value (AAV) grew from $0 to $1.5M.

I keep executives engaged for a long cycle.

Large deals need the CFO and the CIO, and they do not stay engaged on their own. I build the case in their numbers and plan the dates backward from their approval.

Proof: a $5M net-new deal with a cycle past 12 months, signed off by both the CFO and the CIO. It sat inside a 204% year.

The buying journey

From first trigger to signed contract to renewal.

A large deal passes through six stages. At each one, a different group is involved, the buyer believes something different, and a different tool should carry the data.

1 2 3 4 5 6 Trigger Build the group Shape the solution Executive approval Contract and start Renewal A renewal is the next trigger

1Trigger

Who is involved
One executive, or an outside event such as a budget change, a new leader, or a vendor change.
What the buyer believes
Something has to change, but not yet how.
What I do
Find the one or two outcomes the buyer must deliver this year.
Tools that carry the data
Account research, CRM.
Where it usually breaks
The signal stays in a research tool and never reaches the rep who owns the account.

2Build the group

Who is involved
Purchasing, an IT or operations leader, a technical evaluator.
What the buyer believes
Someone else should own the risk.
What I do
Find the person who will push inside the company. Give them what they need to explain the case to others.
Tools that carry the data
CRM, email, call notes.
Where it usually breaks
Contacts and roles live in one rep's head, not in the CRM.

3Shape the solution

Who is involved
Technical specialists, the champion, finance.
What the buyer believes
Will this fit what we already run?
What I do
Bring in the right specialists. Tie the design to the outcome the buyer must deliver.
Tools that carry the data
CRM, quoting, shared documents.
Where it usually breaks
Scope and price change in email, and the quote stops matching the plan.

4Executive approval

Who is involved
The CFO and the CIO. Sometimes legal and security.
What the buyer believes
Show me the return and the risk in my terms.
What I do
Build the case in their numbers. Plan every date backward from the approval date.
Tools that carry the data
CRM, forecast view, the business case.
Where it usually breaks
The approval date is a guess, so the forecast keeps moving.

5Contract and start

Who is involved
Legal, purchasing, delivery, billing.
What the buyer believes
Terms are final once we sign.
What I do
Keep one owner on the path from yes to signature to first delivery.
Tools that carry the data
Contract tool, e-signature, billing.
Where it usually breaks
Signed terms are typed again by hand and start dates slip.

6Renewal

Who is involved
The original champion, finance, often a new executive.
What the buyer believes
Did we get what we paid for?
What I do
Start the renewal plan at signing. Review value with the buyer on a set schedule.
Tools that carry the data
Customer success platform, usage data, CRM.
Where it usually breaks
Risk shows up late, with the renewal date already close.
Five stage playbooks

Hunt. Convert. Expand. Forecast. Close.

Each playbook names what goes in, what I do, which tools are involved, what data must reach the next stage, and the one number I track.

Hunt

Win new accounts.

Inputs
Target account list, outside triggers, contact data.
Steps
Pick accounts by trigger and fit. Find the executive who has the problem. Reach in through the person closest to the work, then work up.
Tools
Account research, CRM, email and call tools.
Data that must flow on
The trigger, the contact map, and why now.

Number I track: days from first qualified signal to first meeting with the person who owns budget.

Convert

Run the deal.

Inputs
First meeting notes, a named champion, the outcome the buyer must deliver.
Steps
Confirm the outcome. Map everyone who must agree. Set exit criteria for each stage that the buyer, not the rep, has to meet.
Tools
CRM, shared documents, quoting.
Data that must flow on
Stage, named roles, agreed scope, and the next dated step.

Number I track: conversion from each stage, counting only deals where the buyer met the exit criteria.

Expand

Grow the account.

Inputs
Current contract, usage, the account plan.
Steps
Review value delivered with the buyer. Find the next problem they must solve. Size it before bringing a proposal.
Tools
Customer success platform, CRM, billing.
Data that must flow on
Usage, value delivered, and each new need entered as an open opportunity.

Number I track: open expansion pipeline per account.

Forecast

Call the number.

Inputs
Stage, exit criteria, close dates, approval dates.
Steps
Check each deal against buyer evidence, not rep opinion. Count a deal as committed only with a named economic buyer and a dated next step. Compare the call to the result.
Tools
CRM, forecast view.
Data that must flow on
Deal facts into the forecast. Misses back into the stage rules.

Number I track: the forecast against the actual result at the close of each quarter.

Close

Get to signature and start.

Inputs
Approved scope, approval dates, contract terms.
Steps
Build a joint plan with the buyer. Work backward from the CFO and CIO sign-off. Put one owner on the paperwork. Hand the account to delivery and a renewal plan at signing.
Tools
Contract tool, e-signature, CRM, billing.
Data that must flow on
Signed terms, start date, renewal date, and the champion, into billing and customer success.

Number I track: days from verbal yes to signature.

Deal and build examples

Four worked examples.

Clients are described in general terms.

Closing side

A $5M data center modernization

$5M total contract value12+ month cycle204% year

Situation. A professional sports organization needed new servers, storage, and networking. Its virtualization vendor had just been acquired, which put future licensing and the roadmap in doubt.

Buying side. Purchasing, IT leadership, the CFO, and the CIO. Many stakeholders, one budget.

What I did. I started with the purchasing agent. I found the Director of IT and built them into the champion by tying the project to the outcomes they had to deliver that year. I brought in internal technical specialists to explain the move to a new platform. A $3M baseline project grew into a full-stack scope with a high-touch rollout.

Result. A net-new win worth $5M in total contract value. The CFO and CIO approved it on return and risk. The cycle ran past 12 months.

Systems that repeat

A retention engine built from zero

Team of five$0 to $1.5M AAV

Situation. A fast-growing real estate CRM startup was losing customers. No team or process owned at-risk accounts after the sale.

Buying side. Subscription customers deciding at each renewal term, and an executive team that needed steady cash flow.

What I did. I built a retention department from the ground up. I hired and managed a team of five and set the KPIs. I wrote a library of templates for common objections and value gaps. I studied subscription term limits to find where customers were most likely to leave, then reached out before they did.

Result. Average annual value (AAV) grew from $0 to $1.5M. The blueprint was adopted across the management team, and I trained the team on the tools and the performance process.

My own build

MidconSight and its CRM design

Permit recordLifecycle stageScore-based routing

Situation. Oil and gas permit filings are public, but a seller cannot tell which filing deserves a call first.

Buying side. A sales team that sells to oil and gas operators and needs to know whom to call and when.

What I did. I built MidconSight. It reads permit filings, matches each one to a company, and rates each operator hot, warm, or cold on its expected pipeline of wells, using measured permit-to-production timelines in Oklahoma. I then designed how it sits in a CRM: a permit record linked to its companies, a lifecycle stage for permit-qualified accounts, and routing by score threshold.

Result. A seller sees who to call first, ranked by a score they can inspect. It is my worked example of a signal, a record, a stage, and a route wired together. See it live at midconsight.com.

My own business

Reliquary Trading Co.

Full cycle sellingSales funnelMarket intelligence

Situation. A small collectibles business has no sales team, so every part of the revenue cycle sits with one person.

Buying side. Collectors who buy singles, graded cards, and sealed product, live and online.

What I did. I run it end to end. I source and price inventory, sell it live and through online listings and in person at card shows, and watch the market to decide what to buy and when. The funnel, the go-to-market choices, and the market intelligence all run through one system I built and use every week.

Result. A working business that shows full cycle selling, from first signal to sale and back to sourcing. See it live at reliquarytrading.com.

The engagement

A 30 day engagement, then a 30, 60 and 90 day rollout.

  1. Week 1

    Inventory the tools. Interview the people who touch a deal.

  2. Week 2

    Trace real deals through every system. Mark each handoff.

  3. Week 3

    Measure the delay. Put dollars on each gap and rank them.

  4. Week 4

    Present the stack map, the gap report, and the workflow blueprint.

What you receive

  • The stack map
  • The gap report, ranked by dollars
  • The workflow blueprint, with a 30, 60 and 90 day rollout
  • A readout for your executives

Five straight answers

Will you push a tool on us?
No. Advice in an engagement follows the numbers. I name a tool only when the evidence shows a tool is the cause.
Will you tell us to replace our tools?
Only when the evidence says a tool is the cause. Most gaps sit in how data moves and who owns the handoff.
Who does the work?
I do. I lead every interview and write every deliverable.
What do you need from us?
A few hours with the people who touch a deal, and one closed deal I can trace from first signal to signature.
How do you handle security and data?
It is part of the approach from day one. Scope, agreement and NDA are settled before I see any data or get any access.
Doug Mayberry

Doug Mayberry

I have sold to executives and IT leaders on large enterprise deals, and managed those accounts after the sale. I studied economics, and I use it to find the outcomes a buyer must deliver and to put dollars on a gap.

I also build my own systems. I know what it takes to wire a signal into a record, a stage, and a route, because I have done it.

If you're looking for a consult, feel free to reach out below.

Enterprise Account ExecutiveC-Suite Relationship Builder
Sales Coach and Sales LeaderCoached and Led Sellers
Data Center SalesComplex, Technical Selling Cycles
Dell TSR, Hubspot (Multiple), Google Cloud + Project ManagementCertifications
LinkedInlinkedin.com/in/doug-mayberry

Start with a stack review.

Tell me where deals slow down. I read every message myself and will tell you honestly if I can help. Hiring or partnering? Say so in the message.

Prefer email or phone? Write to doug@reliquarytrading.com or call (405) 294-2090.

Questions? Check out my LinkedIn.