Find the job you need to get done, then open its workflow, prompt, or skill. From choosing accounts to renewing customers, with the tools for each resource clearly named.
By Vikash Koushik, Head of AI GTM Systems at Docket · Updated Sep 22, 2026
Choose the part of the customer journey that needs attention. Within each stage, resources sit beside the job they help you complete. Start with a recommended resource, then use the related prompts, skills, or connected workflows as the task grows.
Who should we pursue?
Define the accounts worth pursuing, then gather enough evidence to understand them. Work from your customer criteria to a list and an account brief. Keep facts and assumptions separate.
The useful outcome: You can explain why an account fits and point to evidence for the next conversation.
Turn what you know about good customers into explicit criteria. Apply those criteria to a list or territory before spending time personalizing outreach.
Before you move onCheck the shortlist against customers and poor-fit accounts you already know. Record the exceptions.
Bring the company URL, target role, and your offer into one sourced brief. Use the findings to choose a reason to contact this account.
Before you move onOpen the sources. A company fact should support the proposed angle, not just decorate the message.
How do we start a conversation?
Turn the audience and account research into a message, campaign, or timely response. Choose the job that fits your channel, then carry its evidence into the draft and final review.
The useful outcome: A relevant prospect has a clear reason to respond and a concrete next step.
Connect a verified account observation to your actual offer. Draft the first message, build follow-ups that add something, and choose whether video helps the conversation.
Before you move onCheck every personalized claim and make the ask easy to answer. Review the sequence as one conversation.
Start here
For the same job
Review copy, merge fields, source evidence, and the import file together. Use this after drafting, before the campaign reaches a sending system.
Before you move onConfirm that the final import matches the approved copy and that a person owns the send decision.
Choose the path that matches the signal: a known lead who contacted you, or an identified website visitor who still needs qualifying. Give the response an owner and a next step.
Before you move onA visit is a signal to investigate. Check the account and context before treating it as buying intent.
Start with the audience, offer, and approved proof. Create distinct campaign angles, then take the chosen idea into copy or video production.
Before you move onCheck the claim, audience fit, and hypothesis behind each variation before publishing.
Extract the strongest ideas from a webinar or transcript. Give each post, email, or other derivative asset its own audience and purpose.
Before you move onKeep quotations and factual claims tied to the source. Combine drafts that repeat the same argument.
Choose your ad platform. Use the complete workflow for performance analysis and approved changes, or the skill when you need a reusable account review.
Before you move onAgree on the reporting window and decision metric. Review spend-changing actions separately from the analysis.
What is holding up this deal?
Work from the account history to the next buying decision. Prepare for the conversation, follow through on what was agreed, and help the buyer complete the evidence and approvals they need.
The useful outcome: The buyer’s open questions, decision process, commitments, and next steps are explicit.
Use what you know about the account to identify what you still need to learn. Review calls against a clear rubric so the next conversation improves on the last.
Before you move onSeparate confirmed facts from assumptions about urgency, budget, and the buying process.
Prepare a response to the actual concern the buyer raised. Use a battlecard when the question involves a competitor, with evidence behind each claim.
Before you move onCheck the competitor evidence and approved positioning. Keep uncertainty visible instead of inventing a differentiator.
Start with checked notes and a follow-up. Use the fuller workflows when the work also includes CRM updates, qualification, or a mutual action plan.
Before you move onVerify owners, dates, and commitments against the notes before sending or changing the account record.
Start here
For the same job
Use the workflow that matches the document in front of you. Keep approved answers and their sources together so the right owner can review the draft.
Before you move onRoute security, legal, and commercial commitments to the people authorized to approve them.
Choose the workflow you need
For the same job
How do we keep and grow the account?
Start from what the customer is experiencing now: usage, outcomes, support history, and the relationship. Use that evidence to prepare reviews and renewal conversations.
The useful outcome: The account team and customer have an evidence-based view of progress, risks, and the next commitments.
Assemble the account evidence into a QBR that explains progress and outstanding work. Separate current results from the promises in the original sales material.
Before you move onCheck the reporting period, usage figures, and customer outcomes with the account owner before presenting.
Start here
For the same job
Combine usage, support, and account history into a renewal brief. Use the evidence to choose the conversation and actions the account team should own.
Before you move onTreat the risk assessment as a starting point for account review. Confirm the evidence and assign the next actions.
Start here
For the same job
What needs to work across the funnel?
Keep the data, reporting, and recurring work behind every stage dependable. These jobs support the whole customer journey and have their own owners, review rules, and exception paths.
A working system: Each process has a defined input, a reviewable result, and an owner for exceptions.
Start with the problem in the queue: incomplete records, unclear fit, missing ownership, or data that needs correction. Pick the workflow for that specific problem.
Before you move onTest normal and ambiguous records. Review proposed changes before they reach the system of record.
Choose the decision the report must support: the weekly pipeline review, the forecast call, or agreement on the figures across systems.
Before you move onAgree on definitions and reconcile source totals. Keep exceptions beside the number instead of burying them.
Track competitor changes and study why deals were won or lost. Feed the findings back into targeting, messaging, and sales preparation.
Before you move onSeparate observed changes from interpretation, and retain the source material behind each conclusion.
Once the manual result is useful, decide what needs to be packaged, connected, or scheduled. Follow the setup for the actual implementation you choose.
Before you move onTest repeated runs and incomplete inputs. Keep permitted actions bounded and make failures visible to an owner.
Every play above is also organized by role, filtered to what your seat actually uses.
Choose the problem that is holding up progress: finding the right accounts, starting conversations, moving a deal, or retaining a customer. Then choose the specific job within that stage. Each job has a starting resource and the related material you may need next.
Resources are grouped by the job they help you do. An account-research workflow, its prompt, and its reusable skill live together. The labels tell you whether a link is a full playbook, a prompt, or a skill, and identify its tools.
No. Prompts list their supported assistants, skills name their type, and playbooks show their implementation tools. Many existing automation playbooks use Claude Code or Claude-specific features. A shared directory helps you find the task; it does not change the requirements of the underlying resource.
Their guides sit alongside the workflows that involve project files, code changes, and repeatable operations. Follow the guide for the tool you use. A workflow written for one environment needs its instructions, dependencies, and connections checked before being moved to another.
Use the shared role directory for SDRs and BDRs, account executives, RevOps, demand generation, marketing and content, or founders. Each role page includes a starting sequence, review guidance, FAQs, and relevant resources from across this library.
After the inputs and outputs are stable enough to test, the required approvals are clear, and someone owns exceptions. Run it on known examples first, check what happens on a repeated run, and decide how failures will be reported.
Routing, CRM hygiene, reporting, market intelligence, and recurring automation support several parts of the customer journey. They belong in a shared operations section, with links to the specific process you need to improve.