# Spending as Much Time As...  ## Metadata - Author: [[@ibscribe on Twitter]] - Full Title: Spending as Much Time As... - Category: #tweets - URL: https://twitter.com/ibscribe/status/1498894429129609218 ## Highlights - Spending as much time as I do studying / building SaaS products, you tend to see patterns emerge. I’m going to share one today for how to bootstrap a 0 -> 1 SaaS offering in 3 steps. 🧵  ([View Tweet](https://twitter.com/ibscribe/status/1498894429129609218)) - (Yes, I know the diagram looks like a barn - I struggled with how to visualize it.) ([View Tweet](https://twitter.com/ibscribe/status/1498894498100703232)) - My basic thesis here is that many (all?) SaaS products are fundamentally about re-imagining a workflow that is sub-optimal for some reason ([View Tweet](https://twitter.com/ibscribe/status/1498894663121457153)) - if you can figure how to simplify the creation flow for the core user, and create a consumption bridge for adjacent users, you have a product powered by an insight that let’s you skip steps ([View Tweet](https://twitter.com/ibscribe/status/1498894769057005573)) - Bear with me as a I try to make “skip step SaaS” a thing… ([View Tweet](https://twitter.com/ibscribe/status/1498894891492933632)) - When you’re looking to identify a multi-* process, you can take the tactic of exploring workflows that are multi-step, multi-tool, multi-user, or multi-phase. The aha! you bring to the problem is to have a unique point of view on how / why multi-* can be collapsed into a single-* ([View Tweet](https://twitter.com/ibscribe/status/1498895103833751557)) - The opportunity you identified in the first step will dictate how you simplify the end-to-end flow in your subsequent step ([View Tweet](https://twitter.com/ibscribe/status/1498895410894553089)) - a multi-step process is simplified by making it single-step, a multi-user flow is simplified by creating a shared space, a manual input/output is simplified through automation, etc  ([View Tweet](https://twitter.com/ibscribe/status/1498895547159044101)) - The last step in bootstrapping a SaaS product is bridging the collaboration divide between core and adjacent users. Work actually happens across teams, across departments, across organizations… ([View Tweet](https://twitter.com/ibscribe/status/1498895658052296705)) - but because the hierarchical org chart is our default view of the user population, we tend to miss this nuance.  ([View Tweet](https://twitter.com/ibscribe/status/1498895822452244481)) - if you enjoyed this thread 🧵, check out the full post with more examples here 👉🏽 https://t.co/R1nD2xr2QQ ([View Tweet](https://twitter.com/ibscribe/status/1498896266524119041)) - And if you enjoyed the barn diagram follow me @ibscribe (same handle on IG) for more visual frameworks ([View Tweet](https://twitter.com/ibscribe/status/1498896435873415169)) - lastly, if you’re interested in learning more about scaling SaaS products, check out my upcoming live cohort offered via @scholar_site https://t.co/2WX6RLIjZ6 ([View Tweet](https://twitter.com/ibscribe/status/1498896760785162240))