Charlie Property buys abandoned and derelict houses across Australia, renovates them in-house, and holds them as rentals. The business ran on a founder, an EA, a renovation PM, a designer, and a handful of VAs, coordinated through verbal updates and private chat. Three prior builds of their work management system had already failed, in the founder's own words, because they were built right but never adopted.
Where it started
The tooling was never the missing piece. Three work management builds already existed and had died. What was missing was a system the team had a reason to use every day, and someone accountable for making usage stick. Status updates were verbal, handoffs lived in private chat, and leadership spent time chasing people for updates instead of reading them.
Scoping adoption as the deliverable
The engagement was sold as a fixed-fee, milestone-based build with an objective adoption gate written into the contract itself: at least 80% of the team logging in daily for 14 consecutive business days, every role running its core workflow without prompting. That structure exists directly because of the three prior failures. This time, done means behavior, not configuration.
Rebuilding the workspace around roles, not features
The new workspace runs on five role-based lists, Leadership, Operations Daily, Marketing, Operations Weekly, and People & Admin, all sharing the same accountability fields: owner, current state, next step, and due date. The property template itself was rebuilt around the renovation PM's real process: five phases and eleven build steps carried as trade tasks, so a cloned property arrives pre-owned by the right people.
The three prior attempts failed for a reason the founder could name himself, and it was never the software. We started with diagnosis instead of features, and made adoption itself the deliverable.
