§ 05 · About Melbourne · 00:00
37.81° S 144.96° E

A solo studio built to scale.

I run Day Zero Projects as an independent AI operations studio for Australian businesses that have outgrown informal operations. The work exists because most businesses are trying to adopt AI before their operating layer is structured enough for it to work safely.

Scroll
FoundedNovember 2024 HeadcountSolo · scalable capacity
§ 05.01 · What I believe

Most businesses don't have an AI problem. They have an operating system problem, and AI makes that problem visible.

§ 05.02 · Studio

Solo operator. Built to scale.

One accountable owner
Melbourne · Australia-wide
Available · Q3 001
DR

Daniel

Founder · Operator

I work directly on every brief: mapping how the business actually works, exposing the blockers to AI adoption, and designing the operating layer AI needs to work safely.

2024 →Day Zero Projects, Founder FocusAI Operating Readiness, operating model design, knowledge architecture, governance ModeHands-on diagnosis and operating design, not slideware
Available · Q3 002
AI

Scalable Capacity

Specialists · Agent ops

I work solo by default. Outside specialists and agent operations extend research, synthesis, prototyping, documentation, and QA only when the brief genuinely needs that capacity.

ExpertsDomain specialists across legal, financial, industrial, healthcare, and retail sectors AgentsResearch, synthesis, prototyping, documentation, and repeatable delivery systems ReviewEvery output reviewed before it reaches the client, judgment stays with me
§ 05.03 · Principles

Eight rules I don't break.

001

Two engagements, no more.

A hard cap, held to strictly. The work is bespoke, not something to dilute by stacking a third client because the calendar happens to allow it.

002

One accountable owner on every brief.

You work directly with me. When a brief needs more capability, I can bring in specialist support or agent operations, but accountability stays with one person from start to finish.

003

Practical blueprints, not decks.

Every engagement ends with something the business can act on, a diagnosed gap, a designed operating layer, a governance framework, or a rebuilt workflow. The deliverable is the thing that changes how the business runs.

004

Readiness before implementation.

AI does not get implemented into broken operations. The business gets made ready first. If the operating layer is not there, that is the honest answer, given before money is spent finding out the hard way.

005

No in writing.

If your brief is not a fit, you will get a clear no within a week, with reasoning. That is owed more than another signed contract.

006

Quiet by default.

No case studies without permission. No logo-farming. Most of the work will never appear on this site, and that suits everyone, including the next client.

007

Models are tools. Judgment isn't.

AI is used inside the work daily, but the judgment calls stay human: what to build, who to listen to, when to stop. They do not get outsourced here, and they should not in your business either.

008

Leave clean.

Every engagement is designed for a clean handover. If it is done right, the business running the system after Day Zero leaves should not need it back. That is the test.

§ 05.04 · Provenance

A short history.

Nov 2024 Day Zero Projects is founded. Melbourne · Solo studio
Jan 2025 First Phase Two engagement: full ops overhall. Advisory firm · Melbourne
Apr 2025 First Phase Two engagement: full operating system redesign. Advisory firm · Melbourne
Jan 2026 Social enterprise direction becomes part of the studio thesis. Social enterprise
Feb 2026 First internal custom project: Agent first knowledge management. Day Zero Project
Current Two slots open. I am reading new briefs. Today
Engagements shipped 6 From founding · Nov 2024
Briefs declined 7 In writing, with reasoning
Repeat or referral 86% Of accepted work
Average response 31h From brief to first reply
§ 05.05 · Working together

Growing but
getting messy.
That is the brief.