Building an Automated Sales Workflow from Scratch: Step-by-Step Guide

Building an Automated Sales Workflow from Scratch: Step-by-Step Guide

To build an automated sales workflow, define your pipeline stages first, then write one rule per handoff in the form "when this happens, if these conditions are true, do these actions." A small team can build a working version in one afternoon: six stages, two sequences, and six automations covering new leads, replies, booked meetings, stage changes, and lost deals. This guide is that afternoon, step by step, with the exact trigger, conditions, and actions for each rule and a test plan before anything goes live.

If you want the strategy behind sales automation (what to automate, AI versus human SDRs, ROI), read the AI sales automation guide first. This post assumes you have decided to automate and want the build.

What You Will Have at the End of the Afternoon

The finished workflow handles every routine handoff between a lead arriving and a deal closing or being lost:

• A new inbound lead gets an owner, a follow-up task with a due time, and a nurture sequence within seconds of submitting a form.
• A positive reply to a cold email stops the sequence and puts a call task at the top of the owner's list.
• A booked meeting creates a deal, moves the lead's status, and sends a text reminder an hour before the call.
• A deal moving to "Proposal Sent" creates a follow-up task two days out.
• A lost deal enrolls the contact in a long-gap re-engagement sequence instead of disappearing.

The schedule below assumes one person building and a team of one to five reps. Budget about four hours.

Time	Step	Output
0:00 - 0:30	Map handoffs and write rules in plain English	A one-page rule sheet
0:30 - 1:00	Set up pipeline stages and lead statuses	Six deal stages with entry criteria
1:00 - 2:00	Write two sequences	Inbound nurture and lost-deal re-engagement
2:00 - 3:15	Build six automations	All saved as drafts
3:15 - 4:00	Test with dummy records, then activate	Live workflow and a test log

Step 1: Write the Rules in Plain English (30 Minutes)

Do not open any tool yet. List every moment where one person currently has to notice something and do something. For a small B2B team, the list usually looks like this:

1. A form comes in. Someone has to see it, decide who owns it, and reply.
2. A prospect replies to outreach. Someone has to notice the reply among dozens of others and call back.
3. A prospect books a meeting. Someone has to create the deal and remind the prospect.
4. A proposal goes out. Someone has to remember to follow up.
5. A deal is lost. Usually nobody does anything.
6. A meeting is a no-show. Someone has to reschedule.

Now rewrite each one as a rule with three parts. Keep them short enough to fit on one line:

• Rule A: When a form is submitted, if the lead has a company email, assign the next rep in rotation, create a call task due in 15 minutes, and enroll in the inbound nurture sequence.
• Rule B: When a cold email reply is classified Positive, create a high-priority call task due in 30 minutes for the lead owner.
• Rule C: When an appointment is booked, set the lead status to Appointment Booked and create a deal in the Meeting Booked stage.
• Rule D: When an appointment starts in 60 minutes, text the attendee a reminder.
• Rule E: When a deal moves into Proposal Sent, create a follow-up task due in 2 days.
• Rule F: When a deal moves into Closed Lost, enroll the lead in the re-engagement sequence.

If you cannot write a rule in one line, it is two rules. Splitting them keeps each automation easy to test and easy to switch off.

Step 2: Set Up Stages and Statuses (30 Minutes)

Automations fire on stage changes, so stages need clear entry criteria. A stage nobody agrees on produces automations that fire at the wrong time. Use six deal stages to start:

Deal stage	Enters when	Automation that fires
Meeting Booked	A first meeting is on the calendar	Rule C creates the deal here
Discovery Done	First meeting held and the prospect has a real problem you solve	None at first
Proposal Sent	Pricing or a proposal has been sent in writing	Rule E
Negotiation	The prospect has responded to the proposal with questions or changes	None at first
Closed Won	Signed or paid	Add an onboarding rule later
Closed Lost	The prospect said no, or went silent after three follow-ups	Rule F

Write the "enters when" column into a shared doc. The most common reason a workflow misfires is reps using stages differently, not a broken rule.

For leads (before a deal exists), use the status field rather than stages. In PipeCrush the lead statuses are Cold Targeting, Working, Appointment Booked, Verbal Commitment, Closed Won, Closed Lost, and Disqualified. Rule C moves leads to Appointment Booked so the leads list shows who already has a meeting.

Step 3: Write Two Sequences (1 Hour)

Automations enroll people in sequences, so the sequences have to exist first. Write two.

Sequence 1: Inbound Nurture (3 Emails)

This is for people who asked for something (a demo, a quote, a download) and have not booked yet. It runs alongside the rep's call task, not instead of it.

• Email 1, day 0: Confirm what they asked for, deliver it if there is a file, and offer one booking link. Three to four sentences.
• Email 2, day 2: One useful answer to the question most people at their stage ask next. No pitch beyond the booking link in the signature.
• Email 3, day 5: Short check-in: "Did you get what you needed? If a 20-minute call would help, here is my calendar."

Put your booking link in every email. In PipeCrush, a booking made through a sequence link stops the sequence automatically, and so does a Positive or Not Interested reply or an unsubscribe, so nobody gets email three after they have already booked.

Sequence 2: Lost-Deal Re-Engagement (3 Emails)

Lost deals go into a slow sequence with long gaps. Each step's delay can be up to 30 days, so the spacing below fits.

• Email 1, day 1: Close the loop graciously. "Thanks for the time you put into evaluating us. If anything changes, reply here and I will pick it up."
• Email 2, day 31: Something useful with no ask: a checklist, a short guide, or an answer to the objection that lost the deal.
• Email 3, day 61: Soft check-in. "A few months on, is [the problem you discussed] still on the list? Happy to compare notes."

Keep both sequences in plain text with one link each. For the copy patterns behind cold, not inbound, outreach, see the five-touch cold outreach sequence with full example emails.

Step 4: Build the Six Automations (75 Minutes)

Each automation below is written as trigger, conditions, and actions, the same three parts as the plain-English rules. The configuration uses PipeCrush's CRM automations builder, but the logic carries over to any tool with event triggers. Save every automation as a draft until Step 5.

Automation A: New Form Lead to Owner, Task, and Sequence

Part	Setting
Trigger	Form submitted (pick your demo and contact forms)
Conditions	All of: lead email is not empty; lead email does not contain "gmail.com" (adjust or remove if you sell to consumers or sole traders)
Action 1	Reassign owner: round-robin across your reps, notify new owner on
Action 2	Create task: type Call, priority High, due in 15 minutes, assignee record owner, description "Call {{lead.first_name}} at {{lead.company}}: requested via {{lead.form_name}}"
Action 3	Enroll in sequence: Inbound Nurture, skip if already enrolled, unsubscribed, or bounced

Order matters. Reassign first so the task in Action 2 lands with the new owner. Build a second, simpler version of this automation for personal email addresses (task with Medium priority, due in 4 hours, same sequence) so those leads are not dropped.

Automation B: Positive Reply to Priority Call Task

Part	Setting
Trigger	Email replied, classification Positive
Conditions	None
Action 1	Create task: type Call, priority High, due in 30 minutes, assignee record owner, description "Positive reply: call or reply with booking link"
Action 2	Update fields: lead status to Working

Replies are classified as Positive, Not Interested, Referral, Auto-response, Question, or Objection. Add a second automation for Question and Objection replies with a Medium-priority task due in 4 hours. Those need a thoughtful written answer more than a fast call.

Automation C: Booked Meeting to Deal and Status

Part	Setting
Trigger	Appointment booked
Conditions	None (or restrict to your sales booking link if you also take support bookings)
Action 1	Create record: deal, stage Meeting Booked, title "{{appointment.attendee_name}} - first meeting", assignee record owner
Action 2	Create task: type Demo, priority Medium, due in 60 minutes, assignee record owner, description "Prep for first meeting with {{appointment.attendee_name}}: review notes and company site"

Keep this one small. Booking pages already send the calendar invite with the meeting link, so the automation only needs to put the deal in the pipeline and give the rep a prep task.

Automation D: Appointment Reminder Text

Part	Setting
Trigger	Appointment starts in 60 minutes
Conditions	Lead phone is not empty
Action 1	Send SMS from your business number: "Hi {{lead.first_name}}, a reminder that we are meeting in about an hour. The link is in your calendar invite. Reply here if you need to move it."

SMS actions skip anyone who has opted out. Only send texts to people who gave you their number in a context where a reminder is expected, such as a booking form with a phone field. For the full no-show playbook, including what to do after a missed meeting, see the SMS workflow for preventing no-shows.

Automation E: Proposal Follow-Up Task

Part	Setting
Trigger	Deal stage changed, to stage Proposal Sent
Conditions	None (or deal amount greater than a threshold if you only want this on larger deals)
Action 1	Create task: type Call, priority Medium, due in 2,880 minutes (2 days), description "Proposal follow-up: {{deal.title}}"

This rule fires on the stage change, not on the passage of time. It will not notice a deal that has sat in Proposal Sent for three weeks. Cover that with a weekly pipeline review that sorts deals by time in stage.

Automation F: Lost Deal to Re-Engagement

Part	Setting
Trigger	Deal stage changed, to stage Closed Lost
Conditions	None
Action 1	Enroll in sequence: Lost-Deal Re-Engagement, skip if suppressed

If you track a loss reason in a custom field, add a condition so "chose a competitor" and "no budget" go to different sequences. For a deeper version of this rule, including separate sequences per drop-off point, see automating re-engagement for stalled deals.

Step 5: Test Before You Activate (45 Minutes)

Every automation stays in draft until it passes a test. Use dummy records with your own email and phone number so nothing reaches a real prospect.

1. Dry-run each automation. The preview shows how many records it would affect and which actions would run. If an automation you expect to touch one lead says it would touch 400, the conditions are wrong.
2. Submit the form yourself with a company-domain test address. Check that the owner rotated, the task appeared with the right due time, and Email 1 of the nurture sequence arrived with the first name filled in.
3. Submit again with a personal address. Confirm the fallback automation caught it and the main one did not.
4. Reply "Yes, let's talk" to Email 1. Confirm the reply was classified Positive, the sequence stopped, and the call task appeared.
5. Book a test meeting 70 minutes out. Confirm the deal was created in Meeting Booked and the reminder text arrives about an hour before.
6. Drag the test deal to Proposal Sent, then to Closed Lost. Confirm the follow-up task and the re-engagement enrollment.
7. Read the run history. Each run shows a result per action. Anything marked failed or skipped needs an explanation before you go live.

Then activate the automations one at a time, starting with A and B, the two that touch new pipeline. Watch the run history for the first two days before turning on the rest.

Common Build Mistakes

• Two automations on the same trigger doing overlapping things. If A and a second form rule both enroll the lead in a sequence, the second one is skipped as already enrolled, but both create tasks. Make conditions mutually exclusive.
• Tasks with no due time. A task without a due time sits at the bottom of the list. Every task an automation creates should have one.
• Automating a stage nobody uses consistently. If half your reps skip Proposal Sent, Automation E fires for half your proposals. Fix the habit or drop the rule.
• Texting people who did not expect it. Reminder texts are for booked meetings. Do not add SMS to cold outreach rules.
• Building ten automations on day one. Six is enough. Add more only when the run history and your pipeline review show a handoff that is still being dropped.

What to Add in Week Two

Once the six rules have run cleanly for a week, these are the next ones worth building:

• Chat lead routing. If you run a website chatbot, new chat leads arrive through the "lead created" trigger. Route them the same way as Automation A. The chatbot lead qualification setup guide covers the qualifying questions and scoring that should happen before the handoff.
• Closed Won to onboarding. Deal stage changed to Closed Won: create a task for whoever runs onboarding and enroll the customer in a welcome sequence.
• Score-based priority. Lead updated, field lead score changed: if the score is 70 or higher, create a High-priority call task. Set the threshold from your own won deals: look at the scores of the last 20 leads that became customers.
• Missed inbound calls. Call completed, direction inbound: create a callback task for the record owner.

Measuring Whether It Works

Track four numbers weekly for the first month. Each one maps to a rule above:

Number	Rule it checks	What a problem looks like
Time from form submit to first call attempt	A	Tasks created but completed hours late: rep capacity or notification issue
Time from positive reply to response	B	Same as above, for replies
Meetings booked versus meetings held	D	Many no-shows: reminder not sending, or booked too far out
Deals in Proposal Sent older than 14 days	E	Follow-up tasks being closed without a real follow-up

None of these require new software. The run history tells you whether a rule fired; your task list and pipeline tell you whether a human acted on it. When both are true, the workflow is doing its job: every routine handoff happens on time, and your reps spend their hours on calls and proposals instead of remembering what to do next.

Photo by Edmond Dantes on Pexels