The problem in numbers
Count last month's held first meetings, from calendars or scheduler logs, and count the deals created from them. Teams doing this exercise for the first time routinely find a gap of twenty to forty percent. Those are not lost deals. They are meetings that never became anything: no deal, no documented disqualification, no follow-up owner. The prospect showed intent, someone spent an hour, and the system recorded silence.
The other half of the problem is deals created badly. A deal born three days late, titled Intro call, with no value, no close date and the meeting notes in a private notebook, is unworkable by anyone but its creator, invisible to the forecast, and the reason your stage conversion numbers wobble at the top of the funnel.
The design
One rule carries the playbook: every held meeting ends, same business day, in exactly one of two outcomes. Qualified: the lead converts to a deal in stage one, complete with the handoff fields. Not qualified: the lead is archived with a reason. There is no third outcome. The rule is deliberately binary because the leak lives entirely in the undecided middle.
The handoff fields are the contract between the person who held the meeting and everyone downstream. Keep them to five or six: person and organisation linked, deal value estimate, expected close date, lead source carried over, and one qualification note covering pain, budget signal and agreed next step. Mark them as important fields, required at deal creation, so the platform enforces the contract. The discipline of refusing extra fields here is the same one argued in custom fields that earn their place.
Two automations support the rule. First, when a meeting activity is marked done on a lead, create a same-day task for its owner: convert or archive. The task makes the binary rule appear in the rep's list instead of their memory. Second, when a deal is created in stage one, create the next activity automatically, because stage one with no next step is where the freshly converted go to rot. Both are standard workflow automations of the restrained kind described in automations that matter.
Implementation steps
Step one: define stage one's entry criteria in writing, one sentence, so qualified means the same thing to everyone. Step two: configure the required fields at creation. Step three: build the two automations. Step four: brief the team on the binary rule, with the why, in one meeting. Step five: for two weeks, have the sales manager run a daily thirty-second check of yesterday's held meetings against created deals and archived leads. The habit sets in fast when the gap is visible daily, and the check itself disappears within a month.
How you measure that it works
The core metric is meeting conversion accountancy: held first meetings versus the sum of deals created and leads archived with a reason, weekly. The two numbers should match. Any gap is unprocessed meetings, and it should reach zero within a fortnight. Second, field completeness at creation, which required fields hold at one hundred percent by force. Third, watch time from meeting to deal creation fall from days to hours in the activity reports. As a side effect, expect your stage one conversion rate in Insights to become meaningful for the first time, because disqualified meetings stop entering the pipeline as ghost deals.
Common failure modes
The optimistic converter: every meeting becomes a deal because archiving feels like failure, and stage one becomes the new leads inbox. Counter with the stage one entry criteria and by celebrating documented disqualifications in the review, since a fast honest no protects everyone's time. The field workaround: reps enter placeholder values to satisfy required fields. Spot-check new deals weekly at the start, and cut any required field the team keeps faking, because a faked field is worse than no field. The split-motion gap: SDR books, AE assumes, nobody converts. One rule fixes it, whoever held the qualifying meeting converts, and the routing playbook's single-ownership principle applies end to end. And the notes silo: qualification lives in a personal doc instead of the deal. The required note field exists precisely to make the deal the only place the handoff can happen.
Questions
Should the deal be created before or after the first meeting?
After, in most SMB motions. A booked meeting is interest, not an opportunity, and pipelines fill with no-shows when booking creates the deal. Keep the lead in the Leads inbox until the meeting happened and qualification passed, then convert. High-intent demo requests can justify the earlier cut.
Who creates the deal when an SDR books for an AE?
The person who held the qualifying meeting creates the deal, and ownership transfers at creation, not later. Split motions die in the gap where each side assumes the other logged it. One written rule, whoever qualified converts, removes the gap entirely.
Can Pipedrive require fields when a deal is created?
Yes. Important fields can be marked required at creation or at a stage change on the higher plans, and the deal cannot proceed without them. Use it for the handful of fields the handoff genuinely needs. Every extra required field slows every future deal.
What belongs in the deal at the moment of creation?
The minimum that makes the deal workable by someone else: linked person and organisation, value estimate, expected close date, source, and a note with pain and next step from the meeting. If a colleague could not pick up the deal from it, the handoff is incomplete.
Does the Pipedrive Scheduler matter for this playbook?
It helps at the front: bookings land as activities linked to the contact, so nothing arrives by surprise. Any scheduler works though. The playbook cares about what happens after the meeting, and that part is process plus two automations, not tooling.