Product Feature Research

05 - Strategic Bets

๐ŸŽฏ For CreateOS specifically: Your four bets are already identifiable from the Internal-Research docs. Audience: AI-native builders + enterprise agent deployments (not makers, not pro-devs). Autonomy axis: depth (autonomous agent with spend caps) over breadth. Signature pattern: the MPP + router + marketplace combination โ€” no one else has assembled it. Viral loop: "Made with CreateOS" badge with credit reward, specifically tied to MPP-earning agents. Read CreateOS - Three-Factor Inflection for the full formula applied to CreateOS and CreateOS - Positioning and Wedge for why "agent sandbox where the agent earns" is the right narrowing.

Thesis

You don't win by matching Replit and Anything.com feature-for-feature. You win by picking one audience ring + one autonomy axis + one signature pattern + one viral loop โ€” and executing each better than anyone. Four bets, no half-measures.

The four bets you must make

Bet 1: One audience ring

You can't be Replit. Replit serves three ICP rings (non-coders, devs, enterprise) simultaneously because they've been at this for 8+ years. You have one product shape. Pick:

Ring What it means for your product What to copy / avoid
Makers / solopreneurs Payments + ASO + Monetization built-in. No code editor in marketing. Distinctive brand. Copy: Anything.com - Accept Payments + Anything.com - App Store Marketing. Avoid: enterprise compliance theater.
Indie developers Code editor prominent. Command palette. Version control. Agent as an accelerant. Copy: Replit - Command Palette + Replit - Library Panel. Avoid: no-code positioning.
Enterprise SOC 2 + SSO/SAML + SBOM + scan history + account seats. "Contact sales" in nav. Case studies. Copy: Replit - Security Scanning + Replit - Workspace Settings hierarchy. Avoid: single-workspace IA.

What happens if you try all three? You ship mediocre versions of each. Replit can afford this; you can't.

Bet 2: One autonomy axis

Replit productized two at once (breadth via Task Board + depth via Autonomous Build Mode) and bundled both in Core. Anything.com productized one (depth via Max). You should pick one to hero, then optionally add the other later.

Pick depth first if your users are makers; breadth first if your users are devs with complex projects.

Bet 3: One signature pattern, executed better than peers

Every strong product in this space has one thing they do better than anyone. Decide now what yours is:

Signature pattern Reference Your execution bar
Named design systems Anything.com - Named Design Systems Beat Anything by making presets user-extendable, with a marketplace.
Competitive migration imports Replit - Import Wedges Beat Replit by covering 6-8 direct competitors (not 4) and preserving more fidelity.
Agent reasoning transparency Agent Reasoning Display Beat both by combining stages (readable) + collapsible tool calls (auditable) in the same thread.
Persistent workspace / task board Replit - Task Board Beat Replit by making the board free (they gate task creation to Core).
Monetization stack Anything.com - Accept Payments + Anything.com - Monetization Beat Anything by including ASO + subscription + in-app-purchase + affiliate in one bundle.

Bet 4: One viral loop

Replit has the "Made with Replit" badge. Anything.com has no viral loop โ€” Anything's growth depends on paid marketing + creator content. That's a disadvantage you don't want to inherit.

Pick one:

Pick one and invest for 12 months. Viral loops take time to compound.


The anti-bets (what NOT to do)

โŒ Match Replit feature-for-feature

You'll lose. They have more engineers, more years, more distribution. Skip features they have; invest in features they don't.

โŒ Try to serve both makers AND enterprise from day one

The IA conflicts are incompatible: makers want flat "payments first" IA; enterprise wants nested "workspace / account / user" IA. You can't have both without confusing everyone.

โŒ Invent your own shell

The three-pane chat + authoring + preview layout is the right answer. Every competitor has converged on it. Spending design budget on a "different" shell is capital wasted.

โŒ Free tier with no viral or conversion mechanic

A pure generous free tier is expensive marketing that doesn't compound. Every free user must either (a) convert within 30 days, (b) drive new users via a viral loop, or (c) produce a public artifact that drives SEO. If none of these, cut the free tier or hard-cap it.


The "which-bet-should-we-make" matrix

Makers audience Dev audience Enterprise audience
Autonomy bet Depth (simple Max-like mode) Breadth (Task Board) Depth + Plan Mode (auditable)
Signature pattern Named design systems Competitive imports Security + SBOM
Viral loop Templates marketplace "Made with X" badge Case studies + ABM
IA shape Single project, flat settings with sections Project + workspace Workspace > Account > User
Marketing voice Atmospheric, distinct imagery Utility, explicit sub-products Trust badges, logo wall

Pick one column. Execute every row of that column. Ignore the other columns.

Sources