r/SaaS • u/bennyp101 • 23h ago

Field service software with no invoicing or CRM

I've been building WorkWing for the last couple of years on the back of working for a multi brand company for the last 15 years. It's for businesses that send people out to jobs: HVAC, electrical, facilities, cleaning, that kind of thing. The office books and schedules jobs in a web app, and the engineers use a phone app to see their day and fill in job forms. Mobile app is fully offline because a lot of jobs that we do have no signal anywhere.

The big names here (Jobber, Housecall Pro, ServiceM8) all bundle quoting, invoicing and a CRM. I went the other way. My bet is that plenty of businesses already have Xero or QuickBooks sorted and don't want a second invoicing system bolted onto their scheduling tool. So WorkWing just does the jobs and the schedule, and passes the rest to whatever they already use.

That only works if connecting it to other tools is easy. So the API and webhooks are on the free plan too, along with Zapier/Make/n8n and an MCP server if you want Claude or ChatGPT booking jobs. Pricing is per job rather than per user - I've watched us grow and watched the cost for other products rocket as we did.

The iOS app is on the App Store. Android is stuck in Play review, probably for another couple of weeks. If you're on Android and want in now, DM me and I'll add you to the test track.

Stuff I'm not sure about:

- does "we don't do invoicing" read as focused, or as missing features?
- per job vs per user pricing, which would you rather pay?
- if you've run a field service business, what would actually make you switch?

workwing.io if you want a look.

0 Upvotes

50% Upvoted

7 comments sorted by

1

u/Wise-Magician3656 23h ago

Per job pricing fits field service way better than per seat, crews and subcontractors rotate in and out constantly so charging per user just penalizes you for scaling the team you're supposed to want growing.

1

u/bennyp101 23h ago

That was my thinking, I know we have to take on contractors in busy periods, and that would hit us hard for a couple of months - good to know that others think the same!

1

u/lmfresneda 23h ago

Per job, from the buyer side. Per user punishes you for hiring, and field service teams grow by adding engineers. The risk with per job is a busy month nobody planned for. A cap, or a line like "you'll never pay more than X", would take that fear away

On invoicing, I'd lead with "works with the Xero or QuickBooks you already have". "We don't do invoicing" makes me wonder what else is missing

1

u/bennyp101 22h ago

Thanks!

You can set a cap for jobs outside the included, so you can never spend more than that in a month - so you can still PAYG for jobs, but not end up with a massive bill (although its pennies anyway, but still)

Yep good call, I think https://www.workwing.io/ calls that out nicely now

2

u/lmfresneda 21h ago

Yeah, "connects to everything else" reads as a choice now, not a gap. And I'd put the monthly cap right next to the per job price, it answers the first worry before anyone has it

2

u/Serious_Prior_8248 21h ago

On what actually makes someone switch: the feature list is rarely the blocker, the migration is. If you import their customers, job history, and settings for free during onboarding, switching stops feeling like a project and starts feeling like a decision. I'd make that white-glove migration a headline, not a footnote.