Building Custom Software with AI – Why the Math Has Changed

For decades a simple rule held: custom software is for large corporations. Mid-sized companies buy standard software and adapt their processes to it – not the other way around. That rule no longer holds, and the reason is AI-assisted development.

What has changed

Tools like Claude Code or Codex don't just write lines of code faster. They change the structure of the work: a small team – or a single person with process understanding – can now build in weeks what used to take a project team months. The bottleneck shifts from programming to specifying: whoever can precisely describe how a process should work gets working software.

Where custom software makes sense now

Three patterns have emerged from our project practice:

• The gap case: there's a hole between two standard systems, bridged with Excel and email. Exactly these bridges are cheap to build today.
• The differentiator case: a process is what makes a company distinctive. Forcing it into standard software would mean throwing away the advantage.
• The automation case: recurring tasks with clear rules – proposal creation, data prep, reporting – can be integrated directly into the workflow with AI agents.

What has stayed the same

AI writes code, but it doesn't take responsibility for it. Three things remain hand-crafted work: understanding the actual (not the documented) process, deciding what the software should deliberately not be able to do, and operations – updates, security, further development. Software nobody maintains is a liability with a user interface.

Conclusion

The question is no longer "can we afford custom software?" but "which of our processes deserves it first?" Whoever's looking for the answer shouldn't start with the technology, but with the process that creates the most friction today.