Internal business tools
A person in operations, finance, or sales built something genuinely useful with AI. It works. It is also not deployed, not secured, not documented, and not something IT will sign off on. That gap is what we close.
We sign NDAs as standard. Your code, your infrastructure, your data — we work inside your constraints, not around them.
It is almost never the feature work. An internal tool stalls because it cannot pass review, cannot be maintained, or cannot reach the systems it needs. Six versions of the same week we keep having:
The tool works and the department wants it, and it still cannot go live. Usually it is credentials in the source, no audit trail, permissions that do not distinguish an admin from an intern, or data sitting somewhere with no backup. We fix the substance and write the document your security reviewer is asking for.
Someone in operations or finance built something genuinely useful in Lovable or Cursor, and now they have their real job to do — or they have left. Nobody else can safely change it. We take ownership of the code, document it, and hand it to your team in a state they can maintain.
A tool that does not talk to your ERP, CRM, or directory is a second place to type things. We build the integrations and the sync, so it stops being an island.
Almost every AI-built internal tool starts with a single shared password and no roles. We add real authentication against your identity provider, proper role separation, and a log of who changed what.
Getting it onto infrastructure you control — your cloud account, your network, your backup policy — is usually a few days of work that nobody in-house has time to own.
If it holds personal data, GDPR applies whether or not anyone has thought about it. We map what it stores, where it goes, and what has to change, and put it in writing.
We read the code and the deployment, then hand you a written assessment: what blocks approval, what breaks at scale, what it takes to fix each item. Something you can forward to IT.
We close the gaps in priority order — access control, integrations, audit trails, data handling — without rebuilding what already works.
Deployed on your infrastructure, monitored, documented, with your team able to maintain it. No dependency on us afterwards.
The instinct when an internal tool stalls is to either rebuild it as a proper project or buy software that almost fits. Rebuilding discards work that already encodes how your business actually operates — the edge cases someone spent months learning. Buying means changing your process to match a vendor's assumptions.
Finishing what you have keeps the domain knowledge and costs a fraction of either. The review is €750 and tells you exactly what the rest would cost before you commit to anything.
Start with the review
€750 for a written assessment you can hand to IT and finance, credited against the build if you continue. The first 30-minute call is free and you will get a straight answer on whether this is worth doing at all.