I’m James Blewitt, an enterprise architect and Principal at Netlight, based in Munich. I work with business leaders and engineering teams to turn business goals into technical direction, organisational change and working software.
From software engineering to enterprise architecture
My career spans more than twenty years, from software research and hands-on engineering to architecture, engineering management and executive advisory. Since joining Netlight in 2011, I’ve built and launched products, led engineering teams, shaped technical roadmaps and assessed technology organisations as part of acquisition decisions.
I’ve also worked as a software founder and CTO, building and launching a personal financial planning product and developing a data mining and business intelligence product. That experience informs how I approach architecture: decisions need to make sense for the product, the people building it and the business paying for it.
Selected experience
- Establishing enterprise architecture. At a leading European online pharmacy, I supported the creation of an enterprise architecture function, working with executive stakeholders on capability modelling and application portfolio management. I also supported the recruitment of a permanent architect to carry the work forward.
- Architecture in a regulated environment. As lead architect on a medical technology data platform initiative, I worked on the technical roadmap across participating teams and aligned engineering guidelines with the requirements of systems intended for medical certification.
- Technical leadership through expansion. For an automotive retailer expanding across Europe and into leasing, I worked as an engineering manager and lead architect, aligning teams around a shared technical direction. The work included unified authentication and customer self-service.
- Building core product capabilities. As lead engineer and solution architect, I developed a dynamic pricing engine for a European car-sharing business, combining architectural responsibility with hands-on implementation.
- Technical due diligence. Across multiple acquisition assessments, I evaluated software architectures, engineering practices and organisational structures, and presented findings to senior management to support their decisions.
How I work
I’m particularly interested in the connections between business capabilities, software boundaries and team ownership. I use architecture to make choices clearer: where to invest, what to build or buy, and how to organise the work so teams can deliver.
My approach is pragmatic. A model should help someone make a decision. A technical roadmap should reflect business priorities. And an architectural recommendation needs to account for the effort of implementing and maintaining it.
Why I write
This site is where I explore those ideas: software architecture, capability-based planning, technical debt and the changing economics of building software with AI. I write to make useful concepts accessible, question assumptions and share the judgment I’ve developed through practice.
Outside work, I’m a father, an Englishman living in Germany, and a lover of food and travel.
If these are challenges you’re working through too, connect with me on LinkedIn.