Software that heals complexity.
We build new products from a blank page, and we connect AI services to the work people already do. Development here is AI-driven, so there are fewer weeks between the first conversation and something you can click.
First conversation free · Reply within one working day
Where it usually hurts
Symptom
"It all runs on a spreadsheet that nobody wants to touch any more."
Then the rules already exist, just in the wrong place. We start by reading what the spreadsheet actually does, including the parts that live only in your head.
Symptom
"Everyone says AI. Nobody says what it does for us."
We don't train models. We connect the good ones to a real task: reading your documents, transcribing your calls. And we tell you the cost before you commit.
Symptom
"My developers are good. There is just more work than there are of them."
So the useful piece is the one nobody is holding. We ask your developers which parts are fragile before we touch anything, and we tell them afterwards what moved.
What we do
Three ways to work with us
Greenfield builds
A new product, from the first sketch to something live. You bring the problem and the domain knowledge; we bring the architecture, the code, and updates in plain language.
AI engineering
Document and video pipelines, summarisation, transcription, search across your own material, wired into the tools your team already opens every morning, with the costs and the failure cases written down first.
Extra hands
Short freelance engagements alongside an existing team. A feature that keeps slipping, an integration nobody has time for, a second opinion on a build. We work to your conventions, not ours.
How we work
From the first conversation to something that runs
01
A conversation
You describe the problem in your own words. We ask questions until we can describe it back to you.
02
A scope you can read
What gets built, what it costs, and what we deliberately leave out of the first version. One page, no jargon.
03
AI-driven delivery
AI writes and reviews alongside us, under tests and human review. It takes the repetitive work, so the hours go to the decisions and you get working software to try sooner.
04
After it ships
Then it keeps working. We fix what real use turns up, and the next change is a small piece of work rather than a rebuild.
Selected work
Stack
Backend
- C#
- EF Core
- Dapper
- REST APIs
- gRPC
- GraphQL
Data
- PostgreSQL
- SQL Server
- Cosmos DB
- DynamoDB
- Blob storage
AI
- Azure AI
- Document intelligence
- Speech to text
- LLM APIs
Delivery
- Azure
- Docker
- Kubernetes
- Microservices
- Messaging
- CI/CD
Who you'll work with
I founded CodeCure.
I'm a software engineer, and CodeCure, in Izegem, Belgium, is my practice. When you get in touch, you're talking to the person who will design the thing and write the code, not to an account manager who passes it on.
That's deliberate. It means I take on work I can genuinely do well, I tell you early when something is harder than it looked, and nothing gets lost between the conversation and the build.
My background is in building and maintaining real production software: greenfield products, AI services wired into existing tools, and features on platforms that already have customers depending on them.
Contact
Which cure do you need?
A few sentences is enough to start. You'll hear back from a person, and the first conversation costs nothing.