The recipe to build a product studio

1 points by ochysp ↗ HN
First, why a Product studio? Placing multiple bets is better than investing all your time in one single project + no need for funding, no need to quit your job...

Now, the recipe is simple: 1/ All your projects should have almost identical components, example: - Curated directory - Community portal - Deal page

Examples: A website who matches business owners with pre-vetted accountants + community for smb owners to discuss financial matters + finance related software deals.

Key takeaway: Choose carefully your components, you will reuse them later on.

2/ You need a tech stack, preferably a low-code stack to launch cheaper and faster.

This usually is a mix of tools, for the example above, we would use Umso + bubble + airtable + zapier + Facebook groups.

This the simplest form for me to give you some value on how to build a product studio. Now we run our own and partner with creators/entrepreneurs to launch products.

If you have questions, want to launch a product together (like the example above), want advice on tech stack, etc...

Email me mbm@btwinz.com

1 comment

[ 3.1 ms ] story [ 16.7 ms ] thread
I have been thinking about this idea, because I invested in building out a robust web application base in django this past summer and fall.

Built two “components” but not sure if I want to use them in a product studio.

May email you. Beyond quality user account stuff