u/Crazy-Park-2930

Joined Lovable office hours last Thursday. Been a paying user for 11 months and never bothered before. Wanted to share what was actually useful and what wasn't.

Setup: hosted by Nad and Harry (community team), recorded for replay, ~45 minutes, open Q&A throughout.

What was useful:

The unstructured Q&A. Someone asked about workspace knowledge versioning and Harry showed how he sets it up at Lovable. That one answer changed my workflow.

Saw 3 features I had missed in the changelog: the agent comments thread feature, chat history search, and the @ mention for past projects.

Got a feel for what the team prioritizes. Spoiler: it's not what's loudest on Twitter.

A brief unscripted moment where someone asked about the April security incident. Nad addressed it directly, didn't deflect. Earned credibility points.

What wasn't useful:

The first 15 minutes were a feature demo. Could have skipped via replay.

Some questions were way too specific to one person's project. Wasted time for everyone else.

The chat moved too fast to follow. Lots of half-finished threads.

What I'd do differently:

Skip the first 15 if you're not new to Lovable. Write your question in chat early, otherwise you'll miss your window. Save the replay link, the answers compound.

The surprise:

I thought office hours would be a marketing channel. It's not. It's a working session. The team is genuinely there to answer questions and ship better defaults.

If you've been on Lovable a while and skipped office hours, give it one shot. Worth the 30 minutes you'll actually pay attention.

Curious if anyone has gotten value from office hours specifically that they couldn't have gotten elsewhere. Or if it's mostly useful for newer users.

freelance dev who took on small client builds specifically to compare these. 6 client briefs, similar scope across each (auth, dashboard, basic CRUD, stripe checkout, deployment). built each in a different platform.

tested: lovable, bolt.new, base44, replit agent, v0 + manual, cursor + claude.

ranked by "did the client actually use it in production for more than 30 days":

cursor + claude. shipped 6/6. the workflow isn't "AI builds the app." it's "I scaffold, claude fills in, I review every diff before commit." slowest of the lot on day 1 (about 3x slower than lovable). fastest end-to-end because there was nothing to fix at the end. the part that mattered: I owned the codebase, could push to github at any point, could swap claude for another model if I needed to.

v0 + manual. shipped 5/6. v0 handles the UI generation cleanly. limitation is everything past UI. you still wire up backend, auth, payments manually. but the UI quality is consistently the cleanest in the lot and the code extends well. one client wanted to take it in-house and their dev team had no issues picking it up.

lovable. shipped 2/6 (one was a marketing site). fast on day 1. by week 2 every project hits a wall where you can't fix something the AI built without breaking three other things. exported the codebase from one and finished it in cursor in 2 days. since the breach earlier this year I don't put real client data through it.

replit agent. shipped 1/6. agent is genuinely good. the platform around it is the issue. autoscale defaults bit me on a $480 weekend (separate post). exports work but the build is replit-coupled enough that "exporting" still means rebuilding chunks.

base44. shipped 0/6. fast initial scaffolding but the deployed apps had odd issues I couldn't trace back to specific source code. felt like building in a black box. abandoned at week 3.

bolt.new. shipped 0/6. great demos. the gap between "looks like it works" and "actually works in production" was the biggest of any tool I tested. stackblitz environment is impressive but moving the build out of it is rough.

what kept being true across all 6: the tools that let you own the codebase and use version control like a normal repo are the ones that survived past week 2. the ones that locked you into their proprietary environment all hit walls.

best AI app builder for client work is the one you can leave. that turned out to be the criterion that mattered. layout quality, AI smartness, deployment speed were all secondary or tied across the top 3.

caveat: this was specifically for paid client work where things have to keep working after handoff. for personal projects, prototypes, or "show this to my cofounder" demos, the rankings are probably different. lovable on a demo timeline is genuinely impressive.

what's everyone using for paid client work specifically (not personal projects)? and has anyone gotten a long-term shippable build out of base44 or bolt that I'm wrong about?

B2B SaaS, just hit a phase where we're getting 12-18 sales conversations a month. Every conversation wants a tailored deck. We are 5 people. Two of us spend a stupid amount of time on slides.

The context. Our buyer is a non-technical operator. They want to understand the product visually before committing to a demo. A generic deck doesn't get them past that first call. A tailored deck (their use case, their kind of customer, their objections answered) closes about 4x better.

The cost. I track deck creation time. Average is 90 minutes per tailored deck. Times 12-18 a month is 18-27 hours of senior people making slides instead of selling, building, or anything else.

Things I have tried.

Generic deck plus 5 swappable "industry slides." Faster but the conversion drop versus fully tailored was real.

Gamma with custom templates per ICP. Faster at the generation step but the editing still takes 30+ minutes because every prospect has at least one specific thing.

Hiring a contractor for deck production. Tried it. The lag time between "lead came in" and "deck is ready" was longer than the prospect's patience.

What I think I want is a system where the deck is 80% pre-built, the AI fills in the right examples for the prospect's industry, and a human takes 10 minutes to add the last 20%. I just don't know if that exists or if I have to build it.

For folks running a sales motion at this volume — what's your actual deck workflow. Specifically interested in whether anyone has solved the "fast and tailored" version of this without it eating a person's whole week.