u/aditalreadytaken

been running a small renovation company in west yorkshire for about two and a half years. three-man crew. we do kitchens, bathrooms, some extensions. decent work, nothing flashy. close rate on quotes was hovering around 22 percent which felt low but i didnt know what good looked like.

met a plumber named dean at a builders merchant in shipley. he's been solo for nineteen years. asked him what his close rate was. he said about 65 percent. i asked how. he said "i stopped emailing quotes and started delivering them in person."

i thought he was joking. he wasnt.

he drives to the customers house, sits at their kitchen table, walks through the quote line by line, and answers questions on the spot. takes about twenty minutes. he said the close rate went from "about where yours is" to 65 in the first three months after he made the switch.

his logic was simple. an emailed quote gets compared on price because price is the only thing you can compare in a PDF. a quote delivered in person gets compared on trust because the person is sitting across from you and they can see you know what youre talking about. "they're not buying the quote. they're buying whether they'd be comfortable with me in their house for three weeks."

tried it for two months. drove to every quote. sat at the table. walked through it. our close rate went from 22 to 41 percent. the jobs we won were bigger because the conversation naturally surfaced things the customer wanted but hadnt mentioned in the initial brief.

its slower. costs petrol and time. but the maths works out dramatically in favour of showing up.

dean charges more than me and wins more than me. the difference isnt his plumbing. its his presence.

idk man, ive seen 4 people in this sub this month talking about moving to next.js because of "SEO" and they had like 30 users.

if your problem is "im not ranking on google" you dont need next.js, you need to be writing content. switch the stack at like 5k MAU when ssr genuinely starts mattering. before that its premature optimization, classic dev brain rot.

tell me im wrong. genuinely. because i feel like im taking crazy pills watching people migrate stacks before they have a real product.

Service business, 6 of us. Every new client gets a tailored onboarding deck — who we are, the project plan, key team members, communication protocols, success criteria. About 12 slides. Currently takes one of us 90-120 minutes to make per new client.

We onboard 4-7 new clients a month. That's 6-14 hours of repetitive deck work that adds zero strategic value.

I've started thinking about how to automate the bulk of it. The structure is identical client-to-client. Roughly 60% of the content is the same (who we are, our process, communications). 40% is custom (their project plan, their team, their success criteria).

Possible approaches.

A Gamma template with sections that we duplicate and partially overwrite. Faster than starting fresh but still 30-45 minutes per client.

A workflow where Claude takes a filled-in intake form and outputs a Markdown structure that we paste into Gamma to generate the deck. Theoretical 10-15 minutes per client if the chain works.

A more custom build using a templating tool plus a deck generator. Higher upfront cost, lower ongoing.

For folks who have automated their client-facing onboarding decks — what's your actual setup. How long does it really take per client end-to-end. And how often does the automation break in a way that costs you the time savings.

we have 14 people across 7 time zones. india, germany, brazil, japan, california, ny, london.

for two years we did a 'global sync' on tuesdays. 60 minutes. 4 of those minutes mattered. the rest was people repeating context for whoever joined late.

we killed it in january.

now we maintain a rolling weekly doc that everyone updates by their friday. someone in tokyo can read what someone in austin shipped that week without ever being on a call with them. the AI for documents flow we use turns the rolling doc into a shareable summary every monday morning.

meeting count dropped 71% on our team. delivery velocity went up. we measured.

i think the 'global sync' wasn't actually solving the time zone problem. it was solving the writing problem. nobody wanted to write things down. so we made everyone come to a meeting where they could speak the things they couldn't be bothered to type.

remote-first means writing-first. if you're not writing, you're not remote. you're just on zoom in your bedroom.