Getting Started
User Personas

BuildOS serves four distinct roles within a residential GC firm. Each persona uses the platform differently, accesses different modules, and has different definitions of success.

๐Ÿ‘”
Tom
Owner / General Contractor  ยท  owner role

Tom runs the business. He's accountable for everything โ€” revenue, schedule performance, client relationships, and compliance. He's in meetings most of the day and out on site visits in the afternoon. He needs to understand the health of his entire portfolio at a glance without wading through individual project details.

Pain Points Before BuildOS
  • ๐Ÿ˜ค Spends 4+ hours on the first Monday of every month reconciling budget spreadsheets
  • ๐Ÿ˜ค Finds out about schedule slips when clients call โ€” not from his team
  • ๐Ÿ˜ค Material orders that were "someone else's job" get missed
  • ๐Ÿ˜ค Sales pipeline tracked in a shared spreadsheet that no one keeps current
  • ๐Ÿ˜ค Can't see which projects are on the critical path vs. which have schedule buffer
With BuildOS
  • โœ… 8-minute portfolio financial review โ€” all 10 projects, live
  • โœ… Feed card alerts him to budget overruns and schedule risks before they escalate
  • โœ… Approves procurement decisions with one tap from his phone
  • โœ… Weighted pipeline revenue forecast tells him what's likely to close next quarter
  • โœ… Permit issued โ†’ project automatically initialized, nothing falls through the gap
Primary Modules
๐Ÿ’ผ
Sarah
Office Administrator  ยท  admin role

Sarah is the operational nerve center of the business. She manages the CRM, tracks invoices, coordinates with vendors, monitors procurement deadlines, and keeps Tom and Mike from having to deal with administrative details. She's the power user of BuildOS โ€” she lives in the platform all day.

Pain Points Before BuildOS
  • ๐Ÿ˜ค Tracks vendor invoices in a spreadsheet that's always two weeks behind
  • ๐Ÿ˜ค Manually checks supplier lead times and emails PMs reminders to order
  • ๐Ÿ˜ค Manages permits and estimates in separate folders โ€” no single view
  • ๐Ÿ˜ค Spends significant time chasing sub confirmations by phone
  • ๐Ÿ˜ค No visibility into which feed items need her action vs. which have been handled
With BuildOS
  • โœ… Procurement agent surfaces material deadlines automatically โ€” she just acts
  • โœ… Sub liaison agent handles SMS confirmations; she reviews the results in Feed
  • โœ… All estimates, permits, and pipeline data in one place per prospect
  • โœ… Invoice approvals queued in Feed with full context โ€” no hunting for POs
  • โœ… Advancing a prospect to Permit Issued auto-creates the project โ€” no double-entry
Primary Modules
๐Ÿฆบ
Mike
Superintendent  ยท  superintendent role

Mike manages two to four active construction sites simultaneously. He's on-site by 7 AM, juggling crew assignments, sub schedules, inspection deadlines, and daily surprises. He needs fast answers and zero administrative overhead. His primary interface is the daily morning briefing on his phone, delivered before he arrives at the first site.

Pain Points Before BuildOS
  • ๐Ÿ˜ค Spends 30โ€“45 min each morning reviewing texts, emails, and spreadsheets to plan the day
  • ๐Ÿ˜ค Has to manually chase subs to confirm tomorrow's schedule
  • ๐Ÿ˜ค Doesn't know about weather-sensitive tasks until conditions change
  • ๐Ÿ˜ค Task completions don't reach the office until end-of-week check-ins
  • ๐Ÿ˜ค Can't see which tasks are on the critical path without opening a spreadsheet
With BuildOS
  • โœ… 4-minute morning briefing โ€” AI-generated, delivered to his phone before 7 AM
  • โœ… Sub confirmations tracked automatically; he sees status without calling anyone
  • โœ… Weather alerts call out at-risk exterior tasks before the rain arrives
  • โœ… Push notifications when Carlos marks a task complete โ€” instant visibility
  • โœ… Schedule updates after any delay โ€” he sees the new dates, not the old ones
Primary Modules
โ›
Carlos
Field Worker / Crew Lead  ยท  field_worker role

Carlos works on-site, executing the tasks Mike assigns. He may have limited connectivity during the day and isn't expected to use a desktop app. BuildOS reaches him through the mobile app โ€” simple, fast, and designed to work even when there's no cell service. His interaction with BuildOS is minimal but critically important: accurate field data flows back to the schedule, the superintendent, and the finance team.

Pain Points Before BuildOS
  • ๐Ÿ˜ค Has to text Mike to confirm what tasks are assigned for the day
  • ๐Ÿ˜ค Task completions aren't logged anywhere โ€” there's no record
  • ๐Ÿ˜ค Office doesn't know if he's on-site until Mike manually reports it
  • ๐Ÿ˜ค Communication happens entirely through informal texts โ€” no structure
With BuildOS
  • โœ… Task list pre-loaded on his phone every morning with today's assignments
  • โœ… Marks tasks complete in <45 seconds with photo + progress slider
  • โœ… GPS-tagged check-in replaces the morning phone call
  • โœ… Works fully offline โ€” syncs when connectivity returns, no data lost
  • โœ… App available in English and Spanish
Primary Modules

Role Comparison at a Glance

Capability Tom (Owner) Sarah (Admin) Mike (Superintendent) Carlos (Field)
Create / modify projects โœ“ โœ“ โ€” โ€”
View financial dashboard Full Full Summary only โ€”
Manage pipeline / CRM โœ“ โœ“ โ€” โ€”
Update task progress โœ“ โœ“ โœ“ Via field app only
Recalculate schedule โœ“ โœ“ โœ“ โ€”
Approve invoices / POs โœ“ โœ“ โ€” โ€”
Allocate equipment โœ“ โœ“ โœ“ โ€”
View notification feed All cards All cards Role-targeted cards Push only
Field progress reporting โ€” โ€” โ€” โœ“ (mobile app)

For the full permissions matrix, see Roles & Permissions.