Jobber

Jobber is field service management software designed for small-to-medium home service businesses. It covers the full job lifecycle: client management, quoting, scheduling and dispatching, job tracking, invoicing, and payment collection. The mobile app lets field workers view their schedules, track time, create invoices on-site, and collect payments.

Core features include online booking, automated follow-ups and reminders, GPS tracking, route optimisation, and client communication tools. Jobber also handles recurring jobs, which is important for businesses like lawn care or cleaning services that rely on repeat work. The platform includes basic reporting and a client hub where customers can approve quotes, pay invoices, and request work online.

The target market is squarely small service businesses, typically with 1 to 50 employees. Industries include landscaping, cleaning, HVAC, plumbing, electrical, pest control, and similar trades.

Jobber uses a tiered subscription model. Individual plans start at around $39/month for the Core tier, which covers basic scheduling and invoicing. Mid-range plans (Connect) run around $119-169/month and add features like automated reminders, online booking, and QuickBooks integration. The top Grow tier runs $199-349/month and includes job costing, GPS tracking, and more advanced reporting.

The pricing jump from individual to team plans is significant. Adding even one employee to an individual plan forces an upgrade to the team tier, which can roughly double your cost. Additional users beyond the plan's included seats cost around $29/user. There is a 14-day free trial, and annual billing offers discounts of up to 40%.

Payment processing through Jobber Payments adds transaction fees on top: 2.9% plus 30 cents for credit cards, and 1% for bank payments.

Vendor lock-in risk with Jobber is moderate. Core client and job data can be exported via CSV, and the API provides access to most data objects for custom extraction. However, not all data types are easily exportable through the standard UI, and things like communication history, attachments, and custom field configurations may require API work to extract.

The bigger lock-in factor is workflow dependency. Once your team is trained on Jobber's scheduling, quoting, and invoicing workflows, switching to a different platform involves significant retraining and process changes. If you have built custom integrations through the API, those would need to be rebuilt for any new platform.

Overall, getting your data out is achievable with some effort, but the operational switching cost is the real lock-in factor.

Jobber was founded in 2011 by Sam Pillar and Forrest Zeisler in Edmonton, Canada. The company has grown steadily over the past 15 years, reaching approximately $167 million in annual revenue by 2024 with over 100,000 customers. They employ roughly 700 to 1,200 people depending on the source, and have raised around $191 million in total funding from investors including General Atlantic, Summit Partners, and OMERS Ventures.

Jobber remains privately held with the founders still in leadership positions. The company's trajectory has been consistently upward, with strong revenue growth and expanding headcount. There are no signs of instability, and the backing of major growth equity firms suggests they are well-positioned for the long term. This is not a startup that might disappear next year.

Jobber provides a GraphQL API through its Developer Centre, which is modern and reasonably capable. It covers the main objects you would want to work with: clients, jobs, quotes, invoices, and scheduling data. Authentication uses OAuth 2.0, and there is a proper app review process if you want to publish to their marketplace.

Rate limits use a points-based system alongside a hard cap of 2,500 requests per 5 minutes per app/account combination. For most small-to-medium integration scenarios, these limits are generous enough that you will not hit them. High-volume data syncing might need some throttling logic, but it is not as restrictive as some competitors.

The API is actively maintained and Jobber provides template projects on GitHub for both React frontends and Rails backends. Custom integrations can be built without going through the full app marketplace process, which is handy for one-off projects.

Jobber supports webhooks with HMAC-SHA256 signature verification. Delivery is at-least-once, meaning duplicates can occur, so your integration needs to handle idempotency. The setup is straightforward through the Developer Centre.

Jobber supports CSV import and export for clients, jobs, and products/services. You can export your client list with contact details, tags, property addresses, and custom fields. Job data can be imported from spreadsheets, and products/services lists can be moved in and out via CSV.

However, the export coverage is not comprehensive. Not everything in your account can be exported in bulk through the UI. For a full data extraction, you would likely need to use the API, which adds complexity and cost. Attachments, notes, and communication history may not come out cleanly through standard export tools.

Overall, you can get your core business data out, but a complete migration away from Jobber would require some effort and potentially custom scripting via the API.

The developer experience is above average for field service management software. Jobber provides a dedicated Developer Centre with documentation, a built-in GraphiQL tool for testing queries against your own account, and template repositories on GitHub for common app architectures.

Documentation quality is decent. The GraphQL schema is self-documenting through the GraphiQL explorer, which helps when the written docs fall short. There is a dedicated testing signup that gives you a separate Jobber account for integration development, so you are not working against production data.

Developer support is available via email at api-support@getjobber.com. Jobber also maintains an open-source design system called Atlantis for building app UIs that match the Jobber look and feel. The main frustration developers report is occasional gaps in the API schema, where certain data visible in the UI is not yet exposed through the API.