Field service management SaaS
Steward
How a full field service platform — jobs, scheduling, dispatch, quotes, client CRM, a customer portal, and AI invoice chasing — was designed and shipped as a single product.
- Multi-module SaaS
- Client portal
- Claude AI
- Stripe
- Postgres + RLS
What was in the way
- Trades teams juggling jobs across a whiteboard, a phone, and a spreadsheet
- Quotes and invoices living in separate documents with no link back to the job
- Overdue invoices chased manually, or not at all
- Existing platforms priced and structured for far larger operations
What got built
Job records with scheduling, dispatch, and status tracking across the whole lifecycle
Quotes that convert to jobs and then to invoices without retyping anything
A client CRM with contact history and property-level job records
A customer portal where clients follow job status and approve quotes without an account
AI-drafted chase emails for overdue invoices, held for approval before anything sends
Stripe billing, role-based access, and row-level security on every table
Timeline
Built in stages over several build cycles, with each module live before the next started.
Where it stands
Steward runs as a live product with its own marketing page, signup, and billing. Its AI chase workflow never sends without a human approving the draft.
Other builds
Have a workflow like this?
Tell me what your team does by hand today and I'll come back with scope, timeline, and a fixed price.