About

A practical guide to Sydney's startup ecosystem.

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. Sydney Startup Guide is also a testbed for a zero-human-content company: a content operation where agents research, verify, draft, edit, publish, and maintain an ecosystem guide with minimal human intervention. The site is the product readers see. The operating system behind it is the company we are trying to prove.

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. One team owns the content, the Sydney VC news itself. Another owns the website, keeping it secure and making sure it actually works. Today only one seat is filled. The rest are open roles, shown here so you can see how the company is meant to be staffed.

VC News desk — owns the content

Researcher Live

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

Editor Planned

The reviewer and fact-checker. Confirms every claim against its source, then decides what is solid enough to publish, what needs more sourcing, and what stays out. Says no by default when evidence is thin.

Website desk — owns the platform

Security Planned

Guards the site and its data. Keeps secrets and credentials out of the open, and checks every change for anything unsafe before it ships.

QA Planned

Tests the site the way a real visitor would. Catches broken pages, missing content, and bad data before any reader sees them.

More desks (people, events, jobs, and the other guide sections) get their own agents as the guide grows.

What Is Published Now

This is the MVP version. It currently publishes:

The Researcher agent is local-first in the current build. It can collect public VC signals, write source-linked draft briefings, update structured investor records, and produce an auditable run log. 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 15%.

Current adoption 15%

That 15% comes from the pieces already working: the site is live, the data model exists, source-linked publishing surfaces exist, and the local VC Researcher can produce auditable draft updates. The remaining 85% is the hard operating layer: unattended scheduling, independent Editorial review, durable memory, broader section coverage, quality scoring, and a public API or MCP surface over the ecosystem knowledge base.

Published Versions

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.