Leadership

It is Monday morning. You need to know what moved, what is forecasted, which deals are stale, and whether the number in front of you can be trusted. This track teaches you to answer all four in minutes — and, more importantly, to know when a number is solid enough to say out loud in front of a board.

The rest of the company uses the CRM to run deals. Leadership uses it to read them — across all three verticals at once, without asking anyone to build a report. That is a different skill, and it has one governing rule: a dashboard total is a claim, not a fact, until you have seen the records behind it.

Click to enlarge

What You Are Trying To Do

This track is for reading the business, not entering every record.

You are learning how to:

1. Read the rollup - pipeline, won, forecast, and vertical-level dashboards.
2. Check forecast quality - stages, dates, values, stale deals, and missing next steps.
3. Understand win/loss - RFP outcomes by league, time period, and business area.
4. Ask for a number and verify it - use the assistant, then inspect the records behind the answer.

Each of those maps to one lesson. None of them require you to create or edit records — the verticals own their data. Your job is to read it, question it, and send it back for repair when it is not board-grade.

Why the read pattern matters

Every number on a dashboard is an aggregate of individual deal records maintained by the team. When those records are current — right stage, right Bid Status, real close dates, honest values — the rollup is trustworthy. When they drift, the rollup drifts with them, silently. Nothing on a dashboard warns you that a $4M deal has had no activity in ninety days; you find that by drilling in.

That is why this track drills one habit above all others: ask fast, verify before you present. The assistant will give you any number in one line. The dashboard will give it to you in one glance. Neither replaces opening the top five records behind a total before that total goes into a deck. Speed for exploration, records for evidence.

Day 1 / Day 30 / Reference

• Day 1: read dashboard totals by vertical and open the records behind one number.
• Day 30: identify stale deals, missing dates, weak forecast assumptions, and win/loss patterns — and route them back to the owning team as specific asks, not general complaints.
• Reference as needed: exports, assistant prompts, monthly dashboard review, board-level summaries.

Scout Prompts

These three cover most of a leadership review. Copy them as-is, then adjust the vertical or period.

What You'll Learn Here

1. Read dashboards - pipeline, won, and forecast across the business or by vertical, using the ANC 2026 Company Dashboard and its per-vertical tabs.
2. Check forecast and pipeline - how the forecast is built, the 50%-probability convention, and how to separate the realistic pipeline from the long shots.
3. Review win/loss - RFP win rates by league and over time, and how to pull won deals as references for a live pitch.
4. Export and ask - pinning what you care about, exporting from shared views so numbers are reproducible, and getting any figure in one line.

Click to enlarge

Quick Glossary

• Stage - lifecycle stage on a deal.
• Bid Status - bid-flow status.
• FY - fiscal year.
• RFP - client bid request.

Haven't done Core yet? Start there first: Core — Start Here.