About
Hands-on Architects is the joint practice of Maciej Laskowski and Tomasz Michalak. We are two software architects, with 15+ years each, still writing and reviewing code. We work with engineering teams and the leaders responsible for how they build and run software.
Why both of us
We both join the initial conversation and shape the high-level plan. Whoever is closer to the problem leads; the other one pressure-tests.
One of us develops the first iteration. The other reviews the assumptions, options, and consequences. We work through the revisions together, sometimes switching who leads the next iteration. Both of us understand the problem and contribute to the recommendation you receive.
We both work across system design and production. Our different interests help us examine the same problem from more than one perspective.
Maciej is especially drawn to the shape of a system: which boundaries make sense, which options are worth considering, and what each trade-off means over time. He brings that perspective to the team's decisions while considering how the system will be built, operated, and changed.
Working through disagreement
We do not always start with the same view. We work through our differences before bringing you a shared recommendation, with the trade-offs and remaining uncertainty made explicit.
Your team brings the product, domain, and operating knowledge. We explain our reasoning, challenge decisions when we see a problem, and change our position when new evidence calls for it. The decision stays yours.
If we cannot agree on a useful way forward, we discuss it directly. We can agree to stop the engagement rather than keep working without an agreed direction.
Working arrangements
Small, task-based engagements
We work on AI adoption, architecture decisions and reviews, and how teams build and deliver software. Each engagement starts with a bounded question, agreed work, and a written output. Your team takes part in the work.
See how an engagement starts →Mostly asynchronous
We prefer asynchronous collaboration, with live working sessions for the questions that need a conversation. We agree the working arrangement with you for each engagement.
If one of us is unavailable, the other continues where the work allows. Some decisions still need both of us. We plan independent work and shared sessions around those dependencies.
One engagement at a time
We each hold a full-time role alongside HoA and take on one HoA engagement at a time. We agree availability and scope before starting. We only accept work that does not conflict with our full-time employment.
Two invoices, one team
You sign one engagement agreement covering both of us. Each of us invoices through our own registered company, so you'll get two invoices for one team.
Our thinking, in public
We publish The Harness Model and articles on AI adoption, architecture, and engineering. They show how we reason about the work and give you something to examine before we talk.
Read the blog →Get in touch
Tell us what you're deciding - an architecture call, a review, a delivery-process or AI-adoption question - and we'll tell you plainly whether we're the right fit.
Get in touch →