Sarah Chen
This is a design prototype, not a working CRUD app yet.
Carla's brief, verbatim: “i need you to be a world class crm developer and crm designer, what would you do?” My answer was Contact 360° first — because the contacts table is the spine of the schema. Companies, deals, activities, commission_events and ledger_entries all hang off it. Build Contact 360° and the vocabulary for every subsequent surface (Deal 360°, Admin panel, CM cockpit, BD pipeline) is settled.
This page renders a single fully-detailed mock contact (Sarah Chen, a MEMBER+PARTNER mortgage broker in Brisbane onboarded via the MFAA institutional partnership channel) across all eight panels a Flip360 contact record needs. Layout is real; data is mock; brand kit is baked in. Your job: redline as the CX designer. Mine: rebuild. Small surfaces, frequent commits.
What to redline first
Carla — your turn. Some prompts you might use to drive the next redline pass:
- Hierarchy: is the header strip carrying the right four signals (name, role, contact-type duality, status)? Should geo + joined-date move into the header or stay below?
- Left rail order: Identity → Community → UTM → Compliance. Is that the priority a BD or CM actually scans? Should compliance be higher?
- 5-handshake viz: does the example-chain row make the moat visible enough? Should it be the hero panel above timeline?
- Right rail commission ledger: 4-tile grid (earned/paid/owed/clawback) — right metrics? Right order?
- Quick actions: are the 5 actions the right 5? Are any missing? Wrong priority order?
- Notes: BD vs CM vs SYS — right colour-coding? Should member-side notes have a 4th colour?
- Trust signals: is this prominent enough? It's the Flip360 native moat — maybe it should be centre-stage, not right rail.