Two people giving conflicting advice, whose SaaS products have performed comparably well over a roughly 2 year period: @mijustin and @arvidkahl
Arvid says build for a niche which he did. Justin says build for a big market which he did.
What’s the takeaway? 
-
Pokaż ten wątek
-
W odpowiedzi do @petersuhm @arvidkahl
It all depends on your semantics.
The primary message I’m trying to communicate is “the size of the wave you’re trying to catch matters.”
If there’s no evidence of market pull (people actively buying in your category) it’s going to be a lot harder.https://justinjackson.ca/today 2 odpowiedzi 0 podanych dalej 11 polubionych -
W odpowiedzi do @mijustin @petersuhm
I think we are in full agreement here. Your business has to be sustainable from the size of the audience you’re selling to. And for that, your product had to really matter to every single one of them.
1 odpowiedź 0 podanych dalej 2 polubione -
W odpowiedzi do @arvidkahl @mijustin
Well that’s a happy ending! Haha. So Arvid, with the advice you’re giving these days, starting a podcast hosting company would be a great idea for a bootstrapper? How about an ESP? Just trying to understand if y’all are really agreeing or not
1 odpowiedź 0 podanych dalej 0 polubionych -
W odpowiedzi do @petersuhm @mijustin
I think everyone should be using
@TransistorFM for that, of course :) Or you find a sub-niche and build private podcasting tools for companies that only allow on-premise stuff, for example. The trick is to select the audience and probe for problems.1 odpowiedź 0 podanych dalej 0 polubionych -
Gotcha. In my world I think of what you call the “sub-niche” as the niche. Which might be where the semantics come into play. But Transistor has been performing _very_ similar to FP from what I understand, without going sub-niche. Or I might be misunderstanding it! :)
2 odpowiedzi 0 podanych dalej 1 polubiony
I like to think more in terms of: “Who wants this today?” https://justinjackson.ca/build pic.twitter.com/y4cZPGm5g6
Wydaje się, że ładowanie zajmuje dużo czasu.
Twitter jest przeciążony lub wystąpił chwilowy problem. Spróbuj ponownie lub sprawdź status Twittera, aby uzyskać więcej informacji.
building