Lucas Oliver
Founder & Head of Architecture
Connects the business problem to the system behind it. Our founding vision is to build stronger organizations through clear thinking, useful technology and people who grow in capability.
People & purpose
We’re building IAC around a shared belief: better technology should make people more capable, and organizations stronger.

From the founder
We’re building IAC to make things better: the technology, the customer experience and the way people develop through the work.
We want to understand the problem deeply, make complicated things understandable and take responsibility for what we build. The tools matter because of what they help people accomplish.
“Leadership should multiply capability, not concentrate it.”
Lucas Oliver Founder & Head of Architecture
Read the founding perspectiveThe people behind IAC
The perspectives connecting our business, technology and delivery.
Founder & Head of Architecture
Connects the business problem to the system behind it. Our founding vision is to build stronger organizations through clear thinking, useful technology and people who grow in capability.
Head of AI & Development
Brings AI and software development into the same conversation: what can we build that makes a real task easier to understand, decide or complete?
Head of Business Systems & Integration
Focuses on the connections between customer information, collaboration and operational work, shaping business systems that support a more coherent day-to-day experience.
Head of Finance
Leads the finance discipline within IAC, bringing financial stewardship to the foundation of the business as it develops.
Head of Business Development
Focuses on business development: understanding where IAC can help and connecting the right business challenge with a useful next conversation.
Head of Delivery & Coordination
Connects people, decisions and delivery commitments. Laura’s focus is clear next steps, useful communication and handoffs that help the team keep work moving.
What we believe
Our principles should be visible in the way we work, especially when the work gets difficult.
Listen closely. Find the actual problem. Be willing to challenge the first request when a better outcome is possible.
Make assumptions and tradeoffs visible. Surface problems early. Fix what is broken instead of hiding it.
Document what matters, share what we learn and build systems that people can carry forward.
Test the work. Protect the information. Take responsibility for the commitments we make.
A better way forward starts here
Bring the challenge. The messy process.
The idea you haven’t found the words for yet.