u/Miserable_Donut8718

My company put a few of us through presentation skills training last year and I've been going back and forth on whether it was worth it.

The useful parts were small and concrete. Stop reading the slide. Pause instead of saying "um." Look at one person per thought. Plant your feet. None of it was groundbreaking, but having someone film me and play it back was uncomfortable enough that it stuck.

The part I'm less sure about is whether I'd have gotten there anyway just by presenting more often. A lot of what improved was confidence, and confidence mostly came from reps, not from the classroom day.

So I'm curious what others have seen. Did formal training move the needle for you, or was it the volume of actually standing up and presenting? And if training did help, what specifically, so I know what to look for if I ever send my own team.

Bootstrapping a tiny tool and I'm at the stage where I need a landing page to collect emails before I build anything else. I don't want to pay a monthly fee for a marketing site before I have a single user, so I'm hunting for the best free AI website builder that can get me a clean one-pager.

What I actually need is boring:
- One headline, one subhead, a screenshot, an email capture.
- Custom domain if possible, or at least a domain that doesn't look like a demo.
- No hard export lock so I can move it later if the product takes off.
- Fast, because I want to spend my time on distribution, not fiddling.

I've tried a couple of free tiers already. One looked great but wouldn't let me point my own domain without upgrading, which kind of defeats the point for a launch page. Another was genuinely free but every template screamed "template."

For those of you who launched on $0, what free AI site builder did you actually keep using past week one, and where did the free tier bite you later? Trying to avoid rebuilding this three times.

The single highest-return thing I have done with AI is not a clever prompt. It is writing a good profile of myself once and putting it where the model reads it every time: custom instructions, a saved note, a project's memory, wherever your tool keeps context. Every answer after that is calibrated to me instead of to a generic average user.

Here is the template. Fill it in once, keep it under a page, update it when something changes.

```
ABOUT ME
- Who I am and what I do: {{role, field, level of expertise}}
- What I am usually trying to get done here: {{writing, deciding, learning, building, planning}}
- My knowledge level by area: {{e.g. strong on marketing, weak on code. Don't over-explain the first, don't assume the second}}

HOW I WANT YOU TO RESPOND
- Default length: {{short and direct / thorough when it matters}}
- Be willing to disagree with me and tell me when I am wrong. I prefer correction over agreement.
- When you are unsure or guessing, say so. Do not fill gaps with confident-sounding filler.
- Skip the intros and the "hope this helps" outros. Start with the answer.
- If my request is ambiguous, ask before assuming.

WHAT I AM OPTIMIZING FOR
- {{e.g. clarity over completeness, being challenged over being reassured, speed over polish}}

STYLE I DON'T WANT
- {{your pet peeves: buzzwords, emojis, hedging, whatever}}
```

Why it works: most weak answers come from the model guessing who you are and defaulting to the safest, most generic register. This removes the guessing. The two lines that change output quality the most are "be willing to disagree" and "say when you are guessing." The style section is what stops answers reading like a press release. Set it once and it compounds across every chat you have afterward.

What is in your profile that you would call non-negotiable? I am curious which lines other people found made the biggest difference.

Posting this as a real time update because this community actually gets what building from nothing feels like.

Three weeks ago I started a small tool on the side of my day job. Week one I did the classic thing and told myself I had to learn to code properly before I could launch anything real. I lost a whole week to tutorials and built basically nothing usable.

Week two I gave up on that and rebuilt the entire front end on a no code website builder. One landing page, a short explainer, and a simple email capture. It was live by the end of the weekend, which felt kind of ridiculous after the week I'd wasted trying to do it the "proper" way.

Then I did the scary part and actually posted it where people complain about the exact problem I'm solving. Woke up to my first real signups. Somewhere around a dozen over two days, plus one person who replied asking when a specific feature would land, which honestly meant more than the number.

What I got wrong: I spent hours on fonts and colors nobody mentioned once. Not a single early signup cared how it looked, they cared that the headline matched their problem.

What I got right: I shipped the promise and a way to raise your hand before I built the actual product.

Still very early, still figuring out if there's a real business here. Will post the next update when I've talked to a few of these people. For those further along, what did you wish you'd put on that first page?

I keep copying data between two tools by hand and it's mindless. What's the simplest no-code way to wire two apps together and automate it? Non-technical, so ease matters more than power.

Sharing a build because the fix was retrieval discipline, not a better model, and that surprised me.

The job: an agent that produces a first-draft deck for our solutions team from a customer's context. Early version let the model write the deck from its own head plus a short brief. It looked polished and it lied. It would assert a pricing tier we don't offer, cite a case study that doesn't exist, invent an integration. Confident, well-formatted, wrong. Useless for anything client-facing.

What actually worked:

1. Every factual slide has to be grounded. The agent retrieves from our internal knowledge base (product facts, real case studies, approved claims) and each claim carries the source chunk it came from. If there's no source, the slide can't assert it. The agent is allowed to say "no approved proof point for this" instead of filling the gap.

2. Split the retrieval from the writing. One step pulls and ranks the grounded facts, a second step writes the section using only those facts. When I let one call do both it happily wandered off the sources.

3. A cheap groundedness check before render. Every factual line gets traced back to a retrieved chunk, and anything unsupported gets flagged for a human rather than shipped.

For the render itself I used gamma's Generate API since it slots into the pipeline without much glue and the first-draft layout is genuinely presentable. Honest limitation: the credit ceiling is real (roughly fifty generations a month on the tier I was on), so a busy agent will hit it, and the card export doesn't give a clean editable PPTX, so anything the team hand-finishes goes elsewhere. The grounding work is what mattered; the render was the easy end.

The lesson I keep relearning: a generation agent's job is to arrange trusted facts, not to be the source of them. The moment it becomes the source, it hallucinates a very tidy deck.

Where are people putting the groundedness gate, before the write or after? And does anyone let the agent write ungrounded prose for the non-factual framing slides, or clamp the whole thing?

High school teacher, first year really leaning on NotebookLM for prep, and I'm still figuring out the workflow so I'd love to hear how others do it.

Right now my routine is one notebook per unit. I load the textbook chapter, a couple of articles, my old slides, and the standards doc. Then I ask it to draft a week of lessons mapped to those standards, with a warm-up, the core activity, and an exit question per day.

What works well: because it only pulls from what I gave it, the lessons actually match my curriculum instead of some generic internet version. When it references a concept I can click straight to the page in the textbook, which saves me flipping around.

What doesn't: the pacing is always off. It'll cram three days of material into one lesson because it has no sense of how long a real 50-minute class with actual teenagers takes. And the activities skew bland, lots of "discuss in pairs." I rewrite roughly half.

The trick that helped most was asking for a lesson outline first and correcting the pacing in chat before generating anything detailed. Generating full plans straight from sources gives you coverage, not a teachable week.

For teachers further along than me: do you keep everything in one notebook per unit, or split by week? And has anyone found a prompt that gives realistic pacing without hand-fixing it every time?

Electrical contracting. Grew from four guys to nine. Revenue nearly doubled.

Take-home went down.

Took me most of the year to see it. Growing meant a second van, another insurance policy, a bigger tool inventory, and me off the tools and into an office chair. And me on the tools was the most profitable thing in the business, by a distance.

So I replaced the highest-margin worker on the crew, which was me, with an admin job that generates no revenue, and I did this on purpose, because everyone says that's what growth looks like.

The nine-man version of this business makes less per job than the four-man version did. There's more slack, more mistakes, more re-dos, more time spent managing people instead of doing work.

I'm not shrinking back down, that's not the lesson. But I'd tell anyone about to make the jump: run the numbers on what you personally produce before you take yourself off the tools, because nobody does, and it's usually the biggest number in the business.

i run the engagement. i pitched it, i closed it, i architected the whole thing. i brought a junior guy along to the kickoff to learn, six months out of school, lovely, knows a fraction of what i do about any of it.

the client's team addressed him for the entire meeting. asked him the strategy questions. looked to him for the technical answers. at one point the client lead literally said "and what would you recommend we do here," to the junior, about a decision that is mine to make and that i had already made and that the junior did not know the answer to, so he looked at me, and i answered, and the client nodded at me briefly and then turned back to him for the follow-up.

the junior was mortified. he kept trying to redirect, "that's really Sarah's call," and it kept not landing, because the client had decided within the first two minutes who the grown-up in the room was, and it wasn't the woman who built the thing they were paying for.

i've decided i'm not going to contort myself to fix their assumption in real time anymore. i'm just going to note which clients can't figure out who's in charge, and factor it into whether i want to keep working with people whose first instinct is that the woman is the assistant. it's the only vote i actually get, and i'm going to start using it.

the real reason my account isn't growing isn't the algorithm. it's that i have a camera roll full of reels i never posted.

60-something of them. filmed, half-edited, then killed because the hook wasn't sharp enough or the lighting was off or i convinced myself it would flop. i tell people consistency matters and then i sit on a month of content because none of it cleared the bar in my own head.

the ones i did force out, the "good enough, whatever" ones, did fine. some did better than the stuff i agonized over. the perfectionism was never protecting quality, it was protecting me from finding out a reel might flop.

a flopped reel reaches a few hundred people who forget it in an hour. an unposted reel reaches zero, forever. i know this. i still do it.

trying to just post the backlog this week and sit with the discomfort. anyone else stuck in the drafts folder more than the feed?