Consultancies
Build advice on a record the next consultant can understand.
Keep sponsor contacts, discovery notes, project tasks and recommendations together as an engagement moves from the first conversation to a reviewed deliverable.
- 01Clarify the mandate
- 02Investigate
- 03Review advice
- 04Handover
The reasoning matters as much as the result.
A consulting team needs to know which question was commissioned, who can decide and which evidence supports the recommendation. Tsumira combines CRM, shared documents and project organization. It gives the engagement a working home without claiming to replace the specialist models or analysis tools used to develop the advice.
A concrete workflow
Clarify the mandate
Record the question, sponsor and intended decision before planning research.
Investigate
Assign interviews and source review, then maintain shared working notes.
Review advice
Check conclusions, evidence and open assumptions before the client presentation.
Handover
Share the reviewed report and record implementation responsibilities separately.
Map the people behind the engagement.
Record the client company, sponsor and operational contacts separately. Use activities for discovery calls and note unresolved assumptions before writing a proposal. The team can distinguish the person commissioning the work from the people supplying information, rather than treating one email address as the entire customer relationship.
- Companies, contacts and discovery activities
Keep findings distinct from working assumptions.
Develop interview summaries and recommendations in Docs, with shared editing and revision history. Keep source files in Drive and assign research tasks to named colleagues. Review an AI-generated summary against the underlying material before using it as evidence in client advice.
- Shared documents and assigned research tasks
Close the engagement with a usable handover.
Track workshops, draft review and final delivery as project work. Record time against the engagement to understand effort. Share the reviewed document version deliberately and capture the client's remaining decisions. A finished recommendation and an implemented recommendation are different states; your team should record that distinction.
- Project tasks, time entries and file sharing
An illustrative working example
Illustrative scenario: an operating-model review
A consultancy interviews a client's service team. Findings become a shared report, while the engagement owner assigns evidence checks and tracks workshop preparation. The final recommendation is shared after review; unanswered questions remain visible as follow-up tasks instead of disappearing into the presentation file. The engagement owner assigns an evidence check for each disputed conclusion and asks the client sponsor to resolve a scope question. Researchers keep observations distinct from the recommendation. Before delivery, a colleague who did not conduct the interviews reviews whether the report explains its assumptions. That review also checks what is a finding, what is interpretation and what depends on a later client decision. The handover includes owned follow-up rather than suggesting that sending the report completes implementation.
Questions about this topic
Does Tsumira perform the professional analysis?
It organizes the engagement and its material. Specialist methods, models and professional judgment remain your team's responsibility.
Can several consultants write the report?
Docs supports collaborative editing and revision history. Define who reviews the recommendation before it is shared externally.
Can we track non-billable research?
Use time entries to document actual effort and apply your team's review process. A recorded hour is not automatically an invoice.
Can AI send advice directly to clients?
AI can assist with drafts and summaries. Proposed actions require review, and the responsible consultant checks the substance of the advice.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
