Good conversations should lead to finished work.
Your team already talks about the work in Slack. Jared brings a coworker-shaped approach to those conversations: understand what matters, prepare something useful, and keep the person responsible in the loop.
Start with a piece of work, not a giant rollout
Choose a workflow you already understand: a client update, a morning briefing, or a follow-up draft. Give it an owner, a trusted set of sources, and a definition of done. A narrow starting point makes it easier to see what is useful, what needs correction, and where a human decision belongs.
Review the output, including what is missing
A helpful deliverable makes its sources and uncertainty visible. Look for decisions, owners, dates, and open questions. If a task cannot be completed from the available context, a useful outcome is an explicit blocker rather than a confident guess.
Keep preparation and action distinct
The examples on this site show proposed ways to work with Jared. They are illustrative, not customer results or a guarantee that every connected tool supports every action. Confirm the available integrations and approval behavior in your workspace before relying on a workflow.
Choose your first workflow
Each page includes a concrete example, practical checks, and the decision that stays with a person.
Founder briefing
Bring the open questions, customer commitments, and approaching milestones into a founder briefing your team can review in Slack.
Read the playbook 02 / Use case · Client reportingClient status reports
Turn scattered project context into a reviewable client update with completed work, open questions, and next steps.
Read the playbook 03 / Use case · Sales follow-upSales follow-up
Prepare a relevant follow-up from the actual customer conversation, with a clear next step for the account owner to review.
Read the playbook 04 / Use case · Meeting follow-throughMeeting to actions
Use available meeting notes and team discussion to prepare a clear decision record and a reviewable list of next steps.
Read the playbook 05 / Use case · Customer successCustomer success preparation
Prepare an account briefing that connects customer goals, open commitments, and the questions your team needs to resolve.
Read the playbook 06 / Use case · Project handoffsProject handoffs
Prepare a handoff brief with current status, decisions, dependencies, and the next actions the receiving owner should understand.
Read the playbook 07 / Use case · Research preparationResearch briefs
Shape available research and team context into a decision brief that makes sources, trade-offs, and unanswered questions visible.
Read the playbook 08 / Use case · Invoice follow-upInvoice follow-up preparation
Bring invoice context and customer correspondence into a reviewable follow-up brief before the responsible person sends a reminder.
Read the playbook 09 / Use case · Customer onboardingCustomer onboarding handoffs
Prepare a sales-to-onboarding handoff with agreed scope, source-backed commitments, open questions, and an explicit acceptance checkpoint for the incoming owner.
Read the playbookNo pages match that search. Try “review”, “client”, or clear the search.