This case study includes 2 parts:
1. What I discovered at Craft.io and the solution I implemented
2. A simulated analysis using AI-generated data to demonstrate the process and methodology
TL;DR
Found a tracking gap: SDRs and Sales were measuring different dates
Reality: 30% of meetings were rescheduled by around 2 weeks, extending the sales cycle, and 20% no-shows.
Simple solution, implementing one date field of "Original Booking Date" to track when a meeting was booked.
At Craft.io, the sales team reported a decline in meetings, and the quick fix suggested was to update the outbound sequence. I wanted to investigate the underlying cause, and what I discovered is:
1. The SDR (me) was tracking meetings using "Meeting Booked Date" - the day I scheduled the meeting
2. The sales team was tracking meetings using "Meeting Done Date" - when the demo actually occurred
This created three predictable problems:
1. If I booked for next month, I counted it now, they counted it next month.
2. If a demo got rescheduled, it created a gap between the booked and held dates
3. If a demo was canceled or a no-show, it remained on my meeting list but was not reported anywhere.
This, over a few months, led to a compounded data misalignment disaster.
I created a third date field: "Original Booking Date" to capture the exact date I first scheduled the meeting.
With all 3 fields in place, we could now track:
How many meetings I booked each month vs. when they actually occurred
Whether meetings happened on the originally scheduled date
How far out were rescheduled meetings being pushed
What the data revealed:
~20% no-show rate that wasn't visible in either system
~30% reschedule rate with an average delay of 2+ weeks.
The issue labeled as "decline" was not related to the pipeline itself, but rather a scheduling friction problem.
The impact:
Sales, marketing, and SDR teams are now aligned on the same KPIs.
We could proactively address no-shows and reschedules.
Leadership had visibility into the actual length of the sales cycle.
Using a prompt I created, I generated a dataset to simulate the process.
The Prompt
Create a CSV with 1,200 rows that simulates CRM demo status.
Fields:
- meeting_id
- account_id
- ae_owner colon Alex or Moti
- marketing_source colon Outbound; Inbound; Partner; Event; Referral
- contact_channel colon Email; Phone; LinkedIn
- meeting_booked_date colon ISO 8601 YYYY-MM-DD
- original_booking_date colon ISO 8601 YYYY-MM-DD
- meeting_done_date colon ISO 8601 YYYY-MM-DD or blank if not held
Constraints:
- Dates span the last 26 weeks.
- Sources: Outbound, Inbound, Partner, Event.
- Two owners with roughly even distribution.
Output:
- Clean CSV, no commentary, ISO date format YYYY-MM-DD.
The numbers tell the story:
212 no-shows (18%) that weren't visible in either system
829 rescheduled meetings that created timing gaps between booking and execution
Rescheduling clustered heavily in the 1-7 day range (89% of reschedules), but with a long tail extending 3+ weeks out
One field. 18% no-shows exposed. 829 reschedules tracked. Zero guesswork.