Security architecture decisions don't come neatly packaged into a sprint. They come up at random — during a migration, when a vendor proposes a new tool, when a regulator sends a questionnaire, when a developer asks whether something is safe to ship. The question is whether you have someone to ask when that happens.
Here's what happens in real projects. The architecture was designed at the start. Then things change:
None of these happen on a schedule. They happen when they happen. And when they do, you need an answer fast — not in three weeks when the consultant can schedule a follow-up, not when the new hire finishes onboarding.
Full-time hire: You have someone to ask. But you're paying €80K+/yr whether you ask or not. And if the question is outside their expertise (DORA when they know NIS2, supply chain when they know IAM), you still need an answer.
One-time consultant: You get architecture at the start. But when the question comes up three months later, the consultant is gone. You're back to figuring it out alone or scheduling another engagement.
Retainer: You pay ongoing for access. But most retainers are expensive, open-ended, and you don't always know what you're paying for. The incentive is to keep billing, not to solve things fast.
The gap is timing. Architecture decisions come up when they come up. If you don't have someone to call, you either delay the decision (risk accumulates) or make it without architecture input (risk materialises). Neither is good.
Not a retainer. Not a sprint. A working relationship with someone who knows your architecture, has seen your environment, and can answer when you call. Specifically:
A retainer says "you have access to our time." The incentive is to use the time — more calls, more meetings, more hours billed. An architect on call says "you have access to answers." The incentive is to solve the question fast so you can move on.
Retainers also tend to be scoped loosely. "Security advisory services" can mean anything, which means it usually means meetings. An architect on call is scoped to specific deliverables: architecture decisions, compliance questions, vendor assessments, security reviews. Things you can use.
If you're running ongoing projects, have regular compliance obligations, or make technology decisions more than once a quarter, you need someone available — not just someone who was there at the start.
If you're a one-time project with no ongoing decisions, a sprint is enough. If you're a large organisation with a full security team, a hire is better. If you're in between — ongoing decisions but not enough to justify a full-time hire — that's where the architect on call fits.
These aren't sprint-sized engagements. They're questions that need answers from someone who knows your environment. That's the difference.
Aethel Guard offers architecture on call — fixed cost, call anytime, fast answers, security architecture included. Not a retainer, not a vendor relationship. Your architect, not your vendor.