7 Plain English Sales Automations You Can Set Up Today (With Real Examples)

Most sales teams don't automate their pipeline. Not because they don't want to. Because the tools that promise automation require you to build it like a software engineer.

Open HubSpot's workflow builder. You're looking at triggers, conditions, branches, delays, enrollment criteria, and re-enrollment logic. You need to know what you want before you touch it. You need to test it, debug it, and maintain it when your process changes.

Most small teams get halfway through their first workflow and give up. Then nothing is automated. Deals die in silence. Someone blames the reps.

There's a different approach: writing automation rules in plain English, the same way you'd describe the rule to a new hire. "If a prospect hasn't replied in five days, draft a follow-up email." That's it. No triggers. No branches. No engineers.

Briced uses this model. You write the rule in natural language, and the AI handles the rest: reading your email thread, understanding the context, and taking action.

Here are seven automation rules a small B2B sales team would actually want, written in plain English, with examples of what they do in practice.

1. "If a prospect hasn't replied in 5 business days, draft a personalised follow-up email."

This is the one every sales team needs first.

You send a proposal. Silence. You mean to follow up. You get distracted. A week passes. The deal goes cold. Nobody noticed until the pipeline review.

The Briced rule: If the prospect hasn't replied to my last email about this deal in 5 business days, draft a personalised follow-up referencing what we discussed.

What the AI does: it reads your last sent email on the deal thread, drafts a follow-up that references the specific topic discussed (pricing, timeline, technical requirements), and queues it for your review. You read it, adjust if needed, send. The whole thing takes 90 seconds instead of you needing to reconstruct the context from scratch.

What this would take in HubSpot: a workflow with a "Last activity date" property trigger, contact enrollment conditions, a delay step, an email send step, and an unenrollment condition for contacts who already replied. Minimum 45 minutes for a developer-comfortable user to build and test. More for everyone else.

This single automation, deployed across a team of 5 reps, catches 6 to 8 deals per week that would otherwise go cold without a follow-up.

2. "If a deal has been in the same stage for more than 3 weeks, flag it and ask me what to do."

Deals don't always die dramatically. They stagnate.

You have 40 deals in your pipeline. Half haven't moved in a month. You keep forecasting them. Your manager keeps asking about them. Nothing changes because nobody is tracking inactivity automatically.

The rule: If a deal hasn't changed stage in 21 days, flag it and send me a daily reminder until I take action or close it.

What happens: Briced surfaces the stalled deal with context: how long it's been in that stage, the last email on the thread, and a suggested next action. You decide: follow up, mark it closed, or adjust the stage. Either way, you made a decision. It's no longer sitting there polluting your forecast.

If you've ever looked at your pipeline at end of quarter and found deals that have been "in negotiation" since January, you know exactly what this is worth. The follow-up problem runs deeper than most sales teams realise: deals die in silence precisely because nobody has a system that catches them while there's still time to act.

3. "If a prospect asks about pricing in an email, notify me immediately and draft a proposal summary."

Pricing questions are buying signals. They should trigger a response within hours, not days.

The problem: you have 12 active threads. A pricing question comes in at 4pm. You're in meetings. You don't get to it until the next morning. The prospect asked three vendors the same question. Someone else responded first.

The rule: If a prospect uses the words "pricing," "cost," or "how much" in an email, send me a notification immediately and draft a proposal summary.

What happens: Briced reads the incoming email, identifies the pricing intent, notifies you in real time, and drafts a response that already knows the deal stage, the company context, and what was discussed previously. You edit and send.

Speed matters here. Teams that respond to pricing questions within 2 hours close at higher rates than those who respond the next day. The rule removes the bottleneck without you having to monitor your inbox constantly.

4. "If the main contact on a deal hasn't emailed me in 30 days, flag the deal as at-risk."

Sometimes the most important signal is silence from a specific person.

Your champion at the prospect company has gone quiet. That's different from the deal being quiet. It might mean they're no longer involved. It might mean something changed internally. It might mean the deal is effectively dead.

The rule: If the primary contact on this deal hasn't appeared in any email thread for 30 days, mark the deal as at-risk and prompt me to check in.

What happens: Briced reads your email history for that deal, identifies whether the key stakeholder has been active, and surfaces the deal when their participation drops off. Not "no activity on the deal" broadly. Specifically, the absence of the person who matters.

This is the practical difference between inbox-native CRM and a CRM that just logs email metadata. A tool that logs activity shows you what reps entered. A tool that reads your inbox knows whether the key contact actually replied.

5. "When a deal moves to the closing stage, notify my manager and schedule a review."

Closing-stage visibility without manual reporting. That's what this rule does.

Sales managers need to know which deals are near close. Reps don't always update them proactively. Pipeline reviews happen weekly. A deal can move from proposal to verbal agreement in three days without the manager knowing until it's too late to help.

The rule: When a deal moves to "Closing" or "Verbal Agreement," automatically notify [manager name] and add it to the Thursday pipeline review agenda.

What happens: the deal stage advances (Briced updates stages automatically based on email context). The manager gets notified. The deal appears on the review list. No rep had to log anything, and no manager had to check a dashboard.

For founders doing their own sales, this rule looks slightly different: "When a deal reaches verbal agreement, draft a contract summary and route it to my legal inbox." Same logic, different recipient.

6. "One day before a scheduled demo, remind me to review the deal thread and send the prospect a prep email."

Demo preparation is one of those tasks that feels optional until you walk into a 30-minute call and realise you forgot what the prospect asked three emails ago.

The rule: One day before any scheduled demo, remind me to review the deal thread and send the prospect a brief agenda email with what we'll cover.

What happens: Briced reads your calendar, finds the demo event linked to the deal, reads the email thread from the past few weeks, summarises the prospect's stated priorities, and drafts a prep email you can send that morning. The prospect shows up already aligned. You show up prepared.

This automation doesn't look flashy. It consistently improves demo-to-proposal conversion because the prospect feels heard before the call starts.

Pair it with a post-demo follow-up automation and you have the full pre- and post-call sequence running automatically, without the rep having to remember either step.

7. "30 days after a deal closes, send a personalised check-in to the customer."

Post-close follow-up is the most neglected part of B2B sales. Not because it isn't valuable. Because once the deal is closed, the rep is already onto the next one.

The rule: 30 days after a deal moves to "Closed Won," send a personalised check-in email asking how onboarding is going and whether there are any questions.

What happens: Briced schedules the check-in at deal close, drafts an email using the customer's name, the product context from the deal thread, and a specific question about their onboarding experience. You review and send. Or, if you trust the draft quality, it goes automatically.

For a team of 5 reps closing 20 deals per month, this rule generates 20 post-close check-ins automatically. Some become expansions. Some become referrals. None of them would have happened if the rep had to remember to do it manually.

The common thread across all seven

Every one of these automations has the same structure: a condition written in plain English, and an action the AI takes or drafts for you without requiring a workflow builder.

No triggers. No branches. No enrollment criteria. You wrote what you wanted in natural language. Briced figured out the logic.

That's the difference between automation that gets used and automation that gets abandoned halfway through setup. Sales automation software that actually eliminates admin work doesn't require you to become a workflow architect. It requires you to know what you want and let the AI handle how to do it.

If you're still deciding whether this approach fits your team, understanding what B2B sales automation should actually do for small teams is worth reading first. Most automation tools target outbound prospecting sequences. Briced automates the inbound pipeline management side, keeping deals alive, follow-ups sent, and stages accurate, which is the work that typically falls back on the rep.

Getting these running

Each of these rules takes under a minute to configure. You open the automations panel in Briced, type the rule in plain English, and it's live. The AI interprets what you wrote, maps it to your deal and contact data, and runs it against your email threads.

You can add a review step if you want to check drafts before they send. Most teams start in review mode, build trust in the draft quality over a week or two, then switch to automatic for the rules they're confident in.

The result: your pipeline maintains itself. Deals don't go cold in silence. Follow-ups happen. Your manager knows when deals are closing. Your customers hear from you 30 days after close.

You didn't have to build a workflow. You just described what you wanted.

Set up your first automation rule in 30 seconds. Free trial, 30 days, no setup cost.