DCB Events

Where Darren started

DCB Events produces high-quality events. Strong client relationships, repeat business, and a reputation earned through getting the detail right on the day.

Darren was the detail. He was on every major job — managing the crew, managing the client, managing the problems that live events always create. The business ran because Darren ran it. That’s not a business. That’s a job with employees.

The instability he felt was real. Everything lived in his head. Nothing was documented in a system. Inbox-driven workflow, reactive decision-making, no project management structure. Classic early-stage behaviour — the kind that works when you’re small and breaks when you’re trying to grow.

The real problem

When your quality standard lives in your head and not in a documented system, you can’t delegate it. You can’t brief a new team member against it, you can’t hold a subcontractor to it, and you can’t deliver consistently across multiple concurrent jobs without being personally present.

That was DCB’s constraint. Not a lack of capability — a lack of infrastructure. Darren had the clients, the revenue, and the team members. What he didn’t have were the systems that could hold quality without him on every site.

What we worked on

1. Project management infrastructure

The absence of a project management system meant everything was managed by memory and inbox. Building out a structured project board — with milestones, budgets, client meetings, and clear task ownership — was foundational. It moves the business from reactive (responding to whatever arrives first) to planned (knowing what’s happening, what’s due, and who owns it).

2. Templates and standardisation

Ad-hoc briefing emails, unverified budget spreadsheets, informal supplier communication — these were the operational norm. Coaching focused on replacing them: standardised event budget templates, hotel and venue briefing documents, and supplier protocols that set expectations before site inspections. These aren’t just efficiency tools. They’re how quality gets held when Darren isn’t in the room.

3. AI adoption for operational leverage

Darren is a strong adopter of AI tooling — using it for budget templates, traveller profile forms, and briefing document generation. The coaching work extended into how to delegate the setup and management of those systems (not just use the tools personally), so the automation serves the business rather than just the founder.

4. Commercial and legal foundations

Darren was running active projects without signed client agreements. That’s payment risk, scope creep risk, and relationship risk simultaneously. The coaching focus: establish formal engagement terms as standard practice, not an afterthought. Know your payment structure before work starts, not after.

5. Cross-Tasman delivery

DCB Events works across Australia and New Zealand. Delivering in NZ with a remote coordination model — different supplier networks, different logistics, different compliance — requires infrastructure that doesn’t exist by default. Building budget templates and supplier briefing protocols that work for cross-border delivery was part of the active coaching work.

Where Darren is now

The systems are being built. Project management structure in place and expanding. Standardised templates replacing ad-hoc communication. Contracts being formalised as a business standard, not an exception.

The BEF arc for Darren is Existence → Survival → Success. He’s in the Success stage: actively constructing the infrastructure that will let DCB Events deliver at scale without the founder managing every detail. That work takes time to become habit, and it’s the current coaching focus.

The instability Darren felt at the start — the self-doubt, the reactive inbox management, the sense that everything depended on him personally — those are symptoms of a planning gap, not a capability gap. Closing the planning gap is what the coaching has been about.