Boreal BuildOS

What this project proves

• End-to-end contractor workflow from opportunity and estimate through proposal, governed award, Job execution, billing, closeout, warranty, and service
• Field workforce operations covering rosters and calendars, Job and crew assignments, timekeeping, Employee Self-Service, and SMS/reminder workflows
• Procurement and custody controls spanning RFQs, quotations, Purchase Orders, receipts, consumables, equipment, inventory transactions, and employee-issued inventory
• Project controls joining budgets, commitments, actual costs, labour costing, forecasts, changes, billing, receivables, and accounting exchange
• Canadian payroll foundation covering employment, compensation, payroll runs, statutory calculations, remittances, ROE, year-end, and employee self-service
• Governed platform controls including tenant administration, members and invitations, personas, append-only audit history, and Restricted/Suspended tenant enforcement

The problem

Contractors and specialty subcontractors often run estimating, scheduling, field labour, purchasing, inventory, job cost, payroll, billing, closeout, and service through disconnected spreadsheets, accounting tools, messaging, email, and paper.

The result is duplicated entry, weak handoffs between office and field teams, late or incomplete labour and cost information, missed commercial changes, unclear custody of materials and equipment, and limited visibility into whether a Job is actually ready to bill, close, or hand over.

My approach

Model one governed operating lifecycle from CRM and estimate through customer-safe proposal, award confirmation, immutable awarded estimate basis, Job creation, crew execution, cost control, billing, payroll, closeout, and post-handover service.

Give office, field, employee, customer, and Vendor users purpose-built surfaces while preserving tenant isolation, exact permissions, approval separation, audit history, and confidential commercial boundaries.

Treat operational history as durable evidence: issued records, approved baselines, inventory movements, payroll results, audit events, and closeout decisions are corrected through governed replacement, reversal, or supersession rather than silent destructive edits.

Support Canadian contractors through a common core with Project, Service, and Maintenance operating profiles, package entitlements, trade packs, reporting, integrations, and bounded advisory automation rather than separate products for each trade.

Architecture and engineering choices

• Next.js and TypeScript application surfaces with product-owned backend services
• PostgreSQL and Supabase with tenant-safe keys, default-deny Row Level Security, managed authentication, and private object storage
• Modular bounded contexts with authoritative write ownership across estimating, proposal and award, Jobs, workforce, procurement, project controls, billing, payroll, portals, closeout, and service
• Transactional outbox, durable background jobs, idempotent operations, bounded retry, reconciliation, and operator-visible failure handling
• Exact permission and entitlement evaluation with Tenant Admin, support-access, Restricted/Suspended tenant, and high-risk approval controls
• Append-only audit history, immutable commercial and operational snapshots, correlation IDs, and history-preserving reversal/supersession patterns

Truthful scope and boundaries

• Boreal BuildOS is a separate product, repository, database, and runtime from Turnover Ledger.
• AI and automation are bounded and advisory; they do not autonomously approve estimates, awards, changes, invoices, payroll, payments, safety decisions, or closeout publication.
• The platform integrates with accounting and payroll ecosystems without representing itself as the customer's general ledger, bank, or unrestricted external system of record.
• The commercial source repository and customer data remain private; public portfolio material describes product capabilities without exposing tenant data or proprietary implementation details.