u/Several_Function_129

Most of my presentation tips over the years were about making slides look better. This one is the opposite and it did more for me than any of them.

Before I make a single slide, I write the last one. The slide with the ask, the decision, or the one sentence I want people repeating on the way out. If I can't write that clearly, the deck isn't ready and no layout is going to save it.

Then I build backwards. Every slide has to earn its place by moving the room toward that closing line. If it doesn't, it gets cut. Sounds obvious, but it quietly kills the "here's everything I know about the topic" deck that goes nowhere.

The side effect is my decks got shorter and I stopped reordering slides five times the night before. The order mostly writes itself once you know where it ends.

What's the one presentation habit that actually changed your decks, not the flashy trick, the boring one that stuck?

i built this for exactly one reason. my screenshots folder had thousands of files all named Screenshot 2026-something and i could never find a single one.

so one evening i vibecoded a tiny thing that looks at each screenshot, reads what's actually in it, and renames it to something human. receipt-uber-march.png. slack-argument-about-tabs.png.

took maybe two evenings. most of that was me arguing with the model about file permissions, not the actual logic.

i posted it in a random discord thinking three people might care. a couple hundred folks have run it now and i keep getting emails asking can it do this for my downloads folder too. i did not plan for a downloads folder. i am learning what scope creep feels like from the inside.

the part that surprised me was that the boring problem was the good problem. i wasn't trying to build a startup, i just wanted to find one file, and it turns out a lot of people have the exact same tiny annoyance.

what's the most pointless thing you built for yourself that other people ended up wanting?

Curious where people have landed on this. I've tried leaning on the AI report generator for first drafts of monthly client reports, the kind with a few charts, some copy, and a summary page. It gets me a skeleton fast, but the layout usually needs real work before I'd send it. Inconsistent spacing, charts that don't match the brand colors, filler text I rewrite anyway.

Where it does help is the boring structural part, getting placeholder sections on the page so I'm not staring at a blank doc. The actual polish is still manual.

For those of you doing client reports regularly, is the generated starting point a real time save, or do you find you rebuild most of it? Trying to decide how much to rely on it.

https://preview.redd.it/0becr758yxhh1.png?width=554&format=png&auto=webp&s=ffb3b4905087b8b7565b1dd87d4d9a32d9877a37

I run a small shoe and leather repair shop, solo most days. For years my whole tracking system was a stack of tickets and my memory, and my phone rang constantly with people asking if their thing was done.

Two changes fixed most of it. First, a cheap whiteboard behind the counter with every open order, the name, the item, and the promised date, so I can answer any walk-in or caller in about two seconds. Second, I started texting people the minute their order's actually ready instead of waiting for them to check in.

The status calls dropped a lot, which handed me back real time at the bench. And people pick up faster now, so finished orders aren't piling on my shelf for weeks tying up space.

Total cost was a twelve dollar whiteboard and the two seconds it takes to send a text. I don't know why I waited so long to stop carrying it all in my head.

For the shop owners here, how do you track work in progress without it running your whole day? Curious if anyone's got a better system than a board.

Half my work is people handing me a finished Word doc and saying make slides. The trap is treating each heading as a slide and each paragraph as bullets, so you end up with a document on a screen. What works for me is reading the whole thing first and writing one sentence per section that states the actual point. That sentence becomes the slide title. Everything else is either support or gets cut. A 20-page report usually collapses to about 12 slides that way, and the ones I keep each earn their place. The hard part is not the layout, it is deciding what does not survive. How do the rest of you handle the sections a client insists on keeping?

Not an automated 'thanks for following, check out my link' blast, those get ignored or reported, I mean a genuine, specific, human note to new followers when I can. It sounds unscalable and that's kind of the point. A real welcome makes a new follower feel seen instead of like a number, and a follower who's had one real interaction with you is far more likely to actually engage with your content instead of scrolling past it forever. My early-follower drop-off shrank and my engagement rate rose, because I was converting silent new followers into people who'd actually met me. You can't do it for a million followers, but at most stages you can, and the relationship it builds compounds. The un-automatable stuff is often the moat. Do you welcome new followers, or just watch the number tick up?

I ignored hooks for a year and wondered why good content died. Then I started treating the first three seconds as the entire job and everything changed. The framework is simple: the opening frame must do one of three things instantly. Create a gap ('the one setting that fixed my reach'), show the payoff first ('this got 40k saves'), or start mid-action so there's no dead intro to scroll past. What kills reach is the slow build, the 'hey guys, so today I want to talk about', the logo animation. Nobody waits. I now film the hook separately and test three versions of it against the same body, because the hook is 80% of whether the video lives or dies. Same content, different opening, wildly different reach. What's your highest-performing hook style?

As a beginner, the tools that just spit out a big result leave me lost on what to do next. Are there AI tools that walk you through it step by step? Would help me actually learn instead of copy-pasting blindly.

I build quarterly business review decks and the same slide beats me every quarter: the big table. Finance hands me a QBR template that is basically a spreadsheet, 40 rows and a dozen columns, and says "put this on a slide."

Paste it as is and it is unreadable from more than two feet away, so nobody looks at it. Cut it down and someone always wants a number I removed. Screenshot the Excel range and it is a blurry image that does not match the deck and cannot be updated.

What I have tried:

- Pasting as a native PowerPoint table and restyling. Readable-ish, but tedious, and it breaks the moment the source numbers change.

- Linking the Excel range so it updates. Handy until the file moves and the link dies, or it quietly bloats the deck.

- Cutting to the 5 rows that matter and putting the full table in an appendix. Works when I can get finance to agree on which 5 rows matter, which is never.

What I actually want is the executive version on the slide (the few numbers plus the story) with the full grid available but not on screen.

So for people who live in data-heavy decks: how do you handle the giant table? Summarize and appendix it, link it live, rebuild it native, or something smarter? And how do you win the fight with the person who wants every single row kept?

Both launches were micro SaaS, both bootstrapped, both $0 marketing. The difference was entirely process. Writing this down mostly for past me.

**1. Smoke test before building anything.** First time I built for 3 months, then launched to silence. Second time I put up a one-page site with a waitlist before writing real code. I threw that page together in Gamma because it was the fastest way to get something live without touching frontend, though you'd outgrow it the moment you need custom scripts or proper analytics. Carrd or plain HTML would've done the same job. The point wasn't the tool, it was having a page collecting emails while I was still deciding what to build.

**2. Launched where the customers were, not where founders are.** First launch went to the big founder subs. Crickets, because everyone there is selling, not buying. Second time I spent a week finding the 3 niche communities where my actual users complain about the problem, and posted there.

**3. Posted about the problem, not the product.** My best performing post never mentioned I'd built anything until someone asked in the comments. It just described the problem accurately. People showed up to say "this is me" and the signups followed.

**4. Emailed all 47 signups personally within a day.** About half replied. Two of those conversations changed the roadmap, and 4 became paying. At this scale, doing things that don't scale is the whole job.

**5. Treated launch as a 2-week thing, not a day.** First time I "launched" once and waited. Second time I posted different angles in different places over two weeks. Rolling beats big bang when nobody knows you exist.

None of this is revolutionary and the numbers are tiny. But 3 → 47 with the same skill level and less code felt worth writing up.

What moved the needle between your first and second launch?

I spent probably twenty years of my life bending myself into shapes trying to get this man to say he was proud of me. Every grade, every job, every milestone, I'd tell him hoping this would be the one that landed.

He said it last week. Out of nowhere, at the end of a phone call. "I'm proud of you, you know." Just like that.

And I waited to feel the thing. The warmth I'd imagined a thousand times. It didn't come. I just felt tired. Like when you finally get the water you've been thirsty for but you're already past the point where it helps.

I think I grieved the version of him who'd say it a long time ago, and the real one showing up late doesn't fit the hole anymore. The hole closed over into scar tissue. I said "thanks dad" and we hung up and I stared at the wall.

I know I'm supposed to feel healed. Everyone says how nice that must have been. I can't tell anyone that it came fifteen years too late to matter. So I'm telling strangers. Edit: not looking for advice, I just needed to put this somewhere that isn't inside my own head.

I've been fully remote for four years and I genuinely don't know how people did this every day.

The layoff email came Tuesday morning. Restructuring, hard decisions, grateful for their contributions, the usual. Forty people, most of them remote, most of them on the teams that never set foot in our building. Then Thursday we got the other email. Five days in office starting next month. Same signature at the bottom.

Did my test drive yesterday. Left at 7:35 to make it by 9. Sat in traffic 50 minutes to go 16 miles. Garage was $19. My badge didnt work so I stood in the lobby while someone from "workplace experience" reset it.

The office got renovated while we were all home. There's a coffee bar with three kinds of oat milk now. The bathrooms are nicer than the ones in my apartment.

Got to my assigned hot desk. The monitor flickered. The guy two seats down was on Zoom from 9 to 4. I know because I spent the day on Slack with my manager in Austin and the two engineers I actually work with, who are in Krakow. Not one in-person work conversation the whole day.

The dog was waiting at the door when I got home at 6. I took her out, made coffee, and finished the thing I couldn't finish at the office because of the noise.

Nobody on my team thinks the five-day thing is about collaboration. We all read the same two emails in the same week. You do the math they're hoping you'll do.

Started updating my resume between meetings today.

Most writing tips for this thing are surface level. Here's the stuff I actually use daily after about a year, mostly non-code work.

It rewrites better than it writes. Give it your ugly draft and say "tighten this", dont ask it to start from nothing. The blank page is where it goes generic.

"Make it sound less AI" does nothing. "Cut any sentence that sounds like writing, use shorter words, leave one rough edge" does a lot.

Tell it who's reading, not who it is. "Explain this to a skeptical CFO" beats "you are an expert." The audience does the work.

It agrees with you if you let it. I stopped asking "is this good" and started asking "what's the strongest case this is wrong." Night and day.

Give it a reason to be short, not a word count. "this goes in a text" gets brevity that "under 50 words" never does.

Paste the doc, dont describe it. It reads files. I wasted months pasting walls of text when uploading worked better.

Ask for the version it avoided. "what's the riskier take you didnt write" surfaces the better answer maybe a third of the time.

The first reply is the start, not the answer. The good stuff is turn 2 or 3 after you push back. People who judge it on one paste are reviewing a first draft.

none of these are clever, they just took too long to become automatic. what crossed over from "trick I read" to "thing I do without thinking" for you? drop yours below

didn't see this coming.

shipped my saas with 3 plan options. seemed reasonable.

• annual: $290/year
• monthly: $34/mo
• lifetime: $499 one-time

customers switching between plans turned out to be the hardest part of the entire business.

the scenarios that need emails:

1. monthly → annual upgrade (refund partial monthly, charge annual, explain proration)
2. monthly → lifetime upgrade (refund partial, charge one-time, no more renewals)
3. annual → monthly downgrade (refund prorated, schedule new charge)
4. annual → lifetime upgrade (refund prorated, charge lifetime)
5. lifetime refund (rare but happens, refund within 14-day window)
6. annual renewal success (separate flow from initial purchase)
7. annual renewal failure (different from monthly renewal failure)
8. card expiry approaching for annual plan
9. annual cancellation requested (refund? end-of-period? different from monthly cancel)
10. lifetime plan after refund window (no further charges, but they cancelled - state is weird)

each scenario needs its own email. needs to explain whats happening, when, and what the next charge will be.

i shipped these one at a time over 3 months.

each one had edge cases. customers kept emailing confused about charges they didnt expect.

the worst was the monthly→annual upgrade mid-cycle. i had to refund the unused portion of the monthly subscription AND explain that the next charge would be the full annual amount. the email i shipped initially said "your new charge is $290" which made customers think they were being double-charged.

what i learned:

simpler pricing models are not "less revenue." theyre "less customer support and email complexity."

i should have started with monthly-only. added annual at $1k mrr. added lifetime at $5k mrr. instead i shipped all 3 from day 1 and spent 3 months drowning in plan-switch edge cases.

the email templates alone took ~25 hours of writing and testing. plus the state machine logic in supabase. plus the webhook handling for stripe state changes that affect emails. plus the customer support tickets explaining each transition.

if i started over: 1 plan for the first 6 months. add tiers only when revenue justifies the complexity.

the open question:

is there a way to handle plan-switching that doesnt require 10+ unique email templates? or is this just inherent complexity that everyone running subscription products faces?

asking the community:

• have you found a "minimum viable plan-switching email" approach
• how do you handle the state machine between stripe and your db
• whether you ship pricing complexity from day 1 or add gradually
• if youre running multi-tier subscriptions, how many distinct email templates do you have

specifically curious about the technical pattern for "stripe webhook fires → determine what changed → route to the correct email template" without it becoming an unmaintainable mess.

i don't even know what an engagement score is. i found out i had one yesterday.

apparently our company rolled out a workforce analytics platform sometime in q4. nobody told us. it tracks "engagement signals" which based on the HR doc i finally found buried in confluence includes: hours of active screen time, slack message volume, meeting attendance, response latency, and "collaborative footprint." it spits out a daily number. mine has been trending down for ten weeks.

here's what was happening during those ten weeks. i was on a project that required me to read four-hundred page legal documents and write a single 12-page summary. i was on slack less. i was in fewer meetings, by my manager's request, because she wanted me to focus. i finished the project two days early. she told me i did a great job.

the system flagged me anyway. the system does not know about the project. the system knows about typing.

the email says HR wants a 30-minute "wellness check-in" next tuesday to "discuss patterns and identify opportunities to re-engage." my manager forwarded the email with a single line: "this is just procedural, dont worry."

i don't know how to fight this. i don't know what evidence i'm supposed to bring. do i print out the legal summary? do i make a slide deck about the work i did?

this isn't about the engagement score. this is about being graded by software that has no idea what my job is.

made this mistake a few times before i learned it.

a contractor who quotes 30% under market isn't a deal. it's a signal. one of three things is true:

they don't know what their work is worth. you'll teach them by example, and they'll raise rates after you've built workflows around them.

they're new and undertrained. you're paying less because you'll spend hours fixing the output.

they're desperate. the work will be rushed because they're juggling too many clients to make the math work at their rate.

none of these are "you got a great deal."

cheap hires cost in invisible places. rework time. quality variance. context-switching. the senior person on your team reviewing the cheap person's work, which is the actual expense you're paying.

market rate exists for reasons. when you go significantly under it, you're not saving money. you're moving the cost from your invoice line to your team's calendar.

worth paying market rate the first time, every time.

I run a small consulting practice. Made the switch to Gamma as my primary deck tool in late 2024. Just looked at my Gamma library and realized I've crossed 200 decks in there. Posting the patterns in case useful.

What got better with volume.

My deck-making speed compounded. The first 20 decks in Gamma took me longer than they would have in Keynote because I was learning the tool. By deck 50 I was faster. By deck 100 the speed gain was significant. By deck 200 I make decks that would have been 4-hour projects in 60-90 minutes.

My understanding of which decks benefit from Gamma got sharper. Not all decks should be made in Gamma. The ones that work are content-heavy, structurally clear, where the visual treatment is supportive rather than central. The ones that don't are brand-led, design-conscious, or have specific layout requirements that templates don't accommodate.

My templates customization got tighter. The first 30 decks I used the defaults. By deck 80 I had a working theme that matched my brand. By 200 I have three themes for different client types and the brand consistency across decks is meaningfully better than it was.

What didn't get better with volume.

The "AI-generated" feel. Even after 200 decks, decks that I rush through still look like rushed Gamma decks. The tool gives a quality floor and a quality ceiling. The ceiling exists. Speed without thought produces visible patterns.

The collaboration friction. Editing decks with clients in real time is still rougher than I'd like. Most clients I work with end up requesting PDFs because the live-editing flow has too much friction for non-power-users.

Custom diagrams. Across 200 decks, the moments where I needed a specific custom diagram (a non-standard chart, a unique layout, an illustration that fit my exact specification) were the moments Gamma fought me hardest. I've gotten better at working around it. The constraint hasn't changed.

Patterns I see in my own usage.

About 70% of my decks now go through Gamma start to finish.

About 20% start in Gamma and get partially rebuilt elsewhere because the output doesn't fit.

About 10% I deliberately don't use Gamma for. High-stakes pitches, brand-sensitive work, decks for design-conscious audiences.

Decisions I've made.

Kept Gamma as the default. The volume of decks that benefit outweighs the volume that don't.

Kept Keynote installed and current. The 10% of decks that need it deserve the tool that handles them.

Stopped feeling guilty about either. There was a stretch in 2025 where I thought I should commit fully to AI tools because that was the direction the industry was going. I'm now comfortable being a hybrid user. The tool should fit the deck, not the other way around.

What I'd tell someone considering Gamma at this volume.

It pays back. Eventually. The first 30 decks won't show the speed gain that 200 decks will. If you're going to make 4 decks total, you don't need it. If you're going to make 100, you'll feel the difference.

Don't expect it to replace your design judgment. It replaces some of your design execution. Different things.

The AI improvement curve is real but slower than the marketing suggests. The version of Gamma I'm using now is materially better than the version I started with. The version 14 months from now will be better still. The trajectory matters more than any specific moment.

200 decks in. Will keep going.

Small B2B SaaS, $34k MRR, 4 of us. I've been doing all the marketing myself for two years and we have hit a ceiling that I'm pretty sure is just my time, not my strategy.

The dilemma. Hiring a generalist marketer who can do content, paid, email, and a bit of everything for $70-90k feels safer because we don't have the volume to justify a specialist. But every generalist I've talked to is mid at most things and good at none.

The other path is hiring a specialist in our biggest channel (organic/SEO/AEO right now) and just keeping me on everything else for another six months. That probably costs $90-120k for someone genuinely good.

The third path I keep dismissing is fractional. Bring in a fractional CMO 1-2 days a week, agency for the doing. Talked to two and it felt expensive for the actual output.

For folks who have hired their first marketer at this stage — what did you do, and what would you do differently. Specifically interested in hearing from anyone who hired the generalist and regretted it, or hired the specialist and was glad.

every viral reel has the same problem. the algorithm boosts it once, then it dies. you can't repurpose it as easily as IG keeps promising you can.

my workflow as of q1:

step 1 — i transcribe the reel using captions/whisper. takes 90 seconds.

step 2 — i clean up the transcript in a notion doc. break it into 6-8 bullet points. add a hook line at the top, a CTA at the bottom.

step 3 — i drop the doc into Gamma. use the AI to convert docs into slides feature. it spits out a 9-slide carousel within 30 seconds.

step 4 — i tweak the visuals (5-7 minutes), then export.

step 5 — i post the carousel within 4 days of the reel performing.

the carousel pulls 30-40% of the reel's reach as saves. the reel was the awareness vehicle. the carousel is the conversion vehicle. they work in pairs.

last quarter i averaged 2,800 saves per carousel built this way. organic-only. no boost.

people keep asking me how i make so much content. i don't. i make one piece of content and let two formats run it.