u/WrongArmy8900

Genuine question for the BAs here who present to senior committees regularly, because I keep going back and forth and want to know how others have actually landed.

I've spent the last few weeks pulling together findings on a process that's been quietly bleeding money. It's data-heavy. Cycle times across four regions, cost-per-transaction trends, a correlation between one handoff and most of the rework. The analysis is solid. The question is the format for the findings presentation to the steering committee next week.

Option one is a live dashboard. Filterable, drill-down, they can poke at the regions themselves. It's honest, it's the real data, and it shows the depth of the work.

Option two is a static slide deck. I pick the cuts that matter, build the story, and the committee sees exactly what I want them to see in the order I want them to see it.

I've been burned both ways. Last year I brought a dashboard to a committee and lost the room inside five minutes. One director started filtering to his own region, ignored my actual finding, and the meeting became about his pet number instead of the decision I needed. The interactivity worked against me. But I've also built tidy decks that got dismissed as "too cooked," like I'd cherry-picked the slides, and they didn't trust it.

Where I'm leaning now is a deck for the story with the dashboard open in a tab as backup if someone challenges a number. But that feels like a hedge.

So for people who present data-heavy findings to steering committees: dashboard, slides, or some combination? When does interactivity help you and when does it hand the room to whoever wants to derail it?

Custom upholstery shop, small, two part-timers, going on eight years. I expected the money to be the hard part. Some months it is. But that's not the thing that got me.

The thing that got me is that I'm the only person who lies awake about it. My helpers are good people and they do the work and they go home, which is exactly right, that's the deal. But the deposit that didn't clear, the customer who's been waiting on a chair since March, the fabric order that's three weeks late, all of that lives in one head. Mine. Nobody hands that worry off at five o'clock.

I'm not complaining about my staff. I'm saying nobody warns you that ownership is a kind of loneliness. The buck stops being something you say and starts being something you feel in your stomach on a Sunday night.

I got through a bad stretch this spring mostly by finally telling another shop owner two towns over what it actually felt like, and she said "oh thank god, me too," and I nearly cried in a parking lot.

So I'll ask the room. For those of you further along: did the weight of being the only one who cares ever get lighter, or did you just get better at carrying it? Genuinely asking. Some weeks it's heavy.

i sell for a living, so i've read every list of presentation tips. less text per slide, use contrast, tell a story, the rule of three, all of it. fine advice. none of it moved my numbers.

the thing that did: i stopped presenting and started pausing. i'd make a claim, then shut up and let the prospect react, instead of plowing to the next slide to fill the silence.

turns out the silence is where they tell you what they actually care about. every tip about the deck is optimizing the part that matters least. the deck is a prop. the conversation around it is the sale.

best presentation advice i ever got was "the deck is not the pitch, you are." everything else is decoration. what's the one tip that actually changed something for you, not the ones from the listicles.

mid-size catering business in the southeast. ~$840k LTM. instagram is our primary marketing channel for enterprise leads.

we spent ~$4,800 in 2024 on staged food photography. beautiful shots. they got reach. they didn't convert.

this year we cut the staged shoots entirely and switched to behind-the-scenes content. results have been wild.

what we do now:

one of my line cooks films during prep on event days (vertical phone, 2 second clips of specific stations)

i edit together a 30-45 second reel showing the full timeline of an event prep

captions name the client (with permission), the event size, the menu theme

post 2-3 days after the event

the math:

2024 staged shoots: avg reach 4,400, avg saves 9, enterprise lead form fills per post: 0.3

2026 BTS reels: avg reach 2,100, avg saves 22, enterprise lead form fills per post: 1.8

BTS gets 6x the leads at half the reach. and it costs us almost nothing to make.

why it works:

enterprise buyers want to know if you can actually pull off the event. staged shoots show food. BTS shows operations.

the 90 minute window before guest arrival is the hardest part of catering. BTS proves you can run it.

the line cook's hands look real because they are. the staged shoots looked staged.

"you can see us at work" is a stronger trust signal than "look at this perfect plate"

what i won't do:

use trending audio (kills the production calm)

post too quickly (waiting 2-3 days makes the post feel curated not desperate)

show client faces without explicit permission (we've lost 0 clients to BTS posting because we ask first)

what's your "operations as marketing" content if you're in a service business.

Denver, 3 person AAA shop. Started solo 2022. Mid market clients in healthcare adjacent industries. Here is the cold rebuild.

Foundation layer:

• Airtable for client work databases. Clients can read it.
• Make.com over Zapier for new builds. Zapier locks you in too hard on per-task pricing.
• n8n self hosted for sensitive client workflows.

AI website builder tools:

• Webflow for marketing sites where SEO matters
• Lovable for app prototypes where the app is the deliverable
• Framer for landing pages where the design matters more than the database

3 tools because each is best at exactly one thing. Trying to use one for all three is how you ship mediocre work.

AI layer:

• Claude as default model in every workflow
• Claude Code for any scripting needed
• Nothing else as the "agent" layer. Agentic frameworks have failed me 3 times in production.

Client interface layer:

• Softr for client portals
• Gamma as our ai presentation tool for weekly updates, MBRs, QBRs
• Google docs for handoff documentation

Ops layer:

• Harvest for time
• Moxie for invoicing and contracts
• Google workspace for everything else

What I dropped:

• 3 chatbot tools that got outpaced by underlying model improvements
• 2 "AI agent" platforms that were brittle
• Any tool requiring a salesperson to onboard you

Total stack cost: ~$340/mo for a 3 person shop billing ~$32k/mo. I would have spent less and made more if I had started here.

What's in your stack that you wish you skipped.

bangalore. staff PM day job at a global cloud platform. side biz: B2B observability tool. 22 paying customers, ~$3,800 MRR.

every quarter i ship 4-6 new features to my side biz. each one starts with a customer request. each one needs a spec before i build. tested 4 ways to write that spec in 2025.

approach 1: write the spec myself from scratch. used this for years. takes me ~6 hours per spec. cost is ~6 hours of weekend time per feature.

approach 2: write a rough spec, then have claude refine it. takes me ~4 hours of writing + 30 min of claude refinement. cost is ~4.5 hours per feature.

approach 3: dump customer request + my notes into claude, have it draft the spec, i edit. takes me ~90 min total. cost is ~90 min per feature.

approach 4: use an ai product spec generator (built in Gamma) that pulls structured inputs (customer quotes, my notes, similar past features) and produces a spec link i edit. takes me ~30 min total. cost is ~30 min per feature.

what i tracked. quality of the output. how often i had to revise after starting to build. how often the spec missed something the customer actually wanted.

approach 1 quality: high. revision rate: ~14%. spec misses: ~8%. approach 2 quality: high. revision rate: ~16%. spec misses: ~7%. approach 3 quality: medium. revision rate: ~28%. spec misses: ~22%. approach 4 quality: high. revision rate: ~12%. spec misses: ~6%.

approach 4 (the structured workflow) produced the highest quality at the lowest time cost. this surprised me. i expected the manual approaches to beat the structured one.

why the structured workflow won.

the structured workflow forced me to fill in 6 specific fields before generating the spec. customer quote (verbatim). their use case. their current workaround. what they said success would look like. similar past features. potential breaking changes. by filling these fields i was doing the upfront thinking i used to skip.

approach 3 (just dump and edit) felt fast but i was skipping the upfront thinking. the AI filled in the gaps with assumptions. the assumptions were wrong ~22% of the time. revision was expensive.

approach 4 took the same 30 min approach 3 took, but the 30 min was concentrated on filling in the structured fields. the AI then had real inputs to work from. output quality jumped.

the math.

across 6 features per quarter that is 24 specs per year. approach 1 (manual) is ~144 hours per year. approach 4 (structured workflow) is ~12 hours per year. ~132 hours saved. roughly 3-4 weeks of side biz capacity.

what i did with the saved capacity. shipped 2 additional features in 2025 that i would not have had time for. one of those features added 4 customers. ~$680/yr of additional revenue. 4-week ROI on the workflow build.

what i learned about AI-assisted product work.

the AI is not the productivity gain. the structure that forces upstream thinking is the productivity gain. AI without structure produces fast garbage. AI with structure produces fast high-quality output. invest the time in the structure.

if you are a PM (especially solo or side) and writing specs is your bottleneck. build a structured workflow. one weekend of work. pays back in weeks.

[ Removed by Reddit on account of violating the content policy. ]

i build small side projects for fun. wrote previously about my woodworking workshop tool getting 11 paying users by week 5. i started an IG account for it in april mostly because everyone said i should.

posted once a week for 26 weeks. mostly workshop photos. some short video clips of the tool working. occasional behind the scenes content of how i was building features.

results. 280 followers in 6 months. zero signups directly attributed to IG. zero meaningful DMs about the product. one comment from someone who wanted to know what brand my saw was.

i was going to delete the account in october. then i sat down to look at why i had started it in the first place.

i started it because everyone said you have to be on every channel. i kept it up because i felt like i was supposed to. i never actually believed it would work for a tool sold to hobbyist woodworkers in a niche community that does not really hang out on IG.

i did not delete the account. i changed my posting cadence to once a month. just enough to keep it alive. spent the freed up weekly time on the actual community my customers are in (a specific woodworking forum) where i was getting 2 to 3 signups a week without trying.

the channel that does not work for your audience is not a problem to solve. it is a channel that does not work for your audience. let it be small. go where your audience is.