Field crew
Started on the tools.
Framing, forming, site work. The years that taught me how a job actually goes together, and how much money quietly dies between the plan and the field.
Twelve years inside BC construction, field crew to general manager. Then I learned to build the fix: websites, lead systems, dashboards, AI agents. Eunoia is one person who has done both jobs, and still does.
From the field to estimating, project management, and operations leadership, across BC's construction and growth businesses.
Project management and delivery on complex builds. Schedule, risk, vendor management, change orders, owner relationships.
The construction volume delivered under my management, measured in real buildings, not slide decks.

I'm an operator who learned to build. Twelve years inside construction: field crew, estimator, operations manager, general manager. Then Eunoia, where I build the websites, lead systems, dashboards and AI agents a trades business runs on, and stay on to run them. Not a consultant with a deck, not a developer guessing at your business. Both jobs, one person.
I spent a decade and change learning how real businesses actually run, not in theory, not in a case study, but on jobsites at 6 a.m. in trailers doing take-offs, in boardrooms defending budgets, and in ops rooms keeping projects on track when everything was trying to pull them apart.
Somewhere along the way I fell hard for technology, the kind that actually removes friction from the work. I learned to build systems, automate the tedious parts, and apply AI where it makes the team faster and sharper, not where it just looks impressive.
Eunoia exists because the best operators I've worked with all had the same problem: not enough time, not enough leverage, and not enough clarity. Good systems fix all three. Great systems do it in a way that outlasts the consultant who built them.
That's the work. Ship it, run it, hand it over.
Field to GM, then builder. Every stage was earned on real jobs, and every one of them shows up in how I build now.
Started on the tools.
Framing, forming, site work. The years that taught me how a job actually goes together, and how much money quietly dies between the plan and the field.
Take-offs, bids, and the numbers behind every job.
Margins get decided before a shovel hits the ground. I learned to read a job in numbers, and watched one bad assumption eat a quarter's profit more than once.
Schedules, crews, cash, keeping the machine running.
Keeping a dozen moving pieces from colliding, every day. This is where I started building small systems, checklists, boards, automations, because the same fire twice is a process problem, not a people problem.
The whole shop: P&L, people, pipeline.
Every problem in the company eventually crossed my desk. That's where you learn which problems a system could have caught, and how expensive it is when nothing gets built.
Learned to build the fix, automations, dashboards, AI systems.
I fell hard for the technology side and learned to build it properly: automations, dashboards, integrations, AI agents. First for my own shop, then for other people's.
One operator who owns the outcome, end to end.
The two halves became one job: find the constraint like an operator, build the fix like an engineer, and hand your team something they own. It ships every month.
I chose the name eunoia, an ancient Greek word for beautiful thinking and goodwill, because it captures something I try to practice every day: clarity, care, and the intent to leave things better than I found them.
Every system is only as good as the team running it. Change management, training, and adoption aren't afterthoughts, they're the whole job.
I measure success by what stays with you, not how long I stayed around. If the work doesn't outlast me, I didn't do it right.
I'd rather lose the engagement than sell you work that won't move the needle. A short, honest 'no' beats a long, polite yes.
I use what your team will actually adopt. Sometimes that's a cutting-edge agent. Sometimes it's a spreadsheet with a good macro.
The name eunoia means beautiful thinking. I believe the documents, systems, and tools you use every day deserve a little of that, too.
The difference between a system your team tolerates and one they love is a thousand small decisions. I sweat those.
No pitch. Thirty minutes on the thing costing you the most, and how I'd build the fix.