What I mean is that early stage startups will have to bootstrap some cloud infra, but their engineering teams are laser focused on creating value for their users and validating product market fit. Every day that a technical founder/early hire spends writing their cloud story is a day taken away from their runway without (directly) creating value that could lead to revenue or funding.
People will pay you to build out their cloud infrastructure one feature at a time, or pick features off the cart as they want them (so maybe like an all you can eat cloud buffet?). There's a bonus to that too, iterative consulting is a great way to validate a tech stack for a problem domain before you figure out how to turn it into a recurring revenue source.
AWS for all its flaws is actually pretty good for this already, which I think is why it gets so popular with seed stage startups before they get locked in (plus the credits that they give out like candy...). I don't have to think about architecture, I google what aws cli command I need to set stuff up and move on with my life.
People will pay you to build out their cloud infrastructure one feature at a time, or pick features off the cart as they want them (so maybe like an all you can eat cloud buffet?). There's a bonus to that too, iterative consulting is a great way to validate a tech stack for a problem domain before you figure out how to turn it into a recurring revenue source.
AWS for all its flaws is actually pretty good for this already, which I think is why it gets so popular with seed stage startups before they get locked in (plus the credits that they give out like candy...). I don't have to think about architecture, I google what aws cli command I need to set stuff up and move on with my life.