How the Australian Payroll Association shipped 486 pull requests on Payroll IQ, 272 of them from its own CEO, and is taking it to market on one database
In progress. Member launch pilot under way, September 2026.
Pull requests merged on Payroll IQ since May 2026. The association's CEO wrote 272 of them.
Tables, 72 security policies and 18 triggers moved into one shared database without changing a screen.
Pull requests merged by APA's own staff on their Company OS in its first three weeks.
The Australian Payroll Association built its own training product with Claude. It started at a private Edge8 retreat in Vietnam, Edge8 engineers worked beside its CEO from the first month, and five of the team followed at the Sydney retreat. Now the association runs a Company OS of its own, Payroll IQ has moved onto the same database, and members will buy it through the HubSpot portal they already use.
APA knew payroll training better than anyone, and its CEO did not wait for a vendor. In May 2026 Tracy Angwin came to a private Edge8 retreat in Ho Chi Minh City, sat beside our engineers for a week, and built. The first pull request on Payroll IQ landed eleven days after the retreat ended. Then it grew one pull request at a time: levels, modules, quizzes, learning plans, topic mastery, seat tiers, an expert chat. By the second retreat in July it was a real product.
It was also a third system. Members bought and logged in through HubSpot, the expert chat ran as its own app, and Payroll IQ sat on its own database with its own admin. Nothing could be cross referenced, every connection was a link or an API call, and the product had its own checkout beside the one members already used. Payroll IQ was built. What it had not done yet was earn.
“Payroll IQ was built. What it had not done yet was earn. The fastest way to find out whether it is a revenue line is to put it in front of members and let them buy it.”
Dave Hajdu, Edge8
Three retreats before a line of vendor code.
Two private retreats in Ho Chi Minh City with the CEO alone, in May and July 2026, then a two-day Sydney retreat with a team of five. A retreat is not a course. You arrive with a real problem and leave with working software and the habits to keep building it, and the survey before it asks how ready your data and workflows are, because that is what the days are spent on.
- It started at a retreat. A private retreat is a week in Vietnam building your own software in Claude Code with an Edge8 engineer at your elbow. Payroll IQ was not the only thing that came out of it: four other applications were built the same way, from lead generation to onboarding new consulting clients.
- Then the team came. Five of the APA team did the two-day Sydney retreat at the end of August. That is where the confidence and the capability to run an AI program came from. The first pull request on their own Company OS is dated the first day of that retreat.
- Engineers beside the CEO, not instead. Edge8 engineers worked in the same repository from the first month: 214 merged pull requests alongside the CEO's 272. Every change is planned, shipped and verified in production, from a watch counter that stops when the learner pauses to a health check that catches a deleted training video before a learner does.
- A Company OS the APA team runs. One admin for members, content, agents and access. In its first three weeks APA staff merged 57 pull requests of their own, including a newsletter machine that writes an article when a topic is accepted.
- One database, one schema per app. Payroll IQ's 34 tables moved into their own schema inside the Company OS database: 27 unchanged, 72 security policies rewritten, 18 triggers, three storage buckets. One login works in every APA app, and staff access is managed once. Members see no difference. We did it before launch, while there was no customer data to move.
- HubSpot sells it, Payroll IQ listens. Members buy and assign licences where they already buy membership. A licence assigned creates the user and sends a login; a lapsed membership disables access; a reactivated one restores it. Every event lands in an orders log. The separate checkout and sign-up pages are retired.
- Work in units, on a roadmap the client ranks. Four milestones, from one system to live to customers, each card estimated in Human Tokens and visible in the client portal. The pilot only builds what stands between Payroll IQ and its first paying members.
- 486 pull requests merged on Payroll IQ between May and September 2026, 246 of them in July alone.
- Three systems became one database with one login, and the second admin is going away.
- The route to revenue is the one members already use. No new audience, no new sales channel, no second checkout.
- 233 million agent tokens against 71 human hours of direction and review, about 3.3 million tokens for every human hour. The tokens did the volume; the humans did the judgment and the sign-off.
- Five applications out of three retreats, and a team that builds: the people who sat in the Sydney room are the ones merging code three weeks later.
- APA staff ship to their own system: 87 pull requests merged on the Company OS in under three weeks, 57 of them by APA people.
- The pilot is under way. First licences sold, members onboarded and revenue per member will be added here as they land.
Tracy Angwin, CEO, Australian Payroll Association, on the private retreat.
Nobody outside APA could have specified Payroll IQ. A domain expert with an AI pair builds the right product faster than a vendor can write the requirements. Engineers earn their place making it safe to sell.
Moving 34 tables is a week of work with no customer data and a project with it. If a new product will share people, companies and orders with the rest of the business, put it in the same database before launch.
A new product does not need a new checkout. Let the system that already takes the money keep taking it, and make the product listen.
This runs on the same Company OS we install for clients. If you want the people who built it inside your company, talk to us about the roles you actually need.
