Steerco #1 · Mobilisation · scopes ratified

WS1 needs baseline locked to drive Phase 2 KPI calibration

WS4 cannot advance to Built without counsel engagement; longest lead-time of any Phase 1 milestone

WS6 BDM shortlist needs partner sector locked to brief candidates correctly

Verbatim Steerco #1 feedback: "access to the PMO was needed [as] a top nav menu UI entry point rather than navigated from proposals, masterframework then live PMO". The live PMO board (/engagement/pmo) is Mathew’s daily-driver surface during Phase 1, yet it was reachable only via Proposals → Master Framework → Live PMO (three clicks deep). This was an IA mismatch with how the surface is actually used.

Verbatim from Carla 21 Jun 2026: "claude, as workstream lead of workstream TECHNOLOGY i am responsible for the design building and implementation cutover to hypercare, growth and exit of the crm and commission engine, with consult on user requirements from matt and corrina". This formalises the RACI for the platform's two most business-critical surfaces: the commission engine that moves money, and the CRM that holds the federated telephone books. Matt and Corrina are explicitly consulted stakeholders on user requirements only — they do not own technical architecture, sequencing, data model, or compliance scaffolding.

Carla's verbatim instruction Mon 22 Jun 2026: "claude make an entry to the live PMO, backlog item entry — Build CRM — prepare a high level scoping document with a RACI, CORRINA AND MATT for consult on what this CRM needs to do, carla responsible for elicitation of user requirements mapping to functional spec and UAT. TIME 5 DAYS STARTS TODAY MONDAY 22/06/26 END FRIDAY 26/06/26. HIGHEST PRIORITY SPRINT THIS WEEK". This is the scoping artefact sprint — not the build itself. The build sequencing decision lands at Steerco #2 (29 Jun 2026) on the strength of this artefact.

Corrina (WS1 Lead) verbatim Tue 23 Jun 2026, in a working session reviewing the CRM scoping artefact: "the crm tool is being (designed buikt implemented ) in phase 1 project. Then being handed over to bau (hypercare. Growth, exit) as a team carla matt and myself need to ensure we have defined the user requirements for all roles in flip360 to use ince cutover to bau to ensure the business achieves its financial goals... Thats how investors get paid, matt founder gers paid and carla and corrina gwt paid." Deep codebase analysis surfaced 13 distinct roles that materially touch the CRM, not the 4 originally identified (CMO / BD / Sales / CS). The additional 9 roles — Founder, PMO Director/CFO, Platform Admin, Member-side Sales Rep, Member (Referring), Community Manager, Compliance Officer, Finance Operator, Investor Read-Only — are all named in the existing architecture (/architecture.tsx ACTORS, /payouts.tsx Payout Officer, /community-manager.tsx, /investors/* surfaces). Every named principal's Phase 2 performance pool routes through this CRM working: YDT acquisition KPI ladder (Corrina's pool per framework §5.3), CoSai Revenue+NPBT vs Budget (Carla's pool per framework §5.2), exit valuation (Matt's equity), and revenue trajectory (investor pack $240k FY27 → $42M FY31). The CRM is not a feature — it is the operating system the business is sold and listed against.

Carla's verbatim instruction Mon 22 Jun 2026: "i need to set up a deal room on the plaform cosaiflip360.org that is a place where the costs to date and the costs to complete can be capture, stored retrieved analysed and reported. a place where invoices sent and receipts for payment made costs to date and costs to compelte" — refined same day: "i need to track the costs to date and costs to complete by workstream and total of all workstreams, every workstream is responsible for on time, on scope, on budget delivery. the pmo director cosai cfo services carla oliver is accountable for ensuring every workstream delivers on time on scope on budget and must work closely with the workstream leads to ensure this". RACI: WS Leads = Responsible for their own workstream OTOSOB (On Time / On Scope / On Budget); Carla (PMO Director, CoSai CFO Services) = Accountable for the engagement rollup. The deal room is the financial twin of the live PMO board: same workstreams, same governance, but the lens is cash + variance, not RAID + sprint.

Carla's verbatim instruction Mon 22 Jun 2026 (same conversation as D112): "i need an invoice for aud 5000 for the ai workforece credits/tokens to build the commission engine". The Flip 360 commission engine is already live at /app — six functional guarantees met, chain ledger at /chain, Stripe Connect payouts wired, Pine Lawyers Governing Agreement at /legal — but the AI workforce credits that physically powered that build were never invoiced for. CSC-INV-2026-001 (May 2026, $5,500 inc.GST) covered CoSai PMO + technical oversight fees only. CSC-INV-2026-003 closes the gap by recognising the AI compute itself as a discrete line item, retrospectively. This is a recognition invoice (asset delivered), not a forward-funded sprint budget.

Carla's verbatim instruction Mon 22 Jun 2026: "I NEED $500 AUD as the budget for this scope of work, payable today 22 monday 26, cosai cfo services to issue an invoice for payment. cosai cfo services to buy the ai workforce credits (tokens)" — clarified same day: "$500 + $50 GST = $550 total" (the $500 is ex-GST, the gross figure payable is $550 AUD). WS2 Lead is funding the AI workforce credits required to execute WS2-B007 (the CRM scoping sprint). CoSai CFO Services Pty Ltd (where Carla is Principal) procures the credits on Flip 360's behalf under the master engagement signed at /engage in May 2026 (CSC-INV-2026-001). This is the credit-funding sub-invoice — separate from the monthly PMO services invoice.

Verbatim Steerco #1 feedback: "steer co wanted to have 24/7 live access to the status of every workstream.... whats on the backlog for that workstream and what is being sprinted this week mon to sun from the back log, they wanted to be able to access the library of steer co papers, decisions (resolutions) issues/risks via a resolutions and issues, risk register, they wanted to see a workstream status report of done, doing, what up next, and the RAID per workstream, steer co members corrina and matt have NEVER seen a workstream project status report before, and what to see sample data as a show and tell to help them learn how to operate under a PMO governance structure. they asked to be shown the best practice that they could learn ADKAR ways of getting the PMO governance right first time — so a show me an example of what i have to do every two weeks as a workstream report due to steer co and how it gets updated to cosaiflip.org (which is our project management tool — like notion is to the marketplace, but we have an equivalent that is driven on url cosaiflip360.org)". Mathew and Corrina have never seen a fortnightly workstream status report; they need sample data + ADKAR teaching, not a blank template.