Skip to content

[codex] Add CSMO launch strategy docs#731

Draft
teetangh wants to merge 1 commit into
devfrom
feature/csmo-sales-marketing-strategy
Draft

[codex] Add CSMO launch strategy docs#731
teetangh wants to merge 1 commit into
devfrom
feature/csmo-sales-marketing-strategy

Conversation

@teetangh

Copy link
Copy Markdown
Contributor

Summary

Adds a new CSMO strategy pack under docs/sales-marketing/csmo-2026-launch/ for the India-first pre-launch/beta GTM motion.

The pack covers executive GTM thesis, product subsystem selling points, 90-day launch plan, channel playbooks, scripts, hiring and Upwork guidance, competitor battlecards, KPI cadence, and offline partnerships.

Why

The strategy follows the agreed launch assumptions: Indian tech mentors as the first wedge, 10% commission from day one, ₹25K-50K/month budget, intern-first hiring, Upwork only for lead research, LinkedIn as the operating center, and math-first competitor positioning.

Validation

Docs-only change. Verified file list, line counts, and scanned for placeholder TODO/FIXME markers.

@netlify

netlify Bot commented Apr 30, 2026

Copy link
Copy Markdown

Deploy Preview for familiarise ready!

Name Link
🔨 Latest commit 89fab5f
🔍 Latest deploy log https://app.netlify.com/projects/familiarise/deploys/69f2e0c2a344440008495ca4
😎 Deploy Preview https://deploy-preview-731--familiarise.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 45 (🔴 down 13 from production)
Accessibility: 90 (no change from production)
Best Practices: 83 (🔴 down 9 from production)
SEO: 83 (no change from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a comprehensive 90-day launch strategy and marketing documentation for the Familiarise platform, specifically targeting the Indian tech mentor market. The documentation includes executive strategy, product-to-selling-point mappings, channel playbooks, outreach scripts, and hiring plans for interns and contractors. The review feedback correctly identifies several instances where the documentation overstates current product capabilities—particularly regarding enterprise features like SSO, audit logs, and contracts—which are not yet reflected in the Prisma schema. These corrections are vital to ensure the sales and marketing teams operate from a technically accurate source of truth.


"Sponsor expert-led learning for your team or students with Indian billing, program controls, SSO-ready architecture, and auditability."

Enterprise is a real product capability in the schema and app, but it is not the first campaign wedge. Keep enterprise as founder-led design partner sales only until B2C consultant supply shows proof.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

This sentence claims that "Enterprise is a real product capability in the schema". However, the current prisma/schema.prisma only contains basic Organization and Member models. Many of the advanced enterprise features mentioned elsewhere (like SSO, audit logs, and contracts) are not yet present in the schema. It is better to clarify that the foundations are present.

Suggested change
Enterprise is a real product capability in the schema and app, but it is not the first campaign wedge. Keep enterprise as founder-led design partner sales only until B2C consultant supply shows proof.
Enterprise foundations (organizations and memberships) are present in the schema and app, but it is not the first campaign wedge. Keep enterprise as founder-led design partner sales only until B2C consultant supply shows proof.


| Subsystem | Product reality | Selling point |
| --- | --- | --- |
| Consultant profiles | `ConsultantProfile`, domains, subdomains, tags, reviews, verification, work/education/certifications at user level | "Build a credible expert profile with domain tags, credentials, reviews, and verification signals." |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The "Product reality" column states that verification is at the user level. However, in the prisma/schema.prisma, professional verification fields (isVerified, verificationStatus) are located in the ConsultantProfile model (lines 443-444). The User model only handles emailVerified.

Suggested change
| Consultant profiles | `ConsultantProfile`, domains, subdomains, tags, reviews, verification, work/education/certifications at user level | "Build a credible expert profile with domain tags, credentials, reviews, and verification signals." |
| Consultant profiles | ConsultantProfile (verification), domains, subdomains, tags, reviews, and work/education/certifications at user level | "Build a credible expert profile with domain tags, credentials, reviews, and verification signals." |

| Referrals | Referral codes, referral credits, credit usage, referral landing route | "Referral credits can reduce acquisition cost and bring repeat bookings back into the platform." |
| Reviews | Consultant reviews and ratings | "Verified social proof can compound profile conversion." |
| Support/admin | Support tickets, moderation, refunds, disputes, system jobs, maintenance | "There is an operating layer behind sessions, not just a booking page." |
| Enterprise/org layer | Organizations, memberships, programs, billing accounts, contracts, wallets, invoices, SSO settings, audit logs | "Future-ready for sponsored learning, company experts, GST-style invoicing, org programs, and SSO." |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The "Product reality" column for the Enterprise/org layer lists several entities that are not currently present in the prisma/schema.prisma, such as programs, billing accounts, contracts, wallets, SSO settings, and audit logs. The schema currently only supports Organizations, memberships, invitations, and invoices.

Suggested change
| Enterprise/org layer | Organizations, memberships, programs, billing accounts, contracts, wallets, invoices, SSO settings, audit logs | "Future-ready for sponsored learning, company experts, GST-style invoicing, org programs, and SSO." |
| Enterprise/org layer | Organizations, memberships, invitations, invoices | "Future-ready for sponsored learning, company experts, GST-style invoicing, org programs, and SSO." |


- "Familiarise has an organization layer for sponsored learning and expert programs."
- "The model can support buyer organizations, provider organizations, or hybrid organizations."
- "The schema supports memberships, programs, billing accounts, contracts, invoices, rate cards, SSO settings, audit logs, and HRIS stubs."

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

This statement claims the schema supports several features that are missing from the provided prisma/schema.prisma, such as programs, billing accounts, contracts, rate cards, SSO settings, audit logs, and HRIS stubs. It is recommended to update this to reflect the actual schema capabilities to avoid misleading the sales team.

Suggested change
- "The schema supports memberships, programs, billing accounts, contracts, invoices, rate cards, SSO settings, audit logs, and HRIS stubs."
- "The schema supports organizations, memberships, invitations, and invoices, providing a foundation for future enterprise features like SSO and audit logs."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant