CONNECTED PROJECT MANAGEMENT
Run customer projects with the work, people and commercial context together
Plan tasks, organize the team, track delivery checkpoints and explain the project’s status. Connect actual effort and accepted charges to their financial next steps.
A project is the whole engagement
A customer project needs more than a task board. It has a customer relationship, a responsible team, a delivery plan and commercial expectations. Tsumira brings these parts into a common project context. Colleagues can work on individual tasks while the project lead can see deadlines, risks and the next decision, without reducing every conversation or financial document to another checkbox.
Explore each function
See what each capability does, how it works and where it fits into your team’s workflow.
Project tasks
Organize practical delivery work with project context, assignees, priorities, dates and a description that explains what completion means.
Project board
Review the same project tasks as a board, with clear status groups and direct access to the details behind each card.
Project timeline
Review when work is intended to start and finish, then open the underlying task to discuss the people and decisions behind the dates.
Project milestones
Use milestones to describe a delivery checkpoint, associate the relevant tasks and explicitly record when the checkpoint has been reached.
Project risks
Record severity, impact, mitigation, an owner and a follow-up date. Keep important delivery warnings visible in the project assessment.
Project updates
Separate the summary, blockers, decisions and next steps. Prepare a draft first, review its meaning, then publish the agreed project assessment.
Project team
Separate project ownership, management, contribution and viewing. Make the team explicit without treating every task assignment as unrestricted access.
Project templates
Build reusable project structures with roles, tasks, checklists, milestones and timing. Launch a new project from a published version and assign real colleagues.
Project billing plans
Record the agreed project charges, review their acceptance and pass a traceable candidate into finance. Delivery progress and financial issuance remain separate decisions.
Time against project work
Select the available project work in Time, describe what you are doing and run a timer. The resulting entry keeps the task and project references for later review.
Project billing evidence
Connect reviewed project effort and accepted charges to a financial billing basis, with references that make the delivery context identifiable.
Project attention on Home
Home surfaces relevant assigned work and delivery exceptions, with the project context and a concrete reason for attention.
Project work in the day
Connect preparation, delivery and follow-up through explicit tasks, assignees and dates. Use the day’s work views without losing the customer project behind the action.
Plan delivery in the form the team needs
Create a project with its owner, visibility, dates and supported customer relationship. Organize tasks with assignees, priority, descriptions, estimates and delivery states. Use list, table, board, calendar or timeline views of the same work. Milestones name important checkpoints, and published project templates let recurring engagements start from a reviewed sequence of roles, tasks and checklists.
- Tasks and five complementary work layouts
- Milestones and reusable published templates
- Customer context and clear project ownership
Make progress explainable
Project health considers objective facts such as blocked tasks, overdue work and high or critical risks. A risk record can explain impact, mitigation and responsibility. Structured project updates separate the summary, blockers, decisions and next steps, with draft preparation separate from publication. The purpose is a useful account of delivery: what has happened, what threatens the plan and which action someone must take next.
- Delivery warnings with reasons
- Risks with mitigation and ownership
- Reviewable structured status updates
Connect daily work and commercial evidence
Personal work and Home bring relevant assigned tasks and project concerns into the day. Time can use supported project work references for actual effort. Approved time and explicitly accepted fixed-fee, milestone or retainer charges can provide a billing basis for finance. These handovers retain their own review and permissions: a completed task is not an invoice, and an accepted charge is not a recorded payment.
- Daily responsibility and project attention
- Actual effort through the Time workflow
- Reviewed billing basis rather than automatic financial assumptions
A concrete workflow
Set up the engagement
Choose the project, customer, responsible owner and appropriate visibility; start from a published template where useful.
Organize the work
Assign tasks, agree dates and define meaningful milestones and team roles.
Manage delivery
Review the board or timeline, address risks and publish a checked progress update.
Review commercial follow-up
Submit effort or accept supported charges, then continue with financial review and document preparation.
An illustrative working example
Example: a customer implementation
A services company links a new implementation project to the CRM customer and maps a published onboarding template to its team. The board shows the work state, the timeline shows planned dates and a risk records missing customer input. After reviewing progress, the lead publishes decisions and next steps. Consultants submit actual effort while agreed milestone charges follow their own acceptance. The project stays connected without promising that every transition is automatic.
Questions about this topic
Is Projects only a Kanban board?
No. The project includes tasks, multiple layouts, team roles, milestones, risks, updates and supported customer and commercial context.
Can sensitive projects have restricted visibility?
Yes. Projects support team and restricted visibility, with read, write and management authority treated separately.
Can AI assist without publishing an unchecked status report?
Supported AI assistance can prepare update drafts. Publication remains a separate authorized operation and the content should be reviewed against the real project facts.
Does the module replace the entire finance process?
No. It provides delivery context and supported billing evidence. Pricing, tax handling, document issuance and payment keep their own financial workflow and actual implementation scope.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Asana
Workflow concept: Plan a controlled migration of customer projects and their delivery responsibilities.
Slack
Workflow concept: Prepare project decisions with checked context instead of scattered status messages.
Xero
Workflow concept: Design the reviewed handover of accepted project billing evidence to accounting.