Every client call, before, during, and after.
The brief lands in Slack before you join. Answers come from the engagement record while you talk. The recap, the decisions, and the follow-up are done before you stand up.
Before the call
Walk in ready.
- Your day, before it starts
One message at 8:00 AM with every client call on your calendar today and what matters in each: the open thread, who is new on the call, and what changed since you last spoke.
- A brief for every call
Fifteen minutes before you join: where the engagement stands, who is in the room, what to lead with, which questions are still open, and what to watch for. Every line cites its source.
CPQ build is done. UAT is set for Oct 6. SSO is still blocked on the Okta file.
Questions to ask- 1Has the Okta metadata file left IT yet?
- 2Is Oct 6 still the UAT start?
- 3Who owns the approval email template?
During the call
Win the moment in the room.
- Answers from the record, as the question is asked
“What did we agree on pay groups?” Answered from the kickoff transcript, the SOW, and the design doc, with the source, before the client finishes asking.
- Catch it in the room
When an ask contradicts what was agreed, or falls outside the SOW, it is flagged while you can still address it, not discovered at UAT.
- Say it and it is done
Book the follow-up, open the Jira ticket in the client’s words, log the decision, draft the change order. From the call, not after it.
The contract covers two approval levels. A regional VP step would be a third. Flag it as a change order?
Flag itAfter the call
Turn every call into action.
- Notes and next steps, captured
The summary is written, every decision is logged with who made it and where, and every next step has an owner and a date, a minute after the call ends.
- The record, updated
The decision log, the requirements, the plan, and Jira are updated from what was said. Anything outside the SOW is flagged with the clause it touches.
- The follow-up, drafted
The recap email with the decisions, the open items, and the attachments, ready to review and send before you stand up.
- Send the Okta metadata file
- Send the approval email template
- Confirm the regional VP step with finance
- Load the remaining test accounts
Every conversation becomes memory.
# fairbanks-deliverySignals reach the right team
A scope change lands in the delivery channel the moment it is said.
DatafruitNothing is said twice
What changed and what was promised carries into the next brief.
Two things. The Okta file arrives Friday, and a regional VP step was asked for.
Ask across every call
“What changed on Fairbanks since last week?” answered from every call, with the moment behind each line.
Answers from the whole engagement
Bring the Agent to your next client call
One call with a real client, recorded, read, and written up. See what the brief, the flag, and the recap look like on your engagement.
Book a demoExplore the suite of tools
- WorkflowsBriefs, recaps, and status updates that run on their own.30 minutes before a client callWrite the brief, with sourcesYour Slack DM
- 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
