Most writing about Power Platform looks the same: an enthusiastic walkthrough of a new feature, a screenshot from a demo tenant, and a closing line about how much simpler everything now becomes. What is missing is the dull part — what happens to that solution in three years, once somebody else has taken it over, the processes have changed, and a platform migration is due.
That part is the one I find most interesting.
Where I am writing from
I work as a freelance solution architect and consultant. For fifteen years I have been building CRM and business applications on the Microsoft platform — Dynamics 365, Power Platform, ERP integrations, and over the last two years AI agents in Copilot Studio. Between 2017 and 2025 I led a development and consulting team that grew from two people to eight.
The most telling numbers from that period are not about team size, though. They are the start years of individual solutions: 2011, 2012, 2013. Several CRM systems I rolled out early in my career are still running. They have been through two platform generations, a cloud migration, and turnover of people on both sides — and they are still being developed.
That is a perspective you rarely get from typical articles, because it requires staying with one solution long enough to see the consequences of your own decisions.
What this blog will cover
Architecture that survives a handover. Most decisions in a Power Platform project do not show their cost immediately. They show it when another team takes the solution over, or when someone wants to add a capability the original design never anticipated. I am interested in which decisions paid off and which came back as technical debt.
AI agents that actually do something. I currently design and deliver agents in Copilot Studio. Not chatbots that answer questions, but agents that process an incoming e-mail on their own, classify it, open a deal in CRM, and report the result back to the team. The gap between a demo and production is unusually wide here, and worth documenting.
AI-assisted development on real projects. Working with AI lets me run more projects in parallel than I could before. That is not a marketing line — it changed how I work. It also has sharp edges, and those do not make it into the enthusiastic posts.
ALM and CI/CD on Power Platform. I built CROMA as a product on Power Platform with strong CI/CD support. Moving solutions between environments is an area where mistakes are easy to make quietly and expensive to discover late.
What this blog will not cover
No client names, and no details of their processes. On the projects page I describe the segment, the scope and the technologies used — nothing beyond that. Fifteen years of signing agreements has made me take confidentiality seriously, and the company name was never the interesting part anyway.
There will be no recycled documentation either. If I write something up, it is because I ran into it in production.
How often
Irregularly. I would rather publish fewer pieces worth reading than keep a schedule for its own sake.
If any of this is relevant to you, or you are looking for someone to design a solution, write to me at vit.lachner@email.cz or on LinkedIn.