Selected engagements from our team's experience

Real challenges. Practical lessons.

A selection from our broader work across business and technology. These short, anonymized case studies explain the challenge, our contribution, and what the customer received. Each also highlights what matters when tackling a similar problem.

Audience: Software companies and development teams
Engagement: Training and adoption support
Focus: Software development with AI agents

Academy / Training and adoption

From AI tools to a shared engineering practice.

The recurring challenge

Even software companies face uncertainty about where to start with AI and how to turn individual experiments into reliable team practices. Employee concerns and the practical questions of organizational adoption also need attention.

Our contribution

We delivered training and helped implement an agentic AI development methodology and framework, making work performed by AI agents part of a shared engineering process.

See the approach in practice

Our open learning toolkit illustrates the method through task templates, exercises, and review criteria. It connects specifications, independent review, and tests. A fictional reference workload lets readers try the complete workflow.

Scope of the engagement

Training in the development methodology and framework
Implementation and adoption support

What teams received

A methodology for working with AI agents and support for introducing it into development. The accompanying learning material makes our approach to task design and quality checks available to inspect.

What matters in a similar project

Build adoption around the team's real tasks. Agree on what the AI can do, what people must review, and the conditions for accepting the result. That gives the team a practical basis for introducing the approach into everyday work.

An anonymized summary of our training and adoption work across engagements. The linked toolkit illustrates our own approach; it is not a customer's internal project material.

Explore the learning toolkit

Customer type: Banking organization
Engagement: Development-process and legacy architecture modernization
Contribution: Advisory and DevOps implementation

Banking advisory / Our team's experience

Modernizing the architecture and the way software gets built.

The starting point

The bank needed to modernize its established development processes and legacy architecture. The engagement addressed both the technical foundation and how development teams worked.

Our contribution

We assessed development processes, advised on process and legacy architecture modernization, and helped introduce DevOps practices.

Scope of the work

Assessment and modernization of development processes
Advisory support for legacy architecture modernization
Introduction of DevOps practices

Why it matters to the customer

Software evolution depends on how the organization delivers change. The engagement supported modernization of both the technical foundation and development practices, bringing both into the scope of the work.

What matters in a similar project

Review architecture, delivery practices, and responsibilities together. Introduce change in manageable steps, with clear criteria for checking each change and evaluating its results.

An anonymized case study from our team's professional experience.

Context: Critical infrastructure
Engagement: System assessment and modernization planning
Scale: Millions of lines of code, primarily C

Critical infrastructure / Anonymized case study

Millions of lines of C. Assessed in weeks.

The challenge

A critical infrastructure system spanning millions of lines of code was being developed using outdated methods. Moving forward required understanding the largely C-based codebase, architecture, and operating model, as well as the risks in development and quality assurance.

Our approach

We combined static, dynamic, and AI-assisted analysis to map the code and system behavior. Alongside the technical assessment, we examined development and quality assurance practices and identified critical risks.

From assessment to a plan

Starting with the current state (AS-IS), we defined the target state (TO-BE) needed to address the risks. We then developed a sequence of steps designed to minimize the risk of making those changes.

What was delivered

An assessment of the system, architecture, and engineering practices
Risk analysis identifying the critical risks
A defined target state and phased transition plan

What the customer gained

A comprehensive assessment and risk-treatment plan in weeks rather than the months originally expected. The work used approximately one-third to one-half of the time and resources in the original plan. Advanced AI-assisted methods and analysis tools played a major role in making that possible.

What matters in a similar project

At this scale, code analysis needs to connect with an understanding of system behavior and engineering practices. A risk register also needs a target state and an actionable transition plan, with the sequence of changes informed by risk.

An anonymized case study from our team's experience. Time and resource figures are approximate comparisons with the original project plan. The result covers assessment and modernization planning.

Customer type: Electric power engineering company
Domain: Industrial supervision and data acquisition
Engagement: System development and methodology consulting

Power engineering / Anonymized case study

Industrial software engineering, backed by development-methodology advice.

The assignment

The engagement involved developing a SCADA system for the electric power sector. SCADA systems support industrial process supervision and data acquisition.

Our contribution

We contributed to system development and advised on the software development methodology. The engagement combined engineering work with guidance on how the development work was organized.

What we contributed

Engineering work on the SCADA system
Software development methodology consulting

The value of the engagement

The customer received support for the software being built and for the development practices behind it. That combined scope connected implementation work with the way the engineering team delivered it.

What matters in a similar project

Define the required system behavior and acceptance criteria before development begins. Carry testing and traceable review through each change, so the delivered result can be assessed against an agreed standard.

An anonymized case study from our team's professional experience. The scope shown covers system development and methodology consulting.

Application domain: Municipal real estate asset management
Starting point: An unsupported GIS-based application
Engagement: Support and minor development takeover

Municipal software / Legacy System Takeover

The vendor left. The system still needed support.

The customer's situation

The previous vendor terminated its contract, leaving the municipality with a property register that nobody supported. The application was built on a third-party geographic information system (GIS) product and required specialist expertise.

What made the takeover difficult

The underlying framework was closed and could not be modified internally. Developers who knew the application no longer worked for the previous vendor. Recovering that knowledge was a prerequisite for taking over support.

How we addressed it

We located developers who had previously worked on the system and used their knowledge to map the application. AI-assisted assessment accelerated our understanding. This enabled us to take over support and minor development work within a short timeframe.

Responsibilities taken on

Support for the existing application
Minor development work

What the customer gained

A knowledgeable technical partner for the previously unsupported system, available within a short timeframe. The customer also had someone to handle smaller development requests within the existing application.

What matters in a similar project

Recovering knowledge and understanding the limits of closed components are essential to this kind of takeover. Former developers' experience and AI-assisted analysis can help establish what can safely be supported and changed.

An anonymized case study from our team's professional experience.

Talk through your challenge

What would you like to change?

A stalled rollout. Too much manual administration. A business idea worth exploring. Tell us what matters to you.

Talk through your challenge