You joined a company with an active pipeline, a board expecting results, and a sales team that has been running without stage gates, qualification criteria, or a CRM worth trusting. The generic 30-60-90 day plans designed for structured environments do not apply here. They tell you to learn the current sales process. There is no process. They say audit the CRM. The CRM is a collection of what each rep remembered to enter.
This article is a practical sequence for the first 90 days when the job is to build infrastructure while also managing active pipeline and reporting to a board that expects a number. The sequence is not a template. It is an order of operations for one specific situation: building from nothing while under performance pressure.
Why the standard 30-60-90 plan does not apply here
Most 30-60-90 day plans assume the company has a sales process and the VP is learning it. The infrastructure-gap scenario is different: you must build the process while using it. Generic plans tell you to understand the current sales process. There is no process. They say audit the CRM. The CRM has no architecture: it is a collection of whatever each rep decided to enter.
The difference matters because the sequence changes. You cannot install qualification discipline before you know what a qualified deal looks like for this company. You cannot run a pipeline review before there is a pipeline view worth reviewing. You cannot produce a board-defensible forecast before you have evidence to base it on.
The standard plan assumes inputs that do not exist. This one starts from zero.
Days 1-30: Understand what exists before building anything
Do not start building. Start observing.
The most common mistake in the first 30 days is announcing a new process before you understand the sales motion the reps are actually running. Not the one they describe. The one visible in their CRM activity, their call recordings, and their deal notes.
If you need a faster path through this phase, the Foundry Diagnostic compresses the discovery into 10 days with an external audit. It maps the structural gaps and quantifies the revenue leakage without requiring you to spend your first 30 days as the investigator.
Days 31-60: Install one thing completely
The instinct is to fix everything. The right move is to fix one thing to completion. The first infrastructure component to install is the qualification standard, because everything else depends on it.
Why qualification first
Without a shared definition of what a qualified deal looks like, pipeline reviews are subjective. Forecast calls produce a number, not a prediction. CRM data reflects rep confidence, not deal reality. Every downstream problem in the pipeline traces back to the absence of documented qualification criteria.
What to install
A one-page qualification standard. Not MEDDIC or BANT copied from a blog post. A standard built from what you observed in Days 1-30 about what qualified deals at this specific company actually look like.
It should answer:
- What evidence must exist in the CRM for a deal to advance from Stage 2 to Stage 3, Stage 3 to Stage 4?
- Has the rep spoken directly to the economic buyer?
- What is the stated business problem and what is the documented cost of not solving it?
- What is the compelling event or external deadline?
Introduce it in a one-on-one with each rep before any pipeline review. Do not announce it in a group setting first. Test it on five active deals before you call it complete.
Days 61-90: Build the cadence and start the forecast
With a qualification standard in place, the pipeline review becomes possible. Before Day 60, a pipeline review is a conversation about feelings. After Day 60, it is a review of evidence.
Weekly pipeline review cadence
Review every deal in Stage 3 and above, deal-by-deal, not summary-level. The review asks: what is the status of each qualification criterion? What is the next action, who owns it, and by when? A deal with no next step documented by the prospect is a deal at risk.
The first board-ready forecast
State what you know, what you infer, and what the confidence level is. Do not produce a single number without a documented basis. A forecast presented as commit $X, upside $Y, confidence level based on these five deals meeting qualification criteria, is more defensible than a number arrived at by adding up rep commitments.
CRM hygiene standard
Define which fields must be populated before a deal can move stages. This is not a discipline issue. It is a system design issue: the CRM should not allow stage advancement without the required fields. Work with whoever administers the CRM to make stage gates structural, not aspirational.
What to do if 90 days is already behind you
If you are reading this at Day 100 and have not started, start now. The sequence still applies. The cost is that you may be building infrastructure while already under board scrutiny for a missed quarter.
If that is the case, the Foundry Diagnostic compresses the discovery phase. It is a 10-day external audit that maps exactly where the infrastructure gaps are and quantifies the revenue leakage they are creating. It does the Day 1-30 work in 10 days with an external set of eyes, freeing you to manage the pipeline and the board while the structural diagnosis runs in parallel.
The Diagnostic identifies the gaps and quantifies the cost. The Build installs the infrastructure that closes them. If you are already behind, the Diagnostic shortens the path.