About Blue Monk

We build software for problems we've actually had.

Blue Monk exists because of a simple observation: AI is commoditising code-writing. Knowing what to build — and standing behind it in a live operation — is the real moat.

We've run the warehouse. Managed the production line. Shipped 3,000+ orders a week. When we build software, it's because we needed it first — not because a market report told us someone else might.

The Name

Why “Blue Monk”?

Blue Monk is a 1954 composition by Thelonious Monk — one of the most distinctive voices in jazz. Monk played with precision, took unconventional approaches, and never sounded like anyone else. We liked that. We build software with intention, with character, and with zero interest in following the SaaS template.

The Team

Two founders. One operator. One engineer.

A

Ace

Co-founder — Operations & Strategy

Co-owns Threadheads, a DTC apparel company in Melbourne. Runs warehouses, manages production lines, and lives inside the operations that Blue Monk's software is built for. Knows where things break because he's the one who gets the call at 6am.

B

Brett Leggett

Co-founder — Technical

Architect and engineer behind Blue Monk's software stack. Turns operational problems into production-grade systems. Builds things that work under load, not just in demo mode.

The Threadheads Connection

Our first customer is our own operation. That's the point.

Threadheads is a live DTC apparel company co-owned by Ace. Every piece of Blue Monk software ships there first — tested with real orders, real production staff, and real consequences if it breaks. This isn't a sandbox. It's the proof.

When we say the ERP cut workforce needs by ~30%, we measured it on our own floor. When we say it handles multi-warehouse fulfilment, it's because we run it across multiple warehouses right now. We don't ship features we haven't used ourselves.

Work with people who've been in your shoes.