Sample teardown

Three one-page teardowns, with the names removed.

Each one is written by Luis from public information only, before any call or CRM access. The first was written for the new revenue leader of a B2B software company. The other two were built from public signals at two real companies and anonymized for this page. None of the three companies is a client. The reasoning, the check and the fix order are as written.

Get a one-page teardown

Written by Luis, back within 1 business day. No call needed.

To: [First name], Chief Revenue Officer B2B software company · anonymized

Acquired customers are a migration, not a pipeline.

[First name],

[Company] acquired a software product from a large services firm and raised a growth round in the same announcement.1 [Company] says the acquired product’s customers will move onto its platform “without starting over”, and that the services firm keeps delivering through the acquired product.2 One outside write-up describes that product as used by hundreds of multinational customers.3 You joined as CRO about four months later.

From the outside, the hard part isn’t selling [Company]. It’s that one CRM now holds three kinds of revenue that look alike on an opportunity: a new logo, an acquired customer moving over, and an acquired customer buying more on top. If moves are logged as “new business”, the board sees growth that is really retention. And the moves that slip don’t show up as risk at all, because they were never in the forecast as renewals.

Cost of getting it wrong.

Hundreds of acquired customers × the share that stall or leave during the move = the size of the hole. That’s a number to measure in week one, not guess.

What to do, in this order.

  1. One required field on every deal: New logo, Migration, Expansion, Partner-sourced.
  2. A migration record per acquired customer (a simple custom object works): contract end date, owner, partner relationship lead, migration stage and blockers.
  3. Report migration as retention with its own forecast line, and count only the upsell on top as new ARR.
  4. A partner field, so partner-sourced deals get credit without being double-counted.

What not to do.

Merge acquired accounts into existing accounts by name before there is a migration status. You’d lose the only place where the risk is visible.

How to check this.

Pull this quarter’s pipeline and tag every deal where the account came from the acquisition. If more than a few are labeled new business, the board number is mixed.

Happy to be told which part is wrong.

Luis

1 [Company] press release. 2 [Company] blog post. 3 Investor write-up. All three dated the same day; links removed to protect the company’s identity.

  1. Note 01 What public signals show. Starts from dated public signals, so every claim can be traced.
  2. Note 02 The likely gap from outside. One specific way the CRM could be misleading leadership, stated as a guess.
  3. Note 03 Cost of getting it wrong. How to size the problem with your own numbers.
  4. Note 04 What to do, in this order. The fixes in sequence, down to the fields and records.
  5. Note 05 How to check this. One CRM pull your team can run to confirm or reject the diagnosis.

To: [First name], VP of Sales Developer tools company, about 100 people · anonymized teardown from public signals

Define the deal before you move the CRM.

[First name],

[Company] just posted its first dedicated revenue operations role. The post says the team expects to move from HubSpot to Salesforce, wants a target account list ready for every new rep, and needs bookings reconciled to the CRM for commissions.1 The pricing page sells per active user seat, with a no-cost plan, two card-checkout tiers and enterprise contracts.2 This year [Company] also started selling through a cloud provider’s billing3, and it has folded acquired products into the platform.4

From the outside, the risk isn’t the migration itself. It’s that revenue comes in through three doors and only one of them creates a deal: card checkout, cloud billing and sales-led contracts. A seat counts anyone active in the last 90 days, so an account grows or shrinks without anyone touching the CRM. Move that into Salesforce as it is, and the new system inherits three different answers to “how big is this customer”.

Cost of getting it wrong.

Commissions get paid on the deals the CRM can see. Paying self-serve accounts that grow to enterprise size without an owner never become pipeline, and reps argue over accounts that started at checkout. To size it: paying self-serve accounts above your enterprise seat threshold × your average enterprise contract = pipeline nobody owns.

What to do, in this order.

  1. Write the account model before cutover: one account per company domain, with checkout, cloud billing and contracts all linked to it, and a source on every dollar.
  2. One required field on every deal: New logo, Self-serve conversion, Expansion, Product add-on (one value per acquired product line).
  3. A nightly seat count from the product onto the account, and a rule: when a paying self-serve account crosses the enterprise threshold, it gets an owner and a task within 1 business day.
  4. Rules of engagement in writing, including who owns an account that started at checkout, before territories are cut for the next hires.
  5. Then migrate, mapping fields from the model above rather than from what HubSpot holds today. Re-point enrichment and dialer tools last, after the dedupe.

What not to do.

Copy every HubSpot property into Salesforce one-to-one “to be safe”. You’d move the same duplicates and dead fields into a system that is harder to clean.

How to check this.

Export last quarter’s paid revenue from billing and match it to closed-won deals by company domain. If a real share of the money has no matching deal, both the forecast and the commission numbers are missing it.

Happy to be told which part is wrong.

Luis

1 [Company] job post. 2 [Company] pricing page. 3 Cloud provider announcement. 4 [Company] blog posts. Built from public signals only; not a client. Links removed to protect the company’s identity.

  1. Note 01 What public signals show. Starts from dated public signals, so every claim can be traced.
  2. Note 02 The likely gap from outside. Three ways money comes in, and only one of them creates a deal the CRM can see.
  3. Note 03 Cost of getting it wrong. Size the unowned pipeline with your own seat threshold and contract value.
  4. Note 04 What to do, in this order. The fixes in sequence, down to the fields and records.
  5. Note 05 How to check this. One pull your team can run to confirm or reject the diagnosis.

To: [First name], Chief Revenue Officer Data and media platform, under 50 people · anonymized teardown from public signals

The company that pays you isn’t the customer you forecast.

[First name],

[Company] announced you as its first CRO this month, to lead sales and partnerships.1 It sells audience data and campaign measurement to brand teams and to the agencies that plan their media, through a self-serve platform with no minimum spend and a managed campaign service.2 It started as a unit of a digital agency, and much of the team came from there.3 The company is less than two years old and the sales team is small.4

From the outside, the likely gap is that one campaign has three names in the CRM: the agency that buys it, the brand it runs for, and the sister agency that may have brought the relationship. An agency buying for five brands looks like one large account. A brand that switches agencies looks like churn at one account and a new logo at another. And audiences built on the self-serve platform with no minimum spend probably never become a deal at all.

Cost of getting it wrong.

Your first forecast as CRO will be built on accounts, and in this model the account is the wrong unit. Brand budgets are set in planning cycles. If the CRM can’t show which brands sit behind each agency and when each one plans, renewals and expansions show up a quarter late.

What to do, in this order.

  1. Brands and agencies as separate, linked companies, with an agency-of-record link and a start date for each brand.
  2. Every deal carries both the company that pays and the brand it runs for. Report pipeline by brand, not by payer.
  3. A source field: Direct, Agency-sourced, Sister-agency referral, so the parent relationship gets credit without being counted twice.
  4. A planning-cycle date on every brand, with an owner task 90 days before it.
  5. Measurement as a trigger: when a campaign’s results report is delivered, a renewal or expansion deal opens for that brand.
  6. Platform sign-ups matched to a company by domain. Brands and agencies above a set activity level get an owner.

What not to do.

Record brands as notes on the agency account. The first time a brand switches agencies, its whole history leaves with the old agency.

How to check this.

List the last 20 closed deals and write the brand next to each payer. If several payers are agencies and the brand isn’t in a field, pipeline by account overstates concentration and hides brand-level risk.

Happy to be told which part is wrong.

Luis

1 [Company] press release. 2 [Company] website. 3 Team profiles. 4 Public company profile. Built from public signals only; not a client. Links removed to protect the company’s identity.

  1. Note 01 What public signals show. Starts from dated public signals, so every claim can be traced.
  2. Note 02 The likely gap from outside. The payer, the brand and the referrer are three different companies on one deal.
  3. Note 03 Cost of getting it wrong. Why account-level forecasting misreads a brand and agency business.
  4. Note 04 What to do, in this order. The fixes in sequence, down to the fields and records.
  5. Note 05 How to check this. One pull your team can run to confirm or reject the diagnosis.

Get a clear read on your pipeline.

Send your website and what feels broken. Back within 1 business day: the likely bottleneck, the check to run in your CRM and the first fix worth making.

Get a one-page teardown

Prefer to talk? Book a 20-minute fit call · See scope and pricing