diff options
| author | Ben Sima <ben@bsima.me> | 2022-02-02 14:24:38 -0500 |
|---|---|---|
| committer | Ben Sima <ben@bsima.me> | 2022-02-02 14:24:38 -0500 |
| commit | d8ea30042544587d02957fcfb8d0fef687fe9ecf (patch) | |
| tree | 37c510ee25332cd6836ebb466c13e71d6d244faa | |
| parent | 4627a6c59ed8b649ea8d7eb89ced29bfff602906 (diff) | |
Add some structure to the Dragons plan
| -rw-r--r-- | Biz/Dragons.md | 30 |
1 files changed, 25 insertions, 5 deletions
diff --git a/Biz/Dragons.md b/Biz/Dragons.md index 30a3d33..efab00c 100644 --- a/Biz/Dragons.md +++ b/Biz/Dragons.md @@ -10,15 +10,35 @@ Tech debt is a costly liability for medium-to-large developer teams. It's also mostly hidden: the only people that can identify tech debt are the ones tasked with fixing it, and by that time it is too late. -# Value proposition +# Solution + +# Key Metrics + +# Unique Value Proposition Dragons.dev makes tech debt explicit, by identifying it, quantifying it, and making it visible even for managers that are not familiar with the codebase. This way, it can be mitigated and managed before it becomes a problem. +## High-Level Concept + +# Unfair Advantage + +- first mover + +# Channels + +# Customer Segments + +## Early Adopters + +# Cost Structure + +# Revenue Streams + # Growth plan -## Unicorn requirements +## Unicorn Requirements Let's assume a 7x valuation multiple. If each user brings in $500/yr of revenue, then, if we want to be valued at $1B, we need around 285k users. @@ -36,7 +56,7 @@ Of course we would not start with the total market, rather we would plan to grow out of a niche market to begin with. But this is a good estimate of the upper target. -### Sales penetration +### Sales Penetration To get into the market, we'll have to sell on a team-by-team or company-by-company basis. It does not make sense for an individual developer to @@ -79,7 +99,7 @@ lay out the user growth on a 10-year timeline, we get something like this: In order to support 285k users, what would we need? -### Tech infra +### Tech Infra Each team is probably 10-30 users, and they will be pushing code probably 10x per day. So lets assume with 285k users there will be 285k analyses submitted to @@ -95,7 +115,7 @@ Our existing codebase can probably handle this if run on dedicated hardware in a colo, but as we grow we can do load testing to ensure we are ready, and upgrade subcomponents of the codebase as needed. -### Customer support +### Customer Support How many customers can one support staff person handle? 100? 1000? |