Clearer decisions.
Connect people, projects, field activity, and financial performance while work is underway.
OPERATING EXPERIENCE · CONNECTED SOFTWARE
IAC works alongside your team to improve daily operations. We’re building OVERLYN to connect trade contractors and field operations around the way you work.
Who it’s for
Built around the way your operation works. For trade contractors and field service businesses that need their people, projects, equipment, and business information connected—from the field to the office.
Lead it with confidence.
OVERLYN is being built to connect your whole operation—from winning work and delivering projects to understanding business performance.
Our starting point is crew dispatch and field time, connected through one shared Core.
Choose a stage to explore its screens and short previews.
People & operating environment
Clear handoffs keep work moving between the yard, the field, the project team, and the office. OVERLYN is being built to connect that work across trade contractors and field operations.
Start with the modules you need. Connect through one Core. Shape the system around how your business works.
The required shared foundation for people, customers, sites, jobs, permissions, and history.
Connected Through Core & Your Business Logic: Workflows, roles, approvals, and cost structures are shaped through standard settings, supported configuration, and extensions scoped with IAC.
HL-204 Harbor Lane Access Retrofit
Plan connections around the systems you keep.
The platform vision connects one shared record across all 10 stages, from first inquiry to closeout, so customer, site, and job fundamentals can carry forward without re-entry.
Your Business Logic
3 Configuration TiersConfigured around your operation: Standard settings handle everyday structure; supported configuration adapts workflow stages, approval rules, and cost structures; deeper extensions are scoped with IAC.
Cross-Platform Responsibility
Built Into CoreShared foundation governance: Platform reliability, security, permissions governance, and operational hardening are built across the shared foundation rather than sold as a separate app.
Initial Entry Point · Prototype
Dispatch: Daily crew and truck whiteboard scheduling, look-ahead planning, qualification checks, and published schedule revisions.
Time & Approvals (Workforce & Time Approvals Prototype Workflow): Foreman mobile crew plan and actual-hour confirmation, digital sign-off, superintendent day validation, and draft CSV payroll entry preparation.
Planned Module
CRM & Inquiries: Customer context, site history, opportunities, and commercial intake into operations.
Project Management: Awarded scope, job phases, change tracking, documents, and closeout visibility.
Purchasing & Equipment: Vendor purchase orders, subcontractors, owned equipment, fleet vehicles, specialized assets, and rentals.
Safety & Documents: Worker certifications, site credentials, and controlled project documentation.
Automation & Insights & BI: Configurable cross-department workflow actions, exception alerts, and executive decision support.
Planned Module · Planned Concept
Job Costing & SOV & Billing: Planned-versus-actual labor and cost visibility, change impacts, and reviewed Schedule of Values progress-billing preparation.
Planned For Later
Estimating & Inventory: Scope takeoffs and labor assumptions informed by historical actual hours, plus yard, warehouse, and jobsite material availability.
Planned schedule hours and Reported worked hours stay distinct: a schedule never auto-fills a timesheet, and reported hours require supervisor validation before payroll preparation.
Field teams confirm actual hours in OVERLYN Time and superintendents validate against Dispatch context before payroll preparation.
Intended path would map approved external clock-ins into OVERLYN Time for supervisor exception review against scheduled jobs before payroll export.
Time capture and sign-off would remain in your existing payroll or ERP tool with an agreed approved-hours handoff into OVERLYN Core.
Schedule Vs. Timesheet Boundary
Core Data IntegrityExplicit supervisor sign-off required: Dispatch publishes the daily crew plan, Foremen confirm or adjust actual worked hours on mobile, and Superintendents validate the day before any time card queues for payroll.
Distinct Downstream Operational Handoffs · 01
Prototype WorkflowTo Payroll Preparation (Prototype Workflow): Approved time packet ready for payroll export and draft CSV entry across validated crew cards, keeping foreman edits locked after superintendent validation.
Downstream Operational Handoff · 02
Prototype + Planned ConceptTo Job Baseline & Costing (Prototype + Planned Concept): The Job View prototype structures job phases, planned labor, and remaining hours; planned capabilities would connect validated field hours to cost and margin tracking.
Downstream Operational Handoff · 03
Planned ConceptTo Accounting Or ERP Workflow (Planned Concept): Reviewed SOV progress-billing and T&M change documentation route separately to accounting so payroll and project billing stay distinct.
Downstream Operational Handoff · 04
Planned For LaterTo Estimating (Planned For Later): Actual hours for future estimating remain linked to the completed job scope so future bids draw on validated field history rather than unverified assumptions.
Why IAC exists & how we work
We combine operating experience and connected software to help owners, leaders, and teams spend less time holding daily operations together—and more time improving the business.
Connect people, projects, field activity, and financial performance while work is underway.
Protect labor, equipment, and scope margin through clearer handoffs and better operating decisions.
Build repeatable workflows that support resilience, growth, and leadership or ownership transitions.
Working with IAC
Our experience spans field operations, coordination, project management, finance, and leadership. We work with your team to define business logic, configure systems, and support daily adoption.
Trace the handoffs and find where time, information, or accountability gets lost.
Define workflow stages, responsibilities, approval rules, and job structures.
Implement the agreed improvements, with OVERLYN capabilities, extensions, and system connections scoped to their readiness.
Support adoption, review results, and improve the way the operation runs.
The build journal
We are building IAC to turn operational knowledge into systems people can understand, use and improve—and to help those people grow with the business.
A status label is only a start. A useful operational record also makes ownership, missing inputs and the evidence of completion visible.
Why OVERLYN starts with Dispatch and Time & Approvals on one shared Core—and grows toward a connected business.
Start a conversation
Tell us where work gets harder to coordinate, where information gets lost, or what you want the business to become. We can explore operational improvements, OVERLYN, or connections around the systems you keep.
Opens your email application so you can review and send directly.
Three useful places to begin
Where does your team lose time chasing answers?
Which handoffs depend on one or two key people?
What needs to improve for greater control, growth, or an ownership transition?