The prep is done before the call starts.
Workflows run on their own around your client meetings. The brief is in your Slack before the call, the recap is in the channel after, and the status is drafted for you to send.
Start from the library, then write your own
Six workflows every delivery team runs, ready on day one. Change the words and they run your way. Write a new one and it runs on every project from then on.
The brief is in your Slack before you join.
How a workflow runs
Read the last two calls with this client and the decision log. Write me a one page brief with where things stand, what we owe them, and any open questions. Send it to my Slack DM.
Write it like a message
A workflow is when it runs and what you want done, written the way you would ask a colleague. No builder, no nodes.
Pre-call prepOnRuns30 minutes before a client callInstructionRead the last two calls with this client and the decision log. Write me a one page brief with where things stand, what we owe them, and any open questions. Send it to my Slack DM.
It reads the project
Each run works from the calls, documents, decisions, and the client’s system on that project, not a generic prompt.
Pre-call prep51s- ReadWeekly sync, Sep 12
- ReadCPQ design review, Sep 9
- Checked3 open items against the plan
- WroteThe brief, 6 sources
- Postedyour Slack DM
It lands where the team already is
Slack, Teams, a doc in the project, or the decision log. Nobody opens a new tool to find the result.
DatafruitDatafruitAPP9:29 AMBrief for Weekly sync with Fairbanks, 10:00- UAT starts Oct 6. Test accounts are loaded.
- We owe them the approval email template by Thursday.
- Open: SSO is still waiting on the Okta metadata file.
You approve what leaves
Anything meant for the client, or that changes the client’s system, waits for a person to say yes.
Publish “Weekly status, Sep 19” to the client portalPublishedRejectApproved
The brief is in your Slack before the call
Briefs, recaps, and status updates, written from the project and posted where your team will see them.
Book a demoExplore the suite of tools
- Meeting IntelligenceCalls recorded, transcribed, and read for decisions.CPQ design reviewSep 9 · 48m22:40“Let’s keep the quote approval at two levels, not three.”
- TraceabilityEach decision linked to where it came from.REQ-014Quote approval stays at two levelsCPQ design review· 22:40Solution design v2#fairbanks-delivery
- AgentAsk about the project and get an answer with its source.what did we promise on SSO?
Single sign-on through Okta by go-live. Fairbanks owns the metadata file, and it was still open on Sep 12.
Weekly sync, Sep 12 · 14:02