zlacker

>But it does reduced by an order of magnitude the amount of money you need to spend on programming a solution that would work better

Could you share any data on this? Are there any case studies you could reference or at least personal experience? One order of magnitude is 10x improvement in cost, right?

>>soloma+(OP)
I‘m not sure it’s a perfect example, but at least it’s a very realistic example from a company that really doesn’t have time and energy for hype or fluff:

We are currently sunsetting our use of Webflow for content management and hosting, and are replacing it with our own solution which Cursor & Claude Opus helped us build in around 10 days:

https://dx-tooling.org/sitebuilder/

https://github.com/dx-tooling/sitebuilder-webapp

>>Manuel+A2
Thanks for the link.

So, basically you made a replacement for webflow for your use case in 10 days, right?

>>Manuel+A2
I’m not sure the world needed yet another CMS

>>iamacy+Lq
It doesn't. The person is saying they built just the functionality they needed. Probably 25% of a CMS. That's the point.

>>daniel+Nn1
Exactly.

And the big advantage for us is two things: Our content marketers now have a "Cursor-light" experience when creating landingpages, as this is a "text-to-landingpage" LLM-powered tool with a chat interface from their point of view; no fumbling around in the Webflow WYSIWYG interface anymore.

And from the software engineering department's point of view, the results of the work done by the content marketers are simply changes/PR in a git repository, which we can work on in the IDE of our choice — again, no fumbling around in the Webflow WYSIWYG interface anymore.

>>soloma+R4
That's fair to say, yes, with the important caveat that it isn't a 1:1 replacement of Webflow, which is exactly the point.

>>Manuel+Yy1
This is the benefit few understand properly. The storage layer is where you get a lot of benefits.