A business that doesn’t depend on any one person. Including you.
I design and roll out the systems a business runs on: the processes, the software and the AI inside them. The knowledge stays with the company. Work carries on when someone is away or leaves. And the business can grow when the market allows, and scale back in a downturn, without breaking.
- 1997I founded Selmatic, an ERP software company.
- 2003 and 2010I created its two products. Both are still in daily use.
- 2025The Constellation Software group acquired Selmatic.
- TodayI work directly with a handful of clients at a time, so each one gets my full attention.
What you ask for is rarely the real problem
Most owners come in with a specific request: automate a process, or bring AI into a department.
The request is a symptom. The real problem is whatever is costing you money: lost revenue, unnecessary costs, errors, dependence on specific people.
That’s why so many companies pay for ChatGPT, Copilot or Claude and see no return. The tool was applied to the request, not to the problem.
What I do
I find the constraint. Every process, in any industry, has one or two constraints that set the output of the whole business. If the warehouse can ship at most a hundred orders a day, for example, taking on more orders than that doesn’t raise profit, it just leaves more customers waiting. Improving anything else is a cost, not a gain, however good it looks for one department. So I look for the problem whose solution lifts the results of the whole business.
I fix the root cause. That clears every problem it was causing, and where possible, the system is built to handle what you’ll need next.
I see it through to adoption. The work is done when your people use the solution every day, not when it’s handed over.
The answer isn’t always a big project. Sometimes it’s two well-chosen automations. Sometimes it’s a whole new system. Sometimes it’s finally putting to work the tool you’re already paying for. The diagnostic tells us which one fits.
A solution nobody uses is wasted money
Building a system is the easier part today. The hard part is getting people to work in it.
For 28 years at Selmatic, I took systems from the signed contract to the day the company ran on them: training key users, acceptance testing, resistance to change, the first weeks after go-live.
I measure my work one way: is it still in use years later?
Why work with me
I think like an owner, because I’ve been one all my working life. I know from the inside the decisions that can’t wait, the responsibility you can’t hand to anyone else, and what it means to depend on key people. I’ve lived these problems in my own company, and seen them in many others through every system I rolled out.
Three roles in one person. The engineer can build but doesn’t know the business. The analyst knows the business but can’t build. The owner carries the risk and pays them both. Most failures I’ve seen weren’t in the code. They were lost in translation between those three. With me, there’s no translation.
I run my own company this way. Custom Business Solutions has no employees. AI agents carry the workload, with minimal manual work.
I’m personally accountable. From the first call to the day the solution is working in your business.
Where we start: a diagnostic
Before you invest in a solution, you need to know where the value is.
The diagnostic is a short, paid first step. It takes anywhere from a few working sessions to two or three weeks, depending on the size of the company, how many departments and key people are involved, and how quickly meetings can be scheduled.
I learn how the company actually works, pin down the root cause, and confirm the solution is feasible before anything is built. At the end, you have:
- the problems costing you the most, and how much, calculated from your own numbers;
- the solution, and why it’s the right one;
- a phased plan: a fixed price for the first phase, with each later phase priced before it starts.
The fee for the diagnostic reflects its value to your business and is agreed after our first call. If the project turns out not to be worth doing, I’ll tell you.
After the diagnostic
We build in phases, each with a fixed price and a clear outcome.
Most solutions don’t call for new software. They come from making full use of tools that already exist. When something more substantial has to be built, I put together and lead the team, with your own engineers if you have them, or with specialists I bring in for the project. You don’t have to find anyone.
I own the architecture, and I’m accountable for it working for years to come.
After the project
Once the solution is running, I can stay on as your fractional Chief AI Officer. A few days a month, I own your AI strategy and architecture, keep track of what changes, and extend what we’ve put in place. You get the person you need, without adding another key hire you’ll end up depending on.
If you don’t need that, the project ends there, and the system is yours.
Tell me about your business
A few lines is enough: what you do, and what costs you the most money, time or headaches.
On our first call, we’ll pin down the problem and what it’s costing you. If I can help, I’ll propose a diagnostic. If I can’t, I’ll tell you.
I’m based in Bulgaria, one hour ahead of Central Europe. I work remotely and travel to clients wherever they are.