Please Validate my Idea: Launch wizard for AWS

Hello, I'm Victor. My day job is as a Sr Engineer at one of the FAANGs. I have a side hustle as a fractional CTO.

In my fractional CTO practice, I have noticed that many dev agencies still launch infrastructure with click-ops. It must take at least a few hours to get everything set up: launch ec2 instance, install php, point the dns name by hand, etc. And the end result is actually quite bad - stateful infrastructure that can't be easily replaced, where the DNS name is pointing directly to an ec2 instance. Often, they even install mysql on the same host.

All of these things are huge points of technical debt AND it takes longer to do it the wrong way than to do it the right way. My product would save dev agencies time and enable them to deliver a better solution.

My product vision is a website where you can launch new infrastructure into your (or your client's) AWS account in under 3 minutes. You'd go through a wizard where you put in the domain name, then configure your domain registrar with nameservers, then pick a couple more parameters, and at the end you have:

• Scalability out of the box: an ec2 autoscaling group behind the dns name you want, with either Rails, laravel, or nodejs/express installed and running. The database would be on AWS RDS with multi-AZ failover for prod (but not for staging).
• Source control: all the stuff i'll launch for you will live in a github repo. It will have a sample hello world endpoint and the infrastructure defined as code, using CDK. This repo lives in your own account or in your customer's account.
• CI/CD out of the box: the repo will come with preconfigured github actions so when you push to the staging branch it pushes to staging environment, and when you push to the main branch it pushes to prod.
• Several best practices: log pulling out of the box, log statements to cloudwatch out of the box, per-API metrics out of the box, and https out of the box, good load balancer configurations out of the box, database encryption at rest out of the box, etc.

You can come back to the website at any time and have a look at your apps. It would be like a catalog of apps you've launched and are maintaining for customers.

The initial (MVP) version of the platform would only allow you to see the list of apps you have launched and to launch new ones. There would be some deep links into cloudwatch for logs for each app but nothing else in terms of maintenance/observability.

Since the resources are all connected to your aws/github accounts, you can cancel at any time and keep running everything yourself.

My question is to the engineering side hustlers and consultants out there, do you think you'd pay $100/mo for this?

Even a simple yes/no would help. Thanks a lot for reading this far.