Replace Excel with an offline Fillout quoting system

Why Excel quoting breaks for field techs

• Speed: a 700+ line pricing list inside a CRM or spreadsheet takes too long when someone needs a quote in minutes.
• Consistency: different versions of the “same” spreadsheet create pricing drift.
• Offline reality: crawl spaces, basements, and job sites often have no signal.
• Document output: customers don’t want to see your calculator — they want a clean proposal, BOM, and work order.

The target architecture (offline-first)

1) Offline-friendly inspection + quoting UI (Fillout)

• Build the inspection flow with conditional logic (e.g., selecting “full encapsulation” hides “starter” options).
• Use the mobile app workflow so the inspection can be completed offline and synced when back online.
• Capture photos by category (mold, condensation, damage) so they land in the right place later.

2) A quote database that replaces the spreadsheet “master calculator”

• Option A: Zapier Tables — best when you want the database to live inside automation and minimize moving parts. See Zapier Tables.
• Option B: Airtable — best when you need stronger relational modeling, reporting, and heavier browsing. See Airtable.

• Customer/job identifiers
• Quote version/status (Draft → Ready to present → Approved)
• Line items (including long item lists)
• Pricing modifiers (if/then logic)
• Output references (proposal PDF link, BOM PDF link, work order PDF link)

Document generation: proposal, BOM, work order (PDF)

• Keep the PDF template stable (logo/header is enough to start).
• Separate “pricing math” from “customer output.” Customers only see the formatted documents.
• For long item lists, design the template to paginate cleanly (and treat the quote as a data set, not a single text block).

Upload into JobNimbus (and keep it the system of record)

• Store PDFs in the job/customer record.
• Use JobNimbus for execution: scheduling, invoicing, payment links, signatures, and job status.
• Keep the inspection + quoting experience outside the CRM so techs aren’t stuck scrolling a pricing catalog.

Prefilled customer links (so techs don’t search)

• Add a “Start inspection” link in JobNimbus that passes a stable JobNimbus ID into the form.
• When the form syncs, the automation uses that ID to attach documents to the right record.

Phased rollout plan (reduce risk)

1. Phase 1: Replace the spreadsheet
• Build the Fillout form, database, and one PDF (proposal).
• Upload PDFs to JobNimbus.
2. Phase 1.5: Add BOM + work order
• Extend the same data model to additional document templates.
3. Phase 2: Upgrade the sales experience
• Add an iPad-friendly presentation/portal layer on top of the same database foundation.

Common pitfalls (and how to avoid them)

• Trying to rebuild a spreadsheet inside the CRM: you’ll end up with the same scrolling problem.
• No single source of truth for pricing: put modifiers and line items in the database, not in multiple copies of a sheet.
• Offline as an afterthought: design the field flow first, then the back-office workflow.
• Over-optimizing the template too early: start with “good enough” PDFs; iterate once the flow works.

Build this with Connex