u/According_Plane_3396

hired a 54-year-old electrician who'd been out of work for eight months. he's the best employee i've ever had.

his name is gary. found him on a local facebook group in november. he'd posted looking for work. 54, certified, 28 years experience, laid off when his previous employer closed.

the post had three responses. all from people wishing him luck. nobody offering work.

i called him mostly because i felt for the guy. we met at a costa in stockport. he showed up in a pressed shirt, ten minutes early, with a printed copy of his certifications in a clear folder.

he started the next week. first day he rewired a consumer unit in about half the time i'd budgeted for it. the client called me that evening to say "that electrician is the most professional tradesman who has ever been in my house."

seven months later he's my lead on every job. clients request him specifically. he mentors the younger lads on site without being asked. he shows up at 7:45 every morning and i have never once had to follow up on anything he's said he would do.

he told me over a coffee last month that the eight months of unemployment nearly broke him. that he'd started to think his age was the problem and nobody would hire him again.

the hiring market is obsessed with young and hungry. gary is neither young nor particularly hungry in the way startup culture means it. he is steady and thorough and experienced and completely reliable and those qualities are worth more than every 23-year-old hustler combined.

i got lucky. he got unlucky. the luck ran in both directions the day i called.

reddit.com

Our customer implementation went from 6 weeks to 2 weeks. Here's the stack that did it.

Implementation was killing us. CS team was bottlenecked on walking every customer through the same setup steps over and over.

We rebuilt implementation around self-serve content with human support only for complex stuff.

The stack:

  • Notion for the overall implementation checklist and shared timeline
  • Trupeer for step-by-step setup guides customers can follow on their own
  • Loom for context and "why we do things this way" explanations
  • Slack Connect for async questions
  • Calendly for booking help sessions when they get stuck

The Trupeer guides handle 80% of what used to be live calls. Customer follows along, clicks through their own setup, and we're there if they need us.

Implementation time: 6 weeks → 2 weeks. CS team capacity: 8 accounts each → 20 accounts each.

Not magic. Just shifted effort from live delivery to reusable content.

reddit.com
u/According_Plane_3396 — 12 days ago

I do industry talks regularly. Conference keynotes, smaller meetups, internal speaking gigs at portfolio companies. Probably 32-38 talks last year.

Each talk needs custom slides because the audience is different. I have a master narrative deck I pull from but every talk gets specific examples, specific framing for the audience, and updated stats. The work per talk averages 4-6 hours, almost all of it slide assembly rather than thinking.

Tried tools.

Gamma. Tested it for 6 talks last quarter. Two went well. Three were okay. One was a problem because I wanted custom diagrams that Gamma didn't render the way I needed and I had to fall back to Keynote two days before the talk. The speed when it works is real. The fail mode when it doesn't fit is expensive at the wrong time.

Pitch. Slower workflow. More predictable output. The version I'd default to if I were making one big high-stakes deck a quarter rather than 30 medium-stakes decks a year.

Beautiful.ai. Tried it 3 years ago, didn't fit my style. Probably worth retrying given how the tool has evolved.

Keynote with a master template. The most reliable. The slowest. What I default to when I cannot afford a tool failure.

What I'm trying to land on.

A workflow where Gamma (or similar) handles the standard structural slides quickly, and I keep a Keynote escape hatch for the slides that need custom treatment. The current version of this is working in theory. In practice I keep ending up either fully in one tool or jumping awkwardly between them.

For other speakers running this volume - what does your actual production workflow look like. Specifically how do you handle the per-talk customization without each talk eating an evening, and which tools have actually held up across 20+ talks.

reddit.com
u/According_Plane_3396 — 20 days ago

daily standup was 15 minutes. 6 people. 90 minutes/day of team time.

i killed it in march. replaced it with a shared doc. 4 bullets per person. yesterday, today, blockers, asks. due by 10am local.

nobody complained. nobody asked for the meeting back. the AI for documents flow we use makes a weekly digest from the daily docs.

90 minutes/day saved across the team. that's 7.5 hours/week. that's a full extra workday.

the meeting wasn't keeping us aligned. the doc is.

reddit.com
u/According_Plane_3396 — 23 days ago