Manaz Afzal Book a consultation

Work snippet

HubSpot to Jobber: one deal per customer enquiry, with lead source kept

Concept DesignIllustrative integration walkthrough. Business details, figures and records are worked examples.

Enquiries reach this home-services business from the website, paid ads and the phone, and the original Zaps opened a fresh HubSpot deal each time one touched the system. The rebuilt Zapier flow searches before it writes, so an enquiry stays one deal, the Jobber client and quote point back to it, and the owner can judge ad spend by paid jobs.

The problemEvery form, call and quote creates a new deal, so the pipeline looks twice as full.

What changesOne deal per enquiry, linked to Jobber, with the lead source kept.

Area
CRM to job system
Tools
HubSpot · Jobber · Zapier · Slack
Typical scope
US$400-900
Timeline
About 4 weeks · fixed milestones

The situation and what was breaking

One customer could leave three deals behind: a form, a call and a quote. Pipeline value read nearly double, and the source of the lead rarely sat on the deal that closed.

Five Zaps had been added over two years, one per form and one per quote event. None of them looked up an existing contact or deal first, so a customer who filled a form and then called had two deals, and a third appeared when the quote was sent from Jobber.

Lead source was set on the first deal and lost on the others, so won revenue could not be traced to the ads that produced it.

  • 1.8 deals per genuine enquiry
  • Lead source lost on the deal that was won
  • Quotes in Jobber with no link to a deal
  • Sales calling the same customer twice
  • Ad spend decisions made without won revenue by source

What good looks likeOne deal per enquiry, and a report that shows which lead sources turn into paid jobs.

Discovery findings

What a read-only review checks first: six months of HubSpot deals and contacts, the Jobber requests and quotes, and the history of the five existing Zaps.

What a read-only review checks firstWeek 1
IDFindingEvidenceRisk if left
F1No lookup before create in any Zap5 of 5 ZapsDuplicates on every repeat contact
F2Deals per enquiry1.8 on average across 640 enquiriesPipeline overstated
F3Lead source set only on create62% of won deals had no sourceAd decisions blind
F4Jobber quotes with no deal id118 quotesWon and lost not visible in HubSpot
F5Phone enquiries entered by handNo source capturedPhone leads undercounted
F6Zap errors emailed to an old address41 unread errorsSilent failures

Architecture: HubSpot Jobber integration

Three Zaps replace five. Every one looks up before it creates, the deal id travels to Jobber, and errors go to a channel someone reads.

Scroll sideways to see the full drawing

Enquiry to job architectureWeb forms, ads and phone enquiries reach Zapier, which looks up the HubSpot contact and deal before creating; Jobber requests carry the deal id; quote and job status write back; errors post to Slack.020040060080enquirycreate or updaterequest + deal idquote, job statusstageserrorA · SOURCESEnquiriesWeb form, ads,phone logB · ZAPIERLookup firstFind contact,find open dealC · CRMHubSpotOne deal, sourcekept on updateD · OPERATIONSJobberRequest and quotewith deal idE · REPORTWon by sourceDeals, won, paidF · ERRORSSlack #opsZap errors, ownernever create before a lookupsource is written onceand never overwrittenLEAD FLOW · LOOKUP FIRSTManaz Afzal
Lookup-first enquiry flow with deal id carried into JobberSolid: live data path · Dashed: exception path

The screens your team will use

Sales work the pipeline in HubSpot. The Zap steps are documented so the next change does not reintroduce duplicates.

HubSpot · Deals · Enquiry pipeline40 open
New
Garden refresh, rear yardWeb form · Google Ads
Retaining wall quotePhone log
Quoted
Turf and irrigationQ-2290 · $8,400
Hedge and tidyQ-2294 · $1,150
Won
Paving, front pathJ-1880 · $6,200 · Meta Ads
Lost
Pool surroundPrice, Q-2271

Each card is one enquiry. The source shown is the one captured at first contact.

Zapier · Zap · Web enquiry to HubSpot and JobberLive
  1. Trigger: new form entryWebsite form, with UTM fields
    Trigger
  2. Find contact by email or phoneHubSpot search, create only if none
  3. Find open deal for contactOpen pipeline stages only
  4. PathsExisting deal or new deal
    Path A
    Add note, keep source
    Path B
    Create deal with source
  5. Create Jobber requestDeal id in a custom field
  6. !
    On error: post to #opsZap name, step, record link
    Alert

The same lookup steps are used in all three Zaps.

HubSpot · Report · won revenue by sourceLive
Enquiries640six months
Deals6441.0 per enquiry
Won17126.7%
Won value$612,400with a source

Won value by lead source

Google Ads$214,600
Referral$168,200
Meta Ads$96,400
Phone, no campaign$82,800
Organic search$50,400

Only possible once source survives from first contact to the won deal.

How it is built

Turn the old Zaps off one at a time, each replaced and tested before the next.

Module-level build6 modules
  1. Module AInventory

    The five old Zaps listed with trigger, actions, errors and what each was meant to do.

  2. Module BLookup pattern

    Find contact, then find open deal, then create only if none; written once, reused in every Zap.

  3. Module CSource capture

    UTM fields and a phone log form set source once; updates never overwrite it.

  4. Module DJobber link

    Requests carry the HubSpot deal id; quote and job events write status back to the deal.

  5. Module EMerge backlog

    Duplicate deals from six months merged, keeping the earliest source.

  6. Module FErrors and report

    Errors to Slack with the owner, and a won-by-source report the owner can read.

Field mapping and rules

The lookup and the source rule are what stop the duplicates. Everything else is ordinary mapping.

Field mapping
SourceHubSpotJobberRule
Form email / phoneContact lookup keysClient email / phoneLookup before create
utm_source, utm_campaignOriginal source, campaignNoneWritten once
Service typeDeal name prefixRequest titleFixed list
Deal idRecord idCustom field: HubSpot dealRequired on every request
Quote totalDeal amountQuote totalJobber owns the amount
Job statusDeal stageJob statusStatus map
Status map
JobberHubSpot stage
RequestNew
Quote sentQuoted
Quote approvedWon
Quote archivedLost
Job completeWon, delivered

Worked figures

Walkthrough arithmetic: six months of enquiries, before and after the rebuild and the merge.

Duplicates and sourceWalkthrough figures
Enquiries640six months
Deals before1,1521.8 per enquiry
Deals after merge6441.0 per enquiry
Won deals with a source38% → 96%earliest kept
Quotes linked118 → 0unlinked left
Zap errors unread41 → 0Slack owner

Deals per enquiry

Before1.8
After1.0

QA and testing checklist

Every check runs in a copy or on test records first, and each one is ticked with evidence before go-live.

  • T1Repeat contactA second form from the same email adds a note, not a deal.
  • T2Phone then formA phone log then a form keeps one deal and the phone source.
  • T3Source keptAn update never changes the original source.
  • T4Deal idEvery Jobber request created has the deal id.
  • T5Write-backQuote approved moves the deal to Won.
  • T6ErrorA forced HubSpot error posts to #ops with the step.
  • T7Old Zaps offEach old Zap is off before its replacement goes live.
  • T8MergeMerged deals keep the earliest source and all notes.

Scope

AreaIncluded
ReviewSix months of deals, quotes and Zap history, with findings
ZapsThree Zaps with the lookup pattern, replacing five
Source captureUTM fields and a phone log form
Jobber linkDeal id on requests, status written back
MergeDuplicate deals merged, earliest source kept
Errors and reportSlack alerts and a won-by-source report
Not includedAd account changes, website changes beyond hidden fields, or Zapier plan costs

Milestones, week by week

  1. Week 1

    Review and design

    • Zap inventory
    • Lookup pattern
    • Status map
    25% of the fee
  2. Week 2

    Rebuild

    • Three Zaps on test records
    • Old Zaps off one by one
    30% of the fee
  3. Week 3

    Merge and link

    • Backlog merged
    • Jobber write-back
    30% of the fee
  4. Week 4

    Report and handover

    • Won by source
    • SOP
    • 14 days of fixes
    15% of the fee

Handover and keeping it running

Handover pack

  • Zap map each Zap, its steps and why
  • Lookup pattern note for anyone adding a new form
  • Status map Jobber to HubSpot
  • Recorded walkthrough pipeline, Zaps and report
  • Ownership list Zapier, HubSpot and Jobber connections in the business's name
  • 14 days of fixes for defects in the agreed scope

Keep it running

Duplicates come back when someone adds a new form with its own quick Zap. The note says every new entry point uses the lookup steps, and a weekly count of deals per enquiry shows it early.

  • Weekly: deals per enquiry close to 1.0
  • Weekly: #ops errors cleared
  • Monthly: won by source reviewed before ad budgets
  • Optional support hours at US$35 per hour, agreed in writing

Typical scope for this kind of project: US$400-900

About 4 weeks · fixed milestones. The systems health check (US$150, fixed) comes first and confirms the scope. Extra hourly work is US$35 per hour, agreed before it starts. After handover, a set block of hours each month is available at the same rate, agreed in writing.

Discuss an engagement.

Outline the operational problem through the contact form. I respond with a recommended starting point, including whether the US$150 systems health check is the appropriate first step.

Related work snippets

Next step

Bring me the work that repeats.

I scope it in writing, test it against your current process on your own data and hand over everything I build.

Book a consultation