- 28 h
- a week saved on quantity takeoff
- $500K
- a year in added revenue
Cut quantity takeoff time by 28 hours a week and grew revenue by $500K a year.
What we built: AI-assisted quantity takeoff for the estimating team.
I help founders and operating teams find where AI pays back, then help them ship it.
Not ready for a call? Estimate what AI could save your team





Results
Recent work, measured in hours back and money recovered.
Cut quantity takeoff time by 28 hours a week and grew revenue by $500K a year.
What we built: AI-assisted quantity takeoff for the estimating team.
Saved ~50 hours a week across the organization and recovered roughly $25K a month previously lost to errors and missed work.
What we built: Automated workflows across the organization's day-to-day admin.
Cut admin time by 35 hours a week, turned 20 hours of previously unbilled work into billable hours, and captured $200K a year in change orders that used to fall through the cracks.
What we built: Admin automation and change-order tracking across projects.
Early-stage Copilot rollout across a 10-person team already saving ~1 hour per person per week, with most of the runway still ahead.
What we built: A Copilot rollout and hands on training for the team.
Services
Second opinions, advisory calls, and AI roadmap reviews. For founders and leadership teams who want a thinking partner who has shipped this work before, not a deck builder.
Architecture decisions, vendor selection, build versus buy calls, prompt and agent design. Hands on enough to write the code when that's what the work needs.
Workshops and training that get teams fluent in Copilot, Claude, and modern AI tooling. Focused on what actually changes how people work, not generic literacy slides.
Tools
AI goes into the systems your team already opens every day.
AI Savings Calculator
Three numbers, about a minute. You get a simple estimate of the hours and money AI could give back to your team each year.
Fit
Which means being honest about who I'm useful to.
How I think
Most AI projects fail because they pick the wrong one. Choosing right is half the work, and the half nobody puts on the roadmap.
The basic solution that ships beats the clever one that doesn't. Most teams overestimate what AI can do this quarter and underestimate what it'll do in two years.
Demos lie. Users don't. Get something narrow and useful in front of them before chasing something broad and impressive.
About
I've spent the last few years architecting and shipping more than 120 AI systems, for companies from early stage startups to public sector. I write Sweden's largest AI newsletter and run a 3,500 member community where operators learn to use AI seriously. I'd rather build something that works than write a thought leadership post about it.
“Stefcode helped us with the architecture and the results are amazing. We ship things very quick and keep continuing to do so.”
I help companies find where AI actually pays back, then build it with them. In practice that means three things: strategy and sparring for leadership teams, hands on implementation inside the systems you already use, and training that gets your team fluent in tools like Copilot and Claude. You work directly with me, not an account manager.
I start with the problem, not the technology. Most of the first conversation is about where your hours and money actually go. The person who scopes the work is the person who builds it, so nothing gets lost in a hand-off to juniors. And I measure success in hours saved and revenue captured, which is why every case on this site comes with a number.
No. Plenty of teams start from zero. What matters more is having a repetitive process that eats hours every week, like reporting, admin, or quantity takeoff. That's usually where the first win is.
It depends on the scope, so there's no price list. A focused first project costs a fraction of a larger build, and you'll know the scope and the cost before any work starts. The intro call is where we figure out whether the numbers work, before you commit to anything. For a rough sense of the upside, try the savings calculator.
Yes, and I'd recommend it. A good first project is one narrow workflow: one process, one team, one number to move. Once that's working and measured, we widen it.
No. Construction is where some of my clearest results are, but I work with founders and operating teams across industries, from early stage startups to engineering firms and the public sector. The same approach works anywhere a team loses hours to repetitive admin, reporting, or manual data work.
Both. I'm based in Sweden and work with teams internationally, in English or Swedish. Most of the work happens remotely, and on-site days can be arranged when they're worth it.
Work with me
If yours does, you'll know on the first call. One short conversation is usually enough.