About Susipere — technology practice with clarity for decision-makers

Susipere is an operating practice for technology decisions, not a blog about AI trends. This page covers who the work is for, what the three working modes actually involve, where the boundaries are, and why looking across six areas at once — rather than from a single specialism — is what makes an assessment hold up.

Who this is for

Susipere is built for decision-makers and developer teams who have to own a technology decision, not just try one out. The usual starting point isn't general curiosity about AI — it's a specific call to make: should this AI system go live? Which toolchain does the developer team adopt? Where does an automation change a data flow that someone has to be able to justify to a regulator, a board or a customer? Anyone answering these questions doesn't need another primer on AI or cybersecurity — they need an assessment that still holds up under hard questions afterwards. That applies equally to a company introducing its first agentic system and to a developer team resetting its toolchain and review standards.

Three working modes

The work happens in three modes, used alone or in sequence depending on where a decision stands:

Workshops & audits. A workshop puts the team and the decision in the same room: the use case, system boundaries, risks, and what actually happens in production when something breaks — not just what works in a demo. An audit checks an existing system or process — a toolchain, an agentic system, a data flow — against concrete criteria instead of a gut feeling. What comes out is not a slide deck of general principles but a list of findings a team can work through, ordered by what would break first.

Technology reviews. A structured assessment of a tool, framework or vendor before a selection decision gets made: what it actually does, measured against what the marketing claims; where it breaks down alongside the systems already in place; what adopting it means for security, data protection and day-to-day operation, not just for the pilot. The output is an assessment a team can use to make and later defend a decision — not a tool recommendation without context on the team's own setup.

Implementation support. The rollout itself: workflows, approvals, review points and documentation, until a system actually holds up in a team's daily work — not just in acceptance testing. That includes hands-on technical implementation where it's needed, and it doesn't end with handing over a concept to a team that then has to carry it alone.

What Susipere does not do

This is where an operating practice differs from a trend blog:

• No assessment of a tool or approach that hasn't been checked against a real system, in-house or for a client.
• No general tool rankings or best-of lists detached from a concrete deployment context.
• No forecasting about where "AI" as a whole is headed.
• No advisory work that ends with a slide deck and no one following through on, or even checking, the implementation.
• No published assessment that isn't backed by a real system or a real engagement.

If a request falls outside these boundaries, that's a decline, not an exception — the scope doesn't get stretched just to take on the work.

Why the operator's view holds up

The work spans six areas that are entangled in real operation, not separable in practice: AI systems, software development, cybersecurity, data protection, automation and governance. An agentic system is, at the same time, a software development project, a security risk and a governance matter with a documentation requirement. Bring only one of those three perspectives and the other two go unnoticed until they surface in production — usually at a point where fixing them costs more than checking for them would have. Susipere brings all six areas into the same assessment, because those are the questions a system in production actually raises, not the questions a product demo answers.

Next step

Anyone who needs to settle one of these questions — before a tool selection, before a rollout, before a review by a regulator or a customer — can get in touch directly. A short description of the use case and the decision at hand is enough to start a conversation.