Observability
SLOs before dashboards
Most observability spend is decided before anyone agrees what good looks like. That ordering is why the bill grows and the signal does not.
6 min read
Practice 07
Solution Engineering and Delivery
When the roadmap needs building, we build it.
Engagement shapes
Discovery and shaping
2 weeks
Milestone delivery
Priced per milestone
Embedded squad
Monthly
Production hardening review
3 weeks
Who this is for
- Clients who have the plan and lack the capacity
- Teams who want the people who wrote the roadmap accountable for the result
- Organisations moving a proof of concept into production
The problem
A roadmap handed to a team with no spare capacity becomes a document. The gap between advice and delivery is where most consulting value leaks away.
Proofs of concept fail to survive production because the properties that matter in production, observability, failure handling, and operability, were never in scope.
What we do
The workstreams in an engagement
01
Embedded delivery squads
Working alongside your engineers, in your repositories, under your review process.
02
Platform engineering
CI/CD, environments, golden paths, and the developer experience that makes them the easy option.
03
Secure SDLC
Gates, scanning, policy-as-code, and release evidence that satisfies an auditor without stopping delivery.
04
Data and AI platform builds
Ingestion, storage, serving, and evaluation, built for the use cases already chosen.
05
Integration engineering
Identity, ticketing, SIEM, and data systems connected and operable.
06
Production hardening
Taking a proof of concept through the properties production actually requires.
Deliverables
What lands on your desk
You keep all of it, including the method behind it, so the work can be repeated without us.
- Working software in your repositories
- Runbooks and an on-call plan
- Test and evaluation suites
- Architecture decision records
- A handover that leaves your team able to operate it
Standards we work against
- OWASP ASVS and SAMM
- SLSA supply-chain levels
- OpenTelemetry specification
What we do not do
- We do not take delivery work we cannot staff with people who have done it before.
- We do not hand over software without runbooks.
Engagement shapes
Three sizes, not one package
Durations are indicative and depend on estate size. Scope and price are fixed in writing before the engagement starts.
| Shape | Duration | What you get |
|---|---|---|
| Discovery and shaping | 2 weeks | Scope, architecture direction, and a delivery plan |
| Milestone delivery | Priced per milestone | Agreed increments with acceptance criteria |
| Embedded squad | Monthly | Sustained capacity inside your delivery process |
| Production hardening review | 3 weeks | A gap list and the work to close it |
Related insights
Our thinking on this
Next step
Start with a briefing, not a proposal.
Thirty minutes on solution engineering. We will tell you whether we are the right firm for the problem, and who to talk to if we are not.