Jared Tesche · Founder

Built from the jobsite

A year and a half out of university, I was handed a document audit: compare two stacks of spreadsheets, line by line, by hand. Two days of tedious checking, with the same exercise scheduled to happen again next month.

Instead of accepting it as part of the job, I built a process that did the checking automatically.

That was the first fix. I never really stopped looking for the next one.

Every role since has followed the same pattern: find the work that consumes people's time, understand why it exists, and build something that works better.

A weekly progress update that tied up five people became a half-day task. Cost reports nobody trusted became reports that project teams actually used to make decisions. Data scattered across disconnected systems became a single source of truth. Those solutions evolved from spreadsheets into reporting platforms, automation, and AI, but the goal has never changed: make the work easier.

None of this happened in isolation.

Over more than 15 years, I've worked through field engineering, project controls, scheduling, contract administration, and project management on major oil and gas and commercial construction projects. I've managed projects ranging from $20 million to $80 million, including the concrete structure scope on Scotia Place, Calgary's new arena.

I've shovelled concrete with the crew on a blowout, worked through schedule crises, defended forecasts in executive meetings, and led multi-million-dollar projects. I know what the work looks like on site and what the numbers look like upstairs, and I build with both in mind.

That's why I started Infractem.

I've never been interested in technology for its own sake. I've always been interested in removing friction from construction projects. Technology is simply a means to that end, whether that's AI, automation, or even a well-built spreadsheet.

The first step is always the same: understand how your team actually works, identify what's slowing it down, and build the solution that fits your business, not someone else's software roadmap.

How I work

• It has to solve a real problem. If a tool just gives your people another system to learn, it isn't worth building.
• Solutions have to survive real projects. If they don't work when schedules slip, RFIs pile up, and deadlines tighten, they aren't finished.
• Your team should own what gets built. No subscription to me, and nothing you can't run without me.
• Simple beats impressive. The best solution is the one your team is still using six months from now.