Strategy Overview keeps each client's information in modules and brings it together in Reports. This article is the map: where things live, what makes up a Report, and how the pieces connect.
The modules
Your modules run down the left-hand side of Strategy Overview. Each one holds one kind of information for all your clients, outside any one Report, so it stays current between meetings and nothing is lost when you make a new Report.
These modules show up in Reports:
Goals: what the client is trying to achieve as a business.
Technology: their devices and other technology from your integrations, each with a replacement date and budget.
Initiatives: the projects you recommend, with their timing and budget.
Plan: detailed Plans you build for a client from your plan templates.
Agreements: their contracts and recurring costs.
M365 and Tickets: their Microsoft 365 users and licenses, and their tickets from ConnectWise PSA.
Proposals: the opportunities you have with them, from ConnectWise PSA.
Companies: each client's details, including their name, logo and contacts.
A few modules work across all your clients and don't appear in a Report:
Schedule: who leads each client and when you meet with them.
Stack: your Assessment results across all your clients, side by side.
Any custom modules you add, which show another page or tool inside Strategy Overview.
The Strategy module: templates and Reports
The Strategy module is the center of it all: it holds each client's Reports. Every Report is built from your Report template, which you set up in Settings > Templates > Strategy. The template is the structure: it sets which Parts every Report has, in what order, and what each one starts from. Each Report is one client's copy of it for one meeting, filled with that client's information. Configure the Report covers setting up the template.
Every Part's content comes from one of four places:
Kept on the Report: the cover page, the executive summary, any Text Parts and the Assessment. Each new Report copies them from the last one, so you update them instead of starting over.
Live from a module: Goals, Initiatives, Technology, Plan, Agreements, M365, Tickets, Proposals and Contacts. These stay current while the Report is Open.
Calculated: the Dashboard, the Roadmap and the Budget. They work out their numbers from the client's data.
From outside Strategy Overview: External Content shows a web page from a link, and Embed Content shows embed code you paste in.
Most Parts are added in your Report template. A Plan Part is the exception: every Plan is built for one client, so the Plan Part is added on that client's Report, and each new Report that carries over data keeps it.
How the pieces connect
Initiatives tie it all together. Link an Initiative to the Assessment items and devices it addresses, and link Goals to the Initiatives that move them forward. A Goal can also be linked to a Plan or to items in a Plan.
The Roadmap and Budget add up the budgets from the Report's devices, Initiatives, Agreements, Plan items and Assessment items. They only count sources that are on that Report. A few switches decide what counts:
When a device is linked to an Initiative, the Initiative's budget replaces the device's own.
An Initiative with Include in Budget off drops out, so its devices count again.
Agreements that come from ConnectWise PSA start with Include in Budget off, and an agreement you add by hand starts with it on.
A new Report for each meeting
For each meeting you make a new Report, bring it up to date, present it to the client, then complete it. Completing a Report freezes it as the record of that meeting. The Report Cycle walks through it.
Where to start
If you're not sure where to start with a client, this order works for most teams: their Goals, then the Assessment, then their Technology, then the Initiatives that come out of them.
Next: The Report Cycle