About

Enterprise experience. Hands-on AI delivery.

Last Requirement is a founder-led practice. One person owns the engagement, and the delivery method is built so that a small practice can carry real work without hiding who is accountable.

Gunnar Kristoffer Wold

Gunnar Kristoffer Wold

Founder, Last Requirement · Working with clients globally

Gunnar helps organisations turn AI capabilities into useful, dependable systems. He brings more than 20 years across software engineering, product development, enterprise data management and technology leadership, with experience in financial services, insurance, aviation, media and the public sector.

That background addresses some of the hardest challenges in adopting AI: understanding what a business actually needs, deciding which information to trust, connecting existing systems and helping people change how they work. His experience in business analysis and requirements helps turn broad ambitions into clear, testable tasks for both people and agents.

His grounding in architecture and software delivery helps keep rapid AI development maintainable. Years of coordinating cross-functional and distributed teams inform how he structures agent workflows: clear responsibilities, manageable tasks, explicit dependencies and review against agreed outcomes.

Today, Gunnar combines that experience with hands-on work in AI agents, knowledge retrieval, self-hosted models and business software. He helps organisations decide where AI adds value, what it needs to work reliably and where human expertise remains essential.

He holds a Master’s in Computer Science and an MBA in Technology Management, bringing technical depth and commercial judgment to AI adoption.

What we believe

01

Understand the work

Learn how the job is actually done before choosing what to build.

02

Keep architecture deliberate

Decisions get recorded, so they can be questioned rather than inherited.

03

Build systems people can change

A system your team cannot modify is a system you will replace.

The last requirement is often the one that reveals what the system really needs.

Requirements keep emerging during delivery. The method exists to notice them rather than resist them.

Discuss your project