Agencies
Keep the client brief with the work it creates.
Connect client contacts, proposals, delivery tasks and feedback so account managers and delivery teams can work from the same record of the engagement.
- 01Qualify
- 02Plan
- 03Review
- 04Deliver
The handover is part of the project.
An agency engagement rarely fits inside one department. The person selling the work may not write the copy or check the final deliverable. Tsumira brings customer records, tasks, documents and conversations into a shared working environment. Agree who maintains scope and who records client decisions before expanding the rollout.
A concrete workflow
Qualify
Record the contacts, intended outcome and open questions before estimating the work.
Plan
Prepare a brief and distribute the work across named owners and deadlines.
Review
Discuss revisions, record decisions and check the actual time spent.
Deliver
Share the approved file version and capture the next client action.
Turn the inquiry into a usable brief.
Keep the company and its contacts in CRM, then document the request and agreed objectives. A shared brief in Docs gives the project team somewhere to develop requirements. Connect the proposal discussion to the customer instead of leaving important constraints in an individual mailbox.
- Company and contact records
- Editable shared briefs
Separate delivery tasks from client decisions.
Assign tasks and deadlines for research, production and review. Capture the decision that changes the brief, not just the resulting to-do. Team conversations and project documents help explain why a revision exists; time entries show the effort associated with the work.
- Owners and project deadlines
- Time records for actual effort
Share the reviewed version deliberately.
Store deliverables in Drive and choose internal access separately from an external file link. An external link refers to the particular version shared; uploading a revision does not silently replace it. Keep internal feedback in the file conversation and tell the client when a newly reviewed version is ready.
- Version-specific external links
- Internal feedback beside the file
An illustrative working example
Illustrative scenario: a brand launch
A multidisciplinary agency prepares a new brand launch. Account management records the client approval, design works from the brief, and a project owner tracks the remaining copy and delivery tasks. When a late request adds a landing page, the team records the scope change before treating it as another production task. The project owner gives the copy lead a separate task to confirm the new page objective. Account management checks whether the original approval still covers the revised deliverable. The designer keeps working from the current brief instead of interpreting scattered messages. Before client delivery, the team checks the exact file version and keeps internal discussion separate. This small pilot tests whether a colleague can pick up the engagement from its records without requiring everyone to remember the entire sales conversation.
Questions about this topic
Is this only for creative agencies?
No. The page describes cross-discipline agency delivery. Marketing, consulting and production teams can choose the parts relevant to their work.
Does a task completion approve the client deliverable?
No. Record the actual decision and its scope. A completed internal task does not establish an external approval.
Can client files be shared without exposing team discussion?
Drive external links share a specific file version. Internal file conversations are not exposed through that link.
Where should we start?
Use one active engagement with a clear brief, a small task plan and a deliberate handover. Review the process before importing every historical project.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
