The whole team works in the same project, from the first meeting to the handover.
The files, the meetings, the studies and the decisions stay with the plan, the hours and the costs. Whoever joins finds the context, and the Superagent works from it.
Demonstration scenario
Whoever joins the project finds what was already agreed.
A consultancy rolls out a retail chain’s new facility in eight weeks. On day one, the proposal, the contract, the plans and the client’s schedule are already in the project, for the team and for the Superagent.
Thousands of files per project, in folders, with ZIPs extracted and search across the archive.
The kickoff meeting goes from the calendar into the project plan.
The meeting with the client, booked on the calendar, reaches the plan with an owner and a date on every action. Nobody retypes the minutes or sends the tasks around by email.
Google or Outlook calendar with Meet, Teams or Zoom, and in-person meetings recorded in the browser.
- Recording
Plannk joins the meeting on the calendar, records it and transcribes it.
- Summary and actions
Half an hour after it ends, the summary brings the actions with an owner and a date.
- Tasks in the plan
Ana confirms, and the actions become tasks in the chosen milestone.
The study and the research land in the project as soon as they are ready.
In week three, the Resolver study, the research on city requirements, the permit check and the model of the cost by stage reach the same project. The next request starts from them.
The decision is still explained months later.
In week four, the client approves the works in two stages. Ana records the decision with its rationale and the discarded alternative, and whoever joins later asks the Superagent why the works were split.
Whoever coordinates follows the project without a status meeting.
In week five, Ana sees the first stage of the works in progress, the hours against the estimate, the cost against the budget and the purchase that slipped, with the name of whoever owns it.
List and Kanban, and in advanced mode also Gantt, Calendar and Timeline.
Nobody has to remember to check the permit every Monday.
Ana scheduled the browsing on the city portal for every Monday at 9 a.m. The permit status lands in the project and reaches her and the client by email, and Ana pauses, skips or reschedules an occurrence when the plan changes.
The client follows the project through the portal.
In week eight, the client accepts the detailed design and has the stage 1 report to accept, without asking for updates by email. On the team, Ana administers, Paulo and Marina edit and the partner architect can only view.
Frequently asked questions
Does a meeting action become a task without my approval?
No. The summary proposes the actions with an owner and a date, and the tasks are created only when whoever organized the meeting confirms them and picks the project milestone.
Does the Superagent use what is in the project?
Yes, when you select the project in the references. It consults the files, the team, the milestones and tasks, the discussion and what was linked to the project, such as meetings, research, Resolver studies and models.
Does the client see the same screen and files as the team?
No. The portal has its own access, through a code sent by email, and shows the client the progress of the projects released to them, the deliverables for acceptance and the requests.
Who on the team sees each project?
Whoever is on the project team, as admin, member or viewer. If the organization allows it, the project can also be shared with the organization, whose other members can then view it without editing.
Does an automation run even when nobody has Plannk open?
Yes. When enabled and supplied with the required resources, it runs at the configured time. The result stays in the application and in the chosen project, and goes out through the channels you configured.
What happens to an automation when credits are insufficient?
The run does not proceed, and the rule is marked as paused for insufficient credits. Review the balance or configuration before re-enabling it.
The context your team produces stays in the project through the final milestone.
Choose a plan and bring the project already under way: the plan, the next meeting and the routines the team repeats every week.