Systems
These aren't product demos. They're real projects — the problem as it existed, the architecture we designed, and what changed once the system was running.
Field Operations Platform
From Excel screenshots on WhatsApp to real-time operations.
Custom CRM
A CRM that tracks relationships, not pipelines.
An apple farm. The Belgian elections. An IT support company. The non-profit Gabriel coded for at 16.
They deserved better than a template, don't you?
Stop wedging it into someone else's template.
“Could you do this for us?”
Probably — though “similar” rarely means “identical.” Every company has its own processes, data, and team structure. The architecture principles stay the same; the specifics are yours. It starts with a conversation to see if we’re a fit.
A typical shop builds what you ask for. We push back until we are sure what you actually need. Most of the value gets created before any code is written: deciding what to build, what to skip, and how it all fits together. Getting that right is what makes the code worth writing.
We integrate with all of them. For some companies the answer is “keep what works, build around it.” For others it’s “migrate to something you own.” We tell you which — based on your situation, not on which one earns us more work.
If you’d prefer an NDA before the conversation gets into the details of your situation, mention it when you reach out and we’ll work it out. For most exploratory calls it isn’t needed, but it’s something we can sort out when it matters.