Verticals · Construction & field services
Bids, crews, sites — the job from estimate to sign-off.
Bids run as deal pipelines with real amounts and terms, projects nest their site work, and every crew member and site contact lives in one directory with the jobs they touch.
Why one system
Bids in a spreadsheet, jobs in a project app, crews on a whiteboard, punch lists on paper — the job site outruns the office every week.
One system where the bid, the project, the site, and the crew stay in step.
The objects you’d define
bids
deal · attachments · activity
Owner on one side, contractor on the other, an estimate that becomes a contract amount.
projects
hierarchy · workflow · locations
The job itself: phases nest under projects, and gates hold the milestones honest.
site visits
tasks · locations · notes
Scheduled and geocoded — the crew knows where, when, and what was found.
subcontractors
contacts · phone · attachments
One directory of crews and trades, with the paperwork attached to the relationship.
- Invited
- Estimated
- Submitted
- Awarded
A bids pipeline — owner ↔ contractor — same deal primitive, your labels.
How it runs.
The bid is a deal: invited, estimated, submitted, awarded — with the offer amount and the final contract value tracked as first-class fields, not cells in a spreadsheet.
Awarded bids become projects, and the project nests its phases, site visits, and punch lists in one structure. The address is a real location, so the day’s route is a question the system can answer.
Change orders? Two parties, an amount, an approval gate. The shape was already there.
Nomi flags bids sitting in Estimated, schedules the follow-up visit, and answers “what’s open on the Fairview site?” from the project graph.
Nothing here is an industry edition — it’s the same primitives, named by the people who run the business.