Intent boundary: This guide tests Jobber operating fit on the plan and configuration a buyer intends to purchase. It does not repeat the buying verdict, replace the broader one-week pilot, or assume that a successful happy path proves accounting, recovery, or scale.
one synthetic request becomes a completed, paid, explainable job without hidden workarounds
The process succeeds only when the team can explain the result, recover from exceptions, and retain evidence.
The control sequence
Freeze the account boundary
Record the trial or paid plan, included users, add-ons, country, currency, taxes, payment configuration, devices, permissions, and any vendor assistance. A Grow trial cannot prove that a lower paid plan will support the same workflow.
Capture a realistic request
Use synthetic customer data to submit one urgent request with a property, preferred time, photo, access note, and service detail. Verify what survives when the request becomes a quote or job and who owns the next action.
Quote the work and expose a change
Build a quote with labor, material, tax, discount, optional work, deposit, and expiry language where the intended plan permits it. Ask for a customer change, revise the quote, approve it, and confirm that status and financial terms remain traceable.
Schedule under pressure
Convert the approved work, assign the intended field role, then insert an urgent job, move the original visit, and notify the synthetic customer. Measure office effort and confirm what the field user sees after reassignment.
Complete the mobile record
On the actual iOS or Android device, open the visit, start time, add a note and photo, complete the checklist or job form available on the intended plan, capture authorization where appropriate, and close the visit. Record every action that fails under weak connectivity.
Invoice and correct
Create the invoice from completed work, verify the line items and tax, record only a safe synthetic or manual payment, then test one correction. Do not use a real customer or real card merely to complete editorial testing.
Test the accounting boundary
If QuickBooks Online is in scope, use a controlled company and trace customer, item, invoice, payment, edit, refund, and duplicate behavior. Reconcile object counts and totals instead of accepting a successful connection message as proof.
Exit with evidence
Export the records the business would need after cancellation, inspect fields and identifiers, locate attachments and activity history, and document what requires support. End by pricing the same configuration for the expected month 12 team.
Pass conditions for the Jobber decision
| Control | Pass evidence | Investigate | Reject signal |
|---|---|---|---|
| Request to job | Source details and ownership remain visible | Manual re-entry is exceptional and controlled | Routine lead context disappears |
| Quote to schedule | Approval, change, deposit, and job conversion are traceable | One required option sits on a higher plan | The intended sales process needs a shadow tool |
| Office to field | Reassignment and schedule changes reach the intended role | One notification needs a documented manual control | Field users work from stale or incomplete instructions |
| Invoice to accounting | Counts and totals reconcile after an edit | A correction needs a named finance procedure | Duplicates or unexplained balances cannot be recovered |
| Data exit | Core records can be exported and reconciled | Attachments or history need vendor assistance | Required operational or financial evidence cannot be retrieved |
Failure modes to expose
- Testing all features in the Grow trial and then buying Core or Connect without repeating the required controls
- Using only a clean quote and never requesting a change, reschedule, correction, or refund
- Treating mobile app availability as proof that every field action works on both intended devices
- Connecting QuickBooks Online without control totals, a duplicate test, and a correction owner
- Using temporary promotional pricing as the steady-state month 12 cost
- Publishing a numerical winner while material controls remain blocked or conditional
Worksheet questions
- 01
Which exact Jobber plan and add-ons will the business purchase after the trial?
- 02
Which request fields must survive into the quote, job, invoice, and customer history?
- 03
How long should an urgent reschedule take from office decision to field confirmation?
- 04
Which mobile actions must work under weak connectivity on the actual field devices?
- 05
Who owns invoice corrections, failed payments, refunds, and QuickBooks exceptions?
- 06
Which exports, attachments, notes, and activity records are required at exit?
- 07
What is the normal, non-promotional cost for the expected team in month 12?
- 08
Which failure would remove Jobber from the shortlist immediately?