u/Live-Purpose-641

I make small batch hot sauces. Been selling at farmers markets and a few local shops for about three years. A regional grocery chain's buyer agreed to a 30 minute meeting about getting on their shelves. This is the biggest thing that's happened to the business and I'm terrified I'll blow it by rambling.

I've never presented to anyone in a boardroom. My instinct is to bring bottles and just let them taste, but I feel like they'll expect me to actually walk them through something. Numbers, margins, how I'd handle their volume without falling apart.

For those who've pitched a wholesale or retail buyer, how do you make a good presentation that respects their time? Do they want slides, a one pager, or just samples and honest answers? What made a buyer say yes to you, and what made one check out early? I'd genuinely rather learn from your near misses than find out the hard way in the room.

Writing this up because giving an agent a "make a deck" tool sounds trivial and then falls over in production in ways nobody warns you about. This is the setup that finally held.

The job: an agent that, at the end of a research task, produces a pitch deck the user can open. My first version let the agent call a generation API directly with whatever it wanted. It worked in the demo and was a coin flip in production, because the agent would pass a bloated prompt, the API would occasionally time out or return a job that never completed, and there was no graceful path when it did.

What fixed it was treating the deck step as a properly specified tool, not a free-form call:

1. The tool takes a strict schema, not prose. Title, audience, and an array of sections each with a headline and up to three bullets. The agent has to produce that structure, which forces it to decide content before anything renders. Half the garbage output was the agent being allowed to ramble into the prompt.

2. The tool call is async and guarded. It kicks off the generation, polls with a max-attempts ceiling, and if the job fails or times out it does not throw the whole run away.

3. There is a deterministic fallback. If the API fails or the credit ceiling is hit, the same structured outline renders through a plain HTML-to-PDF template instead. Uglier, but the user always gets an artifact. An agent that sometimes produces nothing is worse than one that always produces something plain.

For the primary render I used gamma's API because it slots in without much glue, but the honest limitation is exactly why the fallback exists: the credit pool is small, roughly fifty generations a month on the tier I was on, so a busy agent will hit the ceiling and you need a path for when it does. The fallback is not optional in production.

The general lesson: a generation API is a tool with a schema and a failure mode, not a magic final step. Specify the input, guard the async, and always have a dumber path.

Where do you draw the line on tool schemas for agents, tight and structured, or loose and let the model decide? And does anyone let a generation step run without a fallback in production?

I've tried prettier designs and it didn't move my saves or swipes much. For people who consistently make engaging carousel posts for social media, what's the real lever - the first-slide hook, the design, or the topic choice?

I've never touched the add-ons menu and I suspect I'm missing out. For people who use Google Slides heavily, which add-ons genuinely save time versus being gimmicks? Trying to speed up how I build decks.

Prepping launch assets as a solo with zero design skill, I bounced between gamma and canva for two weeks trying to figure out which one to commit to. Turns out the honest answer was both, for different jobs.

Where gamma earned its place: the demo deck and a quick one-pager. I pasted my messy notes and got a structured first draft in a few minutes instead of staring at blank slides all evening. Fair warning if you need a real .pptx to hand someone, the export got janky on me, my charts flattened into images and a couple of layouts shifted, so I stopped exporting and just shared the link.

Where canva won: the actual social graphics and the app store screenshots. Anything that needed pixel-level control, exact brand colors, one-off sizes. Gamma's card format is fast but it's not built for fiddly single graphics.

So my launch stack ended up being gamma for the deck and the doc, canva for the promo images. Neither replaced the other and I stopped trying to force it.

Anyone else run both, or did you find one tool that genuinely did the whole launch kit? Curious what people are shipping launches with these days.

Small remodeling outfit. Me and three guys.

Finished a kitchen in April. Good work. Walked the whole thing with them, they were happy, they signed off. Final invoice $14,200.

Then nothing. Two months of nothing. Polite emails, then less polite emails, then calls, then a text that got read and not answered.

Everyone says take them to court. And I keep nodding and going home and not doing it, and I want to be honest about why.

It's a week of my life I don't have. It's lawyer money spent to chase money I'm already owed, which feels insane. And there's a version where I win and they still don't pay, and I've spent $3k to get a piece of paper that says I'm right.

Meanwhile the $14k is the difference between me being fine this quarter and not being fine.

What I actually want to know from people who've been here:

Did small claims work, or did you win and still not get paid? Is a mechanics lien worth it at this size, and does it make them pay or just make them dig in? And is there a move before the legal stuff that actually works, or is the polite-email phase just theater?

Never been stiffed this badly and I don't want to handle it stupidly.

i've been at this company eleven months and i think i've heard the phrase "growth mindset" maybe sixty times. all from managers. all directed at women. there is a man on my team who has gotten the same architecture decision wrong three times in a row and nobody has asked him to grow his mindset about it.

my latest skip-level review said i should "adopt more of a growth mindset around feedback." what feedback. when. from whom. obviously not in the review because it would be too direct.

the men in this org get told they are "high performers." the women get told they are "developing." we are all the same level. we are doing the same work.

i think the phrase "growth mindset" is now what "abrasive" was ten years ago. it is the new container for whatever vague gendered observation a manager wants to hold against you without doing the work of actually saying it.

anyway. one of the things i am growing is my tolerance for taking phone calls in the parking lot to vent to my friend who left tech last year. she keeps saying "you'll get there." i don't know what that means. i don't think she does either.

I started writing down things I learned from cases. Not the textbook facts. The stuff between the lines.

Entries like: "Patient presented with X but the actual reason she came was because she was scared it was cancer. Treating the condition is one thing. Addressing the fear is another. Spent 5 minutes on fear. She left more relieved than any medication could make her."

Or: "Missed a diagnosis because I anchored on the first symptom. Patient came with headache, I went straight to migraine workup. Turned out to be hypertensive crisis. Lesson: always check vitals before assuming."

Or: "Family wanted to continue aggressive treatment. Patient didn't. She told me privately she wants to go home. Navigating family wishes versus patient autonomy is the hardest part of this job."

This journal is the most valuable educational tool I own. More than any textbook. Because textbooks teach you medicine. The journal teaches you about being a doctor. Those are different things.

I re-read entries from my first year sometimes. The mistakes I made. The moments that confused me. Many of them are clear now. Some still aren't.

If you're a junior doctor or medical student, start this journal now. Write the things you can't share in case presentations or department meetings. The confusions, the emotions, the ethical grey areas, the moments that made you feel something. Those entries will be more valuable to your growth than any MCQ you ever solve.