Built to order
once, then again.
Produsera is small, unfunded and new. It exists because one company needed a system nobody was selling, and what came out of that build turned out to be worth offering to anyone else with the same problem.
One customer, one system.
In autumn 2025 a Dutch IT services company called IT'er aan Huis was running client relationships across spreadsheets, email threads and sticky notes. They needed a system shaped around how they already worked, not one they had to bend their process around. So we built one: a Blazor CRM for their team and their clients across Amsterdam and Haarlem.
It kept growing in the direction the work pushed it. Quotes needed to become orders. Orders needed stock behind them. Stock ran out, so it needed suppliers, lead times and a way to work out what to reorder before the shelf was empty. None of that was a roadmap — it was the next thing that hurt.
What ended up existing is a free CRM core with 13 operations modules bolted around it. It is the same software that company runs on, opened up to anyone else who holds stock and has to buy it back. That is the whole story so far — there is no second chapter yet, and the 10 design-partner slots exist to write it.
We had already tried buying.
Long before any of this existed, I spent a lot of time inside Odoo. The pitch is genuinely good and the first months are genuinely fast: declare your fields, write the logic, and the interface renders itself. While the questions stay narrow, it delivers exactly what it promises.
Then the questions stop being narrow. A number has to be computed from three others, then computed live, then computed differently for one warehouse. You are writing compute functions, then fighting XML inheritance to move a field somewhere it was never meant to sit, then reading somebody else's override to understand why yours does nothing at all. The week the framework saved you in month one, it bills back with interest in month six.
This was also before you could ask a model what an error meant. The answer lived in a forum thread, in a partner's private repository, or nowhere — and a lot of people were in no hurry to share it. Fighting the tool was the job. Building the thing the business actually asked for was what happened afterwards, if there was time.
Produsera is the reaction to that. Every module here is ordinary, readable code with an interface somebody wrote on purpose. Nothing is generated from a declaration, so nothing has to be wrestled back out of one. That is the whole design argument, and it is why the answer to "can it do X" is usually a conversation rather than an inheritance diagram.
The short version.
Stated plainly, because a young product pretending to be an old one is the easiest thing in the world to catch.
- Autumn 2025
First build
A Blazor CRM for one company in the Netherlands. One system, one problem, and the foundation of everything after it.
- Through 2026
It became a product
The parts that generalised — stock, purchasing, replenishment, returns, accounting — were separated into modules a tenant can switch on independently.
- Now
Open to the first workspaces
The signup is public, the modules work, and the 10 design-partner slots are open. What is missing is other people's real data going through it.
What we hold to.
The software fits the business
Custom fields, roles and module choice are configured in the browser, not quoted as a project. The point is the result, not the rebuild.
Honest beats impressive
This site names only modules you can actually open, and the sample figures on it are labelled as samples. If Produsera isn't a fit for you, the answer to your email will say so.
Nothing charges you by surprise
The 90-day programme takes no card. When it ends the paid modules lock rather than billing you €111 for a catalogue you may have opened twice.
Built to last, not to raise
Unfunded and not chasing scale. The plan is to make money shipping software that a handful of companies genuinely run on, and to still be here in ten years.
What small actually buys you.
Produsera is a small remote operation with no office and no sales floor. Meetings happen on video, in English, and usually with the person who is going to do the work.
You talk to the people who build it
No account executives, no support tier that escalates to someone who has to go and ask. The reply to your email comes from the person who wrote the code it is about.
Fixes ship in days, not quarters
Small and unfunded cuts both ways: there is nobody to chase a bug for you, and nobody standing between the bug and the person who can fix it.
The roadmap is what partners ask for
That is the actual reason the first 10 workspaces are free. Access alone measures usage; a call every couple of weeks tells us what to build next.
What we build with.
Boring, well-understood pieces, chosen so that one small team can hold the whole thing in its head and still ship a fix the same week you report it.
- Interface
- Blazor / .NET 9Server-rendered, one component set
- API
- NestJSREST, and the same one the app itself calls
- Data
- PostgreSQLA separate schema per tenant, not a shared table with a filter
- Identity
- Entra IDSign in with your Microsoft work account, or an email address
- Hosting
- EUSingle region today — ask before you sign up if that matters
Try it, or ask us.
Start on the free core today, or write to contact@produsera.com if you'd rather ask first. A person reads it.