About

A practical guide to Sydney's startup ecosystem.

Sydney Startup Guide is a live, source-verified map of Sydney's startup scene — who's funding what, which companies to follow, where you'd want to work and who with. But it is also something less common: an experiment in running a real company with AI. Not AI writing the content — a working operating model. Specialist agents hold specific jobs — a researcher, an editor that rejects anything it can't verify, security and QA — work under explicit rules, and hand off to each other, with a human reviewing only the weekly release. Every listing links to its source and the run log is public, so you can audit the work. The open question behind it: can an AI-native company hold a real quality bar — accurate, sourced, current — and need less human oversight over time? And like any company, it is built to grow: today it researches, checks, and publishes; as the machine earns trust, new desks come online the way a startup hires — growth and distribution to reach the people it's for, a strategy function to choose new sections and directions, and in time, ways for the company to sustain itself. Behind it is one builder with twenty years across data, technology and AI, betting that you can design and operate a company this way. The org chart below is the first few hires, not the finished company — this is the earliest version it will ever be.

The longer story

Sydney Startup Guide is an independent, pseudonymous project for founders, operators, investors, and anyone trying to understand the Sydney startup scene without spending months piecing it together from scattered sources.

The person behind it has spent roughly 20 years working across data, technology, analytics, and AI: building systems, turning messy information into usable operating knowledge, and helping teams make better decisions from evidence. This site keeps that background anonymous, but the work here comes from that same instinct: structure the useful information, cite the sources, keep improving the system.

Sydney is dear to the founder. This guide is a small thank you to the city: a way to make the innovation ecosystem easier to navigate, easier to join, and easier to grow.

Inspired by Other City Guides

This effort is inspired by the excellent London Startup Guide and the Starter Guide to SF for Founders. Both show how useful a clear, city-specific startup guide can be when it is built for people who are actually trying to get plugged in.

What We Are Trying To Build

The public promise is simple: make this the most useful source of Sydney startup data for founders, operators, investors, and ecosystem builders. Useful means current, source-linked, structured, and practical enough to help someone decide who to meet, what changed, and where the momentum is.

The broader experiment is more ambitious than a guide. Sydney Startup Guide is a testbed for an AI-native company — not just AI writing the content, but a real operating structure: agents with specific jobs (a researcher; an editor that rejects anything it can't verify; security and QA), explicit rules they work under, and genuine handoffs between them, with a human reviewing only the weekly release. The question it is built to answer: can you actually run a company this way — and hold a real quality bar, week after week, with less human oversight over time? The directory is the product readers see. The organisation that produces it is what we are trying to prove you can build — and, like a startup, grow: more roles and desks over time, its own growth and distribution, new directions as it learns where it is most useful.

1 Observe

Researchers watch approved public sources and turn raw signals into structured evidence.

2 Interpret

Specialist agents summarize what the evidence says and flag uncertainty instead of filling gaps.

3 Govern

Editorial checks decide what is publishable, what needs more sourcing, and what should stay out.

4 Publish

The site updates from reviewed data, briefings, and run logs so readers can inspect the process.

The Agent Team

Picture this company as a small organisation where every job is done by software, not a person. Each agent has one narrow job. That is a deliberate design choice, not a limitation. A team of single-job agents is far easier to audit, correct, and trust than one giant model trying to do everything at once. At any point you can see which agent did what, on what evidence, and why. When something breaks, you fix one small role, not a black box.

Like any company, it is organised into teams by what they own. The Content desk owns everything readers come for: the weekly VC news and the seventeen directory sections, each maintained by its own researcher, with an Editor that reviews every researched entry before it can publish. The Website desk owns the platform: a Security agent that audits the site and its supply chain, and a QA agent that checks the build, the data, and every internal link. Two more desks are being hired: Growth & Distribution, to get the guide in front of the people it's for, and Strategy, to choose new sections and directions — with ways for the company to sustain itself a later horizon. The chart below is the first few hires, not the finished company.

Content desk — owns the content

VC News researcher Live

Reads approved public sources, pulls out source-linked funding signals, drafts the weekly briefing, and adds newly discovered firms to the directory.

Section researchers Live

One narrow researcher per directory section — funds, programs, events, workspaces, housing, visas, and the rest. Each re-researches its section on a rolling weekly cadence and stages candidate entries for review. Nothing it finds publishes directly.

Editor Live

The reviewer and fact-checker. Validates every staged entry — schema, source links, liveness of every URL, duplicates — and removes anything that fails. Says no by default when evidence is thin. It has already rejected real researcher output.

Website desk — owns the platform

Security Live

Audits the site every cycle: dependency vulnerabilities, secret leakage, security headers, and third-party origins. A failed audit blocks publishing.

QA Live

Tests the site the way a real visitor would. Checks the registry, the data behind every section, the built pages, and every internal link before any reader sees them.

Agents run on a weekly cycle and changes go live in weekly releases. A human reviews each release diff before it publishes — full autonomy is a later milestone, not the current state.

What Is Published Now

The full directory is live:

The agent fleet is local-first in the current build: researchers, the Editor, Security, and QA all run on a weekly cycle with a human approving the final diff. Unattended cloud scheduling comes later.

How The Stack Works

The site is static and intentionally simple. Astro builds the pages. GitLab stores the markdown and structured data. Netlify hosts the public site. Future Researcher runs will create branches and merge requests instead of publishing directly.

Longer term, the source-linked observations can become a structured memory layer for Sydney's startup ecosystem: firms, people, companies, funding events, relationships, and weekly market signals.

ZHC Progress

If a fully autonomous zero-human-content company is 100%, this project is currently around 35%.

Current adoption 35%

That 35% comes from the pieces already working: the full directory is researched and maintained by per-section agents, an Editor gate validates everything they stage, and Security and QA agents protect the platform — all on a weekly cycle. The remaining 65% is the hard operating layer: unattended cloud scheduling, durable ecosystem memory, quality scoring, and a public API or MCP surface over the knowledge base.

Published Versions

MVP2 · Full directory + agent fleet
Seventeen sections populated by per-section research agents; Editor validation gate; Security and QA agents; weekly local run cycle; editorial redesign.
MVP1 · Local VC Researcher loop
Local-first researcher checks approved sources, extracts high-confidence investor signals, drafts source-linked briefings, and prepares changes for review.
MVP0 · Static guide foundation
Public site, custom domain, seed VC directory, VC News surface, roadmap, and agent run log. No live autonomous research yet.