u/No-Recognition3089

When you feed rough notes to a model and ask for slides, it just chops the notes into bullet points, one note per slide. You get a deck with no argument, just a transcript with borders. This makes it build a narrative spine first, then map slides onto it.

Here are my raw meeting notes: [PASTE]
Audience for the presentation: [WHO] and what they need to decide or do after.
Step 1: From these notes, state the one thing this presentation needs the audience to walk away believing.
Step 2: Lay out 5 to 8 beats that get them there: where they are now, the problem, why it matters to them, the shift, what it means, the ask.
Step 3: For each beat, give a slide title (a claim, not a topic) and 2 to 3 supporting lines from my notes.
Do not use a note that does not support a beat. Tell me which notes you dropped and why.

The part that fixes most decks is "a slide title that is a claim, not a topic." "Q3 Results" is a topic. "Q3 missed on one metric we can fix by Friday" is a claim, and a deck of claims reads like an argument. Making it report which notes it dropped keeps it honest instead of padding weak slides.

I still hand-tune the order after, but it gets me 80% of the way from notes to something presentable. How do others handle the "too many notes, not enough story" problem?

I built my landing page with one of those AI landing page generator tools before launch, and the results were mixed enough that I figured it was worth writing up for anyone about to do the same.

What it got right: it gave me a live page in about an hour instead of the two weekends I usually lose to fiddling with sections. The copy skeleton was fine as a starting point, and the layout was clean by default, so I stopped second-guessing spacing and fonts.

What it got wrong, and where I had to step in:

- The generated headline was generic. It described the category, not the specific problem I solve. I rewrote it to name the exact pain, and that single change moved my signup rate more than anything else.
- It filled the page with three feature blocks that all said roughly the same thing. I cut two of them. Fewer, sharper sections read better than a wall of benefits.
- The auto-written FAQ answered questions nobody was actually asking. I replaced them with the real objections I heard in DMs.
- Social proof placeholders stayed empty because I had none yet. I ended up putting a short honest "here's who this is for" line there instead, which felt less fake than borrowed logos.

The takeaway for me: these tools are good at getting you to a first draft you can react to, and bad at the parts that actually decide whether someone signs up. The specific words are still your job.

For those who used an AI generator for their landing page, what did you keep and what did you throw out? Curious whether people are editing the copy heavily or shipping it close to default.

Quick experiment writeup, because I got tired of guessing whether "be helpful in communities" does anything measurable.

Setup: tiny B2B tool, basically no audience. For 6 weeks I stopped posting anything about the product anywhere. I only answered questions where I genuinely knew the answer, across a handful of Reddit subs, two Slack groups, and one Discord. Rule was simple: no link unless someone explicitly asked what I used.

I tracked every reply in a spreadsheet. Where, the question, whether anyone followed up, and whether it turned into a signup I could trace.

Rough results after 6 weeks:

Somewhere around 90 real replies (skipped anything I couldn't actually add value to).

About 11 people DM'd or asked follow-ups.

7 of those tried the product, 3 are still around a month later.

Things that surprised me:

The replies that converted weren't the clever ones. They were the boring, specific "here's exactly how I'd do that in three steps" ones.

Older threads kept trickling. Two signups came from a comment I'd written a month earlier that someone found through search.

Volume did nothing. Ten thoughtful replies beat forty drive-by ones every single time.

Not life-changing numbers, but it's 3 retained users from zero spend and zero pitching, and the credibility carried over when I did eventually post something direct.

Curious what's worked for others who went the slow community route. Where did your first traceable users actually come from?

client wanted to be everywhere on social but had one person who barely had time to write the blog, let alone repurpose it. so i built a pipeline: every time they publish a blog post, an ai content generator turns it into a batch of short social posts in their voice and queues them as drafts for a human to approve before anything goes out.

honest results after about six weeks, because i hate posts that only show wins. output went way up, they went from posting a couple times a week to daily without more work. engagement was flat at first, the early drafts were generic and safe. it only got better once we spent real time feeding it examples of their best performing past posts and their actual tone.

the approval step is non negotiable. i tried a fully hands off version early and it posted something slightly off brand that we had to delete. now nothing publishes without a human clicking yes, and that one guardrail is what makes them comfortable running it at all.

net, it's a solid time saver but not a set and forget money printer. the quality tracks exactly how much context you give it. anyone gotten the tone to actually match without babysitting every post?

For a while I quietly resented my business partner. I was the visible one, long hours, always in the weeds, and from where I stood he seemed to do less. Then a genuinely bad year hit, and the things he'd been quietly doing, keeping our costs lean, holding cash back when I wanted to spend, maintaining the boring relationships with the bank and key suppliers, were exactly what carried us through while my frantic activity did nothing. I'd been measuring contribution by visible effort, which is a terrible metric. The person who prevents the disaster looks idle right up until the disaster arrives. I owe him an apology I've since given. Whose 'quiet' work in your business turned out to be load-bearing?

I dump raw meeting notes and want reliable structured output - decisions, actions, owners. What prompt pattern gets that consistently without the model missing items or inventing them? Looking for something battle-tested

I need one focused landing page for a new offer, not a whole site. Every ai landing page builder demo looks great until you actually use it. For people who shipped one - which got you to a clean, converting page with the least fuss?

There was never a version of "let's remove all the walls and put everyone in earshot of each other" that was going to make focused work easier. It was sold as collaboration but it was really about cramming more desks into less square footage for less money.

Anyone who's actually tried to concentrate while three conversations, a phone call, and someone's lunch happen within a metre of them knew instantly. People respond by wearing noise-cancelling headphones all day, which defeats the entire "collaboration" premise. We spent two decades and a fortune proving that humans like a door. Groundbreaking.

I want to compare real numbers, because the plan page is useless on this.

Since the last round of changes I have been tracking my own usage. On the heavy reasoning model I am getting cut off at what looks like roughly 45 to 50 long messages in a rolling window before it tells me to wait, and a couple of times it happened faster than that on days I was running longer prompts. On Plus I never watched this because I hit walls constantly. On Pro I assumed I would not have to think about it, and for months I did not.

Before the usual replies: yes, I know heavy reasoning costs more per message, and yes, I have tried spacing them out. I am not asking how to avoid it. I am trying to figure out whether my numbers match yours, or if something is off with my account specifically.

So, roughly, what are you seeing before you get limited on the heavy model? Same ballpark, or very different?

eleven years of data on this, and the correlation has never once broken.

the client paying us the least is the one who calls on saturday. who wants a fourth revision. who questions every line item. who has the most opinions and the least patience and the strongest sense that they are being taken advantage of.

for years i thought this was just bad luck, or that i was attracting the wrong small clients. i now think it's structural, and it's this: for the client spending a small amount, that small amount is an enormous portion of their budget, and possibly their savings. it's terrifying money. every dollar is felt. so they scrutinize, they worry, they need constant reassurance, and their anxiety expresses itself as demandingness.

meanwhile the big client, spending ten times as much, is spending money that is a rounding error to them. it's not their money in any felt sense. so they're relaxed, they trust the process, they don't call on saturday, because the stakes to them personally are near zero.

it's not that small clients are worse people. it's that we're asking them to be calm about an amount of money that is genuinely, existentially significant to them, and they can't be, and neither could i in their position.

which is why i now price so that i don't take on clients for whom my fee is terrifying. not because they're bad clients, but because the relationship is structurally doomed to be painful for both of us, and no amount of good work fixes a client who is scared of the invoice.

asking a narrow group on purpose, because the general advice on this does not survive contact with how it actually goes for us.

i'm a staff data engineer, six years at my company. found out in a roundabout way that a guy who came in two levels below me three years ago is now half a band above me on base. our manager changed last cycle, so the paper trail of how that happened is conveniently gone.

i have a competing offer coming. a real one, not a bluff. i could just take it. but i'd rather stay if they fix the number, and i'm trying to decide how to bring the gap into the room without it turning into a referendum on my attitude.

specifically, for women who have done this and had it actually work:

• did you say the words "i think there's a gap here that isn't about performance," or did you keep it purely about the market offer
• did naming a specific male peer ever help, or is that the exact move that gets you labeled
• did you get the new number in writing before you declined the other offer

i can already hear "well, it's just business" warming up in the comments, and i promise it has never once felt like just business when i'm the one in the chair. a line or two from anyone who's been here would mean a lot.

run a small agency. and the actual exhaustion this year isn't the client work. it's that the ground keeps moving and i keep having to rebuild the thing we sell on top of it.

january we were a "content and SEO" shop. then AI overviews ate organic and i spent a month repositioning us as "AEO/GEO specialists" because that's where the panic and the budgets went. then a core update reshuffled everyone. then the CTR rebound made me wonder if i overcorrected. now i'm reading about AI mode hitting a billion users and wondering if i need to rebuild the pitch again.

every repositioning means new decks, new case study framing, new language on the site, retraining the team to talk about it, recalibrating what we even promise. and the clients just want to know if they'll get customers, which is the one thing that stays the same under all of it.

i'm not burned out on the work. i'm burned out on the meta-work. on having to have an opinion about the future of search every quarter just to describe what we do.

some weeks i fantasize about being a plumber. pipes don't get a core update.

how are the rest of you handling the constant repositioning? do you chase every shift or do you pick a lane and just ride it out and trust it'll still matter? genuinely don't know which is smarter anymore.

kickoff call with a vendor were evaluating. four of us on, im the most senior, im the technical decision maker, the budget is mine to recommend. theres a junior guy on my team, six months in, lovely, knows a fraction of what i know about our stack.

the vendor's solutions engineer addressed every single technical answer to him. i'd ask the question, and the answer would land on the junior guy's face like i hadnt spoken. twice the junior guy actually said "thats really a question for her, she owns this." the SE nodded and then kept doing it.

we're not buying from them. not as some grand statement, just because if thats how they read a room in the sales call where they're supposed to be impressing us, i can only imagine the support relationship.

the junior guy was great about it, for the record, visibly uncomfortable and trying to redirect. i told him afterward he handled it right. small thing. but it's the hundredth small thing, and the hundredth one still costs something. anyone else just quietly route business away from vendors who cant figure out who the decision maker is? feels like the only vote i actually get.

Client wanted an iOS app for nurses to log patient vitals during home visits. Couldn't be a web app (had to be App Store, HIPAA-adjacent). Had to work offline (rural areas, spotty signal). Budget was $11K total including 6 months of support. Timeline was 6 weeks.

I'd built in Glide before. Knew Adalo had improved a lot recently. Hadn't seriously used FlutterFlow but it kept coming up. Spent a month evaluating all three with the same simplified prototype: login, list of patients, vitals entry form, sync queue for offline mode.

Glide got to about 80% in 4 days. Hit a wall on offline sync. Glide's offline mode is read-mostly. Write operations queue but the queueing logic is opaque and the failure modes aren't great. For a client dashboard where you mostly view things, it's fine. For nurses entering data in a basement clinic with no signal, the risk of silent data loss was too high. Loved building in Glide. Couldn't ship in Glide.

FlutterFlow got further. Real Flutter underneath, generates actual native code, exports to a Flutter project you can take to Codemagic and ship to TestFlight. The offline sync was workable with some custom function code. The problem was the price-to-complexity curve. To get the offline sync working properly I had to write Dart in custom functions and at that point I was essentially writing a Flutter app with extra steps. Platform billing was also confusing: team plan to do what I needed plus app deployment fees plus Firebase costs underneath.

Then I tried SAP Build Apps. Yes that SAP. Formerly AppGyver before SAP acquired them. Free tier exists. Generates native iOS and Android apps from a visual builder. Has real offline-first data sync built in, including basic conflict resolution. The interface is rougher than Glide. The community is tiny. There's almost no content about it on YouTube or Twitter.

It shipped. App is in production with 14 nurses using it daily across 3 counties. Offline sync works as advertised. Cost me $0 in platform fees. The client owns the source artifacts.

The reason I'm writing this is that I would not have found SAP Build Apps from the AI recommendations, the Reddit threads, or the YouTube videos. Every comparison post lists Glide, FlutterFlow, Adalo, Thunkable, Bubble. SAP doesn't appear because SAP isn't marketing it to the indie no-code crowd and the indie no-code community has zero relationship with anything SAP. But for offline-first business apps where you need real native, it's quietly the most capable thing in the category.

Caveats so I'm not overselling. The editor is uglier. The community is on enterprise forums not Twitter. If something breaks at 11pm on a Saturday you're on your own because there's no active Discord. The platform is also SAP property which makes some teams nervous about long-term roadmap (fair, though SAP isn't going anywhere).

But the app shipped. Works offline. Was effectively free on the tooling side.

Worth a look if you're picking a mobile no-code platform for anything beyond a basic prototype.

What underrated platforms have people found by accident or word of mouth? Looking for tools that aren't on the standard comparison lists.

She told me yesterday in our weekly. She had been pushing for three months. She had filed paperwork twice. She had escalated to her director. She had quoted my performance reviews. She had documented the work-from-home setup I have built that produces the work she relies on. She did all of this without me asking her to.

The accommodation team denied it last Friday. The note she received said the role was "not on the approved exception list." There was no further detail. She asked for further detail. She was told the approved exception list was confidential.

She told me all of this at 2:30pm on a Tuesday in a meeting that was supposed to be about our Q3 OKRs. She did not cry but she got close. I did not cry but I got close. We did not discuss OKRs.

She said she was sorry. She said it three times. I said it was not her fault and that I knew she had fought it harder than I would have. She said she didn't know what else she could do.

I said "I think we both know what comes next."

She said "yeah."

We talked about my timeline. We talked about what she could put in a reference. She said she would write me anyhting I needed. She said she was sorry again.

I closed my laptop at 3:00pm and sat on the couch with the cat. We did not move for an hour.