1. February Launch Strategy: Samuel & Patrick
Will proposed bringing two partners under Athio for rapid February launches to build credibility and revenue while Brad/Bridger timelines remain uncertain. Samuel (Align360) has a career navigation product with ~1,000 candidates through an affiliate partner. Patrick (Soil King) has a regenerative agriculture AI assistant with proven audience traction (347 signups from a single Instagram story).
Patrick has a 5-month event series starting in March across multiple cities, creating urgency to get the alpha ready in February.
Strategy
Partnership
Discussed: 02:35 - 04:12 | Participants: Will, Jason
2. Derek's Role: Pipeline Ownership vs. Ad Hoc
Jason stressed that Derek's role must be to own the entire pipeline and build systems, not just be an ad hoc middleman. The value of Derek managing Samuel and Patrick is to codify the process — create checklists, SOPs, and repeatable workflows for every stage of the customer journey. Jason referenced the E-Myth concept: build it so anyone could step in and run it.
Will agreed: "Having some launches under our belt is kind of the other main barrier to revenue and sales."
Process
Strategy
Discussed: 04:23 - 07:39, 44:49 - 47:53 | Participants: Will, Jason, Derek
3. Partner Onboarding: The 4-5 Buckets
Jason identified the critical assets needed upfront for every partner launch. These must be collected in one sitting, not dripped over weeks:
1. Brand Assets — images, photos, thumbnails, icons for display
2. ICP Definition — who their audience is, who's currently paying them, what problems they solve
3. Frameworks — their actual teaching methodologies and recipes
4. Pricing/Offering — what the alpha/beta includes and costs
5. Voice Data — large sample of their thinking patterns (podcasts, transcripts, content)
Process
Onboarding
Discussed: 27:06 - 30:36 | Participants: Jason, Will
4. Quality Control Bottleneck Solution: Point-of-Contact
Will proposed that each partner designate a point-of-contact (assistant, team member, or superfan) to handle quality control and feedback during the build process. This prevents the high-value partner from being the bottleneck. Example: Bridger's assistant Aaron could test if the AI "sounds like Bridger" instead of waiting weeks for Bridger to respond.
Jason expanded: this person needs to know the partner well enough to stress-test the AI, not just confirm it uses their catchphrases.
Process
Strategy
Discussed: 33:31 - 36:23 | Participants: Will, Jason
5. Multi-Tenant Architecture & Launch Timeline
Jason confirmed multi-tenant is set up and working. Pattern: [brand].betaapp.io (e.g., careernav.betaapp.io, soilking.betaapp.io). The "beta app" branding feels appropriate since partners are told they're in an alpha/beta group.
Realistic timeline: ~1 week to stand up an alpha workspace if all 4-5 buckets are filled. Additional week for partner QC testing and iteration. Total: 2-3 weeks per partner, depending on responsiveness.
Tech
Process
Discussed: 25:57 - 31:27 | Participants: Jason, Will
6. Ralph Orchestrator & Tech Architecture
Jason described the technical architecture he's building: Redis caching layer (saves tokens for repeated questions), model router (scores question complexity and routes to appropriate model), and agentic skills via Anthropic's patterns. Decided to standardize on Sonnet 4.5 with caching for most chatbots.
The Ralph Orchestrator breaks builds into small PRDs with estimated time, token budgets, and model selection, then loops through each step. If it works, feature development velocity should increase significantly.
Tech
Discussed: 16:30 - 24:42 | Participants: Jason, Will
7. Brad/Tiger Quest Clarity Issues
Jason expressed confusion about Brad's Tiger Quest value prop, branding, and messaging. Will admitted he's "not sure either" and just went through removing unclear language. Key unresolved questions: What do customers actually get for $500? Is it just access to Brad, or do frameworks need to be built? How does it tie to health clinics? Should pricing be much lower for alpha?
Agreed to discuss further but not on this call. Filed as a known uncertainty.
Strategy
Partnership
Discussed: 08:32 - 11:39 | Participants: Jason, Will
8. Hilsoma Healthcare AI Opportunity
Derek presented a friend's healthcare platform (Hilsoma / KilSoma) that connects health experts to consumers based on lab results. They want to clone Dr. Prince for training healthcare providers on reading lab work. Expecting $10M company within 2 years.
Key insight from Derek: Hilsoma's experts are sourced through social media influencers, making it a potential gateway to health influencers at scale — which aligns with Athio's model.
Jason's guidance: Take the discovery call, keep scope atomic and clearly defined, don't over-promise. Get their modules and data, evaluate if it fits. Position as "this isn't our normal model but we're intrigued." Cash deal first, not equity.
Opportunity
Partnership
Discussed: 55:04 - 01:09:30 | Participants: Derek, Will, Jason
9. Voice Agent, MasteryOS & Tooling Updates
Jason reported: voice agent is up and running but costs $60/day in testing. Working on MasteryOS features. Building a sales proposal tool that could itself become a product ("dog-fooding" concept). DNS engine and multi-tenant publishing tools are in the pipeline. Also building a pricing calculator skill to model costs backward from query volume and model selection.
Will mentioned his upcoming move to Austin on Jan 30 and limited bandwidth for the coming weeks.
Tech
Strategy
Discussed: 15:17 - 16:30, 01:06:19 - 01:07:17 | Participants: Jason, Will
D1. Bring Samuel & Patrick Under Athio for February Launches
Both partners will be brought under the Athio fold for February product launches. Samuel's Align360 has a pipeline of ~1,000 candidates via an affiliate partner. Patrick's Soil King has a proven audience and a March event series creating natural urgency. This de-risks the Brad/Bridger uncertainty.
Decided by: Will (proposed) + Jason (approved) | Impact: High — creates revenue path independent of Brad/Bridger
D2. Derek Owns Pipeline + Must Codify the Process
Derek's role is not ad hoc relationship management — he must use Samuel and Patrick as vehicles to build the launch SOP. Every step of the customer journey from networking to live product must be documented as a repeatable checklist. Goal: anyone could step in and continue the process.
Decided by: Jason + Will | Impact: Critical — creates scalable infrastructure
D3. Require Point-of-Contact for Each Partner
Every partner should designate a point-of-contact (assistant, team member, or superfan) who can handle quality control, provide feedback, and stress-test the AI build. This removes the influencer as the bottleneck. Will proposed it; Jason endorsed enthusiastically.
Decided by: Will (proposed) + Jason (endorsed) | Impact: High — eliminates #1 bottleneck
D4. Upfront Asset Collection: 4-5 Buckets Required
Before any partner launch, all required assets must be collected in one sitting: brand assets, ICP definition, frameworks, pricing/offering, and voice data (podcasts/transcripts). No more dripping information over weeks. If partner won't provide, team scrapes independently.
Decided by: Jason | Impact: High — reduces launch time from weeks to days
D5. Multi-Tenant Pattern Confirmed: subdomain.betaapp.io
All alpha workspaces will use the [brand].betaapp.io subdomain pattern. Feels appropriate since partners are in an alpha/beta group. Multi-tenant infrastructure is ready to deploy.
Decided by: Jason | Impact: Medium — removes technical ambiguity
D6. One Week Realistic Timeline Per Alpha (If Assets Ready)
With all 4-5 asset buckets filled, a workspace can be stood up in roughly one week. Add another week for partner QC and iteration. Will suggested one week "to be safe" for setup including assistants and complexity.
Decided by: Jason + Will | Impact: Sets expectations for Samuel/Patrick
D7. Hilsoma: Explore as Scoped Cash Deal
Derek will take a discovery call with Hilsoma/Dr. Prince. Approach: "This isn't our normal model, but we're intrigued." Get their training modules, evaluate scope. If clearly defined (A-to-Z training course), it's doable. Cash deal first — no equity until validated. Could be a gateway to health influencers via Hilsoma's platform.
Decided by: Jason (guided approach) + Derek (executing) | Impact: Potential pipeline multiplier
D8. Aaron Could Train on Hilsoma Project
Will suggested using the Hilsoma project as a training opportunity for Aaron to learn how to build AI assistants and frameworks. Gets Aaron paid work and scales Will's capability.
Decided by: Will | Impact: Team development + scalability
D9. Slack Channels Per Partner
Will confirmed Slack channels exist for Samuel (already set up). Will create a new channel for Patrick. Derek will be looped into both channels to manage partner communication.
Decided by: Will | Impact: Communication organization
D10. Send Summit Latest Athio HTML Code Today
Summit had the GoDaddy domain but didn't know what to publish. Will to send him the most up-to-date HTML code immediately so he can get the site live.
Decided by: Will + Jason | Impact: Unblocks Athio site publishing
A1. Schedule 30-Min Sync with Samuel Next Week
Get everyone on the same page about Align360 scope, affiliate partner pipeline (~1,000 candidates), and launch timeline. Start with one lead source, then expand.
Will
Deadline: Week of Jan 26-31
A2. Schedule Touchpoint with Patrick (Soil King)
Align on rebranding from Probiotic Gardener to Soil King AI, remove proprietary materials, prepare for March event series. Patrick's event tour creates urgency for February alpha.
Will
Deadline: By Feb 7
A3. Loop Derek into Samuel & Patrick Slack Channels
Create Patrick's Slack channel, add Derek to both Samuel and Patrick channels so he can begin managing relationships and building the SOP.
Will
Deadline: Jan 24 (Today/Tomorrow)
A4. Send Summit the Latest Athio HTML Code
Summit has GoDaddy domain but doesn't know what to publish. Will confirmed he just updated the site with new linked code — sending to Summit immediately.
Will
Deadline: Jan 23 (Today) — SENT during call
A5. Analyze Jason's Notion Customer Journey Playbook
Review the Notion doc (first attempt at paint-by-numbers customer arc), identify gaps, remove irrelevant steps, and refine into the actual launch playbook. This is the foundation for the SOP.
Derek
Deadline: Jan 31
A6. Build Launch SOP from Samuel & Patrick Onboarding
Use the real experience of onboarding Samuel and Patrick to create a step-by-step SOP covering the entire customer journey: from prospecting through live product. Include the 4-5 asset buckets as a checklist. "If someone can read, they can do the job."
Derek
Deadline: Feb 14 (ongoing through February)
A7. Set Up Hilsoma Discovery Call with Dr. Prince
Position as exploratory: "This isn't our normal model, but we're intrigued by your business." Get their training modules, understand scope, determine if it's a clearly defined A-to-Z product. Don't over-promise. Ask for their materials to mock up an MVP.
Derek
Deadline: Jan 31
A8. Continue Ralph Orchestrator Development
Finish the orchestrator that breaks builds into small PRDs with time/token/model budgets, then loops through each step automatically. If it works, dramatically speeds up feature development for all launches.
Jason
Deadline: Jan 31
A9. Continue DNS Engine & Multi-Tenant Publishing
Half-developed DNS engine and multi-tenant publishing capability. Will enable publishing to any domain (homepage or subpages) without manual intervention.
Jason
Deadline: Feb 7
A10. Optimize Voice Agent Costs
Voice agent is functional but burning $60/day in testing. Need to reduce costs through Redis caching, model routing, and potentially defaulting to Sonnet 4.5 with caching for most queries.
Jason
Deadline: Feb 7
A11. Build Pricing Calculator Skill
Create a skill that models pricing backward from query volume and model selection, so the team can price products appropriately for any expert's expected usage patterns.
Jason
Deadline: Feb 7
B1. Brad/Bridger Timelines Uncertain
Both Brad (Tiger Quest) and Bridger (Freedom Life) have unclear timelines and responsiveness issues. Brad's value prop and pricing aren't clear even to Will. Bridger's team hasn't responded to submitted frameworks. Neither can be relied upon for February revenue. This is why Samuel and Patrick are being brought in as alternatives.
B2. No Standardized Launch SOP Exists
Every partner onboarding has been ad hoc. Jason created a first-attempt Notion doc but it hasn't been analyzed or refined. Without a repeatable process, each launch requires reinventing the wheel, and balls get dropped. Derek is now tasked with fixing this using Samuel/Patrick as the proving ground.
B3. Partner Responsiveness Stretches Timelines
When asset collection and feedback loops are left to the partner, timelines stretch unpredictably. The "back and forth with people" is the biggest non-technical bottleneck. Solutions proposed: fill all asset buckets upfront in one sitting, designate a point-of-contact, scrape independently if needed.
B4. Framework & ICP Extraction Requires Engagement
Can't build an effective AI clone without knowing the partner's frameworks, ICP, and thinking patterns. The framework is "the recipe" but "the recipe doesn't necessarily sound like the chef." Need large voice data samples AND the actual methodologies. If partners won't provide, team must independently scrape podcasts, TED talks, and social content.
B5. Voice Agent Cost Too High ($60/Day Testing)
Current voice agent testing burns $60/day, which is unsustainable. Mitigation in progress: Redis caching for repeated questions, model routing for complexity-based selection, and standardizing on Sonnet 4.5 with caching. Need to validate cost model before pricing expert products.
The February Launch Imperative
The team has been operating without launches, without a standardized process, and without revenue. February is the forcing function: get products out the door, codify the systems while doing it, and build the portfolio needed to approach bigger clients.
Will's Immediate Priorities
- Schedule Samuel sync call next week — align on Align360 scope, affiliate pipeline, and alpha timeline. Start with one lead source (~1,000 candidates), expand from there.
- Schedule Patrick touchpoint — rebrand under Soil King AI, remove proprietary Probiotic Gardener materials. Must have alpha ready before March event series.
- Loop Derek into Slack channels today — create Patrick channel, add Derek to both. Derek needs visibility to begin managing relationships.
- Manage bandwidth through Austin move (Jan 30) — be selective on attention. Focus only on partner relationship unblocking.
Derek's Immediate Priorities
- Analyze Jason's Notion customer journey playbook — this is the raw material for the SOP. Review it, cut what doesn't work, add what's missing.
- Use Samuel & Patrick to codify the launch SOP — not just manage them, but document every step as a repeatable system. "If someone can read, they can do the job."
- Set up Hilsoma discovery call — position as exploratory. Get their training modules and data. Don't over-promise. Lead the horse to water.
- Collect the 4-5 asset buckets for each partner — don't let it drip. Grab them in one sitting or scrape independently.
Jason's Immediate Priorities
- Finish Ralph Orchestrator — if it works, feature development velocity increases dramatically for all launches.
- DNS engine + multi-tenant publishing — enable self-serve publishing to any domain. Half-developed, needs completion.
- Optimize voice agent costs — $60/day unsustainable. Redis caching + model routing + Sonnet 4.5 standardization.
- Stand up alpha workspaces when assets arrive — ~1 week turnaround per partner if buckets are filled.
The mandate is clear: February = launches. No more ad hoc. Every partner onboarding builds the system. Every launch adds credibility. Every system enables the next launch to be faster.
Next touchpoints: Samuel sync (next week), Patrick touchpoint (by Feb 7), Hilsoma discovery (by Jan 31). Will's Austin move (Jan 30) constrains bandwidth — Derek must pick up relationship management momentum.