1,914 karma · joined April 19, 2021
email: kyle@projectionlab.com
twitter: @_knolan
it's mainly been product-led growth. I've always just been a guy that likes building cool things, and I spent most of the early years head-down coding. anything marketing-oriented was new to me, and not my natural skillset.
gradually PL started getting some attention in the FI / FIRE space, and recently I've begun building out a small team while staying bootstrapped.
https://projectionlab.com/blog/we-reached-1m-arr-with-zero-f...
Maybe I missed it, but was it ever established that these general vulnerabilities are actually relevant to this specific system/implementation?
I wonder if you could bring on just one really good dev who matches that description vs scaling up to a larger team. In many cases, a very small team of A+ players can beat a large team of B players.
Although it sounds like you're saying marketing/distribution may have played a larger role in your trajectory? In hindsight, do you think focusing your team-building efforts on the marketing side would have been a better strategy?
Personal finance is a pretty broad space, and it's common for different people to come to this with varying desires and expectations.
In our experience, the people who see the value in a good long-term DIY financial plan view our current pricing as extremely affordable, especially compared to traditional financial planning services which often charge $3-5k for a PDF and a pat on the back.
Anyway, if automated tracking is the piece that's most important to you, it might be worth noting that we do plan to add more options for that. But that work -- and all the other controversial implications of it that I mentioned in another comment -- just needs to be prioritized against all the other highly requested things on the product roadmap, based on what the community really wants the most.
I'd say we reached PMF a couple years ago the way I define it (solid customer acquisition from organic sources & word-of-mouth, strong retention, sustainable growth).
I was just curious if others might look at it differently, since I know definitions can vary. And like you said, some people might look at this update and dismiss it as still really small-time.
How much of a pain point is support? At that scale, is it becoming a burden without more of a team in place?
I'd be curious to hear more about what the ups and downs on your journey have been like.
Is your sense that we're officially at PMF now? Or maybe last year even?
Or do you think the question is fundamentally subjective and depends on who you ask and what numbers seem compelling to them, like you kind of alluded to before?
so we need to worry less than a venture-backed company probably would about just how far outside of the FIRE community this has a lot of appeal.
that being said, there are certainly a lot of people who would benefit from having a long-term financial plan. here's to hoping your ynab comparison turns out to be apt!
the rear-view thing sounds kinda like "you'll know it when you see it"... which I'm sure is true for some people, but idk if I would know when to declare PMF without a more precise definition.
at the time, I was too risk-averse to go all-in right away, and this was the best de-risking strategy I came up with. luckily, my schedule is now more balanced again. (a little lol)
and then folks would expect every account's asset allocation to be automatically derived from those positions too I imagine? that would differ a lot from how asset allocation modeling and change over time currently works in the tool.
maybe I'm missing something, but it feels like there could be a lot of complexity here that would need to be carefully weighed against the product vision and other things on the roadmap.
1. I don't start a project unless it's something I deeply want to exist for my own personal use. That way I know there's at least one person who would pay for an elegant solution. And even if no one shows up, at least it's useful to me.
2. I don't start a project unless I can envision the solution top to bottom and feel confident about the scope of the technical work. I'm not the most brilliant person at data structures & algorithms, and I prefer solutions where a simple architecture can get the job done. If there are foggy areas in the technical design, or parts I struggle to visualize clearly, to me that's a red flag.
Either way, if your existing customers don't all come from paid channels, and they're loyal, and you've outlasted multiple competitors, that already sounds like a real achievement to me. My progress was slow for years before things started to really pick up, so don't discount signs of traction if there are some meaningful ones.
FYI if you click on a destination name, it's currently throwing a 500 error.
I'd like to think there will still be room for craft/creation if I become a parent someday. But I doubt this level of sustained focus (obsession?) over multiple years would have been possible or responsible in that scenario.