B2B sales automation from first contact to signature
A salesperson should be selling, not holding the process in their head and in a notebook. We join up the whole funnel: an entry condition for every stage, a forecast calculated from data, one place with the history of a deal, a list of what to do today, and handover to delivery on the day of signing. Routing, scoring, follow-up and proposal sending go in as parts of that process, not as five separate scenarios.
- 42 hoursthe average response time to an inbound web enquiry in an audit of 2,241 companies published in Harvard Business Review. It is the only stretch of the B2B funnel anyone has measured
- 14 daysfrom workshop to the first part of the process running on your real deals in the CRM
- 2 to 4 weeksfrom workshop to a joined-up process, from first contact through to handover to delivery
The problem
Why do good deals die in the middle of the funnel?
Tuesday morning. A rep has 60 open deals in the CRM. The proposal went out on Friday and nobody knows whether the client opened it. What was agreed in a meeting ten days ago sits in a notebook only that rep can read. Three deals have been parked at the negotiation stage for six weeks, because nobody ever decided what that stage means. No one here is lazy. The process exists, just not in the system.
The breakdown starts in places the funnel chart does not show. A stage has no entry condition, so everyone moves a deal when it feels about right, and the forecast becomes a sum of moods. One deal is worked by the rep, someone from pricing and a technical person, and the history splits across three mailboxes. After a win the terms have to be told to the delivery team a second time, because all the CRM kept was an amount and a company name.
The time budget is fixed. A week has the hours it has, and a rep gets no more of them because the pipeline grew. What anyone actually measures is only the very start of the process. In an audit of 2,241 companies published in Harvard Business Review, the average response time to an inbound web enquiry was 42 hours, and 23 percent of companies never replied at all. What happens after that, from qualification to signature, almost nobody measures at home, because there is nothing to measure it from.
- A deal sits at the same stage for weeks and nobody sees it
- The board forecast misses the result, because a stage means something different to everyone
- What was agreed in a meeting stays in one person's notebook
- Delivery starts late, because the scope has to be reconstructed from a conversation
- A rep leaving takes the history of a dozen open deals with them
Why now
What changed, so that a sales process gets joined up in weeks?
Every popular CRM has an API and webhooks. HubSpot, Pipedrive, Salesforce and Zoho let you read the whole history of a deal and write a result back into it without clicking through records, and the rules for doing that are published openly, for example in the HubSpot developer documentation. So the process can be described in rules alongside the CRM, and the CRM stays the place where the team sees the state of a case. A few years ago each such rule meant a project measured in quarters.
The second change: this is no longer one big rollout project. The process splits into parts that go in one at a time, and each can be judged on its own. Lead routing assigns an enquiry in seconds, lead scoring sets the calling order, follow-up holds people to what was agreed after a meeting, proposal sending builds the document from deal data, and the sales report recalculates the forecast every morning. This page sits one level up: it is about those parts adding up to a single process. When the problem is the state of the database itself, we start with CRM automation.
The third change is the AI agent. A rule does what it was told, but it will not answer a sales director asking which deals from this quarter have not moved in more than 14 days. BOND, our company AI agent, answers that in a plain sentence in 5 to 10 seconds, from CRM data, with no report to order and no system to log into.
What changes
What does the sales team get?
A stage change has a condition, not an opinion
Every stage gets an entry condition written in one sentence, and the automation checks it at the moment of the move: is there a named decision maker, a budget, a decision date, a proposal that went out. Whatever is missing becomes a task with a deadline instead of quietly disappearing.
The condition is checked when the deal moves, not at the Friday review
A forecast from data, not from hope
Pipeline value is calculated from the stage, the age of the deal and the decision date agreed with the client, by the same formula for the rep and for the board. A deal that has not moved in more than 14 days drops out of the forecast until somebody moves it.
One number refreshed daily from the CRM, instead of two spreadsheets that disagree
One deal, one history
The email thread, the meeting note, the proposal version and the list of people on the client side all hang off the deal. Someone from pricing or a technical person picks the case up without asking the rep for context.
History attached to the deal in HubSpot, Pipedrive, Salesforce or Zoho, not in someone else's inbox
A list of actions in the morning, not 60 deals in no order
The rep gets one list for today: what was promised to a client, whose decision date has passed, which deal has been parked too long. The order comes from scoring and from deadlines, not from what happens to be on the first screen of the funnel.
The list lands in the CRM and on Slack before 8:00, the same one for the whole team
After signing, delivery starts the same day
A won deal creates the project and the tasks, carries over the agreed terms and scope, triggers invoicing and client onboarding. Nobody has to explain to delivery from scratch what the client actually bought.
Scope, terms and the named owner copied from the deal into the task system without retyping
Questions about the funnel in a plain sentence
How many deals from this quarter have not moved in two weeks. How many proposals are past the decision date the client gave us. What do we lose on most often in this industry. The AI agent answers from the CRM.
An answer in 5 to 10 seconds, in English or in Polish, with no report
And in your company
What if our sales look different?
Four sentences we hear most often in a consultation, and how we answer them.
Our sales run on relationships, you cannot automate that.
We do not automate relationships and that is not the point. The automation watches the things that damage a relationship: the material promised in a meeting and sent a week later, the proposal with no reply, the decision date the client remembers better than we do. A person runs the conversation, and the process stops depending on whether that person had a free hour that day.
We have a process written up in a 2023 deck and nobody follows it.
That is almost always the case, which is why the workshop starts from how you sell today, not from what somebody once drew. Stages and entry conditions are signed off by the sales team, not by us. The automation enforces only what that team judged sensible, because rules reps do not believe in get worked around in the first week.
Our sales cycle runs 9 months, an automation will not shorten it.
It will not, and we will tell you so. On a long cycle the automation does something else: it stops a deal sitting still, keeps the history through a change of owner, remembers dates agreed with a client six months earlier, and shows how many deals from the quarter are genuinely alive. The longer the cycle, the more context is lost on the way.
We have HubSpot with workflows, why add another layer?
If the process is narrow and closes inside one system, native workflows are enough and we will say so. An outside layer in n8n, Make or over the API earns its place when a single rule has to touch the CRM, the proposal document, the task system and invoicing at once. Native scenarios then grow into dozens of entries kept by hand.
- CRM
- HubSpot, Pipedrive, Salesforce, Zoho
- Sourcing and outreach
- Website form, LinkedIn Sales Navigator, Lemlist, Woodpecker
- Proposals and documents
- Google Workspace, Microsoft 365
- Team tools
- Slack, ClickUp, Jira, Asana, Notion
- After signing
- Xero, sevDesk, Fakturownia, Comarch Optima
- Data and forecasting
- BigQuery, Google Sheets, GA4, SQL databases
- Automation layer
- n8n, Make, Zapier, custom API integrations
Funnel stages, conditions to move on, and the work the automation does
This is what the process usually looks like once it is joined up. Stage names come from your funnel, and the conditions are set by the sales team in the workshop, because they decide whether the forecast means anything.
| Stage | Condition to move on | What the automation does |
|---|---|---|
| New lead | complete contact details and a reason to make contact | assigns an owner, enriches company data, sets the date of first contact |
| Contact made | a call has happened and the client need is written down | attaches the email thread and the note to the deal, creates the task for the next step |
| Qualification | decision maker, budget and decision date in the deal fields | blocks the move without those three fields and says which one is missing |
| Proposal | the proposal version the client received, attached to the deal | builds the document from deal data, records the send date, watches the follow-up |
| Negotiation | agreed terms and a decision date on the client side | raises a flag after 14 days with no movement and reminds on the promised decision day |
| Won | a signed document and the scope in one place | creates the project and tasks, carries over the terms, triggers invoicing and onboarding |
| Lost | a reason picked from a closed list | schedules a return to the subject after a set time and feeds the reason statistics |
These rows are a starting point. A first rollout usually covers 2 to 3 stages, most often the ones around the proposal, and the rest goes in once the first part holds.
How we work
Five steps from a process in people's heads to a process in the system
Every step ends with something you can judge before you decide on the next one.
Workshop
We break today's sales down into stages and check how long each part takes, where deals sit longest and what happens after a win. We look at the CRM, the calendar, the inbox and the spreadsheets, including the one quietly acting as a second CRM.
Conditions and the forecast
We write down the entry and exit condition for each stage, the definition of won and lost, the way the forecast is calculated, and what the automation blocks as opposed to merely flags. We agree which fields are genuinely needed, because every extra one lowers the odds it gets filled in.
Pilot on one part
We pick one part, usually around the proposal, and run it in 14 days on real deals, alongside the current process. Nothing gets switched off. After two weeks it is clear whether the rule helps the reps or just adds clicks.
The rest of the process and handover after a win
We add the remaining parts: routing, scoring, follow-up, proposal sending and the nightly forecast recalculation. A won deal starts triggering delivery, invoicing and client onboarding on its own. The sales director learns to change stage conditions without raising a ticket with us.
Measurement at 30 and 90 days
We look at three numbers: time spent at each stage, the share of deals with no movement for more than 14 days, and the gap between forecast and actual result. At 30 days we retune the rules, at 90 you know whether the process holds on its own.
Before and after
How a sales rep's week changes
Before
- Monday starts with filtering 60 deals to guess which one to touch
- Meeting notes get typed into the CRM in the evening, or never
- The board forecast is assembled in a spreadsheet on Friday and does not match the CRM
- After a win the rep phones delivery and explains what was promised
After
- The morning brings a list for today, built from deadlines and from scoring
- The note, the email thread and the next step sit on the deal without retyping
- There is one forecast and it is calculated daily from the same data
- On signing day delivery has the scope, the terms and a named owner
The first part of the process runs 14 days after the workshop, the whole thing in 2 to 4 weeks. The gap between forecast and result we judge after 90 days, because there is no honest way to measure it sooner.
For the person signing this off
What a sales director gets out of it
The forecast you give the board stops being your opinion. It is calculated by one formula from data the whole team can see, so the conversation about the quarter stops being a conversation about whether you are cautious or optimistic. You also know how many deals are sitting still, and since when, before anyone asks.
The second thing matters more when the team changes. A rep leaving today takes the history of a dozen open cases, because what was agreed sits in their inbox and in their head. When the process enforces the record, a new person picks those deals up within a day instead of rebuilding the context for a month.
- A forecast calculated one way, the same for you and for the rep
- The process written down and versioned, independent of any one person
- A pilot on one part in 14 days, so the decision on the rest follows a result
- Stage conditions changed on your side, without raising a ticket with us
What it costs
The workshop has a published price, the rollout is quoted after it
The process workshop costs EUR 3,500 net per week, and runs from one to seven weeks. A whole sales process is usually 1 to 2 weeks, because we have to walk through every stage and through what happens after signing. We quote the rollout after the workshop, once it is clear how many stages are in scope, what state the CRM is in and how many systems have to be touched after a win.
You pay the cost of running the automations directly to the tool provider, that is n8n, Make or Zapier, or you pay nothing at all when the scenarios sit on your own infrastructure. No margin from us. The same goes for model costs when an AI agent is part of the process, where a single query costs the provider roughly EUR 0.005 to 0.07.
Process workshop
EUR 3,500 net
per week, a whole sales process usually takes 1 to 2 weeks
A self-contained piece of work. It ends with the process written down, conditions included, and a rollout order you could execute without us.
- A map of today's sales with the time spent at each stage
- Entry and exit conditions for the stages, signed off by the team
- The way the forecast is calculated and the list of fields genuinely needed
- The order of automations and the metrics to measure at 30 and 90 days
- Most popular
Workshop and process rollout
Quoted after the workshop
scope follows from the number of stages and the systems involved after signing
The option most companies choose. The first part runs 14 days after the workshop, the whole process in 2 to 4 weeks, on your real deals.
- Everything in the workshop
- Conditions to move on and next-step tasks wired into the CRM
- Routing, scoring, follow-up and proposal sending as parts of one process
- Nightly forecast recalculation and flags on deals with no movement
- Handover after a win: project, tasks, invoicing, client onboarding
- Training for the sales director on changing conditions without us
Sales process and an AI agent
Quoted after the workshop
for teams that ask about the funnel a dozen times a day
Everything in the rollout plus BOND, the company AI agent that answers questions about the state of the funnel in a plain sentence.
- Everything in the process rollout
- An AI agent wired into the CRM: deal state, forecast, reasons for losses
- Alerts on deals with no movement and on a decision date that has passed
- Access for the reps and for the director, in English and in Polish
The workshop ends with a document that stands up without us: stages, conditions to move on, the way the forecast is calculated and the order of automations. If it turns out the problem is not the process but a shortage of leads or the state of the CRM database, we say so plainly and point at where to start, instead of selling a rollout that would not fix it.
Frequently asked questions
What is B2B sales automation?
It is joining the whole sales process into one mechanism: from taking in an enquiry, through the conditions for moving between funnel stages, through a forecast calculated from data, to handing the case over to delivery after signing. The automation enforces the record, the deadlines and the next step, while the rep runs the conversation with the client. It is not the same subject as a single scenario such as lead routing, because the point here is that individual automations add up to one process.
How long does a B2B sales automation rollout take?
One or two weeks of workshop, then 14 days to the first working part and 2 to 4 weeks to the joined-up whole. The pilot runs alongside the current process, so nothing is switched off until the team confirms that the rule helps. With a badly fragmented CRM the database has to be sorted out first, and the whole thing stretches to 6 weeks.
How is this different from CRM automation?
CRM automation deals with the system: fields, picklists, duplicates, permissions and making the data filterable. This service deals with the process: what has to be true for a deal to move on, how the forecast is calculated, who works on one case and what happens on signing day. If the database is in poor shape we clean it up first, because a rule running on bad data repeats the mistake faster than a person would.
Will automation replace our sales reps?
No. The automation takes over the record keeping, the reminders, the document assembly and the forecast maths, which is the work a rep does after hours or skips. Conversation, discovery and negotiation stay with the person. The point is more hours for conversations inside the same working week, not a smaller team.
How do you calculate the forecast from the funnel?
From the deal stage, its age, the amount and the decision date agreed with the client, by one formula for the whole team. A deal that has not moved in more than 14 days drops out of the forecast until something real happens, because otherwise the funnel swells with cases that are already dead. The formula is set in the workshop and signed off by the sales director, not by us.
What happens after a deal is won?
A win triggers the handover: a project with tasks is created, the terms and scope from the conversations carry over, invoicing gets its notification and client onboarding starts. Whoever runs delivery has the context the same day, without being told everything from scratch. This is the most commonly skipped part of the process and usually the one that spoils the first weeks with a new client.
Do we have to change our CRM?
No. We work with HubSpot, Pipedrive, Salesforce and Zoho, and we build the process logic either in the native CRM tooling or in n8n, Make or over the API, depending on how many systems a single rule has to touch. A CRM migration is a separate decision, and if we think it is needed we will say so in the workshop with reasons, not halfway through a rollout.
What if our sales process is not written down anywhere?
It almost never is, and that is a normal starting point. The first output of the workshop is a process that matches how you sell today, including the exceptions you break on purpose. Only once it is written down can it be automated, because an automation needs a condition, not a feel for the situation.
Let us find out where your deals are standing today
The free consultation takes 30 minutes. You tell us how many open deals you have, what you call your stages and what happens after signing, even if the process exists only in people's heads. We will show you which part can be joined up in 14 days and what needs the CRM sorted out first. You do not have to share any systems at this stage.
We run at most two rollouts at a time, so that someone is genuinely sitting on each of them.
Book a free consultationPS. If a rep told you this quarter that a deal is about to close, and that deal has been parked for six weeks, this is exactly the problem. A process with no conditions does not give you a forecast, it gives you a mood. The workshop starts by writing those conditions down, and the first part runs 14 days later.