diff options
| author | Ben Sima <ben@bsima.me> | 2019-06-12 22:11:25 -0700 |
|---|---|---|
| committer | Ben Sima <ben@bsima.me> | 2019-06-12 22:11:25 -0700 |
| commit | ccc8f334194f4c1103935bbb0173897cee1b8305 (patch) | |
| tree | f9d130dc50be49ef4c13a21b0e0030444aa8d6e7 /plan | |
| parent | 3971bd1e35dc9ec72b3aa50f29b2f82d1e06cf72 (diff) | |
add flash.org notes
Diffstat (limited to 'plan')
| -rw-r--r-- | plan/flash.org | 36 |
1 files changed, 36 insertions, 0 deletions
diff --git a/plan/flash.org b/plan/flash.org new file mode 100644 index 0000000..1c392f0 --- /dev/null +++ b/plan/flash.org @@ -0,0 +1,36 @@ +#+title: Flash +#+description: a system for quickly testing business ideas + +- Each marketing iteration for a product requires some gear. A "gear" pack is just a yaml + file with all data for a single flash test. It will include ad content, + pricing info, links to necessary images, and so on. + - even better: store these in a database? Depends on how often we need to edit them... +- Data gets marshalled into a bunch of templates, one for each sales pipeline in + the /Traction/ book by Gabriel Weinberg (7 pipelines total) +- Each sales pipeline will have a number of integrations, we'll need at least + one for each pipeline before going to production. E.g.: + - google adwords + - facebook ads + - email lists (sendgrid) + - simple marketing website + - producthunt + - etc +- Pipelines will need to capture metrics on a pre-set schedule. + - Above integrations must also pull performance numbers from Adwords etc APIs. + - Will need some kind of scheduled job queue or robot background worker to handle this. + - A simple dashboard might also be useful, not sure. +- Metrics determine the performance of a pipeline. After the defined trial + duration, some pipelines will be dropped. The high-performing pipelines we + double-down on. +- Metrics to watch: + - conversion rate + - usage time - minutes spent on site/app + - money spent per customer + - see baremetrics for more ideas +- This can eventually be integrated to a larger product design platform (what Sam + Altman calls a "product improvement engine" in his playbook - PIE?). + - metric improvement can be plotted on a relative scale + - "If you improve your product 5% every week, it will really compound." - Sam + - PIE will differ from Flash in that Flash is only for the early stages of a + product - sell it before you build it. PIE will operate on existing products + to make them better. |