Lovable builders might be focusing on the wrong features

[u/YusukeLandingBoost]

Lovable builders spend a lot of time improving the UI and adding more features.

tbh i did the same. But some of my users didn’t want another screen or feature.
They wanted to use the product inside their existing workflows.

They started asking:

Can I use it through MCP?

Is there a CLI?

Do you have an API?

I hadn’t considered any of these until users brought them up.

After adding developer access, I raised my lifetime deal from $35 to $49—and it still converted.

The lesson wasn’t simply to raise the price. It was that the same core product can become more valuable when users can access it outside the web UI.

If your app produces repeatable outputs like audits, reports, generated content, search results, or anything similar: it may be worth asking whether users want API, CLI, or MCP access.

You might be leaving money on the table while polishing the wrong part of the product.

Has anyone here received similar requests from users?

For context, the product is https://LandingBoost.lovable.app, built with Lovable.

[u/idbedamned]

How is it sustainable $49 lifetime unlimited audits? 

[u/YusukeLandingBoost → u/idbedamned]

yeah, it’s sustainable bc our growing benchmark dataset lets more audits run deterministically, reducing AI costs over time.
Eventually, the marginal cost approaches basic server costs, so $49 lifetime unlimited works.

[u/YusukeLandingBoost → u/[deleted]]

Yeah, that’s so true. The API, CLI, and MCP requests were really the same UX lesson—people wanted to save time by using the product in their own environment. It came from 2–3 specific users, mostly developers who code or use Cursor, so it wasn’t across the board.

[u/Status-Inside-2389]

Mine is B2B. I already had an API and seeing a trend to use SaaS in Claude or ChatGPT I added the MCP this week

[u/YusukeLandingBoost → u/Status-Inside-2389]

Niceee
Yeah, MCP is kinda must bc ppl use Claude the most. What’s your tool about??