What is Jobber?
Jobber is a business management platform for home service providers, like plumbing, cleaning, landscaping, and HVAC, helping teams quote work, schedule jobs, manage customers, and get paid.
I helped shape Jobber’s first native sales pipeline from an ambiguous product gap into a successful V1 launch.
→ Reframed the problem from lead management to work management
→ Translated fragmented sales workflows into a simple pipeline model
→ Prioritized the MVP scope while shaping the product vision
→ Created the sales workflow foundation for AI prioritization, follow-up recommendations, and future sales automation
For solo service providers, tracking a few leads from memory could still work. But as teams, revenue, and lead volume grows, service providers need more visibility, structure, and flexibility.
Through research, three problems kept showing up.
No clear way to tell where each lead stands
“Every lead looks the same. I can’t tell what stage it’s in, is it in qualified, follow-up, or waiting on a decision?”
Difficult to understand what happened with a lead
“I’m piecing things together one tab at a time — notes in the client record, details in the quote.”
Reframing the problem from tracking leads to tracking sales work
At first, the problem looked like lead management. Service providers were asking for a better way to manage leads and clients. But research showed that lead tracking was only the symptom. What they really needed was a way to track the work required to move each lead toward a sale.
→ That shifted our direction from managing leads to managing the work required to move each sales opportunity forward.
Every service provider sells differently, with sales stages and processes shaped around their business. Despite those differences, we were able to identified a shared set of sales milestones.
Jobber already supported key milestones in the sales journey through workflows and features users knew and trusted.
But these sales workflows/features were fragmented across different product areas. To manage sales, users had to move between pages, piece together context, and rely on memory to track where each opportunity stands.
So the question became:
How might we create one flexible sales pipeline that reflects how each business sells, while still respecting the Jobber workflows and system logic users already relied on?
We explored different views to make sales work easier to see and manage.
Spreadsheet made sales easier to scan, but not easier to understand. Agentic view helped with prioritization, but required trust too early.
→ We shipped Kanban as the V1 foundation, so users can see where sales work stands and act on it.
→ We connected the context behind each sales opportunity, so users can understand what has happened and make decisions faster.
→ We made the pipeline flexible, so users can customize sales stages to match how they actually sell.
→ In v2, we used AI to turn pipeline data into next steps, so users can prioritize what to do.
Sales Pipeline became the most successful beta launch in Jobber history, reaching 3,000+ sign-ups and exceeding the original 400-user target by 7.5x.
3,000+
beta sign ups
400
original target
7.5x
target reached
Sales Pipeline launched to GA in April 2026 and continued to show strong early traction.
Lead to close-won time
-12%
average time to close won
→ Sales Pipeline helped service providers prioritize follow-ups and move leads forward faster
Probe the why sooner
I would have gone deeper on why visibility mattered — not just whether service providers could see their sales work, but how visibility helped them decide what to prioritize.
Bring prioritization into V1 thinking
The pipeline solved visibility, but the bigger question was whether it helped service providers close more work. I would have brought that question into the product strategy earlier.