Every businessis a system.
For years I thought I was building websites.
Then I thought I was building software.
Eventually I realised I was always doing the same thing.
Understanding how something works.
Finding where it loses energy or opportunities.
And improving it in the simplest practical way.
Today I apply that same way of thinking to businesses, software and products.
Everything starts with understanding.
How I stopped building websites and started understanding systems
For years I believed I was building websites.
Later I believed I was building software.
Looking back, neither was really true. The technology changed. The underlying work never did.
Every project started with the same questions.
- How does this work?
- Where is friction created?
- What part of the system is weakest?
- What is the smallest change that could make a meaningful difference?
Real problems rarely fit inside a single discipline. Some require software. Others require better communication. Others require removing complexity rather than adding it.
After enough projects, I noticed something surprising. The industries changed. The technologies changed. But the underlying questions were almost always the same.
Over time I stopped thinking in terms of technologies and started thinking in terms of systems.
That changed everything.
Four connected areas. One healthy business.
Every business is different. Different industries. Different customers. Different technologies.
Yet after working on many projects, I kept seeing the same four forces appear over and over again. When one of them becomes weak, the whole system suffers.
I didn't invent this framework. I recognised a pattern.
01Visibility
Can people find you when they need what you do?
02Trust
Why should they choose you instead of someone else?
03Conversion
Once they're interested, is taking the next step simple?
04Retention
What makes existing customers come back?
- Visibility
- Trust
- Conversion
- Retention
- back to Visibility
These four areas aren't independent. They constantly influence each other.
The goal isn't to optimise one metric. It's to strengthen the entire system.
Four questions worth asking
I ask these questions in almost every business. Not because they provide the answer, but because they usually reveal where the real problem lives.
- Can people find you?Visibility.
- If they find you, why should they trust you?Trust.
- Once they're interested, is taking the next step obvious?Conversion.
- After becoming customers, what makes them come back?Retention.
Understanding usually starts with asking better questions.
Better answers usually begin with better questions.
Products emerge from patterns
Most products don't begin with a startup idea. They begin with the same problem appearing again and again.
You solve it once. Then again. Then again. Eventually the solution deserves to exist on its own.
Every product started as a practical solution to a real problem. Only after seeing the same pattern repeatedly did it become something worth building for others.
- MailBoostRetention
Helping local businesses stay connected with their customers.
- SecureCode HQSecurity & Operations
Keeping secrets secure during AI-assisted development.
- MAKOTechnical optimisation
Helping AI understand web content more efficiently.
Every product is a lesson that became reusable.
Before improving anything, understand it.
I don't believe every problem needs another tool.
- Sometimes the answer is to build something.
- Sometimes it's to simplify.
- Sometimes it's to remove complexity.
- Sometimes the only thing missing is action.
Because without action, there is no data.
Without data, there is nothing to learn from.
Technology should reduce complexity.
Not become complexity itself.
How I think
I like simple things, honest work and clear communication.
I've spent years learning across disciplines that usually stay apart: electronics, industrial automation, backend, infrastructure, AI, security, SEO, and software architecture.
Not because I wanted to know everything, but because real problems rarely belong to only one discipline. Understanding the whole system usually matters more than mastering one specific tool.
Understanding isn't the destination. It's where every meaningful improvement begins.
I don't chase technologies. I chase understanding.
Different formats. One philosophy.
Every improvement takes a different shape.
- A website
- An automation
- An internal tool
- An API
- An open-source project
- A SaaS
The format depends on the problem. The philosophy doesn't.
Every project teaches something.
Some lessons become products. Others simply change how I think.
Observations
I'm constantly observing how businesses, software and technology evolve.
Some observations become articles. Others become case studies. Others become products. Many simply change the way I think.
Everything begins by paying attention.
Let's think together
Nobody understands your business better than you do. You know your customers. Your industry. Your day-to-day challenges.
What I can offer is another perspective. Years spent building software and studying systems have taught me that small improvements often create disproportionate results.
Sometimes that confirms you're already moving in the right direction. Sometimes it helps reveal opportunities that were already there, just waiting to be seen.
If you're building something interesting, or simply feel stuck, I'd be happy to hear your story.
No sales pitch. No pressure. Just a direct conversation with the person building the work.