Architecture for the load you have now and the team you have now. We write down the boundaries, the data flow and how it gets deployed, argue about it with your engineers, then build it.
Service boundaries drawn around who owns what, not a diagram copied from somewhere else. Most architecture pain we see is an org chart mismatch, not a technology problem.
Where data lives, who is allowed to write it, and what happens when two systems disagree about it. Usually the first document of its kind the org has had.
Sized for the traffic you actually get and the on-call team you actually have, not the one you might have in three years.
We do not hand over a diagram and disappear. We write the migration plan and stay through the part where it gets implemented.
Every new feature seems to require touching the same three services, and nobody planned it that way.
A migration keeps getting pushed to next quarter because nobody wants to own the plan.
You are about to make an infrastructure decision that is expensive to reverse and want a second set of eyes before you commit.