Proof, not promises
Cliff Wilson owns HuddleTalent, HR services and recruitment, with a team of four in Sydney. Four months in, the admin after every sales meeting is, in his words, "pretty much 100% gone".
Cliff Wilson
"Now the proposals pretty much write themselves."
Before Seby
"We were working across eight, ten systems: Microsoft 365, CRMs, spreadsheets, Loop, To Do, Zoom." Tools that had their place, but they were all siloed, and nobody used them the same way.
What runs for Huddle now
Marlow & Hale is a fictional Sydney consultancy we built to show the product, with fourteen made-up people and twelve made-up clients. Everything else is the real system. Open it, click around, no sign-in.
Sample environment, illustrative data. Marlow & Hale is a fictional firm created by Seby to show the product.
Seby runs Seby on the same system. Counted on 19 October 2026 from the repositories and the register themselves, not from a slide.
| Number | What it counts | Where from |
|---|---|---|
| 1,141 | changes shipped in the last 14 days | commits written by a person, 5 to 19 October, seven repositories 1 |
| 4,606 | changes shipped in the last 90 days | same rule, same repositories, 21 July to 19 October; the 14-day figure is part of it 1 |
| 183 | live systems on the register | sections marked live on the live systems register, each with its own status check 2 |
| 2,336 | product tickets filed | every one with testable acceptance criteria, or the engine refuses to file it 3 |
| 364 | of those tickets delivered or closed | 177 delivered and 187 closed, the rest in progress, parked or turned down 3 |
| Apr 2026 | running a real company since | Seeda first, then Seby itself from May 2026 |
scripts/count-proof.sh.Not a roadmap. Things that are running today.
A customer texts a change to their website. The agent edits it, runs the site's own brand and analytics gates, and proves the live page changed. Approval stays with a human by default.
A fabricator marked a section on an architect's sheet by text. The brain produced the drawing set, revision by revision, as PDF, DXF and DWG, with every assumed value flagged for the engineer by name.
Every recorded meeting becomes a record: the recording, the summary, decisions, risks and action items with timestamps that seek the player. The follow-up chain runs from there.
Written overnight from the connected sources. Reviewed and released by a person. The same engine writes both.
Every screen we ship is scored at desktop and phone width against a written rubric before a customer sees it. Rework never ships.
Book a call. We look at where your week goes, tell you which job to hand over first, and what it costs.