This is a fair point, but is it a fair comparison with Fibery? Both of those tools - and indeed many other competitors that “did great without individual focus” - are much more straightforward (though sometimes complex) tools. Fibery is more “idiosyncratic”, which makes it a harder sell, a more difficult thing to adopt in a larger group context. I think idiosyncratic tools do better in the individual context, at least to start.
Interesting. You have clearly thought and talked about it a lot. What are the biggest challenges for an “individual focus”? What if it’s not a “focus” so much as a “wedge”, as I mentioned? Implement a few key things that individuals might want, not reorient the whole product. Is this more manageable, something that could even be tested with a couple months of effort and a 6 month marketing push in that direction? 
Also true, except… those startup founders are also mostly suffering from survivorship bias. 
This is what we did and we succeeded, therefore you should also do it". Guess what: 1000s of other companies also did that and also failed. It may be a good idea, but it is not the only good idea. 
Lots of other companies did “preselling”, attracting an audience and even paying users before they even had a product, and ended up doing quite well this way. There are various approaches…
All the more reason to do it in a dedicated tool and not make this a core Fibery use case to aim for, right?
Isn’t this a form of “network” prioritization though?
Mostly yes.
And to whom? I would argue that a large part of that value is that it allows you to replicate other processes from other tools “well enough”. But there are processes and workflows that are so particular and so important that they arguably need more dedicated functionality to really feel/work right.
So, bringing it back around to the original topic of this thread: why is “work management” potentially so important, and perhaps more so than many other features like Form View? (in my opinion)
I believe that “work management” features (reminders/notifications, “watchers”, etc.) become needed for a great many things you otherwise use Fibery for. Let’s take a couple of use cases in this topic for example. You are doing Hiring. You have candidate application inflow, you want to prioritize/rate candidates, discuss, and decide. You now probably want work management inside of Fibery, you want to be notified when your colleague comments or rates or otherwise adjusts a candidate and you want to be able to triage, act on, and file away that notification; you want good, effective discussion features (comments); you want to be reminded to follow-up with a candidate, etc.
Feedback and Issue Management? So we have incoming feedback from various sources, we need to correlate, prioritize, and then act on it. We want reminders to follow-up with users; activity notification in case a colleague finds a spare moment and takes care of that reply already; discussion features to talk about how related one feedback is to another; etc. Basically, same as Hiring.
How about Product Teams? Well… this is obvious. 
Also basically same as Hiring.
Wait a minute, do all(most) all activities maybe need this stuff? Maybe!