Real engagements.
Real findings.

Situation

An existing app built by a team without sufficient experience for the complexity involved. Further development felt risky — it was unclear whether the foundation could support what the product needed to become.

Finding

The codebase reflected the experience gap: structural decisions that would block future development, no clear architecture and significant uncertainty about where and how to extend the system safely.

Outcome

Audit with concrete measures and an architecture blueprint — a documented foundation the team could build on with confidence, and a clear picture of what needed to change first.

Situation

A nearshoring agency had built a custom WMS. Before investing further — more customers, cloud operations, SaaS growth — the client needed an honest answer: what did we actually receive, and is it a foundation we can build on?

Finding

The system was technically solid — modern stack, clean architecture, CI/CD already in place. Better than comparable nearshoring projects. But the real challenge wasn't code quality. The system had no production-ready security (credentials committed to the git repository), no multi-tenancy, no cloud configuration — and the entire development and deployment capability was locked inside one external agency. Not a vendor. A single point of failure.

Outcome

Strategic orientation across four decisions: architecture (Multi-Instance confirmed — no expensive Multi-Tenant rebuild), a two-phase hosting roadmap (Azure for early growth, Hetzner at scale), a prioritised security action plan, and clarity on what it actually takes to turn a working internal tool into an operated software product.

Situation

An important milestone was approaching with an unrealistic timeline — and a key developer had just left the team.

Finding

The agreed scope couldn't be delivered in the remaining time regardless of capacity added. The timeline had been set without technical input and had never been realistic.

Outcome

Scope reduced to what was achievable. Roadmap restructured. Stakeholders aligned on a realistic plan — milestone delivered without a crisis.

Situation

10 months invested in an automation project — only one task delivered. The vendor kept reporting progress but nothing was reaching production.

Finding

The problem wasn't technical capacity. There was no clear accountability structure, no defined handoff points and no shared understanding of what 'done' meant.

Outcome

Process restructured with clear weekly goals and ownership. Remaining automation goals reached within 6 weeks after the changes.

Situation

The app in the App Store had stopped working. Updates were impossible — the codebase was too outdated to maintain or extend.

Finding

Deprecated libraries, no CI/CD, no developer with active knowledge of the code. The existing codebase had no viable path forward — a rebuild was the only realistic option.

Outcome

Clear recommendation with scope and approach defined. App relaunched with a maintainable codebase and stable update process.

Situation

€10,000 invested in an MVP — but the result wasn't usable for testing market fit. The UI looked complete, nothing worked underneath.

Finding

No working backend, no data handling, undocumented and unmaintainable code. The vendor had delivered a prototype that couldn't be built upon.

Outcome

Audit documented what existed and what was missing. Clear scope defined for a lean, testable rebuild focused on what actually needed to work.