FAQ
Common questions about how I work and what to expect.
What does a typical engagement look like?
Most engagements start with a discovery phase — understanding your current architecture, constraints, and goals. From there, I either deliver an architecture roadmap your team executes, or I embed part-time to help implement it. Engagements are typically 10-20 hours per week.
Do you write code or just advise?
Both. I'm hands-on when it adds value — writing proof-of-concepts, reviewing pull requests, or pairing with your senior engineers. But my primary value is in design decisions, technical direction, and unblocking your team. I won't be your full-time developer.
How long do engagements typically last?
3-6 months is typical for architecture and migration work. Some clients keep me on retainer for ongoing advisory after the initial engagement. I don't do one-week projects — meaningful architecture work takes time.
Do you work remotely?
Yes, fully remote. I'm based in Milwaukee (Central Time) and have worked with distributed teams across the US. I'm flexible on meeting times and async communication.
What size companies do you work with?
Typically mid-size companies (50-500 employees) and growth-stage startups with real technical complexity. I've also worked with enterprise teams inside larger organizations. If you have a legacy system and a team that needs architectural guidance, we're probably a fit.
How do you handle confidentiality?
Seriously. I sign NDAs, I don't name clients without permission, and I understand regulated industries (HIPAA, PCI, SOC 2). Your architecture and business details stay confidential.
What if we need to adjust scope mid-project?
It happens. Architecture work often reveals surprises. I'm flexible on adjusting hours and focus as priorities shift — we'll figure it out together.
Have a question that's not here?
Get in touch →