Open source
Open source publishes the SDK and integration layer as open repositories, keeps the hosted Product paid, and answers every issue within 48 hours.
Open source publishes the SDK and integration layer as open repositories and keeps the hosted Product paid. Developers adopt what they can read, run and fork.
Ratings
| Dimension | Rating | Reads |
|---|---|---|
| Scalability | 4 of 5 | high: higher grows further with spend or automation |
| Cost | 2 of 5 | low: lower costs less per Customer |
| Latency | 5 of 5 | very high: lower answers sooner |
Budget
| Property | Value |
|---|---|
| Tier | $0 |
| Minimum effective budget | $0 a month |
How it runs
Repositories live on GitHub and packages on npm. Every issue gets an answer within 48 hours, and every readme puts the hosted product one command away.
Processes
Runs as Content marketing, accountable to the Marketing Team.
Fits
| Fits | Value |
|---|---|
| Family | demand |
| Shelf | Compound: builds an engine that keeps growing (Grow) |
| Moves | Organic share |
| Motions | b2d, b2a |
| Venues | GitHub, npm |
| States | Live, Repeatable, Scale |
Loop
| Step | Value |
|---|---|
| Hypothesis | Answering every issue within 48 hours turns more open-source developers into hosted Customers. |
| Measure | Organic share over 90d, at least 50 observations |
| Learn | The learn step reads the Readout, records Evidence and a Decision, and drafts the next Variant. |
Example
A Startup selling a hosted feature-flag service publishes its client libraries in six languages. Two thousand projects install them, and 3 percent move to the paid service when they need audit history.