Northwind
The client
Raj (marketing), Mia (sales), Dana (events)
Owns the launch. Sees the whole plan, every agency's dates and what's waiting on them, in its own Taskivities.
Solutions · Events & launches
The client and every agency keep their own Taskivities. The agent plans back from the big day, sends each team its part, and follows up every morning until doors open.
Each company runs its own Taskivities with its own people. The agent works across all of them.
The client
Raj (marketing), Mia (sales), Dana (events)
Owns the launch. Sees the whole plan, every agency's dates and what's waiting on them, in its own Taskivities.
Creative agency
Sam, Ines and Theo
Keeps its own Taskivities and its own other clients. Gets only its part of the launch, with dates, and logs its hours as it goes.
Everyone else
Added as they're booked
Connect their own Taskivities, or add their people to yours. The agent plans across all of them the same way.
The chasing that makes or breaks a launch: done every day, written down every time.
From the brief and the day it happens: tasks, owners, working days and what has to be ready before what.
Every task lands in the right company's Taskivities, assigned to the right person, with its date and what it waits on.
Reads every open task on every instance and spots what's late, what's blocked and what's about to be.
Logos, copy sign-off, final files: it asks whoever owns them, marks them urgent and tells the team that's waiting.
It moves everything that depends on a late asset and tells everyone whose date changed, while there's still time.
Someone's off sick the week before? Their task goes to someone on the same launch, with a note saying why.
Write it the way you'd brief an account manager. The agent turns it into a plan and sends it out.
Done. The plan has 8 tasks over 11 working days, with the launch on Nov 30. I've sent Northwind 5 tasks and Brightline 3, and I'll check in every morning.
Nothing new to learn. The events lead sees the week on the board; the designer sees today on their phone, with the agent's note on top.
Pulse 3.0 launch
2 done · 7 not finished · 1 late
Mon · 8:30
Reads every open task on both instances. The messaging doc is done early, so it tells Sam the booth copy can start.
Tue · 11:10
Ines comments that the logo files are the old version. The agent marks Raj's logo pack urgent and asks Raj for the vector files today.
Wed · 15:00
The logos land a day late. Booth graphics and print each move a day, and Ines and Dana get their new dates straight away.
Thu · 8:05
Theo is out. The launch video goes to Sam, who's on the same launch, with a note saying why.
Fri · 16:30
What got done, what moved and what's next, with the agency's hours from the tasks, ready for the client and for billing.
Taskivities keeps a history nobody can rewrite: when each task was planned, when it was done, who moved it and why. After every launch the agent compares the plan with what happened and writes what it learned into a playbook on the project. The next plan starts from there.
Tasks finished on their planned day
Illustration: how a team's plans firm up as the agent learns from each job.
playbook.md
Attached to Pulse 3.0 launch · updated by the Taskivities agent
# What I learned
# Next plan starts from these.
No. An agency can run its own Taskivities (it's free and open source) and keep its other clients there, or you can add their people to yours. The agent works across both.
Only what it's given. It signs in to each company's Taskivities as its own account, sees just the projects it's on there, and every change it makes is in the task history, marked as made by the agent.
Nothing new. They get their tasks on their phone, tick them off and comment when something's stuck. The agent does the chasing and the re-planning.
Anyone on the project can change it back. Nothing is ever deleted: dates move back, handovers reverse, and the history shows what happened and why.
Run Taskivities for your company, bring your agencies in, and let the agent keep everyone on the date.
Also for Construction and Manufacturing.