Business software you buy once.

One deployment fee puts a working application under your own domain, in a database you own, usually within days. A monthly plan keeps it patched, backed up, and supported. Cancel that plan and the application keeps running, because you own it.

A house standing on solid ground with a set of keys in the foreground.

Start from a working application, or start from your process

Two of these are ready to deploy now. The third is where we started, and it is still how the hardest problems get solved.

You have two options, and both of them are bad

Spreadsheets

Fragile. Understood by two or three people. No audit trail, no access control, no way to tell who changed what. They work until the day headcount outgrows them, and then they fail slowly enough that nobody can point at the moment it happened.

SaaS

Priced per seat, forever. You use maybe 15% of the features and pay for all of them. Your data sits on infrastructure you do not control, under terms that change without your consent. The price goes up every year whether your usage does or not. And there is no exit that leaves anything behind.

There is a third option. It is not new. It is how business software was sold before subscriptions took over, and it works better for a company with eleven employees than it does for a company with eleven thousand.

Four steps, measured in days

  1. We talk about your process. Not a discovery phase. One or two conversations to establish which application fits and what has to change about it.
  2. We deploy. Into a dedicated server, under your own domain name, with your own database. One client, one deployment. Nothing shared.
  3. We fit it to your workflow. Field names, stages, roles, reports, integrations. This is where the application stops being a template and starts being yours.
  4. We keep it running. Updates, security patches, backups with point-in-time recovery, monitoring, and support. That is the monthly service plan.

How the model works in detail →

A title document and a key resting on a desk.

What happens if you fire us

This is the question worth asking any software vendor, and most of them have a bad answer. Ours is written into the contract.

  • You keep the running deployment and a perpetual license to use it. Nothing gets switched off.
  • The database and every record in it were always yours.
  • API and integration documentation is delivered with the initial build, so you can hire anyone to work on it.
  • Updates, support, and hosting stop. The application does not.

Modifying the code yourself requires buying the source license, which is a separate one-time fee and is on the pricing page. Reselling the application as a service to other companies is not permitted, though partner arrangements exist and we negotiate them individually.

Read the full terms →

The numbers are on the website

Every competitor in this category makes you book a call to find out what it costs. That is a sales tactic, not a pricing model. Ours is a one-time deployment fee, then a monthly service plan. Nothing is priced per seat, and adding your twelfth user costs the same as adding your second, which is nothing.

Deployment

From $12,000

One time, per application. Half on signature, half at go-live.

Service plan

From $950 per month

Updates, patching, backups, monitoring, hosting, and support.

Customization

Hourly, rate set by your plan

Prepaid blocks discounted. This is where most long-term value goes.

The first 3 deployments signed before 26 November get 40% off the deployment fee, in exchange for a named case study and a reference call. Service plan at full price.

Or start from your own problem

Deployment is the fast path. It is not the only one, and these four are still how most of our work arrives.

How we build

Incremental delivery, pragmatic architecture, and a preference for technology that will still be supported in ten years. Modern .NET and Blazor, chosen because it is stable and well understood, not because it is new.

LogScope

Structured logging and diagnostics designed for complex business systems where observability matters.

View on GitHub →

BlazorToolkit

Reusable components and utilities that improve consistency, productivity, and maintainability in Blazor applications.

View on GitHub →

Development Blog

Articles and insights from real client work, covering patterns, practices, and lessons learned in software development.

Read our blog →

Blog

SharePoint Is a Great Tool Right Up Until It Isn't. Here Is Where the Line Is. SharePoint Is a Great Tool Right Up Until It Isn't. Here Is Where the Line Is.
SharePoint Is a Great Tool Right Up Until It Isn't. Here Is Where the Line Is.

Business systems rarely get designed. They accumulate. Someone needs to track something, so they make a list. It works, so a second list appears. A flow gets added to keep the two in sync. A year later there are eleven lists, thirty-something flows, and a handful of workarounds that made perfect sense to whoever wrote them.

Nobody made a bad decision anywhere in that sequence. Every individual step was the reasonable one. That is precisely why this is worth writing about: the trouble does not come from a mistake you can point at, it comes from a tool being carried past the range it was built for, one sensible step at a time.

14 min read Read more...

Let us talk about your situation

A short call. What you are running now, where it breaks, and whether one of these applications fits. If it does not, we will say so.

Schedule a call