Recommended reading
Unnecessary complexity is an occupational disease in IT. It usually isn't malice — it's five very human reasons: ignorance dressed up in structure, budgets justified by complexity, job security through lack of documentation, vendor math that rewards the longest path, and "best practice" copied without context.
Read more →
Why I Don't Sell My Partners Off-the-Shelf — I Build It for Them
An accounting firm and its competitor use the same SaaS. Where does the difference come from? Mostly from price. Going downward. Why I build for my partners on top of standard systems instead of selling them off-the-shelf — and why AI-assisted coding made it real in 2026.
Read more →
I Built a Sales Pipeline That Drafts Itself
I automated my entire B2B sales pipeline up to the draft stage. The night drafts 50 messages via the Anthropic Batch API, 15 minutes of keyboard approval in the morning, sends go out via Microsoft Graph. The machine prepares, the human decides.
Read more →
15 Hours vs. 150 Hours — When IBM's Quote Wasn't the Only Option
IBM quoted 150 hours for an email migration where every sending system and printer would have been reconfigured. A single Postfix relay solved the same problem in 15 hours, without touching a single sender. A story about why the simplest path is often the best one.
Read more →
I Migrated from Windows to Fedora Linux in One Day — Here's What Actually Happened
An IT consultant switched from Windows 11 to Fedora Linux in one day. NVIDIA drivers, native Docker, 10GB less memory used. What worked, what broke, and why I'm not going back.
Read more →
10 Automations That Save Hours Per Week — and Can Be Built in a Day
10 concrete automation examples for SMBs. For each one: what it does, who it's for, how much time it saves, and how fast it can be built. No coding, no massive projects.
Read more →
A Million-Euro Problem, a Two-Week Solution — How I Built an IGA Platform
Commercial IGA solutions cost six figures and take months to deploy. I built a working proof of concept in two weeks — alone. Here's the architecture and why it matters.
Read more →
Self-healing IT environment — or eternal firefighting?
Break/fix is still the most common and most expensive way to manage IT. A self-healing environment is built on four layers: automation, documentation, regular reviews and expert access when needed.
Read more →
How to build an IT environment that doesn't depend on one partner
Your IT shouldn't collapse because your partner doesn't pick up the phone. Five concrete steps toward an IT environment that works — regardless of who manages it.
Read more →
Why an IT consultant shouldn't sell products
When an IT consultant sells products, their advice is no longer independent. Three problems with the commission model — and why vendor neutrality is the only fair way to do IT consulting.
Read more →
How to choose an IT partner — 5 questions nobody asks
Choosing an IT partner is one of the most important decisions. These five questions separate the salesperson from the expert — before it's too late.
Read more →
SMB IT Checklist 2026
10 things that must be in order at every SMB. A practical checklist and what to do if something is off.
Read more →
How I use AI in practice
AI won't take away IT jobs, or at least not all of them. It removes manual and repetitive work steps, and it frees up the people who use it to do what we're actually good at.
Read more →
When public IT buys the "safe solution", Finland's IT industry loses its edge piece by piece
Entrenched procurement culture erodes the public sector's ability to innovate and weakens Finland's IT industry's growth opportunities. Based on my experience, public procurement is designed to ensure nothing changes.
Read more →