Services
AI Solutions
I’m all about digital growth - for the past 10 years I’ve been working on digital innovations and building dozens of software products. I know each stage of the cycle like the back of my hand. As the CEO at Appunite I coordinate creating exceptional products with entrepreneurs and companies. The combination of my sales and tech experience makes me capable of understanding our clients needs and challenges, and it has helped companies from a variety of industries grow digital. My main goal is always to enable our client to focus on their industry transformation and the core of the business, while Appunite is responsible for building and delivering the products.
Every business I walk into has a story.
Not a marketing story. An operational one. A specific way they've learned to serve their customers that nobody else does quite the same way. An accounting firm that projects an entire year of client tasks in four minutes using templates no generic tool could replicate. A wellness clinic that combines physiotherapy, beauty treatments, hyperbaric therapy, and horse riding under one roof. A recruitment agency whose screening process is so refined it's become their main competitive advantage.
These businesses didn't arrive at their processes by accident. They iterated. They experimented. They built something that works for them - something uniquely theirs.
So here's the question that keeps nagging at me:
Why do all of these companies run their most critical operations on the same generic software as everyone else?
They've spent years perfecting how they work. Then they hand that work over to a tool designed for the average company, built by a product team that has never seen their operation, optimized for millions of users who all get the same features. And when the tool doesn't fit - which it inevitably doesn't - they don't change the tool. They change themselves. They adapt their process to fit the software.
Think about how backwards that is.
Your process is your competitive advantage. Your software should serve it. Instead, it's slowly reshaping it into something generic.
I recently met the owner of a clinic that runs six different service lines across three locations - physiotherapy, beauty, fitness, EMS training, a hyperbaric chamber, and therapeutic horse riding. No off-the-shelf software was designed for this combination. Obviously. Why would it be?
So he settled on a medical booking platform because it handled compliance. But his business isn't just a medical clinic. It's a hybrid unlike anything the vendor imagined when they built the product.
The system crashes during peak hours - between 4 and 8 PM, exactly when 190 patients are walking through the door. Support shuts off at 4 PM. A time indicator line on the calendar - a feature any modern app includes by default - costs 150 EUR per month extra. Processing a voucher payment takes 4-5 clicks and scrolling through a list. There are no analytics. The owner spends three hours every month in Excel manually calculating profitability per therapist because his 8,500 EUR-per-year software can't do it.
His reception team resorts to paper during outages. Paper. In 2026.
He described it in words I hear in different forms from almost every growing business: the software that was supposed to enable the business has become the thing constraining it.
His business model is genuinely unique. His software is generic. And the gap between those two things costs him money, quality, and growth every single day.
This isn't about one bad vendor. It's about how the software industry works.
SaaS products are designed for scale. To reach millions of users, they optimize for the average workflow. They build features that serve 80% of use cases and leave the remaining 20% to workarounds, integrations, or feature requests that may never ship.
For commodity processes - email, basic project management, standard accounting - this is fine. More than fine. It's brilliant. You don't need custom software for email.
But every company has processes that aren't commodity. The 3-5 critical operations that generate 80% of the company's value. The way you recruit. The way you deliver services. The way you manage clients. The way you onboard. These processes are what make you better than your competitors.
And you're running them on the same tools your competitors use.
The SaaS model works because of a hidden assumption: that the cost of building custom software is too high for most businesses, so they'll tolerate the friction of generic tools. For twenty years, that assumption held. Custom development meant six-figure budgets, year-long timelines, estimation roulette, and the ever-present risk that the project would fail entirely.
Renting was rational even when it hurt.
AI has changed the economics of building software in a way that most people haven't fully absorbed yet.
What took twelve to eighteen months can now be delivered in three to nine. AI-assisted engineering has flipped the economics: the cost of building custom software has dropped enough that it now competes directly with the SaaS subscription it replaces. Templates, reusable patterns, and AI handle the repetitive 80% while human expertise focuses on the 20% that actually matters: the domain-specific, context-dependent, production-grade decisions that make software work for a real business.
The moat that protected SaaS vendors for two decades - technical complexity - is draining.
This doesn't mean you should build everything custom. That would be foolish. But it means that for those 3-5 critical processes, the question has shifted. It's no longer "can we afford to build?" It's "can we afford not to?"
We call this shift Process Native Software.
Process Native Software is built from and for your actual business processes. Not configured from a menu of options. Not adapted to fit generic workflows. Built around how you work.
The old frame for this decision was "custom vs. SaaS" - a cost comparison where custom almost always lost. The new frame is "process-native vs. process-hostile" - a value comparison where the question is whether your software enables your competitive advantage or slowly erodes it.
For the clinic owner, process-native means: voucher payments in 2 clicks, not 5. All therapists visible in one calendar view, not behind separate tabs. Real-time profitability dashboards built in, not assembled in Excel. Changes deployed in days, not requested and forgotten. A system that doesn't crash during the exact hours his patients show up.
For an accounting firm, it means: four minutes to project an entire year of tasks for every client, because the software understands their specific templates, role assignments, and service delivery workflow. Not a generic project management tool with a hundred features they'll never use.
For any company with a process worth protecting: software that matches how you work. Not software that tells you how to work.
Let me be direct about something the pitch usually glosses over.
On pure total cost of ownership, custom software is more expensive than SaaS.
A mid-sized company with 100 users on a typical SaaS subscription will spend around 160,000 EUR over five years. The same company building a custom solution will spend roughly 280,000 EUR - development, maintenance, and hosting included.
That's a 120,000 EUR premium. On a spreadsheet, SaaS wins.
But the spreadsheet is lying by omission.
It doesn't count the owner spending three hours every month in Excel because the system has no analytics. It doesn't count reception staff falling back to paper during peak-hour crashes. It doesn't count the 150 EUR per month for a feature that should be standard. It doesn't count the quality degradation when you scale a process on software that wasn't built for it. It doesn't count the customers who leave because "sorry, our system is down" happened one too many times.
The honest math: if 10 people lose 3 hours per week to tool limitations at 30 EUR per hour, that's 234,000 EUR over five years. If 2 people spend 10 hours per week manually syncing data between systems, that's another 130,000 EUR. Add error costs, missed opportunities, quality degradation - and the 120,000 EUR premium starts to look cheap.
But only when the pain is real, quantifiable, and connected to a process that actually differentiates the business.
When the math doesn't work, I tell people to stay with SaaS. For 90% of use cases, that's the right answer. The default should always be: use the generic tool. Build custom only where it genuinely matters.
The initial build is only half the story. The ongoing relationship is where Process Native Software fundamentally diverges from both SaaS and traditional custom development.
In the old model, changing your software was a negotiation. File a ticket. Wait for prioritization. Hope it makes the roadmap. Get a version that's close to what you asked for but not quite. Meanwhile, the business has moved on.
In the new model: message your team. Describe what you need. It ships in hours.
The clinic owner mentioned wanting NFC keychains so patients could tap to check in and automatically deduct from their vouchers. With his current vendor, that's an idea he files away as "someday, if they ever support it." With process-native software, it's a feature that can be scoped and built. The business imagines the improvement; the software catches up the same week.
This changes what software is. It stops being a fixed constraint you work around. It becomes a living system that evolves as fast as the business does.
An accounting firm owner described the shift like this: "In the old world, you submit a feature request and wait months. In the new world, you write on Slack what you want changed and it's done in 1-2 hours." That's not an incremental improvement. That's a different category of relationship between a business and its tools.
Something structural is happening beneath the AI hype cycle.
For two decades, the software industry told businesses: you can't afford custom, so rent generic and adapt. SaaS vendors built empires on this message. And for most things, they were right.
But the economics have changed. The cost of building has dropped. The speed has increased. The risk has been reduced by proven patterns and AI-assisted engineering.
This doesn't mean SaaS is dying. For commodity processes, it will remain the right choice indefinitely. But for the processes that define how a company competes, the assumption that renting is the only option no longer holds.
The companies that see this first won't just have better software. They'll have operations that evolve faster, scale without degrading quality, and accumulate institutional knowledge in systems instead of in people's heads.
Every business has a story. A specific way they've learned to serve their customers. The question is whether the software they depend on tells that story - or slowly rewrites it into something generic.
Process Native Software is a bet that the story matters.
