NavigateMENU / 04
More
Elsewhere
AI systems, in practice · Project boards
Turning Slack messagesand calls into tasks
Work gets agreed in Slack threads, on calls and in shared links. Whether it reached the project board used to depend on someone remembering. We built three tools that put it there, so the board stays complete and the client never has to ask twice.
Where agreed work got lost before
A project board is only as good as what someone typed into it. Work gets agreed in a Slack thread on Monday, on a call on Tuesday and in a link dropped into a channel on Wednesday. Some of it reached the board. The rest lived in people's memories, and the project manager spent part of every week reconstructing it. The client felt the gaps as a request they had to repeat, or a deliverable nobody owned.
Where the tasks come from
Scroll to watch a Slack request, a shared link and a call each turn into entries on the board, with an owner and a date.
Said in Slack, said on a call. Written down by whoever remembers.
5 said0 on the board
How each piece works
Slack requests become tasks.
When someone asks a named person to do something in a project channel, a small prompt appears in the thread with the task, the owner and the date filled in. Anyone can add it, edit it or dismiss it. A vague message gets silence, because a wrong guess is worse than no prompt. The system works out which project it belongs to, and the prompt says only what, who and when, so it's safe in front of a client.
Shared links are filed on the project.
Design files, documents and review links posted in Slack are offered to the right project, and one click files them there. A link someone turns down is not asked about again. Meeting and chat links are left alone.
Action items from calls become tasks.
Every call transcript is matched to the right deal or project. The system reads it for what people agreed to do and drafts those as tasks, each with an owner and a due date where the call gave one. A person reviews the drafts, and only approved ones reach the board.
Try turning a Slack message into a task
Post a message in the project channel and see what the system does with it. Add the task, change it first, or dismiss it. Then try the vague one.
Post a message
# brand-refresh
Jordan
Sam, can you send the revised logo files by Friday?
Want me to make this a task?
Send revised logo files
Sam · due Fri, Oct 9
Written for a shared channel: what, who and when. Nothing internal.
Brand refresh board
Tasks
- Collect brand questionnaireOct 2
- Draft three logo directionsOct 6
Files
- Brand questionnaire
Results
- the board fills from conversations people were already having
- Nothing to remember
- tasks, files and call follow-ups sit on the project itself
- One place
- they stop repeating themselves, and what was agreed turns up with a name and a date
- Clients notice
More systems we've built
Quoting and billing small client requests
Clients ask for small changes in their portal, AI drafts the scope and hours, and approving them sends the invoice to Xero or QuickBooks and puts the work on the project board.
See how it worksGrows revenue · Client experience · Saves timeAI · Automation · Integrations
Google review requests and matching
Requests go out after a project wraps. New reviews come in daily, each matched to the contact who wrote it, and a person confirms the uncertain ones.
See how it worksClient experience · Grows revenue · Saves timeAutomation · Integrations · AI
Project management for up to ten projects per person
The system reminds clients on its own, drafts each weekly report from the calls and tasks, and answers questions about any project from inside Claude or ChatGPT.
See how it worksSaves time · Cuts costsAI · Automation · Integrations