|
|
|
|
|
by cschreiber
1114 days ago
|
|
You can separate the target audience into three main camps: Technical people at startups. In smaller companies that can be the CTO, in larger companies it is usually individual contributors. They are using Fastgen to extend their existing product or build the backend for small internal/external tools. Solo entrepreneurs or small bootstrapped teams that are using low code tools to power most of their business. They would use a Frontend builder like Webflow or WeWeb for their Frontend and Fastgen to power the backend. Freelancers and Agencies. They are enabled to quickly prototype and build projects for their clients. The visual nature of Fastgen makes it easier for clients to understand and provide feedback on the processes. Before our launch today, we were running a private beta for 3 months. We had users from all the categories above participate and worked closely with them to improve the product |
|
As a backend-developer I’d never use your tool, because it is limited to the set of building blocks you’re offering.
As a no-code developer “REST APIs, CRUD operations and dynamic workflows on top of a Postgres DB” are foreign words to me. Why would I even need that? And even if I needed that, why would I use something that is limited instead of a low-code tool like Windmill, Retool or Trigger.dev?
I think you really have to think about who is going to be using the product and what are their requirements. Maybe the type of customers didn’t even need an API in the first place?