Thanks! We're always paranoid that we're too slow, for whatever it's worth.
We're still iterating on the supporting models and frameworks. We think a lot about pace layering -- how do we have teams that think on multi-year horizons (infrastructure, security, etc.) alongside teams that are rapidly iterating at much earlier stages of development. I think a lot goes wrong when organizations insist on too much consistency in their operating approach.
We've now identified a few semi-formal mechanisms that have helped substantially. (For example: larger companies tend to want to aggressively standardize roles. This makes sense when operating at scale but less so in the early days. So, we've made it easy to hire for ill-defined roles in nascent product areas -- we figure we can codify those roles later as needed and that doing so sooner is a premature optimization.) We'd certainly consider writing a blog post once we feel that they might be generalizable.
(If anyone reading this is interested in helping us figure things out, please do apply. We're particularly interested in hiring engineers who are interested in these questions.)
We are trying to figure out how to do this at Clever, and I know others like Segment (https://segment.com/blog/finding-product-market-fit-again/) are thinking about this as well, so hopefully we can start putting together some advice on how to create an "engine" for layering new products onto an established platform.
I know there's Atlas, but for a bootstrapper I can't afford it (especially when I don't know anything about legal stuff).
Also, their (estonian) corporate taxes are higher than ours.
I have years of experience with “big data” but I’ve always thought payments would be a good, similar vertical that would be far more interesting
Do you have a link? Thanks.