People decide and the tools draft.
{{product.name}} splits a strategy engagement into tools that draft and people who review. A team member approves each output before anything builds on it.
A fast draft is only useful if the team can trust it.
The tools stream a first draft in moments. {{product.name}} puts a review step after every draft, so people check, edit and approve it before it becomes context for the next tool.
Three habits change when a team works in {{product.name}}.
The project lead owns the engagement record.
Whoever creates a project becomes its lead and is the only member who can delete it. Everyone on the project can run tools, review outputs and manage membership. [Replace: confirm the intended permission model]
- Create the project and add the team.
- Run tools or bundles and choose which approved outputs feed each one.
- Comment on, edit and approve outputs.
- Open the Summary page and export the deck.
Six working principles shape how teams use the suite.
Approval gates chaining.
Only approved outputs become context for later tools or appear in the summary.
Work is scoped to a project.
Runs, comments and edits belong to one project, and only members can open it.
Inputs are structured.
Each tool asks for the fields its analysis needs, so a brief is complete before the model runs.
Iteration is recorded.
Regenerating after feedback increments a counter, and every edit keeps the text before and after.
Model choice is configuration.
An allowlist decides which models can be called, and tools name a tier, not a model.
Sign-ins are logged.
Microsoft Entra ID signs people in, and admins can see the access log.
Four agents group the 17 tools under one project lead.
Creates the project and adds the team. Reviews outputs and approves the ones the team builds on.
Seven tools: STEMPLE, Five Forces, key competitors, tech trends, regional drivers, SWOT and the resource and asset inventory.
Two Ecosystem Mapper tools build the value network and evaluate the market. The Interview Synthesizer turns interview notes into themes for the strategy review and the culture tool.
Seven tools: strategy review, financial logic, portfolio and business models, core capabilities, transformation programs, innovation maturity and change resistance.
Roles decide who can open a project and who administers the suite.
Assigned to the person who creates the project. Only a lead can delete it.
Accepted roles for the people doing the work. Team member is the default when you add someone. [Replace: confirm how these differ]
A role the API accepts for people who follow the work. The backend does not yet limit what a viewer can do. [Replace: confirm intended access]
The default role on first sign-in.
Set through the admin email list or in the admin panel. Admins manage users, projects and the access log.
Reviewers add comments and edit the text. Each edit stores the text before and after.
An approved output becomes context for later tools and appears in the summary.
Regenerate an output after feedback. The iteration count goes up each time.
Teams start with one project and one bundle.
-
Step 1
Create a project
Add the project details and the team, then make it your active project.
-
Step 2
Run a bundle
Run the external landscape bundle, review each output and approve the ones you want to carry forward.
-
Step 3
Build the summary
Run the internal assessment and synthesis bundles, then open the Summary page and export the approved outputs to PowerPoint.
A new tool is one entry in a registry.
- Each tool is defined in one file: its prompt, input form, upstream tools and model tier.
- A tool joins a bundle by adding its id to the bundle steps.
- Phases 2 and 3 have no tools yet. [Replace: confirm roadmap]
See how a team gets access.
Request access, create a project and run a first bundle. The Get started page walks through each step.