Platform Blueprint · v6 — Prepared for TSP by Social Lexicon

The Coaching Portal, Rebuilt

A custom member portal for the TSP Mastermind — four subsystems replacing CoachSimple, Calendly, and Google Calendar, while Keap, Vimeo, and Google Meet + Gemini stay exactly where they are. This proposal is built directly from your development brief, and this revision finalizes Google Cloud as the hosting environment.

Revised: September 17, 2026 Your brief dated: August 2026 Soft launch target: May 2027 Members: ~150 Hosting: Google Cloud
Updated at your request — launch date moved to May 2027; Notes Pipeline and Scheduling re-sequenced from parallel to sequential to use the extra runway to de-risk rather than just to relax
01

Executive summary

We know why you're replacing your current system — you've lived with the friction every day. Your development brief tells us precisely what should replace it: a custom portal built around four subsystems — training library search, core portal & member records, a coaching notes pipeline, and automated scheduling — sitting on top of Keap (staying, your system of record for status and billing), Vimeo (staying, your ~500 hours of training video), and Google Meet + Gemini (staying, your notetaker). CoachSimple, Calendly, and Google Calendar as a standalone scheduler are being retired.

Three of the four subsystems already have complete design specs, data schemas, and screen mockups — your team did real work before we ever got involved. That changes the shape of this proposal: this isn't a from-scratch discovery exercise, it's sequencing an already-designed build and validating the one genuinely open technical question, how Gemini's notes actually get into the system.

Your soft launch has since moved from the third week of December 2026 to May 2027. That roughly triples the runway — from about 14 weeks to about 36 — and we've put the extra time to use in two ways: Subsystems 3 and 4 (Notes Pipeline and Scheduling) now build sequentially instead of in a tight parallel sprint, giving the no-human-approval scheduling agent a dedicated hardening window instead of sharing one with the notes pipeline; and the five previously out-of-scope member-facing pieces — the 90-day visual tracker, onboarding dashboard, in-portal chat, event tickets, support tickets — now have a real option to be folded into this build instead of waiting for a second phase. We've left that as a decision for you to make in Section 11, not an assumption we've made on your behalf.

This revision also finalizes our hosting recommendation to Google Cloud — detailed in Section 04 — since every system this build touches outside of Keap is already Google Workspace, and adds Cloud Storage as the object-storage layer for transcription working files, notes-doc archives, and backups.

02

Four problems, four subsystems

Every pain point you described to us and every problem named in your brief traces to one of four fixes. Laid out side by side, the scope stops looking like a wish list and starts looking like a punch list.

ProblemWhere it shows upFixed by
People are the wiring between systems. Booking one call takes ~15 minutes of re-keying the same five facts across four tools. Wrong coach assigned, members double-booked — both are re-keying errors, matching what your team described: unscheduled requests sitting in a queue (the Javier example). Subsystem 4 Automated Scheduling
Anything needing separate maintenance goes stale. "Hot Sheet" member profiles are built once at intake and never updated. Coaches walk into calls blind. Echoes what you told us about the flat, unsortable revenue table and the fixed onboarding questionnaire. Subsystem 2 Core Portal — records that update themselves from live inputs, not a form filled out once
Ten years of coaching content is unreachable. ~500 hours in Vimeo with no way to search it. A direct match to your own words: "I couldn't actually tell you" what the most popular or most-viewed content is. Subsystem 1 Training Library Search
Data is not extractable. Wins, revenue, action steps, and goals can't be downloaded for analysis. Matches your own revenue-table complaint almost verbatim — "no way to sort things." Subsystem 2 Core Portal — a reporting/export layer joinable against Keap data
The notes pipeline is the connective tissue. Subsystem 3 isn't a direct answer to any single numbered problem — it's what keeps Subsystem 2's member records from going stale again the moment the portal ships. Every call auto-publishes structured notes to the record it belongs to, which is the actual mechanism that prevents Hot Sheets from freezing at intake a second time.
03

Why build, not buy

Your own tool inventory already answers this: CoachSimple, Calendly, and Google Calendar as a scheduling front end are being replaced; Keap, Vimeo, and Google Meet + Gemini are staying. We reviewed three platforms for context before recommending this direction — CoachSimple (your incumbent), Kajabi (the course-builder UX your team named as its bar), and Mighty Networks (the closest thing on the market to a mastermind-community platform).

PlatformStrongest atWhy it's still not the answer
CoachSimpleCoaching-specific vocabulary out of the box; same backend runs RECoach.me for real-estate coaching franchises.No content analytics, unsortable revenue, a dead scheduling tab, and — as your brief notes — no path to Gemini-based notes, Whisper-searchable video, or Keap-tag-driven access.
KajabiThe drag-and-drop course builder your team named directly; bundled marketing and a branded app on Growth+.Has no concept of a coach-matching scheduling agent, a Gemini notes pipeline, or Keap as an external system of record — your actual operating model would be bolted on with brittle automations, not built in.
Mighty NetworksBest-in-class community/engagement layer; native apps at its Pro tier.Same gap as Kajabi, plus lighter course authoring — and neither platform can search ten years of Vimeo video the way Subsystem 1 is scoped to.

None of the three run a Keap-tag access model, ingest Gemini notes, or offer hybrid search over an existing Vimeo library — which is exactly the ground your four subsystems are built to cover. Custom is the only path that makes your existing Keap/Vimeo/Meet investment work together instead of around each other.

04

System architecture

One database, four subsystems, nine integrations, hosted end to end on Google Cloud. Keap stays the system of record for member status, billing, and access — everything else in the portal reads from it and writes structured data back out to it, never the reverse.

STAYING — SYSTEMS OF RECORD Keap status · billing · tags Vimeo ~500hrs training video Google Meet + Gemini calls + notetaking SUBSYSTEMS (NEW) 1 · Training search 2 · Core portal 3 · Notes pipeline 4 · Scheduling agent SHARED DATA LAYER Postgres + pgvector member records · goals notes · transcript vectors SUPPORTING SERVICES Whisper transcription LLM: extraction · matching Drive watch / poll listener Email + SMS (Postmark/Twilio) Cloud Run workers + Tasks STAYING Helpscout support · under review

The nine integrations, as scoped in your brief

#IntegrationWhat's needed
1KeapRead contacts, read/write custom fields, webhooks on tag add/remove — the canonical member ID and the access-control mechanism.non-trivial
2Google CalendarCreate/modify/cancel events, read availability across every coach's calendar.standard
3Google MeetAuto-generate meeting links via the Calendar API — mandatory, since Gemini only attaches to Meet.standard
4Gemini notes ingestionGet note output into the system automatically — the biggest technical unknown. See Section 05.non-trivial
5VimeoList videos, pull files/titles/dates/play stats — one-time bulk pull, then ongoing for new uploads.standard
6Whisper (OpenAI)Transcription with word-level timestamps — one-time bulk run.standard
7LLM APINote extraction, accountability-email drafting, video tagging, booking-request interpretation.standard
8Transactional emailAccountability emails and booking confirmations — Postmark/SendGrid, or route through Helpscout.standard
9SMSBooking confirmations by text — already part of the current SOP.standard

Recommended stack

LayerRecommendationWhy
DatabasePostgreSQL + pgvector, run as Cloud SQL for PostgreSQL — confirming the assumption in your briefOne database serves both structured records and transcript-passage vector search. A separate vector store would be an extra operational system for no real gain at this scale (~500 videos, ~150 members). Cloud SQL's pgvector support is a managed, officially supported extension — no separate vector database to run, patch, or secure. AlloyDB for PostgreSQL is the natural upgrade path if the training library or member base grows well past this scale, since its built-in ScaNN index outperforms pgvector's HNSW at larger vector counts — the same Postgres wire protocol either way, so it's a resize decision, not a rewrite.
ApplicationNode.js/TypeScript or Python, containerized, deployed on Cloud RunCloud Run services (always-on) host the API and the always-listening pieces (the Drive watch endpoint, the scheduling agent); Cloud Run Jobs handle bounded batch work (Vimeo bulk pull, Whisper transcription runs) with timeouts up to seven days — comfortably enough for the ~500-hour backlog without needing a separate VM or Kubernetes cluster to operate.
Object storageCloud StorageWorking audio/video during transcription, archival copies of Gemini notes docs pulled from Drive, encrypted backup exports, and member-uploaded revenue documentation — lifecycle-managed and CMEK-encrypted rather than living on local disk or a separate storage vendor.
Job queue / asyncCloud Tasks for retryable work, Pub/Sub for event fan-outThe Drive API can publish its push notifications straight to a Pub/Sub topic — the Section 05 watch channel becomes a native GCP subscription instead of a webhook endpoint the app has to defend on its own. Cloud Tasks handles retry/backoff for Keap reconciliation, accountability email sending, and SMS confirmations, each independently, so one fragile step never blocks a request.
HostingGoogle Cloud Platform, end to endEvery external dependency this build has outside its own code — Meet, Gemini, Calendar, and Drive — is already Google Workspace, and the Section 05 notes-ingestion fix already runs on a Google service-account identity. Hosting the app, the database, and that identity on GCP keeps them inside one IAM boundary instead of stitching a second cloud vendor's credentials into an already Google-native pipeline. See the table below for the full service mapping.

Why Google Cloud specifically

This build's dependency graph already leans almost entirely on Google. Keap is the one system of record that doesn't; everything else — the video call, the notetaker, the calendars, the file that carries the notes — is Google Workspace. Hosting on GCP isn't a generic "pick a cloud" choice; it's a decision to stop crossing a vendor boundary for pipelines that never needed to cross one.

FunctionGCP serviceRole in this build
ComputeCloud Run (services + jobs)API, coach/member web app, the always-on scheduling agent and Drive-watch listener, and bounded batch jobs (transcription, bulk Vimeo pull).
DatabaseCloud SQL for PostgreSQL (pgvector) → AlloyDB if scale demands itMember records, goals, revenue, notes, and transcript-passage vectors — one instance, automated backups and point-in-time recovery built in.
Object storageCloud StorageTranscription working files, Gemini notes doc archive, backup exports, member-uploaded documentation.
Async / queueCloud Tasks, Pub/SubRetryable webhook and notification delivery; the Drive push-notification channel from Section 05 publishes here natively.
Identity backing Section 05IAM + a dedicated Workspace service accountThe centralized Meet-organizer identity that makes the Gemini notes pipeline tractable is already a Google identity — GCP IAM governs it directly rather than through a second vendor's credential store.
Secrets & encryptionSecret Manager, Cloud KMSKeap, OpenAI, and LLM-provider API keys held outside application config; CMEK-managed encryption keys for Cloud SQL and Cloud Storage.
Perimeter & accessCloud Armor, Identity-Aware Proxy, VPC Service ControlsWAF/DDoS protection on the public app; the admin and coach interface gated behind the same Google Workspace SSO coaches already use for Meet and Gemini; database and storage traffic kept off the public internet.
CI/CD & observabilityCloud Build, Artifact Registry, Cloud Logging/Monitoring, Error ReportingContainer builds and deploys, and the logging/alerting layer that catches problems before they reach your members.
One vendor, one IAM system, one bill — this also keeps vendor governance and credential management simple, since there's no second cloud's credentials to rotate or audit alongside Google Workspace's own.
05

Solving the Gemini notes unknown

This is the question your brief calls its largest unknown, and we want to answer it concretely rather than leave it open. Google's own documentation for "Take notes for me" confirms the constraint: when a Meet call ends, Gemini saves the recap as a Google Doc into the meeting organizer's Drive, in a "Google Meet" folder, attaches it to the Calendar event, and emails a link to whoever was granted access. There is no dedicated webhook or API built for this — which is exactly why it reads as an unknown.

The way through it is in how the calls get booked, not in how the notes get read. If Subsystem 4's scheduling agent creates every coaching-call event under one dedicated Workspace identity — a service calendar, not each coach's personal one — every Gemini notes doc for every coach lands in that single account's Drive. One Drive to watch instead of monitoring N coaches' personal accounts, which would otherwise require Workspace domain-wide delegation and admin consent per coach just to read their files.

Primary: Drive watch channel

Register a Drive API push-notification channel on that one service account's "Google Meet" folder. New file → webhook fires → pull the doc via the Docs API → hand off to the extraction layer. Fast, but watch channels expire and need scheduled renewal.

Belt and suspenders: polling fallback

A worker polls that same folder every few minutes for files created since the last check. Catches anything a lapsed watch channel misses — cheap insurance on the pipeline's single biggest dependency.

Fallback if centralizing isn't possible

If coaches must remain individual meeting organizers for calendar-ownership reasons, the same pattern still works via a Workspace service account with domain-wide delegation, reading each coach's Drive — more setup and an admin-consent step, but the same mechanism underneath.

Recommend validating this in Phase 0 — run one real coaching call through the centralized-organizer pattern before committing engineering time to Subsystem 3, since the whole notes pipeline gates on this working as described.
06

Answers to your questions

Taking the questions from your brief in order — technical first, then commercial.

1 · How would you get Gemini meeting notes into the system automatically?

Covered in full in Section 05 — the short version is: centralize the Meet organizer identity and watch its Drive, with a polling fallback. We recommend validating this first, in Phase 0, since it gates the entire notes pipeline.

2 · Any concerns with Keap's API and webhook reliability at your volume?

Not at ~150 members — Keap's published limits (1,500 requests/minute on OAuth2 tokens, up to 10,000/minute per application instance) are far beyond what a portal this size generates. The real risk isn't volume, it's that webhook delivery on any platform is best-effort, not guaranteed. We recommend treating Keap webhooks as the fast path for tag-change access updates, backed by a nightly reconciliation job that polls Keap directly and corrects any drift — so a missed webhook never permanently locks a member out of, or leaves them in, a portal tier.

3 · Multi-coach availability across Google Calendars — how much complexity does that add?

Less than it sounds. Google's FreeBusy API accepts multiple calendar IDs in a single query, so pulling every coach's open slots isn't the hard part. The real complexity is app logic: matching a request to a coach by specialty and capacity, honoring the "one open booking per member, released on a timer" rule, and handling per-member time zones cleanly. That logic belongs in Subsystem 4's booking state machine, not in the calendar integration itself.

4 · Preference on hosting and stack? We've assumed Postgres + pgvector.

We agree, and cover it in full in Section 04 — Postgres + pgvector is the right call at this scale rather than running a separate vector database alongside it. On compute, this revision recommends Google Cloud specifically: Cloud SQL for PostgreSQL (pgvector-enabled), Cloud Run for the application and its background workers, and Cloud Storage for everything file-shaped. The reasoning is dependency-driven, not generic cloud preference — Keap aside, every other system this build touches (Meet, Gemini, Calendar, Drive) is already Google Workspace, and the Section 05 notes-ingestion fix already runs on a Google service-account identity. We'd like to confirm this with you in Phase 0 alongside the notes-ingestion validation.

5 · Can this be priced per subsystem so we can sequence the build?

Yes — and it should be, since three of the four subsystems already have complete designs, which lowers estimation risk on those specifically. The previously-deferred member-facing pieces (90-day tracker, onboarding dashboard, in-portal chat, event tickets, support tickets) are better scoped as their own line item once they have a design pass, whether that happens inside this build now or afterward.

6 · What would you recommend building first?

Training Library Search — it's independent of the other three, fully designed, and gives your team (and your membership) a fast, visible win before the harder integration work starts. Core Portal comes next, since Subsystems 3 and 4 both need member records and Keap-driven access to build against. With the launch date now in May 2027, Notes Pipeline and Scheduling can run sequentially rather than in parallel — see the roadmap in Section 11.

7 · What's your estimate for the training library search alone, as a contained first project?

Your own design-side estimate — 2–3 weeks and under $500 in one-time API cost — covers the transcription/embedding pipeline. Building the hybrid-search UI and timestamped playback on top of it is additional engineering time on the same order; a single engineer working through Vimeo pull → Whisper → chunk/embed → search → playback end to end is a reasonable scope for roughly 3–4 weeks. This is a rough order of magnitude, not a firm quote — we'll firm it up once we've scoped it against our actual rate and availability.

8 · Ongoing maintenance and support model?

We recommend a monthly retainer covering three things specifically: pass-through API costs (Whisper, LLM, embeddings), active monitoring of the two most fragile, most novel pieces in this system — the Gemini-notes ingestion pipeline and the scheduling agent — and a defined bug-fix SLA. Those two pipelines depend on external services with no formal API contract (Drive-based notes ingestion, LLM-driven interpretation), so they're the parts most likely to need attention after launch. We'll provide support and training on the app once it's launched, and we're positioned to support any updates after that — see Section 13 for the ongoing partnership model we're proposing.

9 · What do you need from us to give a firm number?

Everything already offered: the full ~7,000-word design spec, the annotated mockups for the five designed screens, the current-state SOPs, sample Gemini note outputs for extraction testing, and discovery access to Keap, Vimeo, and CoachSimple. Add one thing — a short technical discovery session to test-run the Section 05 notes-ingestion approach and confirm Keap webhook access — before firming a fixed number on Subsystems 3 and 4 specifically, since those carry the two non-trivial integrations.

07

Security, hosting & the data model

Two constraints from your brief shape this more than anything generic: coaching notes are visible to every coach but never queryable across members (browsable per-member only, since only the training library is meant to be searchable), and nothing in the system is ever deleted — goals and commitments are marked done, in progress, or no longer relevant, and stay in the record permanently.

Access controlKeap tags remain the source of truth for who can see what; the portal enforces record-level permissions on top — a coach reaches every member's notes, a member reaches only their own.
Data modelAppend-only for goals and commitments: status changes are new rows or status fields, never row deletions, which also gives a free audit trail of a member's actual 90-day history.
The one review gateNotes auto-publish with no human check; only the accountability email draft waits for approval. That single checkpoint is worth instrumenting carefully — it's the one place a bad LLM output reaches a member directly.
Encryption & secretsTLS in transit; encryption at rest via Cloud KMS-managed (CMEK) keys on Cloud SQL and Cloud Storage; API keys for Keap, OpenAI, and the LLM provider held in Secret Manager, never in application config.
Network & perimeterCloud Armor in front of the public app for WAF/DDoS protection; Identity-Aware Proxy gating the admin and coach interface behind the same Google Workspace SSO coaches already use for Meet and Gemini; VPC Service Controls keeping Cloud SQL and Cloud Storage traffic off the public internet.
Service identityThe Section 05 centralized Meet-organizer account is a dedicated Google Workspace service identity, scoped through IAM to exactly the Drive folder it needs to watch — the same access boundary that protects the database also governs the one account with the widest reach into coaches' calendars.
BackupsAutomated, encrypted, point-in-time recovery via Cloud SQL's built-in backup and restore — coaching notes and revenue history are not the kind of data to risk on anything less.
08

iOS and Android

Members and coaches both need this on a phone — a coach checking a Hot Sheet before walking into a call, a member logging a monthly revenue number between meetings.

PhaseApproachWhat it delivers
At soft launchMobile-first responsive web app, installable as a PWAHome-screen icon on both iOS and Android, an offline-capable shell, push notifications on Android — full mobile coverage with zero app-store review risk to the launch date.
Post-launchNative wrapper (React Native/Expo or Capacitor) around the same codebaseApp Store and Google Play listings, full iOS push notifications, native camera/file access for revenue documentation. With the extended runway, this could also move earlier — we've put that question to you in Section 14.
09

Coach & admin interface

Your brief calls the coach dashboard "the highest-stakes screen in the system" — the dense, at-a-glance member snapshot a coach reads in the sixty seconds before a call starts. It already has mockups; our job is to build it exactly as designed and not let scope creep dilute its density.

Coach dashboard

Per-member snapshot: current goal-cycle status, latest structured notes, revenue trend, open action items and dated commitments, upcoming session — the "walk in prepared" screen the current system can't provide.

Member records

Full history per member, browsable, never queryable across the roster — notes, revenue entries, intake form versions, goal history, all append-only.

Scheduling oversight

Visibility into the booking agent's assignments with admin override for every rule it enforces — coach match, one-open-booking limit, timer release.

Accountability email queue

The one human-approval checkpoint in the system — drafts generated after each call, held for review before sending.

Reporting / export

Wins, revenue, action steps, and goals, exportable and joinable against Keap data — the direct fix for "data is not extractable."

10

Member interface

Coach-facing views are designed; member-facing views are not — this is the one piece of the "already-designed" subsystems that still needs a design pass before it's built.

Dashboard

Current goal-cycle status, next scheduled session, recent notes summary.

Training library

Hybrid search across ten years of Vimeo content, results linking straight into the video at the right timestamp.

Booking

Request a session; the scheduling agent matches a coach and confirms — no back-and-forth, one open booking at a time.

Revenue & goals

Monthly revenue entry, 90-day goal tracking against the member's own history.

My notes

Own coaching-call notes and action items — never another member's.

Previously held out of scope: the member-facing 90-day visual tracker/journey, an onboarding dashboard, in-portal 1:1 chat, event ticket claiming, and support tickets. With the launch date now in May 2027, Section 11 treats folding these into the build as an open option rather than an automatic deferral.
11

Phased roadmap to launch

Your launch date has moved from the third week of December 2026 to May 2027 — the runway triples, from about 14 weeks to about 36. Rather than just stretch every phase proportionally, we've put the extra time to use in the two places it matters most: Subsystems 3 and 4 now run sequentially instead of in a shared parallel sprint, and the integration/hardening phase before launch is substantially longer, especially for the scheduling agent, which is the one subsystem shipping with no human approval step. The exact week is still to be finalized with you — the bars below assume the third week of May 2027, mirroring your original "third week" framing, but we'd like to confirm that with you (see Section 14).

Sep 14 – 20, '26
Sep 21 – Oct 16
Training search
Oct 19 – Dec 11
Core portal
Dec 14 – Jan 29, '27
Notes pipeline
Feb 1 – Mar 26
Scheduling agent
Mar 29 – May 14
Integration & hardening
Week of May 17
Discovery Subsystem 1 Subsystem 2 Subsystem 3 Subsystem 4 Hardening Launch

Phase 0 — Discovery & validation · Sep 14–20, 2026

Unchanged — no reason to delay this. Validate the Section 05 notes-ingestion pattern against one real call; confirm Keap API/webhook access and rate limits directly; audit the ~500-video Vimeo library for metadata quality; stand up the Cloud SQL/Cloud Run/Cloud Storage foundation from Section 04.

Phase 1 — Training library search · Sep 21–Oct 16, 2026 (4 weeks)

Vimeo bulk pull → Whisper transcription → chunk into passages with timestamps → embed → hybrid keyword + semantic search → results linking into the video at the right moment. Ships standalone — your own brief's "good first deliverable." A week more relaxed than the original estimate, not because the work grew, but because there's no reason to rush a phase this well-scoped.

Phase 2 — Core portal & member records · Oct 19–Dec 11, 2026 (8 weeks)

Keap-tag-driven login and access; the coach dashboard from its existing mockups; the member dashboard, designed fresh in this phase; goal and 90-day cycle tracking with carry-forward; monthly revenue entry; versioned intake forms; the reporting/export layer joinable against Keap data. This is the natural point to decide on the previously-deferred member-facing pieces (90-day visual tracker, onboarding dashboard, chat, tickets) — if you want them in this build, their design pass belongs here, alongside the member dashboard's own design work.

Phase 3 — Coaching notes pipeline · Dec 14, 2026–Jan 29, 2027 (7 weeks, spans the holidays)

The centralized-organizer ingestion pattern, the structured extraction layer (session focus, strategic direction, action items, dated commitments, flags), auto-publish to the member record, and the accountability-email approval queue. Now standalone rather than sharing a sprint with Scheduling, with slack built in for the holiday period.

Phase 4 — Automated scheduling · Feb 1–Mar 26, 2027 (8 weeks)

The booking agent — request interpretation, coach matching by specialty and capacity, multi-calendar availability, the one-open-booking-at-a-time timer, Google Meet creation, email/SMS confirmations, and admin override for every rule. This is the one subsystem shipping with no human approval step, so it gets a dedicated window rather than sharing time with the notes pipeline — including real slack for adversarial testing, deliberately trying to trigger a double-book or a mismatched coach before real members can.

Phase 5 — Integration, UAT & hardening · Mar 29–May 14, 2027 (7 weeks)

Full end-to-end testing across all four subsystems together, staff training on the coach dashboard and override tools, a phased internal pilot before the wider soft launch, and — given how much runway this phase now has — room to also harden the scheduling agent against edge cases a tighter timeline wouldn't have allowed time to find.

Soft launch — week of May 17, 2027 (assumed; confirm exact week)

Released to a pilot group first, with the scheduling agent's admin override live and watched closely through the first bookings.

Phase 6 — Full rollout · June 2027 onward

Expand to all ~150 members once the soft launch holds up under real use. Then, whatever wasn't folded into Phase 2: the native iOS/Android app wrapper, and any of the five previously-deferred member-facing pieces you chose to leave for later.

12

Scope guardrails & open items

Six things we'd like to pin down with you: confirming the exact soft-launch week in May 2027, since this plan currently assumes the third week; confirming the Section 05 notes-ingestion pattern actually works end to end on a real call, since the entire notes pipeline depends on it; deciding whether coaches can operate under a centralized Meet-organizer identity or whether domain-wide delegation is required instead; sizing the nightly Keap reconciliation job against real tag-change volume; deciding whether the five previously-deferred member-facing pieces get folded into Phase 2's design pass now that the runway allows it, or stay out for Phase 6 — worth resolving early, since that decision changes Phase 2's scope; and, given Subsystem 4 ships with no human approval step, agreeing on what "ready" looks like for the scheduling agent specifically, since a mistake there reproduces the exact double-booking problem this whole build exists to fix. We've turned these into direct questions for you in Section 14.

13

Support & ongoing partnership

Two commitments worth calling out on their own, separate from the build itself.

Post-launch support and training. Social Lexicon will provide support and training on the app once it's launched — your staff and coaches won't be handed a finished system with no one to walk them through it. This covers onboarding your team to the coach dashboard, override tools, and reporting layer described in Sections 09–10.
Ongoing updates. Any updates to the app after launch — bug fixes, refinements, new features — can be supported by Social Lexicon. If approved, we can formalize this into an ongoing support model, building on the monthly-retainer structure already outlined in Q8 above (Section 06), rather than requiring you to find and onboard a new developer for every change.
14

Questions for the stakeholders

Before we lock this plan in, here's what we need your team to weigh in on — grouped by topic, not by how urgent each one is. The last six come directly from a second round of admin-tools footage your team shared with us.

Launch weekCan you confirm the exact week in May 2027 you'd like to soft-launch? This plan currently assumes the third week (targeting May 17), but we want that locked before we finalize Phase 5's schedule.
Notes-ingestion validationCan we get access to run one real coaching call through the centralized Meet-organizer pattern during Phase 0? And separately — can your coaches operate under one shared Workspace identity as the meeting organizer, or does your team need each coach to remain their own organizer for calendar-ownership reasons? This decision shapes how Section 05's fix gets built.
Keap access & volumeCan you confirm Keap API/webhook access details ahead of Phase 0, and give us a rough sense of how often member tags change day to day? That number sizes the nightly reconciliation job correctly from the start.
Previously out-of-scope piecesDo you want the five previously-deferred member-facing pieces — the 90-day visual tracker, onboarding dashboard, in-portal chat, event tickets, and support tickets — designed and built as part of Phase 2, now that the extended runway allows it? Or should they wait for Phase 6? This decision changes Phase 2's scope, so we'd like it early.
Scheduling agent readinessSubsystem 4 goes live with no human approval step. What would your team need to see in testing to trust it with real bookings — specific edge cases, a minimum error rate, a trial period with manual spot-checks? We want to agree on that bar together before Phase 5 wraps.
Pricing structureWould you like us to price this per subsystem, as discussed in Q5? If so, are you comfortable firming up Subsystems 3 and 4 only after the short technical discovery session in Phase 0 (Q9), given those two carry the non-trivial integrations?
Google Cloud ownershipAre you comfortable with Google Cloud as the hosting environment? If so, who should own the Cloud billing account and the Google Workspace admin console access needed to set up the Section 05 service account — your team, ours, or a shared arrangement?
Ongoing support modelDo you want to move forward with the monthly retainer we've outlined in Section 06 (Q8) and Section 13? If so, what should it cover beyond pass-through API costs, notes-pipeline and scheduling-agent monitoring, and a bug-fix SLA?
Native mobile app timingWould you like the native iOS/Android app wrapper (Section 08) pulled earlier into the roadmap, or should it stay a Phase 6 item after the web-based PWA covers you at launch?
Budget & decision timelineDo you have a budget range and an internal decision timeline you can share? That helps us sequence the roadmap in Section 11 around what's actually approvable, rather than around an assumption.
Course & lesson authoringYour admin-tools walkthrough shows your team building new templates (courses) and worksheets (lessons) directly inside CoachSimple — a workflow you called clunky, and noted a platform like Kajabi handles more easily. None of the four subsystems in this proposal cover authoring new course content; Subsystem 1 searches your existing ~500-hour Vimeo library, it doesn't create new lessons. Should course/lesson creation be built into this portal, stay on a separate tool going forward, or is new-course creation rare enough that it's out of scope either way?
Staff & coach access managementYour current system's "Coaches by Portal" tool lets you control which staff members see which parts of the admin backend. Should the new portal include an equivalent admin screen for managing coach and staff access, on top of the Keap-tag-driven member access already scoped in Section 07?
Member lifecycle & login resetToday you can mark a member inactive — keeping their records intact — and reset their login credentials directly from the admin panel. Can you confirm this maps cleanly onto Keap status tags, or does the new portal need a dedicated "reset login" admin action alongside it?
Non-video resource libraryYour walkthrough also describes a separate library for non-video assets — PDFs, worksheets, the portal banner image, coach headshots — distinct from the Vimeo-based Training Library Search in Subsystem 1. Should the new portal include an admin tool for managing these non-video resources and branding assets, or will that stay outside this build?
How "wins" get capturedToday, wins are gathered manually by watching your Facebook group. Section 09's reporting layer treats wins as an exportable field, but Subsystem 3's automated extraction doesn't currently define "wins" as its own output alongside action items and commitments. Should we add wins as a field the notes pipeline extracts automatically, or will coaches keep logging them by hand?
Membership tier modelYour walkthrough notes you've moved away from a "teams" tier and now run essentially two — mastermind and collaborative. Can you confirm this is how Keap tags currently segment your membership, so Subsystem 2's access model is built against the tiers you actually use today?