# Jobber vs HouseCall Pro: Research for No More Chores **Date:** March 10, 2026 **Context:** Evaluating replacements for Launch27 for a ~$712K/yr residential cleaning company in Toronto using subcontractors. Key requirement: full API for AI-driven operations (read/update/cancel bookings programmatically). --- ## 1. API Capabilities ### Jobber - **API Type:** GraphQL API (developer.getjobber.com) - **Read bookings/jobs:** ✅ Yes. Full query access to jobs, visits, clients, quotes, invoices - **Create bookings:** ✅ Yes. Mutations for creating jobs, clients, quotes, invoices - **Update/reschedule:** ✅ Yes. Mutations to update job details, reschedule visits - **Cancel:** ✅ Yes. Can update job status (cancel/close) - **Webhooks:** ✅ Yes. App-level webhooks for job events, client events, invoice events. Available via their app marketplace integration - **Authentication:** OAuth 2.0 for third-party apps; API access via Jobber's developer platform - **Documentation quality:** Good. GraphQL schema is self-documenting. Developer portal at developer.getjobber.com with guides, schema explorer, and examples - **Rate limits:** Present but reasonable for normal operations - **Plan requirement:** API access requires **Grow** or **Connect** plan (not available on Core) - **Key advantage:** GraphQL means you can fetch exactly the data you need in one request. Flexible querying. - **⚠️ Note:** Jobber's API is primarily designed for their app marketplace partners. To build a custom integration, you need to create an "app" in their developer portal. This is free but requires registration. ### HouseCall Pro - **API Type:** REST API (docs.housecallpro.com, hosted on Stoplight) - **Read jobs:** ✅ Yes. GET endpoints for jobs, customers, employees, estimates, leads - **Create jobs:** ✅ Yes. POST endpoints to create jobs, customers, leads, estimates - **Update/reschedule:** ✅ Yes. Can update jobs, add attachments, modify schedule - **Cancel:** ✅ Yes. Job status management available - **Webhooks:** ✅ Yes. Events for jobs (created, scheduled, completed, paid), estimates (created, scheduled, completed, won), and customers (created, updated) - **Authentication:** Both API keys (for Pros on MAX/XL plan) AND OAuth 2.0 (for integration partners) - **Documentation quality:** Good. Hosted on Stoplight with interactive API explorer, try-it functionality, and clear endpoint descriptions - **Rate limits:** Yes, with 429 responses including `RateLimit-Reset` header - **Plan requirement:** API access requires **MAX** or **XL** plan - **Key data model:** Uses Employee (field tech or office admin), Company, Customer, Job, Estimate, Lead terminology - **Confirmed from docs:** "With the Housecall Pro API, you can: Create customers or get customer information, Create employees or get employee information, Create jobs or get job information, Create/get/add attachments and links to jobs, Receive events when jobs are created/scheduled/completed/paid" ### API Verdict **Both have solid APIs that solve the Launch27 limitation.** Jobber's GraphQL is more flexible for complex queries. HCP's REST is simpler and more straightforward. Both support full CRUD + webhooks, which is what Leah (AI receptionist) needs. --- ## 2. Subcontractor Support ### Jobber - **Contractor model:** Jobber primarily uses the term "team members" and is designed around an employee model - **Subcontractor support:** ⚠️ Limited native support. You can add team members and control what they see/access, but there's no explicit "subcontractor" classification with 1099 tracking - **Pay tracking:** Has payroll integrations but primarily for W-2/T4 employees. For subcontractors, you'd track payments separately or use their "sub-contractor" workaround (adding them as limited users) - **Dispatch:** ✅ Yes. Assign jobs to specific team members, GPS tracking, route optimization - **1099 support:** ❌ No native 1099 generation. You'd need external accounting for this - **Workaround:** Many cleaning companies use Jobber with subcontractors by adding them as "limited users" and tracking payments through QuickBooks/Xero integration - **⚠️ Canadian context:** Jobber is Canadian (Edmonton, AB), so they understand the Canadian contractor model well even if the UI doesn't explicitly label it ### HouseCall Pro - **Contractor model:** Also primarily employee-focused in terminology ("Employee" is a core entity) - **Subcontractor support:** ⚠️ Similar to Jobber, no explicit "independent contractor" classification. Workers are "Employees" in the system - **Pay tracking:** Has HCP Payments for collecting from customers, but subcontractor pay is separate - **Dispatch:** ✅ Yes. Job dispatching to team members, GPS tracking - **1099 support:** ❌ No native 1099 generation - **Workaround:** Similar to Jobber, add contractors as team members with appropriate permissions ### Subcontractor Verdict **Neither platform natively handles the subcontractor model well.** Both treat workers as "employees" in the system. This is industry-standard for field service software. The workaround (add contractors as limited team members, track payments externally via QuickBooks/Xero) works fine and is what most cleaning companies do. **No meaningful difference here.** --- ## 3. Booking Form / Online Booking ### Jobber - **Embeddable form:** ✅ Yes. Embeddable booking widget for websites - **Customization:** Moderate. Can customize services, add service descriptions, set availability - **Home size/room-based pricing:** ⚠️ Somewhat. You create "services" with pricing. Can create services like "2-bedroom clean", "3-bedroom clean" etc. Custom fields available for additional info - **Online request vs. instant booking:** Supports both request-based (you approve) and instant booking - **Client hub integration:** Booking ties into their client hub for self-service ### HouseCall Pro - **Embeddable form:** ✅ Yes. Online booking page, embeddable on website - **Customization:** Moderate. Similar approach, define services and pricing - **Home size/room-based pricing:** ⚠️ Same as Jobber. Create service tiers. HCP also supports price ranges - **Booking flow:** Professional-looking booking flow that captures customer info and service selection ### Booking Form Verdict **Neither matches Launch27's specialized cleaning-service booking form** (which was purpose-built for home size, number of rooms, extras). Both use a more generic "select a service" approach. You'd create multiple service variants (e.g., "Standard Clean - 1 Bed", "Standard Clean - 2 Bed", etc.) or use their custom form capabilities. **This is the biggest compromise in switching from Launch27 — you lose the specialized calculator-style booking form.** May need a custom front-end that feeds into the API. --- ## 4. Recurring Bookings ### Jobber - **Recurring jobs:** ✅ Yes. Full recurring job support - **Frequencies:** Weekly, every 2 weeks, every 3 weeks, every 4 weeks, monthly, custom intervals - **Management:** Can edit individual occurrences or the entire series - **Via API:** ✅ Can create and manage recurring jobs through GraphQL API - **Scheduling:** Visit scheduling with recurring patterns, drag-and-drop calendar ### HouseCall Pro - **Recurring jobs:** ✅ Yes. Recurring job functionality - **Frequencies:** Weekly, biweekly, monthly, custom - **Management:** Edit single or all future instances - **Via API:** Needs verification — webhooks fire for individual job instances. API creation of recurring series may be limited - **Scheduling:** Calendar view with recurring job visualization ### Recurring Verdict **Both handle recurring cleanings well.** Jobber may have a slight edge with more granular frequency options (every 3 weeks is common for cleaning). Both allow editing individual instances, which is critical for the AI to reschedule individual visits. --- ## 5. Pricing Flexibility ### Jobber - **Service-based pricing:** ✅ Define prices per service type - **Custom pricing:** ✅ Per-job custom pricing, quote-based pricing - **Add-ons:** ✅ Can add line items to jobs - **Discounts:** ✅ Percentage or fixed discounts on jobs/invoices - **Frequency discounts:** ⚠️ Not automated. Would need to set up different service prices or apply manual discounts for recurring customers - **Square footage pricing:** ⚠️ No native calculator. Would create service tiers or use custom fields ### HouseCall Pro - **Service-based pricing:** ✅ Define prices per service - **Custom pricing:** ✅ Per-job pricing, price ranges - **Add-ons:** ✅ Additional line items - **Discounts:** ✅ Available on invoices - **Frequency discounts:** ⚠️ Same limitation as Jobber - **Square footage pricing:** ⚠️ Same — no native calculator ### Pricing Verdict **Both are comparable.** Neither offers the sophisticated home-size-based pricing calculator that Launch27 has built-in. This would need to be handled in a custom booking form or by creating detailed service catalogs. **The AI (Leah) could calculate the right price based on customer data and apply it via the API.** --- ## 6. Customer Portal ### Jobber - **Client Hub:** ✅ Yes. Full-featured customer portal called "Client Hub" - **Self-service:** Customers can view upcoming jobs, approve quotes, pay invoices, request new work, view job history - **Branded:** Can be customized with company branding - **Communication:** Two-way messaging between client and company - **Rescheduling by customer:** ⚠️ Limited — customers can request changes but not directly reschedule in most configurations ### HouseCall Pro - **Customer portal:** ✅ Yes. Customer-facing booking and communication - **Self-service:** View jobs, pay invoices, book new services, leave reviews - **Branded:** Company branding available - **Communication:** In-app messaging, automated notifications - **Rescheduling by customer:** ⚠️ Similar limitations ### Portal Verdict **Jobber's Client Hub is generally considered more full-featured** than HouseCall Pro's customer-facing tools. Both provide the basics. In your case, the AI receptionist (Leah) would likely handle most customer interactions anyway. --- ## 7. Pricing / Plans (as of early 2026) ### Jobber | Plan | Price (USD/mo, annual) | Key Features | |------|----------------------|--------------| | **Core** | ~$49/mo | 1 user, basic scheduling, invoicing, CRM | | **Connect** | ~$129/mo | Up to 5 users, online booking, automated follow-ups, QuickBooks integration | | **Grow** | ~$249/mo | Up to 15 users, job forms, quote follow-ups, GPS tracking, API access | - **API access:** Grow plan required (developer.getjobber.com) - **Additional users:** Extra cost per user on some plans - **Canadian pricing:** May differ slightly (Jobber is Canadian, may price in CAD) - **⚠️ Pricing may have changed — verify on getjobber.com/pricing** ### HouseCall Pro | Plan | Price (USD/mo, annual) | Key Features | |------|----------------------|--------------| | **Basic** | ~$79/mo | 1 user, scheduling, dispatching, invoicing | | **Essentials** | ~$189/mo | 1-5 users, online booking, QuickBooks, reporting | | **MAX** | Custom pricing | Unlimited users, API access, advanced reporting, dedicated support | | **XL** | Custom pricing | Enterprise features, strategic account management | - **API access:** MAX or XL plan required (confirmed from docs) - **MAX pricing:** Not published — requires contacting sales. Typically $300-500+/mo based on user reports - **⚠️ Pricing may have changed — verify on housecallpro.com/pricing** ### Pricing Verdict **Jobber is likely cheaper for API access** (~$249/mo for Grow) vs HouseCall Pro MAX (custom pricing, likely $300-500+/mo). However, for a $712K/yr business, either is reasonable. **Factor in the cost of running the subcontractors as "users" — need to know per-user costs.** --- ## 8. Migration from Launch27 ### Jobber - **Launch27 migration tool:** ❌ No dedicated tool - **Data import:** ✅ CSV import for clients/customers. Job history would need manual or API-based migration - **API-based migration:** ✅ Could write a script to export Launch27 data and import via Jobber's GraphQL API - **Migration support:** Jobber offers onboarding assistance, which may include migration help ### HouseCall Pro - **Launch27 migration tool:** ❌ No dedicated tool - **Data import:** ✅ CSV import for customers. HCP has a data migration team for larger accounts - **API-based migration:** ✅ Could script import via REST API - **Migration support:** MAX/XL plans come with dedicated onboarding, which typically includes migration assistance ### Migration Verdict **Neither has Launch27-specific migration.** Both support CSV import and API-based migration. For a $712K business, either platform would likely assign dedicated onboarding support. **The key data to migrate: customer list, service preferences, recurring schedules, pricing. Job history is nice-to-have but not critical.** A custom migration script using Launch27's export + new platform's API is the most reliable approach. --- ## 9. What It Replaces vs What Stays ### With Jobber **Replaces:** - Launch27 (booking, scheduling, recurring jobs, customer management, invoicing) - Potentially some GHL CRM functions (Jobber has built-in CRM, client communication, automated follow-ups) **Keeps:** - GHL — for marketing automation, email campaigns, landing pages, pipeline management (Jobber's marketing features are basic) - Twilio — for AI receptionist (Leah). Jobber has its own SMS but doesn't replace a custom AI voice agent - Aircall — unless you route calls through Twilio/Leah entirely **Integration points:** - Jobber ↔ GHL: Via Jobber API + GHL webhooks/API. Sync customers, trigger automations on job events - Jobber ↔ Twilio/Leah: Leah reads/writes Jobber via GraphQL API for booking management - Jobber ↔ QuickBooks/Xero: Native integration for accounting ### With HouseCall Pro **Replaces:** - Launch27 (same as above) - More GHL overlap — HCP has stronger built-in marketing (review management, email marketing, follow-ups) - Potentially Aircall — HCP has built-in VoIP phone system (but it's US-focused) **Keeps:** - GHL — for advanced marketing automation (though overlap increases) - Twilio — for Leah (AI receptionist) - May keep Aircall unless HCP's phone system works in Canada **Integration points:** - HCP ↔ GHL: Via HCP API + GHL integration - HCP ↔ Twilio/Leah: Leah uses REST API for booking management - HCP ↔ QuickBooks: Native integration ### Stack Verdict **Jobber is more "focused" — it does scheduling/booking/CRM and lets you keep GHL for marketing.** HouseCall Pro tries to be more all-in-one, which creates more overlap with GHL. For your use case (where GHL handles marketing and Leah handles phone), **Jobber's cleaner separation is probably better.** Less tool overlap = less confusion about where data lives. --- ## 10. Final Verdict ### Recommendation: **Jobber** (with caveats) **Why Jobber wins for No More Chores:** 1. **API Quality:** GraphQL API is more flexible and powerful than HCP's REST API. For an AI-driven operation where Leah needs to query complex data (e.g., "find this customer's next recurring visit and reschedule it"), GraphQL is significantly better 2. **Canadian company:** Jobber is based in Edmonton. Better understanding of Canadian business needs, tax requirements, and likely CAD billing 3. **Cost:** API access at ~$249/mo (Grow) vs HCP's MAX (likely $300-500+/mo custom pricing) 4. **Cleaner stack integration:** Jobber focuses on scheduling/booking/CRM, letting GHL handle marketing cleanly. Less overlap, less confusion 5. **Client Hub:** More mature customer self-service portal 6. **Recurring scheduling:** Strong support for the weekly/biweekly/every-3-weeks model that cleaning companies use 7. **Developer experience:** GraphQL schema explorer + good docs make it easier to build Leah's integration **Where HouseCall Pro would win:** - If you wanted to consolidate more tools (reduce GHL dependency) - If you needed built-in VoIP (though less relevant in Canada) - If you wanted their dedicated data migration team - Their REST API is simpler if your developer is more comfortable with REST **Caveats / Things to verify before deciding:** 1. **⚠️ Verify current pricing** — Both platforms change pricing regularly. Check getjobber.com/pricing and request HCP MAX quote 2. **⚠️ Test the booking form** — Neither will match Launch27's purpose-built cleaning calculator. Assess whether Jobber's online booking meets your needs or if you need a custom front-end 3. **⚠️ API trial** — Sign up for a trial of both and test the specific API operations Leah needs (create booking, read recurring schedule, reschedule visit, cancel visit) 4. **⚠️ Subcontractor workflow** — Test how each handles adding/managing subcontractors as limited team members 5. **⚠️ Per-user pricing** — With 15-30+ subcontractors, user-based pricing could add up. Clarify per-user costs on both platforms 6. **⚠️ Webhooks latency** — Test webhook delivery speed. For real-time AI operations, webhooks need to fire quickly 7. **⚠️ GraphQL mutations for recurring jobs** — Specifically test: can Jobber's API modify individual visits within a recurring series? This is critical for Leah --- ## Quick Reference Links - **Jobber Developer Portal:** https://developer.getjobber.com - **Jobber Pricing:** https://getjobber.com/pricing/ - **Jobber Features:** https://getjobber.com/features/ - **HouseCall Pro API Docs:** https://docs.housecallpro.com - **HouseCall Pro Pricing:** https://www.housecallpro.com/pricing/ - **HouseCall Pro Partner Program:** https://www.housecallpro.com/partner-program/ --- ## Confidence Levels | Item | Confidence | Notes | |------|-----------|-------| | API exists and supports CRUD | ✅ High | Confirmed from both platforms' docs | | Webhook support | ✅ High | Confirmed from HCP docs; Jobber documented | | Pricing figures | ⚠️ Medium | Based on recent knowledge but may have changed | | Subcontractor handling | ✅ High | Well-documented limitation in both platforms | | Booking form limitations | ✅ High | Both use generic service selection, not cleaning-specific | | Jobber GraphQL superiority for AI use | ✅ High | GraphQL's flexibility is objectively better for dynamic queries | | HCP MAX pricing range | ⚠️ Low | Custom pricing, estimated from community reports | | Migration capabilities | ⚠️ Medium | Neither has L27-specific tools; general import confirmed |