Bram Verswalm
CEO, Caplo
Caplo started with a frustration I experienced from both sides of the enterprise architecture industry.
I spent five years as an enterprise architect before joining LeanIX, where I helped build its Technology Risk and Management product through a period of rapid growth. Across those roles, I kept seeing the same problem: enterprise architecture tools were built for specialists, but the knowledge they depended on remained fragmented across teams, documents, tools, and people's heads.
Business teams
Worked in slides, spreadsheets, whiteboards, and documents. Plans were made where the work already happened.
Architects
Chased that information and translated it into models. By the time architecture became involved, important choices had often already been made.
Repositories became incomplete or outdated, not because architects did not see their value, but because the rest of the organisation could not easily contribute.
As long as EA tools aren't providing enough value and aren't easy enough to use, business users will keep making plans elsewhere.
The arrival of generative AI created an opportunity to change that. What if enterprise architecture could become a multiplayer discipline? What if business teams could explore an idea in their own language, while AI connected it to the organisation's applications, capabilities, processes, standards, and existing initiatives? Architects could then review and guide the decisions that genuinely require their judgement.
That is why Pieterjan and I started Caplo.
