MemberIntel V2 Specification

Status: Draft v0.2 (2026-04-29)
Owner: Blair (CEO, MemberPress / Caseproof)
Working name: MemberIntel (internal — not committed)
Builds on: SPEC-v1.md + SPEC-v1.5.md

---

1. Overview

MemberIntel V2 expands the product to BuddyBoss customers — the first cross-platform release leveraging the sister-company relationship between Caseproof and BuddyBoss. Critically, BuddyBoss is launching its own native Memberships product within ~2 months of this spec being written, and BB Memberships is built on MemberPress under the hood. From a data and engineering perspective, BB customers using BB Memberships are effectively MemberPress customers wearing a different brand. V2 takes advantage of that to ship full MemberIntel feature parity (advisor + dashboard + chat + agent / write-actions + “Set up FOR ME” greenfield wizard) for BB customers, without the heavy platform-abstraction work that real cross-platform expansion would require.

V2 is therefore primarily a partnership integration project rather than a platform-abstraction project. The genuine cross-platform engineering — building the abstraction that supports a fundamentally different platform — happens in V2.1 (Paid Memberships Pro) and V2.2 (Kajabi). V2 sets the stage for that work by formalizing the platform-tagging system in the brain and the platform-aware AI prompting, but does not yet require a per-platform connector framework.

The strategic intent: leverage the sister-company channel to add BuddyBoss’s customer base with low engineering risk, build MemberIntel revenue + brain density from a friendly market while the harder integrations are designed, and establish “MemberIntel works with MemberPress, BuddyBoss, and the leading WordPress membership stack” as the V2-launch narrative — en route to “any membership platform” by V2.2 + V3.

For unchanged scope (V1 architecture, brain mechanics, V1.5 agent + greenfield wizard, compliance commitments, base pricing model), see SPEC-v1.md and SPEC-v1.5.md.

---

2. Goals

Primary

• TAM expansion via partnership — open MemberIntel to BuddyBoss’s customer base with the sister-company channel covering acquisition.
• Full-feature cross-platform proof point — ship the entire MemberIntel experience (including agent + wizard) for a non-MP-branded platform, demonstrating the product’s reach without committing to deep platform-abstraction work in V2.
• Foundation for V2.1 / V2.2 — introduce platform tagging in the brain and platform-aware AI prompting so PMP and Kajabi work in V2.1 and V2.2 is incremental, not architectural.

Secondary

• Grow the global brain with BuddyBoss-flavored, community-focused playbooks that improve answer quality for community-led membership operators.
• Validate joint go-to-market motion between Caseproof and BuddyBoss; learn what partnership channels work before pursuing partnerships with non-sister-company platforms.
• Build MemberIntel revenue and customer base while V2.1 (PMP) and V2.2 (Kajabi) are designed and built.

V2 Success Metrics (priority order)

1. BuddyBoss customer signups within first 6 months of V2 launch. Target: 1,000+ BB customers connected to MemberIntel (mix of free + paid).
2. BB free → paid conversion rate. Target: 5–10% (parity with MP free → Pro conversion from V1).
3. AI quality parity across MP and BB customers. Internal eval: chat responses to BB-customer scenarios should score at least 90% as well as equivalent MP-scenario responses on the eval suite (allowing for community-context differences).
4. Brain growth, BB-tagged. ≥30 hand-written BuddyBoss playbooks at launch, growing to 60+ within 6 months. Cross-pollinated entries tagged for relevance.
5. Agent / wizard adoption among BB customers. % of BB Pro customers who use the agent at least once, % who run the “Set up FOR ME” wizard during onboarding. Sets a baseline for V2.1 / V2.2 (which won’t have these features).

---

3. Non-Goals (V2 explicit exclusions)

Inherits all SPEC-v1 and SPEC-v1.5 non-goals. V2 specifically does NOT do:

• No PMP support in V2. PMP is V2.1.
• No Kajabi support in V2. Kajabi is V2.2.
• No support for BB customers who do NOT use BB Memberships. V2 requires BB Memberships (which is MP underneath). BB customers running other membership solutions are out of scope until V2.1 (if PMP) or later.
• No deep platform-abstraction layer in V2. BB Memberships = MP underneath, so V2 reuses the V1 / V1.5 MP integration directly. The abstraction is built in V2.1 when PMP forces it.
• No mobile app of MemberIntel. BuddyBoss App (BB’s mobile product) does not require MemberIntel to ship a mobile app in V2. Responsive web only.
• No Pro+ tier. Single $29/mo Pro tier across MP and BB. Pro+ remains V3+.
• No agency tier. Multi-site / per-seat pricing remains V3+.
• No SOC 2. Continues GDPR + CCPA only.
• No expansion of agent action surface beyond V1.5 categories (membership level CRUD, content protection rules, email / dunning configuration). BB Memberships exposes the same MP MCP, so the agent surface is identical.

---

4. ICP Updates

V1 / V1.5 ICPs from SPEC-v1.md §4 and SPEC-v1.5.md §4 remain unchanged. V2 adds:

BuddyBoss community-membership operator (new persona)

• Profile: WordPress site owner running BuddyBoss Platform + BB Memberships. Operates a community-led membership site — paid groups, paid forums, premium content, course access, member-to-member networking. May also use LearnDash (or BB’s native course features) for educational content.
• Pain points: knows community engagement matters but doesn’t know which engagement signals predict retention; not sure how to balance free-community vs paid-tier mix; doesn’t know how to price community access vs. content access; doesn’t know what to do when engagement dips. Subscription-business pain points (churn, MRR, conversion) are present but secondary to engagement-business pain points.
• Acquisition channel: owned via sister-company partnership — in-BuddyBoss-admin banner, joint email campaigns, BuddyBoss community marketing, joint webinars / content. This is a critical advantage over arms-length cross-platform expansion (PMP, Kajabi).
• Their job: “Tell me what’s working with my community + membership setup, and where I can grow engagement and revenue together.”

---

5. Pricing & Packaging

5.1 Tiers (unchanged from V1)

BuddyBoss customers using BB Memberships use the same pricing model as MP customers per SPEC-v1 §5.1:

• Connected Free tier: capped chat (5 msgs/mo Haiku), monthly snapshot dashboard, weekly digest, brain contribution.
• Pro tier: $29/mo per site. Unlimited Sonnet chat, live dashboard, full reports, agent / write-actions, “Set up FOR ME” wizard.

5.2 Sister-Company Promotional Considerations

These are open product-marketing decisions, not technical scope decisions, but worth flagging:

• Free Pro period for BuddyBoss customers at V2 launch? A 30- or 60-day full-Pro promotional period for the BB customer base could drive rapid adoption. Cost: real Pro-tier API spend during the promo. Decision lives with marketing + the BB partnership.
• Bundled offering? BuddyBoss may want to bundle MemberIntel into a higher BB subscription tier as an upsell. Drives BB upgrade revenue (BB-side) and MemberIntel adoption simultaneously. Requires partnership negotiation; not assumed in V2 scope.
• Reciprocal promotion? Caseproof promotes BuddyBoss to MP customers wanting community features; BuddyBoss promotes MemberIntel to BB customers. Cross-promotional baseline expected from any sister-company integration.

5.3 Trial Mechanics

Trial mechanics from V1 + V1.5 carry forward. BB customers using the “Set up FOR ME” wizard trigger the 14-day Pro trial (card required), identical to the MP customer flow.

---

6. The Brain (V2 updates)

6.1 Platform-Tagged Brain (introduced in V2)

The two-tier brain architecture from SPEC-v1.md §6 is unchanged in mechanism. V2 introduces platform tagging on brain entries to support V2 BuddyBoss content and prepare for V2.1 / V2.2:

• Global brain entries carry a platforms field: ["memberpress"], ["buddyboss"], ["memberpress", "buddyboss"] (entries that apply to both), or ["all"] (general entries that apply to any platform).
• Retrieval at query time filters by the active customer’s platform plus ["all"] entries. A BuddyBoss customer’s chat retrieves BB-tagged + general entries; never MP-only entries.
• Per-customer brain entries inherit the customer’s platform automatically.
• Existing V1 / V1.5 brain entries are tagged retroactively (default memberpress or all based on content lead review).

6.2 BuddyBoss Brain Seed (V2 launch)

• ~30 hand-written BuddyBoss-flavored playbooks at launch. Topics weighted toward community-engagement strategy: launching paid groups, balancing free vs paid spaces, member onboarding into community, engagement-driven retention, community-led growth, pricing access vs content.
• BuddyBoss official documentation indexed and tagged.
• General membership-business playbooks already in the brain (tagged ["all"]) remain available to BB customers.
• Authored by the existing content lead, with BuddyBoss subject-matter input via the partnership.

6.3 Cross-Pollination (V2 updates)

V1 cross-pollination mechanism (SPEC-v1 §6.3) extends naturally to platform-tagged brain entries. The content lead determines tagging during candidate review. A learning surfaced from a BB customer that’s about community engagement specifically gets tagged buddyboss; a learning that’s general (e.g., “members who post within the first 7 days of joining are 3x more likely to renew”) gets tagged ["all"] and benefits all platforms.

6.4 Content Lead Capacity (carried forward and worsened)

By V2 launch, the existing content lead has authored:

• 50–100 MP playbooks (V1)
• 30+ V1.5-focused playbooks (greenfield-oriented)
• 30 BuddyBoss-flavored playbooks (V2)

Plus ongoing cross-pollination review across thousands of customers across two platforms. One person is overloaded. A second content lead should be hired before V2 launch — likely with community / BuddyBoss subject-matter familiarity, since BB content is the V2 push and PMP / Kajabi are coming in V2.1 / V2.2.

---

7. BuddyBoss Integration

7.1 Underlying Architecture

• BB Memberships = MemberPress under the hood. Same data model, same MP MCP, same agent action surface.
• MemberIntel V2 reuses the V1 / V1.5 MP integration directly. No new connector built.
• The BuddyBoss-specific work is around branding, in-BB-admin entry points, and BB-flavored UX touches — not around data access.

7.2 Customer Connection Flow

• BuddyBoss customers see a “MemberIntel: AI for your BuddyBoss community” banner in BB admin.
• Click-through authenticates to memberintel.com using the shared license / partnership-validated identity (specifics owned by the partnership integration; likely mirrors the V1 MP-license-based auth pattern).
• Customer arrives at memberintel.com signed in, with their BB Memberships data already syncing (since the underlying data is MP, the existing pipeline picks it up).

7.3 Data Sources (V2 for BB customers)

Source	Path	Use
BB Memberships data	Same as MP path: live sync via the existing V1 MemberPress integration.	Per-customer dashboard, chat context, brain enrichment, agent actions.
BuddyBoss community data (groups, forums, posts, member activity)	New: BuddyBoss REST API for community engagement metrics.	Engagement-focused dashboard widgets, chat context for community questions.
Stripe / PayPal data	Same as V1: Stripe Connect (if applicable) or customer-OAuth into their own Stripe / PayPal.	Revenue / churn / dunning.
Customer’s public site	Same as V1: weekly Claude-based site analysis.	Per-customer brain site profile.

The BB community data (engagement metrics) is genuinely new — the V1 / V1.5 product had no equivalent. This is the only meaningful data-pipeline addition in V2.

7.4 BuddyBoss Community Metrics

New dashboard widgets and AI tool calls for BB customers:

• Active community members (DAU / WAU / MAU within BB groups + forums).
• Posts per active member per week.
• New-member 7-day engagement rate (% of new members who post in their first 7 days).
• Group health (active vs dormant groups).
• Engagement-to-retention correlation surface (the AI can correlate community engagement signals against subscription churn from the BB Memberships side).

These are V2-specific dashboard sections only shown to BB customers. MP-only customers do not see them.

---

8. AI Architecture Updates

V1 / V1.5 AI architecture (SPEC-v1 §8.4 + SPEC-v1.5 §5) carries forward. V2 changes:

8.1 Platform-Aware Prompting

• System prompt for BB customers includes BB-specific context (“the user runs a BuddyBoss community-membership site; balance community-engagement advice with subscription-business advice”).
• System prompt for MP-only customers is unchanged.
• The AI knows the active customer’s platform and adapts terminology, context, and the kind of advice it gives.

8.2 Tool Surface Extension

The V1 / V1.5 tool surface (SPEC-v1 §8.4 + SPEC-v1.5 §5) gains BB-specific extensions:

• query_community_metrics(metric, time_range) — new tool, BB-only, queries BuddyBoss community engagement data (active members, posts, group activity).
• All other V1 / V1.5 tools (query_customer_metrics, search_global_brain, search_customer_brain, update_customer_brain, analyze_site, mp_action) work for BB customers because BB Memberships = MP underneath.

8.3 Eval Suite Extension

V1 / V1.5 eval suite extends with BuddyBoss-specific scenarios. Cross-platform eval ensures the AI answers community-flavored questions well for BB customers without dropping quality on MP-customer scenarios.

---

9. UI Updates

V1 / V1.5 UI carries forward. V2 changes:

• Platform indicator in app header. Subtle badge (“MemberPress” or “BuddyBoss”) so users know what platform context their MemberIntel session is in.
• BuddyBoss-specific dashboard sections. Community engagement widgets layered alongside the existing MP-style KPIs (members, MRR, churn). Visually integrated into the same dashboard.
• Onboarding entry from BB admin. Banner in BuddyBoss admin (parallel to the V1.5 MP-admin banner) offering “Set up FOR ME” + 14-day Pro trial during BB Memberships setup.
• Marketing site updates at memberintel.com. Pricing page lists supported platforms (MemberPress + BuddyBoss). BuddyBoss-specific landing page / hero variant. SEO content for community-membership keywords.

---

10. Compliance & Privacy Updates

V1 / V1.5 compliance carries forward (GDPR + CCPA, per-tenant isolation, consent flows, no fine-tuning). V2 additions:

• BB customer ToS / consent. Same terms as MP-customer ToS, with BB-platform-specific language. Authorize per-customer brain accumulation, cross-pollination contribution, no fine-tuning.
• Sister-company data sharing terms. The Caseproof–BuddyBoss partnership requires legal documentation around what data flows between the companies, who owns what, and what the customer-facing consent looks like. Phase 0 work item for V2.

---

11. Technical Stack Updates

V1 / V1.5 stack carries forward. V2 additions:

• BuddyBoss REST API client. Library for hitting BB community endpoints with auth, retry, and rate-limit handling. New, separate from the MP pipeline (since community data isn’t in BB Memberships / MP).
• Platform tag column on global brain entries. Index on platforms for retrieval filtering.
• Platform field on customer accounts (memberpress or buddyboss). Drives prompting, dashboard variants, marketing copy, and BB-specific tool routing.
• BB admin banner integration. Coordinated with the BuddyBoss product team. Mirror of the V1.5 in-MP-admin banner.
• Sister-company auth bridge. Implementation depends on the partnership. Likely a shared license-validation flow or a SAML / OAuth bridge. Owned jointly by Caseproof + BB engineering during Phase 0.

---

12. Implementation Phases

Build kicks off immediately after V1.5 launch. Same team: 4 engineers + 1 designer + 1 PM + content lead + (planned) a second content lead with community subject-matter experience.

Estimated V2 duration: ~3 months.

Phase 0 — Pre-Build (Weeks 0–4, parallel with V1.5 wind-down)

• Hire second content lead (community / BuddyBoss familiarity preferred).
• BuddyBoss partnership agreement + data-sharing terms finalized with legal.
• BB admin integration scoped jointly with BuddyBoss engineering team.
• BuddyBoss REST API audit: confirm it exposes the community engagement data MemberIntel needs.
• Launch promotion plan agreed with BuddyBoss marketing (free trial period, joint comms, etc.).

Phase 1 — BuddyBoss Integration (Months 1–2)

• Platform tag column + retrieval filtering added to brain.
• Existing MP-relevant brain entries tagged retroactively.
• Account model extended with platform field.
• BuddyBoss REST API client + community engagement data ingestion.
• BB-specific dashboard widgets.
• BB-specific system prompts + AI eval scenarios.
• Sister-company auth bridge in place; in-BB-admin banner coordinated.
• BuddyBoss-flavored playbooks authored (~30 by launch).
• Milestone (Month 2): internal beta with 10–20 hand-picked BB customers.

Phase 2 — Polish + Launch (Month 3)

• Iterate on community-dashboard UI based on beta feedback.
• Iterate on prompts + brain entries based on AI eval drift.
• memberintel.com marketing updates (pricing, BB landing page, SEO content).
• Joint launch comms with BuddyBoss.
• Public V2 launch.

V2.1 — Paid Memberships Pro (post-V2 launch, ~3 months)

• Real platform-abstraction work begins: refactor V1 / V1.5 data layer into a connector framework (MP becomes one connector implementation; BB largely reuses MP since BB Memberships = MP).
• PMP REST API connector built against PMP’s public API.
• PMP customer-OAuth Stripe / PayPal flow.
• PMP-specific dashboard variants.
• Content lead authors ~30 PMP playbooks (~60% net-new, ~40% adapted from existing brain).
• PMP customers get advisor-only experience: dashboard + chat + how-to instructions. No agent. No “Set up FOR ME” wizard. Pro-only at $29/mo (no free tier for PMP).
• Estimated duration: ~3 months. V2.1 ships ~6 months after V2 launch.

V2.2 — Kajabi (post-V2.1 launch, ~4 months)

• Kajabi connector built against Kajabi’s public API.
• Kajabi-specific brain content (~30 playbooks).
• Kajabi-specific positioning vs Kajabi’s internal AI (“deeper operator advisor than Kajabi AI”).
• Same advisor-only feature set as PMP V2.1 (no agent, no wizard).
• Pricing: TBD — likely $29-49/mo given Kajabi customer budget.
• Estimated duration: ~4 months. V2.2 ships ~10 months after V2 launch.

V3+ (post-V2.2)

• Pro+ tier introduction (~$79–99/mo) — features TBD; possibly multi-site, agency features, premium AI capabilities.
• Agency tier (multi-site / per-seat pricing).
• Cross-customer benchmarks (if the legal Phase 0 work from earlier specs has been completed and ToS coverage exists).
• SOC 2 Type 1.
• Additional platforms: Thinkific, MemberMouse, LearnDash, Mighty Networks, Circle, etc.
• Possibly: agent / write-actions extended to non-MP platforms (large engineering effort per platform; gated by demand).

---

13. Risks & Open Questions

Risks specific to V2

1. BB Memberships launch slips. V2 assumes BB Memberships ships within ~2 months of this spec being written and is mature by V2 build kickoff (~12 months from now). If BB Memberships slips, V2 ICP shrinks (only BB customers who adopt BB Memberships are addressable). Mitigation: regular checkpoints with BuddyBoss engineering during V1 / V1.5 build; V2 scope can be adjusted if BB Memberships is delayed.
2. Sister-company partnership friction. Joint ventures with parallel orgs always require coordination overhead — engineering APIs, marketing comms, customer support boundaries, revenue split (if any). Mitigation: written partnership agreement before V2 build; named owners on both sides.
3. BB customers not adopting BB Memberships. Some BB operators may stick with their existing membership tooling (other plugins, custom builds) instead of switching to BB Memberships. They’re out of V2 scope. Mitigation: V2.1 (PMP) covers a major alternative; BB-customers-on-other-platforms wait for V2.1+.
4. Community-engagement insights are harder than financial insights. “MRR rose 5%” is unambiguous; “engagement is healthy” is fuzzy. The AI must translate community signals into actionable advice, not just describe metrics. Mitigation: heavy investment in community-specific playbooks during V2 brain seeding; eval suite enforces actionability of community advice.
5. AI quality degradation across platforms. Adding BB-specific prompting + retrieval logic could introduce regressions in MP-customer answer quality. Mitigation: cross-platform eval suite blocks any release that drops MP-side scores.
6. Content lead overload. Already cumulative across V1 + V1.5 + V2 ; adding the second content lead by Phase 0 is required, not optional.
7. Brand confusion. MP customers wondering “why does my AI tool work for BuddyBoss?” Mitigation: positioning leads with the sister-company relationship — confidence, not apology. Also, MP customers see the same product depth they’ve always had; BB customers get the same depth.
8. Free Pro promo cost during launch. If you offer BuddyBoss customers a 30- or 60-day free Pro period at V2 launch, costs scale with adoption. Mitigation: hard token caps even during the promo period; explicit budget cap on the promo.

Risks unchanged from earlier specs

Differentiation from generic AI; site data sync reliability; hallucination on financial data; cross-pollination privacy slip; support burden; brand dilution; hiring risk.

Open Questions

• Q1. BB Memberships launch date — confirm timing and stability before V2 build kickoff.
• Q2. BuddyBoss partnership terms — data sharing, joint marketing, revenue arrangement, support boundaries. Phase 0 deliverable.
• Q3. BuddyBoss admin integration UX — final placement and copy for the in-BB-admin banner. Owned jointly by Caseproof + BB product teams.
• Q4. Free Pro promotion at V2 launch — duration, eligibility, budget cap. Marketing decision.
• Q5. BuddyBoss REST API surface — confirm it exposes group activity, post counts, member engagement data at sufficient depth for the V2 community-metrics dashboard.
• Q6. Second content lead — sourcing, voice fit, joint sourcing with BuddyBoss content / community team?
• Q7. Multi-platform accounts — does a single MemberIntel account support a customer running BOTH MP (one site) and BuddyBoss (another site)? V2 default is one account per site, but multi-site support is a real customer ask. Worth a separate decision before V2.1 (where multi-platform single-customer becomes more common).
• Q8. BB customer support — channeled through MemberIntel’s support, BuddyBoss’s support, or shared? Define before launch.

---

14. Glossary (additions to SPEC-v1 §15 + SPEC-v1.5 §14)

• BuddyBoss — sister company of Caseproof, makers of the BuddyBoss community / membership / app platform for WordPress. The first non-MemberPress platform supported by MemberIntel.
• BB Memberships — BuddyBoss’s native Memberships product, built on MemberPress under the hood. Powers V2 integration without a new connector.
• Sister-company channel — the shared-organization marketing and engineering relationship that makes BuddyBoss customer acquisition “owned channel” rather than cold marketing.
• Platform-tagged brain entry — a global-brain entry with a platforms field indicating which platforms the entry applies to (memberpress, buddyboss, multiple, or all). Introduced in V2.
• V2.1 — the Paid Memberships Pro expansion that follows V2 BuddyBoss launch by ~3 months. The first true platform-abstraction project.
• V2.2 — the Kajabi expansion that follows V2.1 PMP launch by ~4 months. The first non-WordPress platform.