Choose Your Track
A role-based decision tree for getting to the right CRM, service, and proposal training fast.
Start with the work in front of you. Then jump to the training that matches it.
Three tools carry the whole operation, and each track teaches one of them plus the seams between them. The CRM holds Companies, opportunities, and the pipeline — it is where deals live and where every other system reports back to. The Proposal Engine is where RFPs get analyzed, priced, and packaged into one-pagers and SOWs — and everything it generates attaches itself to the right CRM deal automatically. The Service Dashboard runs the field — tickets, events, technicians, venue hardware — and mirrors into the CRM in about a second. You do not need to learn all three. You need to learn yours, plus where your work hands off to the next person's.
Fast route
If
Your first task is an RFP, one-pager, SOW, or pricing package
Then
Start with Proposals, then connect the output back to the CRM.
If
Your first task is pipeline, forecast, Company history, or deal ownership
Then
Start with Sales / CRM.
If
Your first task is a venue issue, ticket, event, or display readiness check
Then
Start with Services.
If
Your first task is a number, board update, or stale-deal review
Then
Start with Leadership.
Start Here
Reading the business rather than working a deal? There is a fourth path: the Executive Summary track teaches dashboards, forecast quality, win/loss reading, and the habit that separates leadership users from everyone else — never quoting a rollup without drilling into the records underneath it. It takes about 20 minutes and assumes nothing.
How The Work Flows Between Tools
Before picking a track, it helps to see the one flow every track plugs into:
The connected flow
- 1
A deal is logged in the CRM — Company, owner, due date, bid status.
- 2
The RFP is analyzed and priced in the Proposal Engine; outputs attach back to the CRM deal automatically.
- 3
The bid goes out, and the deal moves through the Bid Tracker to Won, Lost, or No Bid.
- 4
Won service work runs in the Service Dashboard and mirrors into the CRM in about a second.
- 5
Leadership reads the dashboards that all of the above feeds — without asking anyone for status.
Every track on this page is a slice of that flow. Sales owns the ends, proposals owns the middle, services owns fulfillment, and leadership reads the whole thing.
Badge System
Use these badges to know where the work happens:
| Badge | Means | Color |
|---|---|---|
| PROPOSALS | Proposal Engine work: estimates, one-pagers, SOWs, RFP triage, proposal files | Blue |
| CRM | CRM work: Companies, Opportunities, People, views, notes, dashboards | Green |
| SERVICES | Service Dashboard work: tickets, events, venue operations, technician flow | Orange |
| CONNECTED | Cross-tool handoff: work starts in one place and syncs or attaches to another | Purple |
Decision Tree
Q1: What is your first task tomorrow?
Q2: Are you trying to do work or read work?
- Do work: pick Sales / Technology, Services, Media & Sponsorship, or Proposal Engine.
- Read work: pick Leadership or dashboards.
- Clean work: pick Working Standard first.
Q3: Is the answer client-facing?
- Yes: verify the source records before sending.
- No: use the assistant for speed, then clean the record if you find a gap.
The distinction matters because the cost of being wrong is different. An internal number that is slightly off costs a correction in a meeting. A client-facing number that is off costs trust. When the output leaves the building — a proposal figure, a service status, a renewal quote — open the records behind it first. When it stays internal, move fast and fix the data as you go.
I need to sell, price, or move a deal
Start with the Sales / Technology track. Learn Companies, pipeline hygiene, pricing status, proposal handoff, and dashboards.
I need to track what's broken or happening at a venue
Start with the Services track. Learn tickets, events, venue activity, Company history, and venue health checks.
I need to build or review proposal work
Start with the Proposals path. Learn RFP triage, estimates, SOW generation, Mirror Mode, and CRM auto-attach.
I need to keep records clean
Start with Working Standard. Learn duplicate prevention, ownership, notes, source-record updates, views, and verification.
I need to read the numbers
Start with Leadership. Learn dashboards, forecasts, win/loss, exports, and assistant-supported reporting.
Real Scenarios
Sales Scenario
It is Thursday. A team asks for an LED board budget before Monday. You need to know whether the Company already exists, what similar work is on file, whether pricing is complete, and what the next proposal step is.
Open:
- Core: Finding Anything Fast
- Sales & Account Management
- Technology: Your Pipeline
- Proposal Engine: Estimator
Where this lives
Company history and pipeline status live in the CRM. Pricing and proposal work live in the Proposal Engine. Finished proposal artifacts attach back to the CRM record.
Services Scenario
It is game week. A venue has an open display issue, a scheduled event, and a client asking whether the site is ready. You need the Company, tickets, event activity, and recent service notes in one place.
Open:
- Core: Getting Around
- Services & Operations
- Venue Services: Service Tickets
- Service Dashboard: Tickets
Where this lives
Client and Company context live in the CRM. Day-to-day service work lives in the Service Dashboard. Synced ticket and event history rolls back into the CRM Company view.
Proposal Scenario
An RFP lands with a tight deadline. You need to triage the document, price the deal, generate the SOW, and make sure the final files are attached to the right CRM opportunity.
Open:
- Core: Working Standard
- Proposals & Estimation
- Proposal Engine: RFP Analyzer
- Proposal Engine: SOW Generation
- Proposal Engine: Universal CRM Push
Glossary
SOW, RFP, Mirror Mode, and Universal CRM Push are defined in the glossary.
Leadership Scenario
Board call in two hours. You need open pipeline by vertical, this year's realistic forecast, and the renewal runway — and each number has to survive a follow-up question. The dashboards give the rollups; the discipline is drilling into the records behind each one before quoting it.
Open:
- Executive Summary
- Leadership: Dashboards
- Leadership: Forecasting & Pipeline
- Core: Asking for Numbers
Where this lives
The rollups live on the CRM dashboards. The records that create them live on Companies and opportunities. The verification habit lives in you.
Before / After
The goal of training is not more clicks. It is cleaner work.
That contrast is the whole point of every track on this page. The tools are already connected — proposals attach themselves, service work syncs itself, dashboards read live. What training adds is the human half: records created in the right place, linked to the right Company, updated when the state changes. Ten clean records beat a hundred stale ones, because clean records are the only ones anyone downstream can act on.
Outcome Labels
When you are not sure which product name to search for, search by outcome:
- Price a deal -> Proposal Engine estimator and Technology proposal lessons.
- Build a one-pager -> Proposal Engine projects and CRM opportunity handoff.
- Respond to an RFP end-to-end -> the RFP to Win workflow map.
- Track what's broken -> Service Dashboard tickets and Venue Services Company view.
- Check venue health -> Service Dashboard venue pages and CRM Company history.
- Staff tonight's game -> Service Dashboard events and the technician workflow.
- Clean a record -> Core Working Standard and account cleanup.
- Read the business -> Leadership dashboards and CRM reporting.
- Prep a renewal conversation -> Leadership win/loss plus the Company's service history.
Your First Week
However you route, the first week looks the same for everyone:
Week one, any role
- Finish your track — 20 to 30 minutes, once, properly.
- Do the real version of your track's first scenario on live work.
- Find one record your role depends on and verify it is clean: owner, dates, links.
- Ask Scout one question you would normally ask a colleague, and check the answer against the records.
- Walk one handoff past your own tool — open the CRM deal your proposal attached to, or the Company page your ticket synced to.
Key takeaways
- Pick the track that matches tomorrow morning's task, not your job title.
- The three tools are already wired together — training teaches your slice plus the handoffs.
- Client-facing answers get verified against source records; internal answers optimize for speed.
- The badge colors tell you where work happens: blue proposals, green CRM, orange services, purple handoffs.
- Clean records are the deliverable — every track ends in the same working standard.