CUSTOM SOFTWARE

Custom business software for small and mid-sized companies.

Paying for software your team works around? With AI coding agents and the right person steering them, a tool built around the way you work is no longer a luxury – and it belongs to you.

Book a free 30-minute call

Why off-the-shelf tools stop fitting.

Many companies pay monthly for SaaS tools full of features nobody really uses – yet missing the ones they actually need. The way your firm is organised can only be approximated with custom fields. The reports you actually steer by live in spreadsheets synced by hand. And with every seat paid for, each additional user becomes a budget question, so half the team works from exports and screenshots instead.

Building your own used to mean months of work and budgets only large corporations could justify, so making do was the rational choice. AI coding agents have changed that calculation. With the right person steering them – someone who understands your business, writes and reviews the code, and tests what the agents produce – a tool built around the way you work can be ready in weeks, and it’s entirely yours. I’ve seen first-hand how much relief and excitement a step like this can spark at the top.

The kinds of tools this is good for.

Anything where the way you work is specific enough that standard tools fight you. Some examples from my own work and from the conversations I have:

01

CRM and sales.

Deals, clients, conversations and reports organised the way your firm actually sells – by vertical, region or team – with forecasts you no longer rebuild by hand.

02

HR and onboarding.

People, roles, contracts, leave and onboarding checklists in one place, with the access rules and the integrations to payroll or finance that a spreadsheet can’t offer.

03

Projects and resources.

Who is working on what, with which budget and until when – connected to the deals they came from and the invoices they turn into.

04

Incoming payments and receivables.

What should come in this month – rent, instalments, invoices – next to what has actually landed on the bank account: matched automatically, overdue items flagged, and the reminder sent straight from the tool – as recently requested by a real estate business.

05

Internal knowledge and portals.

A home for the documents, decisions and know-how your team keeps asking each other for, with search that works – and the natural place for an AI assistant later.

Weeks, not months – and you own the result.

We start with how your team actually works, not with a feature list. Together we design the tool around that, and I build it – writing and reviewing the code myself, sped up by AI coding agents whose work I test. Whenever it’s possible and makes sense, we hook it into the tools you already use: your email, your files, your project system, Slack. A first usable version arrives early, and we shape the rest from real use.

What you get belongs to you: the code sits in your own repository, the data in your own database, hosted in whichever region your data needs to stay. No per-seat fees, so the whole company can work in it, not just the people with a license. And it is built on a standard, widely used stack – so any developer can continue it, not only me.

The foundation AI needs.

A tool like this is often what makes AI pay off in the first place. An assistant that reads your inbox and calendar, drafts follow-ups or reminds you who to call next is only as good as the system it runs on – it needs clean data about clients, deals and conversations to work from. A custom tool gives you exactly that, in a shape you control. Which is why the companies I work with usually get the foundation right first, and add AI carefully on top.

Sometimes the standard tool is the right answer.

If your process is close to the standard and a good tool exists for it, use the tool – bookkeeping is the obvious example. Building pays off where the way you work is genuinely your own, where you are paying for seats and features you don’t use, or where the spreadsheets around a tool have quietly become the real system. If that isn’t your situation, I will tell you so in the first conversation.

What this looks like in practice.

AI-READY CRM

A CRM that finally fits

This is more than a new CRM. For the first time, the whole firm sees the same picture of our business – on a system we own and can keep building on, AI included.
Johannes Suikkanen, CEO, Gemic

The challenge

Gemic, a global strategy and innovation consultancy with four offices and around 60 people, ran its sales on Pipedrive, but had long outgrown the standard setup. Its verticals, the principle the whole firm is organized by, could only be approximated with custom fields. The reports the firm actually steered by – by vertical, sales and revenue against target, a forecast weighted by deal stage – lived in spreadsheets synced by hand. Sales conversations, too, ended up in a makeshift spreadsheet of their own. And with 20 paid seats, every additional user was a budget question.

What I built

A CRM built around how the firm actually sells. Every view – deal board, reports, conversations, clients – switches between verticals and regions at a click. Sales and revenue are tracked against each vertical’s targets, with a forecast weighted by deal stage. Sales conversations live in the CRM itself, linked to clients and deals – so the team can finally see who last spoke to whom, how actively each vertical is talking to the market, and which clients have gone quiet. New deals announce themselves in the right Slack channels and flow into the firm’s project system, and the full Pipedrive history came across, cleaned up. Code and data belong to Gemic.

The outcome

Operations loves it, because it finally does what they need – and the spreadsheets around it are gone, from the reports synced by hand to the makeshift log of sales conversations. With no per-seat fees, the whole firm works in it now, not just 20 seat holders, which CEO Johannes Suikkanen values for the transparency and ownership it creates. AI comes next: reading inboxes and calendars, drafting follow-ups, sending proactive reminders. The team deliberately chose to get the foundation right first – and to add AI carefully on top.

The questions that come up in almost every first conversation.

How long does a custom tool take?

A focused tool – a CRM, a project overview, an internal portal – typically takes weeks rather than months, with a first usable version early on. Larger platforms grow in stages, with something in daily use at each step, instead of one big launch at the end.

What does it cost compared to SaaS?

In the projects so far, the build has cost roughly what the company was paying for a year of seats on the tool it replaced – sometimes a bit more. From the second year on, the subscription money stays with you, and so does the tool. Where exactly it lands depends on your team size and what the tool has to do; I give you a clear estimate after a first conversation.

Who owns the code and the data?

You do. The repository lives in your account, the data in your database, and you can take both elsewhere at any time. There is no license, no lock-in and no fee for leaving.

Where is it hosted, and what about the GDPR?

Wherever your data needs to stay – a European cloud region, your own cloud account, or on infrastructure you already run. Roles and permissions, audit logs and backups are part of the build, not an add-on, and the privacy notice for the tool is written alongside it.

Can we migrate from the tool we use today?

Yes. The history comes across, cleaned up on the way – in the CRM case below, the entire Pipedrive history was migrated and the spreadsheets around it retired. Migration is planned from the start so there is no day when the team has to work without its data.

What happens after launch – and if we stop working together?

Once it’s live, I help you keep the tool in good shape and grow it as your needs change – or I show your team how to do that themselves. Because the code is yours and built on a standard stack, any developer can continue it. Nothing depends on me staying.

Can AI be added later?

That is the idea. The tool is designed so that assistants and agents can work on top of it – reading the data, drafting, reminding – once the foundation is in place. Several of the companies I work with have chosen exactly this order: the system first, AI next.

INVITATION

Let's find your first step.

Tell me which tool your team is working around today. I read every message myself and normally reply within a working day.