blob: 1c392f0118cced9f8a3cc46c2d11e3d0d095b6d4 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
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.
|
