[Draft note for Manuel]: mirror of the ES version — same note about optionally adding your actual methodology (ADRs, C4, etc.) applies.

An architecture mistake doesn't show up on day one — it shows up six months later, when adding a simple feature takes weeks because the system wasn't built to grow that way. This service covers two distinct moments:

Before building: I design the architecture of a new system — what components exist, how they talk to each other (synchronous via APIs, asynchronous via events with Kafka), what database and why, and what scalability and cost trade-offs each decision implies. The result is a document your team can execute, not an idea in my head.

On an existing system: I review production architectures to identify real bottlenecks, technical debt that actually matters (vs. debt that can wait), and scalability risks before they become an incident. Especially useful before a funding round, an external technical audit, or a large migration.

This service doesn't replace your development team — it complements it with an outside, experienced perspective, from systems that can't afford to fail (real-time tracking for a satellite fleet, high-traffic platforms with legacy system integrations).

Got an important architecture decision to make, or a system that no longer scales well? Let's talk.