Pick and Adapt Your Automation

You've been through five courses that each built something concrete: a CRM hygiene check, a stage-based follow-up cadence, a proposal template, a pipeline dashboard, and a meeting-intelligence workflow. This capstone has one job: get you to actually ship one of them, adapted to your real CRM and your real data, instead of letting all five stay theoretical.

The deliverable for this lesson: pick exactly one automation, and adapt its spec to your actual tools. Not "understand all five better" — pick one, and make it real. Trying to implement everything at once is how these projects stall; a single automation, fully working, beats five that are each half-built.

Choose based on where your biggest, most obvious pain currently is — not based on which sounded most interesting in the course. Concretely:

• Choose the CRM hygiene bot if your team's honest answer to "do we trust our forecast" is shaky, or if you know your pipeline has real rot — stale deals, missing fields, duplicates — that nobody's caught.
• Choose the follow-up cadence if you know your team's outreach is currently one-size-fits-all, or if hot post-demo leads are going cold because follow-up isn't fast or specific enough.
• Choose the proposal template if your proposals are still built by copying an old file, and you've had at least one close call with a stale price or wrong customer detail slipping through.
• Choose the pipeline dashboard if your pipeline reviews are still dominated by a single total-value number, with no visibility into velocity, stage win rates, or forecast accuracy.
• Choose the meeting-intelligence workflow if good information from real calls is routinely getting lost because nobody has time to write a proper CRM update after every conversation.

Once you've picked, go back to that course's spec-writing lesson and redo it with your real details. Every course in this track produced a spec — rules, thresholds, a template structure, trigger → action pairs, or a field mapping. The version you built while reading the course was necessarily somewhat generic; this capstone step is about rewriting it with your actual CRM's field names, your actual sales cycle lengths, your actual team's tools. This is where "I understand the pattern" becomes "I have something that fits my org."

What "adapted to your actual org" concretely means: your real CRM's stage names, not generic placeholders; your real thresholds (how many days actually counts as stale for your sales cycle, not a generic 21-day default); your real delivery destination (the channel or tool your team actually checks); and an honest answer to who on your team actually owns acting on it, by name, not "someone."

Why this has to be adaptable, not a copy-paste of the course's examples. Every example in this track was deliberately built tool-agnostic — CRM hygiene rules as pseudocode, cadences as trigger → action pairs, proposal templates as fields-to-document structure — specifically so it would transfer to whatever CRM, spreadsheet, or automation tool you actually have, rather than assuming one specific product. This lesson is where that transfer actually happens, for real.

▶️ Try this

Pick your one automation right now, based on your real, current pain point — not the one that sounds most impressive. Pull up that course's spec lesson again and rewrite the spec with your actual CRM field names, thresholds, and team details. By the end of this exercise you should have a one-page spec you could hand to a colleague and have them understand exactly what it does and why.