Decision brief — 01

Protect the outcome.Make the trade-offs visible.

I’m René Brauwers. I help Business and Engineering turn strategy, risk and complexity into decisions teams can execute.

  • Head of Enterprise ArchitecturePerpetual Corporate Trust
  • Former Microsoft Azure MVPBuilder credibility, carried forward
  • Sydney, AustraliaRegulated financial services
Editorial illustration of René winking beside a human-guided architecture and AI decision pathway.
Builder → advisor → enterprise decisions

What I bring to the room

Clear decisions that survive contact with delivery.

  1. Decision clarity

    Frame the real problem, expose the trade-offs and give leaders a recommendation they can act on—with cost, risk and operating consequences visible.

  2. Architecture teams use

    Turn strategy into practical guardrails, patterns and roadmaps that help Product and Engineering move with confidence and speed.

  3. Responsible modernisation

    Apply cloud, data, integration, automation and AI where they create real advantage—with safety, governance and regulatory rigour designed in.

Builder to advisor

Engineering reality belongs in the boardroom.

My foundation is hands-on: software, enterprise integration, automation and cloud. It lets me move from executive consequence to engineering reality without losing either. That grounding matters when a clean strategy meets legacy constraints, delivery pressure and the consequences of operating change.

Today I lead Enterprise Architecture at Perpetual Corporate Trust, working across Business, Engineering, Product, Data, Security and Risk to improve technology decisions in a regulated environment.

Earlier in my career I was recognised as a Microsoft Azure MVP and contributed through technical writing, book reviews and community sessions. The products changed; curiosity and practical judgement stayed.

Operating position

Architecture earns its place by improving the decision.

My role is not to create more architecture. It is to make the consequences of a choice clear enough for people to act.

Start with the outcome

Lead with the business consequence and the decision that needs to be made. Technology comes after context.

Make trade-offs explicit

Good advice makes cost, risk, reversibility and organisational impact understandable—not artificially simple.

Stay close to delivery

Strategy loses value when it cannot survive engineering reality. Keep the feedback loop between intent and execution short.

Protect the outcome, not the architecture function.

— An operating principle

Systems thinking

Fix the system, not the symptom.

Most problems that reach a decision forum are symptoms. I look for the loop that produces them, so the fix holds and the next decision gets easier rather than harder.

  1. Root cause before the fix

    Trace a problem back to what keeps producing it before choosing the remedy. A fix that skips the cause tends to come back with interest.

  2. See how the pieces connect

    People, process, platforms and data behave as one system. Mapping the dependencies stops a local change from creating a distant failure.

  3. Trade-offs in the open

    Cost, risk, reversibility and operating impact sit side by side, so the people who are accountable can choose with their eyes open.

  4. Evidence over gut

    Tests, telemetry and real usage settle the argument. Opinion can start the conversation; evidence should finish it.

  5. Prevention over recovery

    Guardrails, automation and short feedback loops stop the same incident from happening twice. Recovery still matters; it just shouldn’t be the plan.

Things I’ve built

The builder never left.

Personal projects built in my own time, described here rather than linked. They keep my advice honest about what it takes to design, test, ship and run a working system.

  • Live

    A browser maze game

    An immersive maze game for phone and desktop, built on a .NET engine that procedurally generates mazes as JSON blueprints. Free play needs no account, download or payment; optional blockchain features sit behind independent release flags.

  • Unreleased prototype

    A practice-management prototype for a veterinary clinic

    Born from a conversation with a mate who is a vet: a practice operating system for a single clinic, with the animal as the clinical spine. An offline-capable field app for staff, voice-drafted notes that a person reviews, and a separate portal for owners. Staff make and sign every clinical decision.

  • Personal use

    An automated asset-accumulation system

    A deterministic, auditable, fail-closed system that accumulates a digital asset on a public ledger. Strategy, risk, signing, submission and reconciliation never depend on an LLM, and it runs only from accepted, immutable container images.

  • Work in progress

    A character-creation and catalogue platform

    A container-first .NET and React platform for generating and curating characters with AI, with a prompt studio that audits every rendered prompt, encrypted provider secrets, multi-factor sign-in and privacy controls such as customer export and erasure.

  • Personal use

    A sensor-driven room pet

    A small ESP32 device with air-quality, CO2 and climate sensors that gives a room a personality and nudges you to ventilate, heat or cool. A self-hosted .NET control centre manages telemetry, character profiles and signed over-the-air updates.

  • Work in progress

    Crypto tax and portfolio tooling

    Tools that reconcile crypto transactions and estimate Australian capital gains: FIFO lot accounting across the July to June financial year, the 12-month discount, strict validation with per-transaction traces, and historical AUD price downloads.

  • Live

    This website

    ASP.NET Core Razor Pages behind an nginx gateway, a governed content studio, a privacy-first recruiter portal, and CI that tests and scans every change before publishing container images.

  • 2010 to 2017

    Enterprise integration tooling

    Years of .NET integration side projects: custom mapping functions and REST message inspectors for an enterprise integration platform, a dynamic WCF service host and invoker, and a cloud orders API demo built for a community integration event.

Human direction / Machine execution

The new working model.

Yes, this website was coded by AI. I’m the mere mortal who supplied the guardrails, intent and judgement. Welcome to the new world.

The machine accelerated the execution. I remained accountable for the choices, standards and outcome—the same model I expect wherever capable technology meets consequential work.

A clearer conversation

A difficult technology decision?

If it sits between business ambition, risk and delivery reality, I’m always open to comparing notes.

Recruiters and talent partners: I don't publish an email address. Sign in to the recruiter portal (or request verified access) to get in touch and view my full profile and resume.