Original Summary

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.   submitted by   /u/bennyp101 [link]   [comments]

  • 情报分类：工作与职业机会
  • 分类依据：内容涉及招聘、求职或职业发展
  • 信息来源：Reddit · SaaS
  • 发布时间：2026/10/2 19:13:58