Twenty years of building things that have to hold up.

From the workshop to the cloud.

I started in a carpentry workshop before I ever touched a line of code. My family ran a small joinery business in Poland, and by my teens I was framing roofs, cutting structural timber, and learning precision the hard way — where a millimeter of error shows up years later, in a door that won't close or a roofline that won't sit right. "Measure twice, cut once" stopped being a saying and became a habit.

I trained as an electronics and IT systems technician, then spent the next two decades doing something that probably shouldn't have worked as well as it did: building a career in Microsoft cloud and SaaS sales — Microsoft 365, Power Platform, Dynamics 365, Azure — while never actually putting the tools down. I restored a wooden yacht plank by plank. I built custom furniture to client specification. I designed and built my own house, foundation to finish. On weekends I renovated apartments — plastering, wiring, flooring — for people who needed it done right, not just done.

Along the way I built a sales department from zero, launched partner and reseller programs, automated CRM systems for companies selling everything from identity-verification software to IoT fleet monitoring, and earned Microsoft's CSP and AEP partner certifications. In 2018 I founded my own Microsoft cloud consultancy. Framewright is the next chapter — built specifically for small and mid-sized businesses that need someone who understands both the technology and what it actually takes to run a hands-on business, because I've done both.

Measure twice. Cut once.

In construction, a mistake you don't catch early doesn't stay small — it gets built over, buried, and expensive to fix later. Technical debt works the same way: a website nobody can update, a CRM three people configured three different ways, a sales process that only works because one person remembers all the exceptions. Framewright's job is to catch that early. We assess before we build, prioritize before we spend, and build systems that are still working the way you expect three years from now — not just the day we hand them over.