I work inside project delivery — understanding how real construction work moves, seeing where the friction is, and building the operational systems, standards, automations, and visibility layers that make it cleaner, faster, and more repeatable.
I sit at the intersection of project delivery, construction technology, and workflow governance. My value is in taking fragmented field and office processes — the ones that slow teams down, create documentation gaps, and produce decisions based on incomplete information — and turning them into structured, repeatable systems.
That means understanding how work actually moves on a project: how things get named, routed, reviewed, logged, escalated, turned into decisions, and preserved for turnover and historical tracking. That is not admin work. That is operational infrastructure — and most construction companies are bad at it.
Academic background: B.S. Industrial Design, M.S. Construction Management. I think in systems, build for the field, and design for people who don't have time for tools that don't work.
Bid leveling, subcontractor scope gap analysis, pre-qualification, and buyout coordination. I build the structure that makes procurement decisions faster and better-documented — so the risk is visible before it's a problem.
Managing the pipeline between field crews, subcontractors, architects, and PMs — RFIs, submittals, change orders, and inspection tracking. The goal is zero lag between a question in the field and an answer in the record.
Building the naming conventions, routing logic, SOPs, and documentation frameworks that make project records consistent, complete, and useful — not just filed. Systems that support turnover, audits, and decision-making.
Designing and deploying automation pipelines — email triggers, AI document processing, folder-to-system handoffs — that reduce manual entry and keep information moving without someone having to remember to push it.
Building structured trackers tied to schedule dependencies, approval cycles, and material lead times — with logic like critical path flags and RAG status conditions. Turning workflows from reactive management into proactive systems.
Configuring and connecting Procore, OpenSpace, DroneDeploy, and M365 into integrated field-to-office workflows. Platform adoption structured around how your project actually operates — not how the manual says it should.
A seven-phase operational evolution — from using AI as a task assistant to architecting end-to-end systems where data flows cleanly, decisions are faster, and teams operate with less friction. This is the progression that built the practitioner.
Started using AI for drafting, cleanup, and summarization. Focus was speed — not systems. Key realization: AI reduces friction only when inputs are structured.
Built repeatable formats for meeting minutes, submittal naming, and RFI logic. Used AI to enforce consistent tone, standardized language, and clear categorization across project records.
Broke internal operations into inputs → actions → outputs. Identified patterns across submittals, RFIs, and procurement. Started asking: where are delays created, what is repetitive vs. decision-based?
Built Excel trackers tied to schedule dependencies, material lead times, and approval cycles. Introduced critical path flags, days-to-required-on-site, and RAG status conditions.
Designed pipelines: email → folder → trigger → AI processing → system update. Introduced event-based triggers, system-to-system communication, and controlled permissions for automation.
AI used to analyze response times, identify approval delays, and surface risk before it impacts schedule. Built insights around which workflows consistently lag and where decisions stall progress.
Designing end-to-end workflow systems — not improving individual steps. Core principles: clarity over complexity, structured inputs equal reliable outputs, automation should follow logic not replace it. The goal: environments where data flows cleanly, decisions are faster, and teams operate with less friction.
Meeting minutes in construction are consistently late, inconsistently formatted, and manually produced — creating project record gaps and PM overhead. I built a local Python agent that monitors a folder for incoming transcripts, parses the content, and automatically injects structured output into the OLSEN Excel meeting minutes template, mapped to specific cell addresses.
Subcontractors with executed contracts but missing Procore directory entries create coordination breakdowns on active projects. Built a structured gap analysis tool that cross-references contract records against directory entries.
Traditional bid leveling is time-intensive and reliant on the estimator's memory of scope. I integrated Claude into a structured workflow for rapid scope gap identification across subcontractor bids — surfacing inconsistencies in minutes.
No structured process existed for evaluating subcontractor risk prior to invitation to bid. Built a structured intake and scoring packet with weighted criteria covering safety record, bonding capacity, financial health, and project experience.
Field finish status tracking relied on verbal updates and disconnected punch lists with no real-time visibility. Built an Excel-based QR code system linked to Procore, allowing field teams to scan space codes and update finish status directly to the project record.
Field documentation from 360-degree capture and aerial surveys existed in silos, disconnected from the Procore project record. Built a documentation pipeline that integrates both platforms directly into structured Procore records for each project phase.
Most construction firms have the same problem: the work is getting done, but the system around the work is broken. Naming is inconsistent. Routing is manual. Approvals stall. Documentation gaps show up at closeout. Decisions get made on incomplete information.
I come in at the process level — not to replace your team's judgment, but to build the operational infrastructure around it. Structured workflows, standardized formats, automation where it actually adds value, and visibility layers that surface what matters before it becomes a problem.
Engagements are scoped, contracted, and fully documented. You own everything when I leave.
Firms where the work is getting done but the system around the work is broken. Inconsistent naming, manual routing, stalling approvals. I come in and fix the operational infrastructure so the project runs cleaner.
Small-to-mid-size firms scaling up and adopting Procore for the first time. I build your workflows, standards, and data structures correctly from day one so they support growth instead of fighting it.
Organizations bringing in new platforms — Procore, OpenSpace, DroneDeploy — who need someone who understands both the tool and the actual construction workflow it needs to support. Technology should follow the work.
I get inside how work actually moves on your project. I find where friction lives, where information disappears, and what is already being done that could be structured better.
I design and implement the workflows, standards, automations, and visibility layers that fix the specific friction points identified — scoped precisely, built for your team, documented as I go.
Full deployment, team training, and complete SOPs. Everything I build is yours — the logic, the tools, the documentation. You do not need me there for it to keep working.
Available for project-based engagements, workflow audits, and technology implementation. If your operation has friction you cannot quite name — or systems that technically work but create more work than they save — that is the conversation to start.