Adam's progress (verbatim positions from the call)
- Cloud independence reached. Adam: "I'm in the process of getting all of those processes that pull that data, analyze that data, and provide the insights... up in the cloud. So there's no dependencies on your Mac being open, and when tabs being an opening Chrome and everything like that for it to operate." The data ingestion + analysis fleet now runs on Cloudflare in the background. Removes the Mac-must-be-on dependency that has been a freshness ceiling on the existing GC system.
- Software shape: "Spotfire-style data + analytics hub." Levers, scenarios, modeled outcomes. 900 leads currently enriching with contact data via the SOT → BeenVerified → HubSpot → SmartLead chain.
- Security posture. Adam: "SOT 2 Athra security protocols" — phonetic for SOC 2 Type II. Built to enterprise-deployment grade so the system can stand up immediately for additional managers / territories without retrofitting.
- Property scout is autonomous + reliable. Running ~2 weeks without hiccups; 4–15 fresh leads per day surfacing through HubSpot with full property specs.
- Voice-tuner + refresh-sweep button. Drafts in Gmail get auto-rewritten in Joseph's voice using ingested transcripts as the voice corpus. Refresh-sweep button manually re-runs the sweep mid-session (for when a conversation just happened and a draft needs the new context folded in immediately).
- 3-click bulk enrichment flow. SOT → BeenVerified → SmartLead, surfaced directly in the platform UI.
Live walk-through, page-by-page (what Adam showed)
| PWA page | What it does |
|---|---|
| Sources tab | Adam's first stop daily — health check on every data ingestion path. Shows Cloudflare process status. Avoids AI dependency for core ingestion (only analytics layer uses AI). |
| Today | Decision tiles surface every important next-move Joseph needs to take that day, drawn from Gmail correspondence + transcripts + system events overnight. Each tile is clickable → opens the artifact (draft, meeting invite, follow-up) ready to evaluate + send. |
| Open pipeline | "Nerve center" — every deal, every contact, every commission. Drill-downable, clickable, actionable from inside the platform. Mirrors HubSpot's deal-stage layout with adapted field names (commission per deal mapped through HubSpot quirks). |
| Outbound | Property-scout flow visualization. Shows what's coming in, what's getting kicked out (filtered by Rachel-rejection patterns the system has learned), what's surfacing as hot. |
| Atlas Playground | Scenario modeling — cost-of-customer-acquisition, commission targets, activity-required-to-hit benchmarks. "Crystal ball level analytics engine." |
| Market metrics | Pulls live from KeyData + Track. Pricing-action suggestions surface as "take action" tiles on the Today page when the market signals a move. (Pricing actions route to Rachel — Adam noted that's her lane.) |
Authorizations resolved + outstanding
| Item | Status |
|---|---|
| HubSpot contact-owner ID | ✅ Resolved live on call via Joseph's screenshare + URL copy-to-chat |
| Brain dump (full platform list + credentials Joseph has) | 🟡 Joseph TO email Adam — committed to send by end of day 5/11 |
| OAuth (Google Workspace) | 🟡 Scheduled Thursday 5/14 — 15-min screenshare walkthrough |
Schedule + Wednesday target
- Joseph OOO: Thursday 5/14 + Friday 5/15 + possibly Mon 5/18 + Tue 5/19
- Wednesday 5/13: Adam's target to "have Joseph's instance stood up with data plugged in" — locked-in milestone. Adam will temperature-test against his own client/closing calendar and confirm by Tuesday morning if the date holds or slips.
- Adam acknowledged the OOO stretch means Joseph will be pinged across multiple locations to step in. The platform needs to "service" him through those interruptions.
Commercial state (verbatim)
- Current: $3,000 upfront, held for the development period
- Forward: tiered subscription model TBD — Adam's attorney Brad is drafting operating + management agreements; gaps + blind spots being identified
- Skin-in-the-game framing: Adam explicitly wants Joseph rewarded in the operating agreement structure because Joseph is going through the dev cycle with him
- Adam: "I don't want to overcharge or anything like that. Just want to make sure that there's something coming from this that allows me to make the investments that I have to make."
Multi-market expansion (held for after Joseph's instance is dialed in)
- Joseph mentioned 3 other locations / managers want to work with him
- Adam's structural offer: "what if it turned into a situation where I know how to fucking run it. They want to work with you. You and I share in the proceeds."
- Estes Park + Breckenridge holds confirmed off the immediate roadmap — they revisit only after Joseph's instance is stable + Lindsay/Cord/Michael/Maura have run the diligence
Stakeholder roll-out plan
| Phase | Stakeholders | Adam's prep |
|---|---|---|
| Phase 1 walk-through (after Joseph dialed-in) | Lindsay Lockard + Cord Corcoran | "first eyes" — high-level; Lindsay goes deeper |
| Phase 2 | Michael LeClerc (Dir IT) + Maura Wall (Dir Marketing) | Analytical — they'll rip into the HubSpot connections; Adam building a PowerPoint that addresses each bucket's specific concerns so the call drills into the right details |
Open items Adam logged for himself
- Add a HubSpot meetings link inside the platform (Joseph asked for it)
- Add SMS / texting options
- Build the PowerPoint walkthrough for Lindsay + Cord + Michael + Maura
Open items Joseph logged for himself
- Email Adam the brain-dump list of every platform + the credentials Joseph has access to (Adam asked for it explicitly; Joseph committed to send "right at the end of the day")
- Record the management-agreement talk-track (HubSpot calls + Fathom + Gemini) to share with Adam so Adam can learn Joseph's spiel before building the talk-track into the platform's auto-draft flow
- Address the Hadank preliminary-contract process gap — Rachel auto-sends a pre-fill contract; Joseph doesn't want contracts in a prospect's hand without walking through it in person. Process change needed on Rachel's side.
What this means for the current GC system
- The system you've been building (Mac-resident chrome_bridge fleet, scheduled tasks, audit gates) and Adam's Phase 1 platform are converging on the same architecture: cloud-resident processes, voice-tuned drafts, sources-health-first dashboards, decision-tile UX. Worth treating Adam's platform as the v2 destination, not a parallel build.
- The audit-pass chain you spent today hardening (claim_audit + voice_check + commitment_audit + body_verify + reply-context cert + no-stacking MCP cert) is the kind of structural rigor Adam's platform will need to absorb when it takes over outbound drafting. Worth packaging those as a portable module Adam can ingest when he gets to Phase 2 outbound automation.
- The Hadank pre-fill contract issue is the next concrete deal-blocker — Joseph flagged it on the call as his next focus. Worth surfacing in the next morning brief.
How to use this memory
When the next dev session with Adam happens, agent should:
1. Re-read this file for context
2. Cross-check against the latest Adam transcript for delta
3. Update the schedule / open items section with anything new
4. NEVER cite specifics from this synthesis in outbound to anyone outside SkyRun without source-verifying against the verbatim transcript file (Gmail msg 19e184eb108db490)