Consulting · Contracting · Platform Architecture

Bring me in when the AWS estate technically works but operationally nobody trusts it.

I help teams clean up platform sprawl, put guardrails in the right layer, modernise awkward workloads, and cut through the process theatre that slows delivery down.

Download consulting resume See selected work →

What you get

Direct engagement, not account management layers.

Best Fit

Platform estates with unclear ownership, noisy controls, expensive runtime habits, and too much manual governance.

Typical Outcomes

Cleaner boundaries, stronger reporting, safer delivery defaults, and less wasted compute.

Bias

Hands-on, blunt, implementation-led work. Not architecture theatre.

Proof surface

Useful because the work changes operating behaviour, not just diagrams. Public-facing examples:

Governance & Controls

✓

Improved compliance execution in regulated AWS estates through guardrails, reporting, control redesign, and better ownership flow.

Cost & Operating Discipline

$$$

Delivered material annual savings through commitment optimisation, workload reshaping, lifecycle control, and tighter platform habits.

Workload Modernisation

ECS

Moved long-running workloads into cleaner event-driven patterns with better isolation and scaling behaviour.

Reliability Under Pressure

20→0

Reduced critical website dropouts for Australian Museum from roughly 20/day to zero through architecture and performance fixes.

Three recurring problem shapes

What I usually help with.

AWS governance reset

Fix where SCPs, detective controls, exceptions, ownership, and reporting have drifted apart.

Platform operating model cleanup

Untangle platform, security, and delivery boundaries so the platform becomes easier to trust and easier to use.

Workload and cost modernisation

Rework runtime and lifecycle choices that create cost drag, scaling pain, and fragile operations.

How I work

Find the operating constraint first.

I'm usually most useful when a team already has dashboards, tickets, policies, and committees, but still cannot explain who owns the real boundary or why the platform behaves the way it does.

What I avoid

No appetite for architecture cosplay. If the goal is to produce a shiny target-state deck with no implementation path, I'm the wrong person.

Engagement shapes

Different entry points. Same bias toward practical change.

Short Intervention

Assessment and direction

Fast review of platform governance, workload shape, or cost discipline with a blunt set of findings and a practical sequence of fixes.

Hands-On Delivery

Contracting / implementation

Come in and build the missing pieces: guardrails, reporting, workload boundaries, delivery automation, or the migration plumbing nobody wants to own.

Bridge Role

Architect who still ships

Useful when a team needs architecture decisions grounded in actual platform delivery rather than slideware or committee output.

Strong fit vs weak fit

Where I tend to add value fastest

AWS estates with governance debt and ownership blur
Teams stuck between architecture intent and operational reality
Modernisation work where runtime shape matters as much as code
Cost problems caused by platform design, not just spend visibility
Environments that need practical leadership without management fluff

Where I'm probably the wrong hire

Pure strategy work with no implementation path
Teams looking for a generic cloud cert consultant
Long discovery projects that avoid hard technical decisions
Places that want architecture documents more than platform change

How to start

The first useful conversation is simple.

Tell me what is messy.
Tell me what is politically sensitive.
Tell me what is costing time or money.
I'll tell you where the real problem probably is.

Book a conversation

Prefer email? [email protected] Review selected work →