Skip to main content

Bike4Mind Strategy

Company-wide strategy for Bike4Mind: product, engineering, packaging, sales, marketing, and how they relate to each other.

This site is a documents-only knowledge base. Markdown in, judgment out.

What lives here

  • Product — roadmap, positioning, feature bets
  • Engineering — architecture direction, platform choices, build/buy
  • Packaging — SKUs, tiers, bundles, entitlements
  • Sales — motions, ICP, segments, channels, partners
  • Marketing — narrative, positioning, audience, GTM
  • Integrations — how product + eng + sales + marketing fit together

Use the sidebar on the left to navigate. Use Memos (top nav) for dated strategy notes and announcements.

What does NOT live here

This repo is intentionally scoped to what we build, who we sell it to, and how the parts fit together. It does not contain:

  • Capital, fundraising, cap table, ownership, dilution, valuations
  • Cash, costs, expenses, burn, runway, financial projections
  • Pricing expressed in dollar amounts, revenue forecasts, financial models
  • Salaries, compensation, equity grants, hiring budgets, headcount cost

Money lives in a different repo. Keep this one focused on strategy and structure.

In scopeOut of scope
Packaging tiers and what features go in eachDollar prices for those tiers
What roles we need and on what teamsWhat we pay them
Which markets we attack and in what orderRevenue forecasts for those markets
Architecture direction and platform betsInfrastructure cost projections

How this site evolves

The directory structure will be refactored as material accumulates. Don't over-organize early. When a category has earned its keep, it gets a folder.

Conventions

  • One topic per file. Long is fine; sprawling is not.
  • Use HTML tables (<table>), not markdown tables. The rendering stack here and across other Bike4Mind sites prefers HTML.
  • Use &quot; and &apos; in HTML content.
  • Date every decision. Include the date in the file or filename. Strategy without dates rots.
  • Cross-link related docs liberally. The graph matters more than the tree.