Skip to content

End-to-end B2B sales system

This is a sample build. The company, FleetFlow AI, is fictional, and the deals in the pipeline are demo records. The system around them is complete and is the same structure I set up for clients.

Role
System design and CRM build
Built in
HubSpot (also mapped for GoHighLevel)
Covers
Lead capture through closed won
Status
Sample build with demo data

Why a sample build

Client systems are full of client data, so I can’t show them. This one I built from scratch for a made-up company, FleetFlow AI, a fleet management SaaS for logistics companies running 10 to 200 trucks. The HubSpot account is real; the deals in it are demo records.

Who it sells to

  • Company: 20 to 150 employees, $5M to $50M revenue, 10 to 200 trucks, US regional and long-haul.
  • Today: spreadsheets or an old TMS, and willing to move to the cloud.
  • Buying committee: the owner signs off, the operations manager champions it, and the finance manager checks the contract and price.
  • Pain: 3 to 5 hours a day on manual dispatching, invoices going out 5 to 10 days after delivery, and no view of profit per route.

The pipeline

Eight stages from new lead to closed, each with an entry rule, an exit rule and an owner, so nobody has to guess when a deal moves or who has it.

  • New lead: first contact attempted within 5 minutes, assigned round-robin.
  • Attempting contact: follow-ups on days 1, 3, 5, 7 and 10, then closed lost with the reason “No response”.
  • Qualified: fit confirmed and pain stated; handed from SDR to account executive.
  • Discovery, demo, proposal, negotiation: each step creates the next task, so the deal can’t sit still unnoticed.
  • Closed won or lost: won deals go to onboarding; lost deals need a reason before they can close.

Routing on the form

The lead form asks for fleet size, and that one answer decides where the lead goes:

  • 1 to 9 trucks: nurture emails, no rep.
  • 10 to 200 trucks: a rep right away.
  • 200+ trucks: flagged as enterprise and sent to a senior account executive.
  • Free email address: low-priority queue.

Automations

  • New lead: confirmation email, Slack alert, rep assigned, and a call task due in 5 minutes.
  • After discovery: a solutions consultant is assigned, a demo prep checklist is created, and the booking link goes out.
  • After the proposal: follow-ups on days 3, 7 and 14, then closed lost on day 21 with a short survey.

Qualifying the lead

Instead of asking about budget first, the questions start with the problem: what isn’t working in dispatch today, how many hours it takes each week, what they’ve already tried, and what happens if it isn’t fixed in 90 days. Budget and decision-makers come after the problem is clear.

Reporting

The dashboard tracks the numbers the stages make possible: time to first contact, lead-to-qualified rate, demo-to-close rate, deal size, cycle length, pipeline value and the reasons deals were lost. The targets were set at under 5 minutes to first contact, a 45-day cycle and an $18,000 average deal.

Those are targets for the design, not results: with demo data, there is nothing real to measure.

Let’s work together

Location
Montreal, QC
Local time
9:30 AM
© 2026 Raven LionhartEN / FR / AR