§ 06 · Contact Melbourne · 00:00
37.81° S 144.96° E

Tell me what you're trying to fix.

I read every brief personally. If your problem is a fit, you'll hear back directly, not from an SDR, within two business days.

Scroll
Briefs openQ3 2026 · Two slots Avg. response time31 hours
§ 06.01 · Brief

A short brief is enough.

01 · Your nameRequired
02 · EmailRequired
03 · CompanyRequired
04 · RoleOptional
05 · Engagement typePick one
Phase One · AI Readiness Phase Two · Strategy to Shift Both phases Not sure yet
06 · Areas of interestPick any
Readiness diagnostic Operating system design AI governance Knowledge architecture Data readiness Workflow redesign Leadership & staff alignment
07 · Indicative budgetOptional
  • Under $50k AUD
  • $50k to $150k AUD
  • $150k to $500k AUD
  • $500k+ AUD
  • Not yet defined
08 · TimingOptional
  • This quarter
  • Next quarter
  • Within six months
  • Exploratory only
09 · The briefRequired · 1 to 3 paragraphs

By sending, you agree that I may store this brief for the purpose of responding. I don't share it. Ever.

§ 06.02 · Direct

Or reach me directly.

01 · New briefs

For new briefs.

Read personallydaniel@dayzeroprojects.com
02 · Press

Quotes, panels, writing.

Replied within a weekinfo@dayzeroprojects.com
03 · Everything else

Hello, in general.

For partnerships & curiosityinfo@dayzeroprojects.com
§ 06.03 · Common questions
001

How do you decide which briefs to take?

+

Two engagements at a time. Fit is the only filter, a real problem, a decision-maker in the room, and a twelve-month horizon that is reachable. Briefs get declined often, and quickly.

002

What does a typical engagement look like?

+

Most engagements begin by clarifying the problem, the operating gaps, and the decision that needs to be made. From there, I recommend the right service or next step. Every engagement ends with a practical deliverable the business can use, not a strategy deck.

003

We already use AI tools. Does readiness still matter?

+

Probably. Most businesses using AI tools are using them on top of an operating layer that was never designed to support them. That creates inconsistent outputs, unmanaged risk, and staff using tools without clear rules. The tools themselves are not the problem, the operating foundations underneath usually are. If your data is unreliable, your processes are informal, or your knowledge is scattered, adding more tools will not fix that.

004

Are you Melbourne-only?

+

Based in Melbourne, with a preference for in-person work at least monthly. Currently engaging with businesses across Australia.

005

What if my problem isn't really an "AI" problem?

+

That is probably because most businesses do not have an AI problem. They have an operating system problem. Messy processes, unreliable data, scattered knowledge, and unclear ownership. If that sounds familiar, it is exactly what I work on. AI readiness starts with fixing the operating layer underneath, not adding tools on top.

006

How private is what I send?

+

I read every brief personally and store them encrypted. They are never used to train models. They are never shared with prospective collaborators without written consent. If an NDA is needed up front, ask.

§ 06.04 · A standing offer

Too much depends
on too few people?
Write to me.