u/Crazy-Park-2930

I run a small commercial cleaning company. Most of my work has come from word of mouth, but I finally got a shot to pitch a property management group that could roughly double my accounts. They want me to come in and "present" to three of their managers next week.

Problem is I've never done a real presentation in my life. I'm fine one on one across a table. Put me in front of a slideshow and a room and I freeze up.

I don't want to overthink it, but I also don't want to walk in with a wall of text on a screen and read it off like everyone hates. For those of you who've had to pitch to a company like this:

- Do you actually build slides, or just talk and hand them something on paper?

- How many slides is too many for a 20 minute thing?

- What do you put on the screen versus what you just say out loud?

Trying to figure out how much to prepare without going down a rabbit hole. What's worked for you when the account was worth it?

Genuine question for people who make posters in Canva a lot. Every time I go to make one now there's the AI poster maker option pushed at me, and I keep going back and forth on whether it's worth using.

When I've tried it, it gets me a layout fast, but it never feels quite right. Spacing is off, the type choices are generic, and I end up rebuilding half of it anyway. At that point I'm not sure it saved me time versus just starting from a blank canvas with a decent template.

On the other hand, for a rough first idea when I'm stuck, it's occasionally useful as a starting point I can tear apart.

So I'm curious where people actually land:

- Do you use it for a first draft and then fix it, or skip it entirely?

- Has it gotten good enough to trust for anything client-facing?

- Or is a saved template plus doing it by hand still faster for you?

Feels like half this sub is tired of the AI stuff being pushed everywhere, so I'm expecting mixed answers, but I'd genuinely like to know if I'm sleeping on something useful or right to mostly ignore it.

​

I spent a while frustrated that AI writing help gave me output that was technically fine and totally lifeless, so I stopped asking for finished text in one shot. The workflow that actually stuck for me is two passes, and it changed the quality more than any prompt trick.

First pass, I don't ask it to write anything good. I dump my rough notes and ask it only to organize them into an outline and flag what's missing or thin. No prose yet. This is where it earns its keep, because it catches the gaps I'd have written around.

Second pass, I fill the thin spots myself with real detail, then ask it to draft from the completed outline in short, plain sentences. Because it now has actual substance to work with instead of vibes, the draft comes out specific instead of generic.

Then I do the last edit by hand. I never ship its exact words. It gets me from blank page to a solid draft, and I finish it so it sounds like me.

The thing that made the biggest difference was separating "think about the structure" from "write the words." When I asked for both at once I got mush. Split into two steps, each one gets noticeably better.

Curious what everyone else's writing workflow looks like. Are you one-shotting it or running it in stages like this?

Putting the finishing touches on my launch and I've attached a screenshot of my plan. I'm sure there are obvious gaps I can't see from the inside. For those who've launched, what did I forget or underestimate? Genuinely want the holes poked.

​

I keep hearing it saves hours but for me the output needs so much fixing it's a wash. Where has an ai content generator genuinely saved you time, and where did it just move the work around?

Not the best feature, the first one. the one that saves them from the mistake everyone makes in week one. I’ll go first: the card count setting, because the default padded 10 cards is how every wall-of-filler deck starts.

Every time I ship a small tool I hit the same wall. The project has zero users and zero revenue, so paying a monthly subscription for a launch page feels ridiculous. But every "free" builder I try has the same catch: the free tier either slaps their branding on your page or locks custom domains behind the paid plan. Which I get, that's the business model, but it means "free" really means "free ad for them on your project."

My current workaround is plain HTML on GitHub Pages with a cheap domain pointed at it. Costs nothing, loads fast, looks like it was made in 2011. Which, in my hands, it was.

Before I write the same index.html for the fifth time: has anyone found a genuinely free setup that doesn't scream free tier? Or is GitHub Pages plus an hour of CSS still the honest answer for pre-revenue projects?

Also half-wondering if the branding badge even matters. Does anyone actually judge a side project for having a builder's logo in the corner, or is that just my ego?

Fourth year. Chemistry. The data is done. The experiments worked, which is somehow worse, because now there's no excuse left.

I have 40,000 words. I need maybe 25,000 more and a lot of restructuring. And I have not opened the document in five weeks.

I open my laptop. I do everything else. I answer emails from undergrads with a speed and thoroughness that nobody has ever asked for or needed. I have reorganized my reference library twice. I built a genuinely beautiful note-taking system instead of writing, and it is well-structured, and it contains nothing.

I know every piece of advice. Pomodoro. Two hundred words a day. Just open it. Shitty first drafts. Body doubling. I can recite them and none of them touch this, because the problem is not that I don't know how to write. The problem is that opening the file means finding out whether the last four years were worth anything, and as long as it stays closed, the answer isn't in yet, and not-knowing is more bearable than the possibility of the answer being no.

My supervisor thinks I'm "in the writing phase." She sent an encouraging email last week. I felt like a fraud reading it and I still haven't replied.

I'm not asking for tips. I have tips. I have an entire elaborate system of tips that I built instead of writing.

What I actually want to know, from anyone who has been in this specific hole: how did you actually open the file? Not the technique. The technique isn't the thing. What actually happened, internally, on the day you finally opened it?

Posting as craft, not complaint.

it will help you do exactly what you asked for, brilliantly, and it will never once say "this is a small ambition and you could be attempting something much better."

i noticed this about my own use. i'd ask for help improving a slide. and it would improve the slide, genuinely, materially. what it never said, because it doesn't work that way, was "the slide is fine, but this entire presentation is answering a question your audience doesn't care about."

a good colleague does that. a good colleague looks at the thing you're grinding on and says "why are you even doing this." that intervention, the one that saves you a week by killing the work rather than improving it, is the single most valuable thing another mind can offer you, and it's structurally unavailable here, because the model takes the frame you hand it as the world.

it optimizes within your ambition. it does not challenge the size of your ambition. and because it's so good at the optimizing, the experience of using it feels like progress, and you can spend a very long time making excellent progress on something small.

the partial workaround is to explicitly hand it the bigger frame: "before you help, tell me whether this is the right thing to be spending time on, and what a more ambitious version of this project would look like." it can answer that. it just never volunteers it, and you have to remember to ask, and the whole trap is that when you're deep in something you don't think to.

Bootstrapped SaaS, and last spring our open rates quietly fell off a cliff. From a healthy 40-something percent down to single digits over maybe six weeks. I assumed people just stopped caring.

They didn't. The email was going to spam and I didn't know, because it landed fine in my own inbox. Classic.

Turns out figuring out how to improve email deliverability is mostly unglamorous plumbing. We'd never set up the authentication records properly when we migrated domains. SPF was there, DKIM was half-configured, DMARC didn't exist. Mailbox providers had slowly decided we were sketchy.

Fixed the records, warmed the domain back up slowly instead of blasting our whole list, and started actually removing people who hadn't opened anything in months. Took about three weeks to recover.

The part that stung: I'd been writing better subject lines the whole time, optimizing the wrong layer. Nobody was rejecting my copy. The mail server was rejecting me before anyone saw a word.

Check your plumbing before you blame your writing.

PSA because this catches someone here every week. if your Supabase emails are landing in spam or not arriving, the cause is usually one of these, in order: you're still on the built-in default sender for real traffic. it's testing-only, low limits, no reputation. move off it first, this is most cases. i moved to dreamlit since it reads my db, but honestly any real sender beats the default. your domain isn't authenticated. no SPF/DKIM/DMARC is an automatic spam flag no provider can fix for you. fresh domain, no warmup, sudden big send. looks identical to spam to gmail. receipts and marketing sharing one reputation, so a bad campaign drags your auth emails down. fix those before you blame your provider or switch tools. i switched once before fixing DNS and it changed nothing. what was your actual fix? curious how often it's just the default sender..

Two of us, no marketer, and email is somehow one of our better channels. the system is almost too simple to post, but it works. we don't have a calendar or a strategy deck. we have four automations that run forever (welcome to activation, a go-quiet nudge, trial-ending, failed-payment) and one human email we send whenever we genuinely have something to say. those automations run off our app data directly through dreamlit, so there's no separate list to maintain, which is the only reason two of us keep them accurate. that's it. the automations do the heavy lifting because they hit people at the right moment regardless of whether we're paying attention. the occasional human email keeps us from feeling like a robot. what makes it survivable without a hire is refusing to run a "real" program. the founders i know who burned out on email tried to act like a marketing team they didn't have. do less, automate the moments that matter, write like a person when you do write. what's your no-team email setup look like?

We let our copywriter go in the spring. "AI can do it now." what actually happened is the AI produces something competent and lifeless, and i, the marketing manager, spend hours every week injecting the specificity and the actual human detail back into it, which is the exact thing the copywriter used to do, except now it's buried in my job and unpaid and uncredited.

leadership thinks we saved a salary. we kind of did, on paper. what we actually did is take a specialized job, blend it into mine, and pretend the machine does it. the irony is that the more human mess i put back in, the better it performs, which is just a slow rediscovery of why we hired a copywriter in the first place.

im not anti-AI. it's a fine first-draft machine. but "we replaced the writer with AI" really means "we replaced the writer with the AI plus an unacknowledged amount of someone else's time," and nobody wants to hear that part because it ruins the savings story.

anyone else become the secret human layer that makes your company's AI output usable? how do you make the invisible labor visible without sounding like you're resisting progress?

22 clients. 14 years solo bookkeeping practice. Mostly small businesses across mixed industries (restaurants, contractors, retail, services, 2 SaaS).

For 14 years I've been a generalist. Take all comers, learn the industry quirks as I go. Worked fine. Income has been steady at ~$110-140k/year depending on the year.

For 14 years I've also watched bookkeeping niching specialists (restaurant bookkeepers, e-com bookkeepers, contractor bookkeepers) charge 1.5-2x my rates. And keep their clients longer.

Considering a niche play. Probably contractors (I have 4 contractor clients already, I know the QBO setup for construction better than I know my own taxes, and the market is large in my region).

The math if I niche:

Higher rates (could probably charge ~$650/mo vs my current $380/mo average)

22 clients down to maybe 16-18 (some current clients won't fit the niche)

Net effect: similar revenue, less complexity, faster work per client

The concern:

14 years of generalist reputation in my city

The non-contractor clients I'd lose are some of my favorite people

The niche pitch ("I only work with contractors") feels presumptuous

Feedback wanted from fellow solo financial pros:

Anyone do the generalist → niche transition mid-career? How did you handle the existing client conversation?

Is the niche premium real or a marketing fantasy?

Did anyone niche and then regret it?

For tooling: I'd rebuild my business proposal template word doc to reflect contractor-specific pain (job costing, AIA progress billing, prevailing wage compliance) and use an ai report generator to make my client month-end summaries more contractor-flavored.

Looking for the honest take. Not the LinkedIn version.

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.