Quote Goat Platform
2027 Program Proposal

1. Estimating: Go/No-Go Decision Support + Bid Pipeline

Before estimating hours are spent on an opportunity, management gets a scored recommendation with the history to back it up.

• Configurable go/no-go scoring (customer history, project type, region, margin potential, bonding) with a recommendation and override-with-reason
• Per-OpCo scoring models: each OpCo maintains its own criteria and weights, or shares the enterprise model
• A decision log: every go and no-go recorded with reason codes, sliceable by customer, region, type, and OpCo
• A decision-point panel: win rate on similar bids, bid margin on won and lost bids, and actual margin on won jobs once live cost data flows (feature 4)
• Bid pipeline hardened to production: win/loss analytics, saved views, multi-OpCo filters, export

Not in the price, added only by change order: A formal approval workflow on the go/no-go decision; the expected-value-of-bidding indicator; the estimating capacity check; similar-bid lookup. Loading historical bid data is priced separately, case by case.

2. Change Orders

Change orders priced the same way the job was bid: From the same cost structure and resource library, not a side spreadsheet.

• Create a CO from the project cost breakdown using bid-time rates and markups
• Per-OpCo markup rule sets, with an admin UI to manage them
• Full lifecycle: Draft, priced, submitted, approved, rejected, with the audit trail, plus a schedule impact entered on the CO (days and notes)
• Approved COs roll into revised contract value and budget automatically; original vs. revised always visible
• Per-project CO register with print-quality owner packages on each OpCo's letterhead; on approval, Quote Goat exposes the revised values through its documented API for Kelso's MuleSoft integration to carry into NetSuite (the feature 5 model)

Not in the price, added only by change order: E-signature routing; field T&M tickets converting to COs; approved COs adjusting the feature 9 schedule automatically.

3. Production Units Capture (Desktop)

Production quantities recorded against the project cost breakdown from the desktop. This is the deliberate first step: It is the structure the mobile app later feeds, and it replaces the 2026 interim where production lands in NetSuite statistical accounts.

• Cost breakdown lines flagged as production-tracked, with unit of measure and budgeted quantity (pounds, linear feet, weld inches, and the rest)
• Fast grid entry of installed quantities by period, with validation, edit history, and locked periods; crew/foreman attribution and photo attachment on every entry
• Percent complete by line from installed vs. budgeted quantity, with the production rate needed to finish
• Production dashboard: Installed vs. budget, trend, and lines at risk

Not in the price, added only by change order: Quantities pushing back to NetSuite during transition. Loading history from the 2026 interim is priced separately, case by case.

4. Live Cost: Budget vs. Actuals

NetSuite cost transactions flow into Quote Goat continuously, so the platform shows live budget vs. actuals on the same structure the job was bid and produced against. Actuals also feed estimating intelligence (feature 1).

• A receiving interface built for reality: Safe against duplicates and out-of-order events, with a queue and replay for anything that fails, and a monitoring view
• A transaction layer inside Quote Goat: Records mirroring what NetSuite sends, with the transaction type (vendor bill, credit card, journal, expense report, check), the vendor or employee behind it, date, amount, and source reference, so reporting can slice by vendor, type, or cost code
• Transactions land against the project and cost breakdown automatically where the coding allows; anything that cannot be placed queues in a review workbench for a human decision instead of disappearing
• Built for Kelso scale: Hundreds of budget lines and tens of thousands of transactions per large job, with screens that stay fast
• Project cost screen: Budget, actual, remaining by cost code and line, drill-down to transaction detail, export

Not in the price, added only by change order: Divergent cost-coding conventions per OpCo; a near-real-time service level instead of hourly. Purchase orders and committed cost are explicitly out of scope for this feature and this program.

5. NetSuite Sync: Integration Support

Kelso builds and operates the integration on MuleSoft, the same platform used for your other integrations. Quote Goat makes that easy and inexpensive, the way a mature platform enables a connector:

• Complete interface documentation: schemas, authentication, error handling, sandbox guide
• Field-mapping workshops with your integration team
• Sandbox environment and question turnaround within the included support hours
• Joint validation of the first sync before production cutover

Boundary: support covers enablement of the integration as designed in the workshops. Work inside Kelso's MuleSoft flows or NetSuite configuration is Kelso's, or billable beyond the included hours.

6. RFIs, Submittals & Daily Reports

These workflows run today on NetSuite in your sandbox and move to NetSuite production as the 2026 interim. This feature rebuilds them as their permanent home on the platform. Nothing learned is thrown away, and your teams arrive already trained on the workflows. The functional spec is the NetSuite interim as documented in a joint baseline dated at signing; changes made to the interim after that baseline are scoped as additions.

• RFIs: Create, assign, route, respond, ball-in-court, aging, log, attachments
• Email-in / email-out RFI workflow: RFIs go out by email and replies are captured back onto the RFI thread with their attachments
• Submittals: Register, revision cycles, review statuses, lead-time visibility
• Daily reports: Crew, weather, work performed, delays, photos and notes, searchable history
• Core services built once here, then applied to every feature as it emerges: the attachment service, a core email service, and a core notification service with a consolidated notification center (one feed with read/unread state and per-user preferences), plus print/PDF output

Not in the price, added only by change order: Outside parties (architects, engineers) responding inside the platform; their replies by email are captured by the email-in workflow. Records in flight on the NetSuite interim finish there; migration is out of scope. Mobile push notifications ship with the feature 7 app.

7. Mobile Field App

Foremen and superintendents working from their phones: units complete against the cost breakdown, photos from the field, and daily reports filed the day they happen. Mobile lands after features 3 and 6 on purpose, so field data has live structures to land in.

• On the Apple App Store and Google Play from day one, from one codebase inside a native shell; public listing or private (Apple Business Manager) distribution is your IT's call, and either way the app is manageable through your device-management (MDM) tooling
• Push notifications on iPhone and Android, wired to the feature 6 notification center
• English and Spanish field surfaces from day one
• Units-complete entry with budget context, designed with 2-3 of your field users, piloted mid-build with real foremen through TestFlight and Play test tracks
• Native camera capture with compression and background upload, with a best-practice photo policy included: Compressed capture, full-quality cloud originals, retained for the life of the project with closeout export
• Thumb-friendly daily report flow; tolerant of weak connections (queued submits, saved drafts)

Not in the price, added only by change order: RFI/submittal view-only screens on mobile; kiosk login for shared crew tablets. This feature tolerates short signal drops; the full zero-signal workday is feature 8, next.

8. True Offline Field Capture

A full workday with zero signal. Plants, mechanical rooms, basements, and remote sites are exactly where your crews work and exactly where phones lose coverage. A foreman opens the app in the morning, works all day with no bars, and entries captured offline are queued durably and synchronized when connectivity returns; conflicts are surfaced for review rather than silently resolved.

Why this is its own feature and not a toggle: The base mobile app queues a submit and retries through short drops. True offline means the phone becomes its own small system of record for the day, and that is an architecture change:

• The data lives on the phone. Projects, cost lines, budget quantities, and form templates are stored on the device and refreshed whenever there is signal, so the app never needs to ask the server anything mid-shift
• A real sync engine. A day of entries and photos survives the app being killed, the phone rebooting, or the battery dying, then resumes mid-sync with server-side deduplication and resumable upload when coverage returns for ninety seconds in the yard
• Conflict resolution. Two foremen offline against the same cost line cannot silently overwrite each other. Quantities merge; true collisions go to a review queue a human settles
• Photos at job-site volume. Gigabytes of offline photos get compressed, capped, and uploaded in the background without filling the phone or draining the battery
• Security and trust. Logins survive the offline day with the device data encrypted, and every entry keeps its true capture time in the same audit trail as online work

Not in the price, added only by change order: Support for shared crew tablets; multi-day offline stretches at remote sites; offline RFI/submittal authoring.

9. Scheduling

Scheduling on the same structure the job was bid and produced against, arriving last by design, after cost and production data are live so the schedule reflects reality.

• Interactive Gantt on the cost breakdown: Drag to move, dependencies, critical path, print
• Master schedule per project, weekly short-interval plans, three-week look-ahead with constraint flags
• One import format, selected at design time (MS Project XML unless agreed otherwise); each additional format is a priced option. Baseline vs. current always visible
• Where activities map to production-tracked lines, percent complete flows onto the schedule automatically

Deliberately not included: resource-loaded scheduling and crew leveling (kept "just enough" by design). Not in the price, added only by change order: Two-way sync with P6 or MS Project; portfolio views across all jobs.

10. Checklists, Issues, Photo Log & Your Field Forms

The quality loop plus the forms your field actually runs on. Your five forms (daily safety sign-off, T&M documentation, equipment inspection, near-miss, daily production sign-off) ship built for you, best-practice, on a lean runtime with signature and photo capture; new forms arrive as small change orders, and a self-serve builder where your admins design their own templates is pre-scoped for whenever you want it. Roles, permissions, and the enterprise admin console are core product, part of our platform investment, never a line item.

• Your five field forms, built for you: Fill on desktop or phone, submission logs with counts and export, PDF per submission
• Checklist templates with pass/fail/N/A, notes, and photo evidence per item; runs assigned to areas or cost lines with completion tracking; failed items spawn issues automatically
• Issues/punch list: create from anywhere, assign with due dates, ball-in-court, per-project log with aging and a close-out report for turnover
• Photo log: one project-wide gallery aggregating photos from daily reports, production entries, issues, and checklists, filterable and linked back to their records

Not in the price, added only by change order: the self-serve forms builder (pre-scoped, ~$60,000); commissioning-grade certification chains; owner-facing punch access; SLA escalation rules. The forms capture safety forms; a dedicated safety management module is a third-party product and outside this program.

11. Document Management, Three Tiers

Project documents living on the platform: specs, contracts, and drawings in permissioned folders, with drawings on a foreman's phone instead of a walk back to the trailer. In the program with all three tiers; each tier prices only its additional work and delivers early on purpose: files land alongside feature 6 (RFIs and submittals attach to documents) and the drawing viewer lands before the mobile app it rides in.

• Tier 1 - Files, versioning & permissions: 400 hrs, $60,000. Templated project folders, upload and preview, version history with an unambiguous current copy, role-based access including per-folder mobile visibility, search. Specs, contracts, and subcontracts store here.
• Tier 2 - Drawing management: +275 hrs, $41,250. Drawings as first-class objects: sheet numbers, disciplines, revision control, current-set vs superseded, and a field-friendly viewer inside the mobile app.
• Tier 3 - Markups & transmittals: +250 hrs, $37,500. PDF markup layers per user, formal transmittal packages with cover sheets and send logs.

Not in the price, added only by change order: Migrating existing files from SharePoint or network drives (priced separately, case by case); OCR of sheet numbers; a portal for transmittal recipients; RFIs pinned at their location on drawings (view-only overlay); offline drawing sets on the phone (priced with feature 8).