Invisible pipeline account teardown checklist

Use this checklist to tear down one named target account before you waste time on broad research or random outreach. The goal is simple. Decide if the account is worth active pursuit, identify the strongest pain, map the right stakeholders, and choose the next play with enough proof to move.

Use the same checklist across three named accounts when you want a clean side-by-side read on where the real opportunity sits.

Phase 1. Prep the account

1) Confirm the account is a real fit

• Company size, business model, and market match your offer. - Pass if the account fits your ICP on at least 2 of these 3 points. - Fail if the account is outside your core range on size, model, or market. - Fix by moving it to nurture or removing it from active pursuit.
• The account has a clear reason to buy from a vendor like you. - Pass if you can name one business problem your product solves for this account type. - Fail if the best answer is “we should probably reach out.” - Fix by writing a one-line fit statement using your product in plain language.
• You have a basic account brief in hand. - Pass if you know the company name, main products, recent direction, and known contacts. - Fail if the account is still a blank page. - Fix by pulling company site, LinkedIn, recent news, and CRM notes into one page.

2) Mark obvious disqualifiers early

• No obvious conflict with your offer, segment, or price band. - Pass if nothing in the account profile blocks a sale at the outset. - Fail if they are too small, too large, wrong region, or already committed to a direct competitor. - Fix by stopping the teardown and logging the disqualifier.
• No recent event makes the account unusable right now. - Pass if there is no merger, freeze, reorg, or legal issue that kills near-term motion. - Fail if the account is in a buying freeze or major internal change. - Fix by moving to a later date or a lighter touch sequence.

3) Gather the minimum data set

• Website and product pages reviewed. - Pass if you can state what they sell, who they sell to, and where they claim value. - Fail if the site is vague or outdated and you cannot tell what matters. - Fix by checking pricing pages, case studies, and product messaging first.
• Recent news checked. - Pass if you have at least one current event, launch, funding note, or market move. - Fail if you have no current trigger. - Fix by searching company news, press releases, and trade coverage.
• Careers page and job posts checked. - Pass if open roles show where the company is investing or under pressure. - Fail if you skip hiring signals. - Fix by flagging roles tied to growth, systems, ops, or revenue teams.
• LinkedIn company page and leadership profiles reviewed. - Pass if you can name the leaders tied to growth, ops, revenue, or transformation. - Fail if you do not know who owns the problem. - Fix by listing the top 3 to 5 people to inspect next.

Phase 2. Build the pain map

4) Find the strongest buying signals

• At least one external trigger is visible. - Pass if news, hiring, product changes, leadership moves, or market pressure point to a live issue. - Fail if the account has no visible reason to change. - Fix by looking for funding, expansion, new regions, new products, or competitor pressure.
• At least one internal clue points to pain. - Pass if your CRM notes, call notes, or past losses mention a repeated problem. - Fail if internal notes are generic or empty. - Fix by pulling every prior contact and sorting for repeated pain language.
• The pain is tied to revenue, cost, speed, risk, or capacity. - Pass if the pain affects a number leaders care about. - Fail if the pain is just a convenience issue. - Fix by rewriting the pain in business terms.

5) Rank each pain signal

Use this table for every signal you find.

• Pass if at least one pain is marked Strong and one more is not Unsupported.
• Fail if all pains are weak or unsupported.
• Fix by dropping weak signals and finding better proof before you spend time on outreach.

6) Write the pain in one sentence

• You can state the pain in one short line. - Pass if the sentence names the problem, the likely owner, and the business effect. - Fail if the sentence sounds like a generic pitch. - Fix by writing it in this format: “They are under pressure to {{business outcome}} because {{signal}} is driving {{cost/risk/speed issue}}.”
• The pain connects to a stakeholder who would care. - Pass if a VP, director, or business owner would lose time or money if the issue stays open. - Fail if you cannot name who feels it. - Fix by tying the pain to a role, not a department.

7) Separate real pain from noise

• The issue shows up in more than one place. - Pass if the same problem appears in at least two sources, such as hiring plus news, or website plus call notes. - Fail if you only have one thin signal. - Fix by holding the account in research until another signal appears.
• The pain is current, not stale. - Pass if the signal is recent enough to matter now. - Fail if the signal is old and no longer active. - Fix by re-checking the last 30 to 90 days of public changes.

Phase 3. Map stakeholders and buying path

8) Identify the likely owners

• You have a list of decision makers, influencers, and blockers. - Pass if you can name at least one person in each bucket. - Fail if you only have a company name and no people. - Fix by mapping leadership, line-of-business owners, and adjacent ops leaders.
• At least one owner matches the pain. - Pass if the role and the pain line up cleanly. - Fail if the pain is important but the owner is unknown. - Fix by searching for leaders tied to that function on LinkedIn and the company site.

9) Check access before you commit

• You can reach one relevant owner with a credible angle. - Pass if you have a path through email, LinkedIn, referral, partner, or co-sell. - Fail if the contact map is empty. - Fix by finding a warmer route or using a different account.
• The message can speak to their actual job. - Pass if you can write a first line that sounds specific to their role. - Fail if the opener would fit any company. - Fix by using the pain sentence and role together.

10) Check for blocker risk

• A likely blocker is known. - Pass if you already know procurement, IT, finance, or another group will get involved. - Fail if you assume a smooth path with no proof. - Fix by adding the blocker to your map and writing for that objection early.
• Internal ownership is not split in a way that kills momentum. - Pass if one owner can move the issue or sponsor the next step. - Fail if no one has accountability. - Fix by targeting the role with the most control over the pain.

Phase 4. Rank the opportunity

11) Score the account on four factors

Use a simple 1 to 3 score for each item.

• Pass if the total is 9 or higher.
• Fail if the total is 8 or lower.
• Fix by improving the weakest factor before you move to outreach.

12) Make the call

• The account is marked pursue, nurture, or pass. - Pass if you can make the call in one line and defend it. - Fail if the account sits in limbo. - Fix by forcing a decision on the strongest evidence available.
• The reason for the call is recorded. - Pass if the reason names pain, fit, access, and urgency. - Fail if the reason is “looks interesting.” - Fix by writing the shortest possible decision note.

Decision rules

• Pursue if pain is strong, fit is clear, and you can reach an owner.
• Nurture if fit is decent but pain or access is weak.
• Pass if the account fails fit, has no real pain, or has no credible path in.

13) Pick the next play

• The play matches the strongest signal. - Pass if your outreach or co-sell motion lines up with the top pain. - Fail if the message is generic. - Fix by basing the play on the best signal, not the easiest contact.
• The play has one clear objective. - Pass if the next step is a meeting, intro, validation call, or partner motion. - Fail if the play tries to do too much. - Fix by narrowing to one outcome.
• The first message uses the pain, not your product sheet. - Pass if the opener names the issue and why it matters now. - Fail if it reads like a product dump. - Fix by rewriting it around the business problem.

14) Choose the right motion

• Direct outreach fits the access path. - Pass if you have a reachable owner and a clean angle. - Fail if you are guessing at contact quality. - Fix by moving to a warmer route or using a different stakeholder.
• Co-sell fits the account structure. - Pass if a partner, advisor, or internal ally can open the door faster. - Fail if co-sell is just a habit. - Fix by using co-sell only when it shortens access or improves trust.

Phase 5. Compare three named accounts

15) Run the same teardown on all three

• Each account has the same fields filled in. - Pass if all three have fit, pain, stakeholder, score, and next play. - Fail if one account has more detail because it happened to get more time. - Fix by completing the missing fields before comparison.
• Each account has one top pain and one likely owner. - Pass if each account can be explained in one line. - Fail if any account still feels fuzzy. - Fix by sending the weaker one back to Phase 2 or 3.

16) Compare hidden opportunity side by side

• Pass if one account clearly stands out on pain, fit, or access.
• Fail if all three look the same because the teardown was too shallow.
• Fix by going back to the weakest rows and tightening the evidence.

17) Check for the fastest validation path

• The strongest two or three accounts can be validated quickly. - Pass if you know which accounts deserve immediate proof. - Fail if you are still guessing. - Fix by using a short validation sprint before full outreach.
• Vitelis can be used to compare hidden opportunity across the short list. - Pass if a free Proof of Value Creation would help rank the strongest accounts faster. - Fail if you only have one account in view and no comparison point. - Fix by lining up three named accounts and using the same teardown process on each.

Failure response

What failure looks like

• The account has no current trigger.
• The pain is weak or unsupported.
• You cannot name an owner.
• The score stays below the pursue line.
• The next play is a guess.

What to do next

1. Stop the teardown and log the failure reason.
2. Push the account to nurture if the fit is decent but the timing is wrong.
3. Remove the account if the fit is bad or the pain is not real.
4. Re-run the checklist only when new evidence appears.
5. If you have three accounts, compare them again and move time to the one with the strongest score.

Readiness check

Minimum standard to proceed

• One named account has a clear fit.
• One strong pain signal is verified.
• One relevant stakeholder is mapped.
• The score is 9 or higher.
• The next play is defined.

Next action

• If all five are true, move the account into active pursuit and run the next play.
• If one or more fail, send the account back to the failed phase and fix the weakest item before spending more time on it.