Kickserv

Kickserv is field service management software designed for home service businesses like plumbers, electricians, HVAC technicians, cleaners, landscapers, and general contractors. It handles the core workflow of a service business: managing customer contacts, creating estimates, scheduling and dispatching jobs, tracking time and expenses in the field, and generating invoices.

Key features include proximity-based dispatching with map views, real-time job status tracking, GPS monitoring of field workers, expense documentation with receipt uploads, and a mobile app for iOS and Android. It offers three scheduling views (schedule, calendar, and dispatch grid) and 25 pre-built reports across sales, work, and finance categories.

The platform targets small to medium service businesses, typically teams of 2 to 20 people. It positions itself as a simpler, more affordable alternative to heavier platforms like ServiceTitan.

Kickserv offers three main paid plans, all with a 30-day free trial and no long-term contracts. The Start plan runs $60 per month on annual billing ($75 monthly) for up to 5 users and covers the basics including automated reminders, reports, time tracking, and QuickBooks Online integration. The Run plan at $119 per month annual ($149 monthly) supports 10 users and adds dispatch mapping, GPS check-ins, custom fields, and custom reports. The Scale plan at $199 per month annual ($249 monthly) covers 20 users and adds custom templates and review functionality.

QuickBooks Desktop integration costs an extra $50 per month, and additional users beyond plan limits cost $29 each. There's also a "Kickback" discount programme where processing a minimum payment volume through Kickserv's payment system gets you 5% off your subscription. Annual billing saves 20% across all tiers.

For the feature set, pricing is competitive. It's noticeably cheaper than platforms like ServiceTitan, though you get less capability in return.

Lock-in risk with Kickserv is moderate. Your core data (customers, jobs, invoices) can be exported via CSV reports or extracted through the API, so you won't lose your business records if you decide to leave. However, there's no bulk migration tool, and any custom templates, workflows, or configuration you've set up would need to be rebuilt from scratch in a new platform.

The biggest lock-in factor is probably the QuickBooks integration. If you've built your financial workflow around the Kickserv-QuickBooks sync, unpicking that and reconnecting through a different platform takes effort. But the underlying data is still yours and accessible.

Kickserv was founded in 2006 by Todd Eccles, who grew up in a multi-generational plumbing and HVAC family business. The software actually traces back to 1999, when the team built one of the first web-based scheduling and CRM tools for service companies. It originally launched as ServiceSidekick before rebranding to Kickserv in 2011.

The company has changed hands several times. ReachLocal acquired it in 2014, then Gannett took over when they bought ReachLocal. The founders bought it back in 2021, forming a company called Norman's Dojo, Inc. Most recently, EverCommerce (NASDAQ: EVCM) acquired Kickserv for $15 million in August 2023. EverCommerce is a publicly traded SaaS company with roughly $718 million in annual revenue and around 1,750 to 2,300 employees. They own over 30 service business software products.

Kickserv has a respectable 4.4 to 4.5 star rating across major review platforms like Capterra, G2, and Software Advice, with over 700 reviews. The mobile app ratings are considerably lower at 2.8 on Google Play and 3.2 on the Apple App Store.

Kickserv has a REST API with interactive documentation available via Swagger at app.kickserv.com/api-docs. Authentication uses Basic Auth with per-employee API tokens. The API was originally XML-based but has been updated to a v2 version.

The practical experience is fairly limited. There's no published information on rate limits, no webhook support, no sandbox or testing environment, and no official SDKs. There's a community Ruby wrapper on GitHub, but that's about it. Kickserv explicitly states they cannot help with implementation or development of your integrations, so you're on your own.

The API covers core resources like jobs, customers, and invoices, but the lack of webhooks means you'll need to poll for changes, which is inefficient for real-time workflows. For simple read/write operations, the API works, but building anything sophisticated requires patience and custom engineering work.

No webhook support documented. Integrations need to poll the API for changes, which limits real-time use cases.

Getting your data out of Kickserv is possible but not seamless. The platform supports CSV export for custom reports, which covers the basics like jobs, customers, and invoices. The API provides programmatic access to your data, though you'll need development resources to extract it comprehensively.

There's no one-click full data export feature. If you're migrating away, you'd likely need a combination of CSV exports and API calls to get everything. Import capabilities exist for adding items and contacts, but there's no documented bulk migration tool for moving to Kickserv from another platform either.

Vendor lock-in risk is moderate. Your core business data is accessible, but any custom workflows, templates, or configurations would need to be rebuilt in a new system.

The developer experience is on the basic side. The Swagger-based API documentation at app.kickserv.com/api-docs is functional and lets you test calls against your live data, which is helpful. But there's no sandbox environment, so all testing happens against real data.

There are no official SDKs, no Postman collections, and no changelog documenting API updates. Rate limit behaviour is undocumented, which means you won't know the boundaries until you hit them. The one community library (a Ruby gem) hasn't seen recent activity.

Kickserv's explicit statement that they can't assist with integration development means the developer community and self-service documentation are all you've got. For a developer accustomed to well-documented APIs like Stripe or Xero, this will feel bare-bones. For a straightforward integration pulling job or customer data, it's workable.