You do not need 40 automations. You need six. Each one has a clear trigger, a clear action, and a real number of hours it gives back every week. The printable card writes the six sentences for you.
“I do not need 40 zaps. I need the five rules that buy back my Friday.”
It comes up in every operator thread about automation. The buyer is not anti-automation. They are anti-overengineering. The last evaluation ballooned into 14 zaps and a monthly bill, and the operator is still the one chasing every follow-up by memory.
The six rules below are the floor. Each one is a sentence the operator already knows how to say. The card writes them down cleanly, names the trigger, names the action, and prints the hours back next to each.
Each rule is a 10-word sentence. The trigger is an event your CRM already sees. The action is a step it already knows how to take. The hours-back figure is a conservative composite for a 1 to 50 person services team running 30 to 80 active deals.
When a meeting on a deal ends, draft a follow-up email tied to the deal record.
When a deal has not moved stage in 14 days, flag it on a daily digest to the deal owner.
When a website form is submitted, create a lead record and assign the owner by territory or round-robin.
When an inbound email arrives from an address that matches a contact, attach it to that record automatically.
When a meeting on a deal is 24 hours away, send a reminder to the deal owner with a one-line prep note.
Every Monday at 9 am local time, send the deal owner a digest of advanced deals, stalled deals, meetings this week, and follow-ups owed.
A rule you can read out loud is a rule any CRM can run.
The six rules work in whatever CRM you have today. HubSpot. Pipedrive. Attio. Notion. Airtable. Syncek, when the automation layer ships. The card is portable on purpose.
If the sentence runs past 10 words, the rule is not ready. Trim until the trigger and the action both fit. Then build the version on the card, not a richer one.
The order matters less than the cadence. One per day forces you to test each rule in isolation. Day seven is the day you trust them. The order on the card is the order most operators report works.
Every red flag on the card lives on the trigger side: a calendar bug, a 7-day window that became noise, a missing whitelist. Tighten the condition. The action is almost always the obvious one.
Past the floor, the marginal hour-back drops fast and the maintenance cost rises faster. Run the six for ninety days. Then, if a seventh rule comes up twice in operator threads, you have earned the right to add it.
One page. A4 and US Letter. Six rules with trigger, action, hours back, and red flag. Print it, tape it next to the monitor, hand it to the next ops hire on day one.
Download the PDFSix CRM automations every small team needs.
Short answers. The long-form reference covers the rest.
Six rules cover the floor for a 1 to 50 person team: the post-meeting follow-up draft, the overdue-deal alert at 14 days, lead routing on form submit, email-to-record capture, a 24-hour meeting reminder, and a weekly status digest. Each rule has a clear trigger, a clear action, and a conservative hours-back estimate.
Together they buy back 7 to 12 hours per week for a team running 30 to 80 active deals. The reference card writes the six sentences for you.
A CRM automation is a sentence: when X happens, do Y. The trigger is an event the CRM can detect (a meeting ending, a form submission, a stage that has not moved in 14 days). The action is a step the CRM can run (draft an email, flag a deal, create a record, send a digest).
If you cannot say the rule out loud in 10 words, the rule is not ready to ship. The card forces every rule into that 10-word shape.
Forty zaps is the ceiling, not the floor. The six rules cover the highest-leverage moments a small team forgets to act on: a meeting that just ended, a deal that has stalled, a lead that just arrived, an inbound email tied to a contact, a meeting one day out, the Monday status check.
Past the floor the marginal hour-back drops fast and the maintenance cost rises faster. Six is the small number that keeps working. After ninety days you have earned the right to consider a seventh.
The rules are written so any CRM with native triggers and actions can run them. That includes HubSpot, Pipedrive, Attio, Notion, Airtable, and Syncek when the automation layer ships.
If a vendor cannot run a rule as named, the card tells you exactly which capability gap to ask about. The card is portable on purpose. Your data is yours; the rules are yours too.
Conservatively, 7 to 12 hours per week for a team running 30 to 80 active deals. Each rule's hours-back figure is a composite estimate, not a single magic number.
The post-meeting follow-up and the email-to-record capture do most of the heavy lifting at 2 to 3 hours per week each. The 24-hour meeting reminder saves the least time per week, but stops the deals you would have forgotten about entirely. That second number does not show up on a stopwatch.
Not yet. The automation surface is on the Syncek roadmap, not in the closed beta. The reference card is vendor-neutral on purpose, so you can turn the rules on inside whatever CRM you are running today.
When Syncek ships its automation layer, the six rules are the first surface we are building. The closed beta you join from this page is the channel we use to tell you when that ships.
Map your current zaps to the six rules first. The ones that overlap stay where they are; the card is the spec, not the implementation. The ones that do not map are the candidates to retire next quarter.
Most operators we talk to find three to five zaps doing roughly what the card describes, plus four to nine zaps that nobody remembers turning on. The retire-the-unused-zaps pass is the second hour-back the card buys you.
A single printable PDF. One page. Both A4 and US Letter sized so the same file works on either side of the Atlantic.
The English and Spanish versions are separate files. Tick whichever boxes you want when you submit the form.
No. Email is used to send the card and the occasional Syncek update. No phone, no company size, no drip nurture, no “just checking in” follow-ups. Unsubscribe is one click.
Honest pricing. No per-seat surprises. Same posture on the email list.
The full article, with every rule's worked example, common pitfall, and implementation note, is at syncek.com/blog/six-crm-automations-every-small-team-needs. The PDF is the printable. The article is the reference.
The same operating system, four different design problems. The other three cards are below.
Four recurring passes on the team calendar. Weekly 10 minutes, monthly 30, quarterly 90, annual half-day. Vendor-neutral.
See the calendar [ B ] The second companionFive stages, five disqualification rules. The model every small-team deal lifecycle fits inside, with no parking lots.
See the 5-stages cardPrint the card. Read each rule out loud. Turn on one a day for six days. Day seven, the operator gets their Friday back. That is the whole model.