Haris + Alex | Altitude
matchedTue, Nov 18, 2025, 3:00 PM • —
Client
Altitude Create
Participants
0 attendees
Action Items
16
16 pending
AI Meeting Analysis
AI GENERATEDClient Sentiment
[~]MIXEDThe conversation shows forward momentum and optimism around process improvements, monetization, and hiring, but also highlights friction and risk: stalled WebRTC due to missing requirements, uncertainty around PHP stability, and concerns about maintenance fees and vendor transitions.
Meeting Quality
Relationship Status
stableExecutive Summary
The meeting aligned on shifting new website builds to BrandRap/Grand Rap while temporarily keeping existing sites with current vendors, alongside addressing maintenance cost and platform stability risks (notably PHP support). The team also discussed stalled WebRTC deployment due to missing requirements, a new coaching monetization credit model, and process improvements via ClickUp, supported by a plan to hire a technical lead to unlock potential investment.
Key Topics Discussed
Decisions Made
- ✓New website projects will transition to Grand Rap/BrandRap; existing sites remain with current vendors in the interim.
- ✓Client request and project communication will be centralized through ClickUp to reduce delays and improve visibility.
- ✓A technical lead hire (Silicon Valley) will be pursued as part of a strategy to unlock up to $1M in investment and improve execution capacity.
- ✓A coaching monetization approach using a credit system (with first lesson free for new users) will be explored as the preferred direction, pending refinement/feedback.
Follow-up Items
- →Inform Patrick he is removed from new website projects and finalize a transition plan for his current design commitments.
- →Send Haris’s team 4–5 websites by early next week to start the service handoff.
- →Schedule and run onboarding with Nick to align on sales process and communications.
- →Provide the team and Patrick with detailed onboarding flow and product profile guidance.
- →Review Campus Connect documentation and provide feedback on UI and feature specifications.
- →Decide whether to continue with Patrick for Campus Connect design based on deliverables quality/timeliness.
- →Arrange a test environment release (e.g., TestFlight) of the Whoosh app for Derek to test in real-world conditions.
- →Coordinate with technical/legacy support to assess PHP bug fixes vs. need for a rebuild.
- →Obtain Google Analytics access for site traffic monitoring and reporting.
- →Evaluate pricing for maintaining transitioned websites, including potentially lower fees for legacy/existing sites.
- →Prepare an internal proposal on service costs and communicate it to Alex.
- →Set up ClickUp communication workflows and ensure notifications trigger at new project stages.
- →Run a progress/readiness check on WebRTC chat implementation and define integration points.
- →Review and summarize Alex’s recent document updates; identify missing feedback and gaps in Campus project requirements.
- →Prepare for and attend the morning status meeting to clarify requirements and confirm project readiness.
- →Draft and send a detailed credit-system framework for coach pricing to Alex for feedback.
Open Questions
- ?What is the finalized transition timeline and scope for moving websites from current vendors to BrandRap/Grand Rap?
- ?What maintenance pricing model will be used for existing sites vs. newly transitioned sites, and what SLAs are included?
- ?Can the current platform remain stable with ongoing PHP support constraints, or is a rebuild required (and on what timeline/budget)?
- ?What are the exact WebRTC product requirements, user flows, and integration points needed to ship (and who owns the PRD)?
- ?Will Patrick remain involved in Campus Connect design, and what deliverables/criteria determine that decision?
- ?What is the final credit pricing structure (credit packs, coach rates, platform take rate, refunds/expiration) and how will it be tested?
- ?What are the concrete hiring requirements, compensation range, and timeline for the Silicon Valley technical lead role?
- ?What investment milestones/conditions are tied to hiring the technical lead and improving execution?
AI Recommendations
- ★The meeting produced clear strategic direction (website transition, ClickUp process, hiring intent) and a robust action list, but key blockers remain unresolved—especially missing WebRTC requirements/PRD, unclear maintenance pricing, and uncertainty on platform viability—reducing immediate execution readiness.
Analysis generated: Dec 15, 2025, 7:45 PM
Action Items
Prepare internal proposal on service costs and communicate to Alex
Review Campus Connect documentation and provide feedback on UI and feature specifications
Decide on whether to continue with Patrick for Campus Connect design based on deliverables
Arrange test environment release (e.g., TestFlight) of Whoosh app for Derek’s real-world testing
Coordinate with technical and legacy support to explore PHP bug fixes or necessity of rebuild
Gain access to Google Analytics for site traffic monitoring
Inform Patrick about removal from new website projects and finalize transition plan for his current design commitments
Provide Haris’s team with 4-5 websites by early next week to initiate service handoff
Schedule and coordinate onboarding meeting with Nick, ensuring alignment on sales processes and communications
Provide detailed onboarding flow and product profile guidance to the team and Patrick
Coordinate team communication setup via ClickUp and ensure notifications for new project stages
Provide detailed credit system framework for coach pricing to Alex for feedback
Prepare for and participate in morning meeting to review project statuses and requirements clarification
Evaluate pricing structure for maintaining transitioned websites, considering lower fees for existing sites
Review and summarize Alex’s recent document updates; highlight missing feedback for campus project requirements
Facilitate progress update and readiness check on WebRTC chat implementation and integration points