Hubsays Proof
A short public scan of outcomes, systems work, and the parts worth putting on the table.
Selected Proof

Commercial outcomes, systems judgment, and evidence that stays readable.

This is the fast-scan version. The point is not to dump every artifact in public. The point is to show the strongest measurable outcomes, the shape of the systems work, and the operating posture behind it.

If you need the shortest route into the story, start here, then go deeper through Brendan’s profile, the architecture gallery, or the public GitHub surface.

Headline proof

A few numbers that explain the shape of the work quickly.
ARR
$6.8M+

Net-new ARR contribution at Atlassian, including a stretch where the output landed around 27% of team production.

Portfolio
EUR 1.5M+

Enterprise portfolio ownership across 40+ accounts, with product adoption and renewal pressure living in the same lane.

Adoption
22%

Time-to-value reduction driven by clearer onboarding, cleaner handoffs, and tighter internal coordination.

Account Base
750+

Enterprise accounts touched across scaled portfolio work, enablement loops, and customer-facing execution.

What the proof actually says

Revenue and systems work belong together because the handoff between them is where a lot of good work usually dies.
Commercial

Revenue and retention work that stayed measurable

The strongest commercial signal is not just one big number. It is repeatable contribution across portfolio ownership, expansion, adoption, and lower friction between teams.

That includes $6.8M+ in net-new ARR contribution, a EUR 280K+ expansion close, and churn pressure reduced through more structured customer systems.

Read the time-to-value case
Systems

Bounded automation instead of automation theater

The systems work leans toward deterministic artifacts, human-in-the-loop control, auditability, and local-first operation. The aim is not shiny agent demos. The aim is repeatable judgment under pressure.

Public-safe examples include release auditing, structured output validation, privacy-first operating rules, and architecture notes that can be inspected without giving away the private loop.

Read the live tooling loop
Operator Signals

Strategic depth shows up outside work history too

Multi-agent chess, game design, and product building are not side decoration here. They sharpen long-horizon planning, counterplay thinking, and trade-off discipline in a way that translates directly into architecture and delivery work.

That is part of why the public studio now includes active game lanes beside the systems writing.

Read the chess note

Go deeper from here

The next click depends on whether you care most about the person, the operating model, or the artifacts.
Profile

Brendan Davies

The recruiter-safe profile pulls together role fit, selected proof, public product lanes, and the cleanest route into the broader story.

Open the profile
Architecture

Operating model and system notes

The architecture gallery is where the public-safe implementation detail lives: system shape, delivery logic, and the reasoning behind the build.

Open architecture
Code

Public GitHub surface

Scanners, audits, deterministic helpers, and tooling that came out of real work rather than decorative portfolio filler.

Open GitHub