Original Summary

I do web work for a roofing company in Franklin County, Missouri. Last year I sat in their office for a day and counted: JobNimbus for the CRM and estimates, CompanyCam for photos, QuickBooks Time for the crew clock, Sortly for the trailer inventory, EagleView per roof for measurements. Five logins, five bills, and the office manager typing the same address into three of them. So I built Fieldplate. It's the whole job in one place: lead comes in, you quote it (with a roof sketch tool so you're not paying per address), the homeowner opens a link on their phone and signs, the crew clocks in on the job, takes photos that land on the job automatically, the trailer stock gets consumed against it, you invoice, they pay on the same link. Scheduling, a customer portal, reports, and CSV imports so nobody has to retype their customer list to try it. A few decisions I'd defend: It works with no third-party services connected. Maps are self-hosted, email goes through whatever SMTP you have, the payment processor is optional. I didn't want a product whose monthly cost is a stack of other people's APIs. Phone first for the crew, no app-store app. It's a web app that they add to the home screen. Camera, clock, schedule, that's it. Every record edit is audited and nothing is hard-deleted, because a roofer's dispute with an insurance adjuster is won or lost on who changed what and when. Stack, since people ask: TypeScript end to end, NestJS on Fastify, Postgres with row-level security per tenant, Next.js, BullMQ, Postgres-backed outbox for events, Playwright suite that runs on every push and deploys if green. It's free right now while a handful of local contractors beat on it. If you run a trade business, or you've built for one, I'd like to hear what you'd expect it to do that it doesn't. fieldplate.org   submitted by   /u/Scarfaceb1tch [link]   [comments]

  • 情报分类：工作与职业机会
  • 分类依据：内容涉及招聘、求职或职业发展
  • 信息来源：Reddit · SaaS
  • 发布时间：2026/9/27 22:52:15