Opens in a new tab

DISCOVER / MY APPROACH

I don't start with AI. I start with what you actually need.

Someone comes to me and says, “I think my business needs AI.”

My first reaction? Interesting! Tell me what you’re trying to improve.

Because wanting AI and needing AI are two very different things.

Maybe you’re spending hours on tasks that should take minutes. Maybe your team is juggling five different applications that barely communicate. Or perhaps you’ve already introduced AI, and the results aren’t quite what you expected.

Whatever brought you here, I’m interested in what happens behind the scenes.

What’s working? What isn’t? What’s taking too long? And why?

I know, I know. You probably came looking for solutions, and here I am asking questions!

But there’s a good reason for that.

01 / UNDERSTAND THE PROBLEM

First, I want to understand the problem.

Imagine telling your mechanic that your car is making a strange noise.

Would you feel comfortable if they immediately suggested replacing the engine?

Probably not! You’d expect them to investigate first.

Well, that’s how I see business technology.

Before recommending a new system, I want to understand what your business actually needs and where things are going wrong.

Sometimes the problem is obvious. Sometimes what looks like the problem is only a symptom of something happening elsewhere.

And those distinctions matter.

Because automating a broken process doesn’t necessarily fix it. Sometimes it just makes the mistakes happen faster!

I’d rather spend a little more time asking the right questions than help you invest in the wrong solution.

Can I ask you something?

Does this way of approaching a problem speak to you?

YOU SAID / YES, ABSOLUTELY!

Wonderful! Then we’re already looking in the same direction.

There’s something reassuring about knowing why you’re making an investment before committing your money, time, and energy to it.

And once we understand what really needs attention, the possibilities become much more interesting.

YOU SAID / NOT REALLY

Fair enough!

Sometimes you’ve already spent weeks thinking about a problem. You’ve done your research, and you’re ready to move forward. The last thing you want is someone asking another hundred questions!

I understand that. I’m not interested in making a simple project unnecessarily complicated.

But I will want to check that the solution you’re considering can actually deliver what you expect. A few good questions at the beginning can save quite a few unpleasant surprises later.

And once I understand what we’re trying to accomplish, we can get to my favorite part. Exploring the possibilities!

02 / EXPLORE THE POSSIBILITIES

Now, what could we actually do about it?

Here’s where things get interesting.

There are often several ways to solve the same problem. And they don’t all involve artificial intelligence.

For example, if a task always follows the same rules, why ask AI to figure out what to do every single time?

A straightforward automation might do the job faster, more reliably, and at a lower cost.

On the other hand, if the work requires understanding different situations, interpreting information, or making sense of unstructured content, AI might be genuinely useful.

And sometimes, neither is appropriate.

A clearer procedure, fewer unnecessary steps, or better communication between people might be all that’s needed.

Yes, sometimes my recommendation is to use less technology!

I know that sounds rather unusual coming from someone who designs intelligent systems.

But I’m not here to sell you software. I’m here to find what works.

So how do I choose?

I look at five things.

Will it make a meaningful difference?

Not just because something can be automated, but because doing so actually improves the business.

Does it really need this technology?

If a simple, predictable solution works, adding AI may introduce costs and uncertainty without adding value.

Can we rely on it?

A system that works beautifully during a demonstration but fails when your team needs it isn’t particularly helpful.

What will it really cost?

Not just the subscription. I consider implementation, maintenance, ongoing usage, training, and the effort required to keep everything running.

And who remains in control?

Your data, your processes, your important decisions. I want you to understand what you’re investing in and avoid unnecessary dependence on a particular provider.

These questions help me decide what deserves to be built, what can be simplified, and what we should probably leave alone.

But making recommendations is only part of my work.

03 / FROM IDEA TO WORKING SYSTEM

And yes, I can build it too!

This is something important I’d like you to know.

I’m not someone who simply hands you a report and says, “Good luck!”

I’ve spent years developing websites, integrating applications, building automations, and figuring out how to make different technologies work together.

I enjoy the investigation, certainly.

But I also enjoy turning a good idea into something that actually works!

Once we’ve agreed on the direction, I can design the architecture, select the appropriate technologies, and implement the solution.

Sometimes I build it myself. Sometimes I use AI-assisted development or involve a specialist when their expertise is useful.

What matters is that every part has a clear purpose, and the finished system works as intended.

I don’t believe every business needs an elaborate technological masterpiece.

You need something appropriate to your operations, your people, and your goals.

And I won’t consider the job finished simply because the software runs.

We’ll need to know whether it does what we intended.

Can your team use it comfortably? Does it handle mistakes? Can you see when something goes wrong? Is it making the work easier, or just moving the complexity somewhere else?

Those questions deserve answers too.

04 / WORKING TOGETHER

There's something else I'd like us to agree on.

When I work on a project, I take responsibility for the technical decisions and the quality of my work.

But I don’t want to make important business decisions in your place.

After all, it’s your business!

You understand your customers, your people, your priorities, and the realities of your day-to-day operations.

I bring my technical knowledge, experience, and an independent perspective.

And when we put those together, we have a much better foundation for making good decisions.

That doesn’t mean you’ll have to become a technology expert or spend your evenings learning how everything works.

Quite the opposite!

My job is to handle the complexity while keeping you informed about the things that matter.

One more question, if you don't mind!

Would you like to stay involved in the important decisions as your system takes shape?

YOU SAID / YES

Excellent! I like working that way.

I won’t ask you to decide which API to use or how to structure the code. That’s my responsibility.

But when a decision affects your business, your budget, or the way your team works, I’ll want your input.

And I’ll explain your options in a way that makes sense without a technical dictionary!

YOU SAID / I’D RATHER LEAVE IT TO YOU

I understand! You’ve got a business to run, and the whole point of asking for professional help is to stop having to figure everything out yourself.

You can absolutely leave the technical decisions to me.

But there will be moments when I need your input, particularly about your business priorities, your customers, or how your team actually works.

I won’t involve you in every technical detail. I will make sure the decisions that belong to you remain yours.

That’s the kind of working relationship I appreciate.

Clear responsibilities. Open communication. No unnecessary complications.

And something else that’s important to me: when the project is finished, you shouldn’t feel that your business has become dependent on a mysterious collection of tools that only I can understand.

I want your systems to serve your business, not the other way around.

05 / RELIABILITY & INDEPENDENCE

What happens when something doesn't go as planned?

Because it will happen.

A service changes its pricing. An integration stops working. An AI model produces an unexpected answer. Someone on your team uses a form in a way nobody anticipated.

Technology isn’t perfect. And neither are the people using it!

That’s why I think about reliability before problems occur.

Can we recognize a failure? Can we recover without losing important information? Does somebody need to approve an action before it happens? What would stop working if a provider disappeared tomorrow?

I don’t expect to prevent every possible problem.

But I do want to design systems that are understandable, maintainable, and capable of handling ordinary surprises.

And if we discover something isn’t delivering the expected value? Then we revisit it.

A good solution shouldn’t become sacred simply because we’ve already invested time in building it.

Sometimes improving a system means changing it. Sometimes it means removing something. And sometimes the smartest decision is to stop.

The goal isn’t to keep the technology busy. It’s to help your business work better.

06 / WHAT IT MEANS FOR YOU

So, what does all this mean for you?

If you’ve made it this far, you probably understand why I don’t begin every conversation by recommending the latest AI tool.

I’m enthusiastic about technology. I genuinely enjoy discovering what it can accomplish.

But I’m even more interested in what it can accomplish for you.

I want to understand what you’re trying to achieve.

I want to explore the possibilities without unnecessary complexity.

I want to recommend what makes sense, explain why, and help you put it into practice.

And I want you to remain in control of the business you’ve worked so hard to build.

That philosophy can be summarized in one sentence:

Intelligent where it matters.
Deterministic where it doesn’t.
Owned by the business.

It’s the principle behind the way I investigate, design, implement, and improve business systems.

And it’s also why I don’t believe in one-size-fits-all solutions.

Your business deserves more thought than that.

07 / WHERE WE GO NEXT

Now, perhaps we should talk about yours!

We’ve spent a few minutes exploring how I approach my work.

But there’s still something I don’t know.

What brought you here?

Maybe you’ve been wondering whether AI could help your business.

Maybe you’ve already tried a few things and aren’t satisfied with the results.

Or maybe you have a specific project in mind and want someone who can help you make it happen properly.

Whatever the reason, I’d be interested in hearing about it.

And if you’re wondering what kind of work I can take on, what an engagement looks like, or what level of investment to expect, I’ve prepared a page just for that.

Shall we take the next step?

No pressure. Just a clearer picture of what we could accomplish together.

And if all you’re looking for today is a little inspiration, you’re welcome to explore the articles and interactive stories I’ve shared.

There’s plenty to discover there, too.

One last thing…

You don’t need to understand every technology available.

You need to understand what your business is trying to achieve.

I’ll help you figure out the rest.