Four shapes that most Tropibyte work takes. If yours does not fit any of them, say so in the first email. The shape matters less than whether the problem is one I can actually help with.
A written assessment of a Windows codebase: architecture, risk, dependency and toolchain health, test coverage, and a prioritized remediation plan. Delivered as a document you own and can hand to anyone. Frequently the first step before a larger engagement, and frequently the only step needed.
Taking a shipped Windows product that has become difficult to change and making it changeable: builds that reproduce, tests where there were none, the crash class that has resisted diagnosis.
.NET Framework to .NET 8. Win32 or MFC to WinUI. Incremental and shippable at every step; no rewrite-and-pray.
Ongoing senior capacity for a team without a native Windows specialist: architecture decisions, code review, and being the person who can answer the hard question.
Most engagements start as an audit and turn into something else once the actual state of the codebase is clear. A short email describing the problem is enough to work out which shape makes sense, and you will get an honest answer within one business day, including when the answer is that I am not the right person for it.
