Our vertical is operations and manufacturing.
We tackle startups from various geometry : i.e. types of product (SaaS, marketplace, AI, user-led, sales-led, tech-led), type of market (SMBs, Big Cos, competitive, to be educated).
As a comparison, other venture builders can have a different approach : scoping the target startups to be launched at the intersection of the target business set (e.g. cyber, sales, procurement) and their skillset (e.g. prosumer SaaS, startup segment).
In the first configuration, we accept to digest a higher variability, resulting in different needs according to the context. This is the elasticity we need to master.
We must consequently pilot the cohort process in a more elastic way.
More variability and ambiguity implies more operational process to pilot the overall launch.
This process aims to deeply understand the changing context of a startup, from various expert point of view and pilot the resource and OSS help.
For founders, it aims to give you full transparency on OSS resources, have a single points of contacts with OSS directions to share the same informations and get one clear answer on high level topics, to foster collaboration with OSS and with other founders.
Typical implication is that we will still give roughly 9 months of resources on startups but these could be spread out across a 12 or 18 months length, balancing temporary work, iteration and validation on the system, and moments of pure execution.