Custom Operations Platform
One system for a field-service company that was running on spreadsheets, inboxes and disconnected apps.
- Status
- In production
- Role
- Design · engineering · deploy · support
The first system we built was for a veteran-owned cleaning and facilities contractor our founder runs. Leads, quotes, jobs, crews, invoicing, government bids and social posting lived across spreadsheets, inboxes and disconnected apps. We built one platform — from lead intake to paid invoice — that the business runs on every day.
Every part of the operation lived somewhere different. Leads arrived by email and phone and were re-typed into a spreadsheet. Quotes were Word documents. Jobs were on a shared calendar with no link back to the customer. Invoices were generated by hand and chased by hand. Government bid opportunities were tracked in bookmarks. Nothing talked to anything.
- Leads copied from inbox → spreadsheet by hand
- Quotes as Word docs, invoices in a separate tool
- Job schedule on a calendar with no customer link
- SAM.gov opportunities tracked in browser bookmarks
- 1099 / subcontractor records reconciled at year end
- Social posts written manually when there was time
- Leads land in one pipeline, are scored, and get an AI-drafted first reply
- Quote → job → invoice → Stripe payment in a single flow
- Crew scheduling with route-aware assignment and a client portal
- SAM.gov opportunities pulled automatically into a bid tracker
- Subcontractor and 1099 tracking that stays current all year
- AI-drafted, scheduled social posts on the company's channels
- 1InterfaceServer-rendered web app + secure client portal (invoices, messages)
- 2ServicesLeads · Clients · Quotes · Jobs · Invoices · Employees · Schedule · Bids · Social
- 3IntegrationsStripe payments · Gmail · Google Maps geocoding · SAM.gov · Meta Graph API
- 4AILead scoring, first-reply drafting, post generation — behind guardrails, reviewed before send
- 5Data & infraSQLite (WAL) → nightly backups; Linux VPS, nginx, systemd; owned by the client
- 01Inbound lead → score → draft reply → owner approves → sent
- 02Job marked complete → invoice created → payment link emailed
- 03Daily SAM.gov pull → matched opportunities → bid pipeline
- 04Weekly content plan → AI drafts → scheduled → published
- Python
- FastAPI
- SQLite
- Stripe
- OpenAI API
- Google Maps
- SAM.gov
- Meta API
- nginx
- systemd
The company stopped operating out of its inbox. Intake, quoting, scheduling, billing and bidding now happen in one place, with a single record per customer — and the owner can see the state of the business from one screen.
- Modules in production
- 8
- leads · clients · quotes & invoices · jobs · scheduling · bids · social · portal
- Integrations
- 5
- Stripe · Gmail · Maps · SAM.gov · Meta
- Admin time saved / week
- —
- measured with client
- Invoice-to-payment time
- —
- measured with client
