u/Proud-Bath-3731

quick story for the solo crowd. i run a small service business, just me. for the longest time my "website" was a single page i threw together that honestly looked like a side project, because it was one.

a few months ago i rebuilt it with an ai website builder over a weekend. nothing fancy, but it's clean, consistent, has a proper services page, some real testimonials, and it loads fast. maybe 8 hours total.

the part that surprised me was the change in how prospects talk to me. before, i'd get "is this just you?" and haggling on price. after, i've had two people ask about my "team" and nobody's blinked at the same rates i was almost embarrassed to charge before. the site didn't change what i deliver at all. it changed what people assumed about me before we even talked.

i'm not saying a nice site replaces good work, it doesn't. but as a solo operator, looking established is doing quiet work for me in every first impression. it's probably the cheapest credibility i've ever bought.

anyone else notice a clear before and after when you finally fixed your site? trying to figure out what else moves that perception.

Small service business, roughly eight months in. Leads have picked up and I'm sending more proposals than ever, which is a good problem. The bad part is I don't really have a business proposal template. Every one is copy-pasted from the last deal and lightly edited, so half of them still have the previous client's name buried somewhere, and the pricing section looks different every time.

I want to build one solid version I can reuse and stop reinventing it at 11pm the night before it's due.

What I have so far, roughly in order:
- Short recap of their problem in their own words
- What I'll actually deliver, in plain language
- Timeline
- Price, with two or three options
- A bit about me and past results

What I keep going back and forth on:
- Do you lead with price or bury it near the end? I've heard both.
- Options versus one flat number. When I give three tiers most people pick the middle, but a couple got confused and ghosted.
- How much "about me" is too much. Feels like nobody reads it but leaving it out feels naked.
- One page or a longer doc. My deals are usually a few thousand, not enterprise.

For those of you further along, what does your proposal actually look like now versus when you started? What did you cut that you thought mattered? Trying to build something I'll still use in a year instead of patching this mess again next week.

Classic trap: I used to spend a full weekend on the MVP site before I had a single user, then wonder why I burned out before launch. This round I got the site up in an afternoon, and I want to share both the win and the mistakes so it is actually useful.

The win: I got a clean, hosted, mobile-friendly page live in one sitting. I used Gamma for it since it turns a prompt into a hosted page, with the honest catch that it tops out at a simple one-pager, so I went in already knowing I would migrate if the project ever got real traction. For an MVP where the only real job of the site is to explain the thing and capture interest, that was exactly the right amount of effort. The weekend I saved went into talking to five potential users, which was worth infinitely more than pixel-perfect hero sections.

What I would do differently next time: 1. Write the copy before opening any builder. I let the tool generate placeholder text and then spent longer editing generic filler than I would have spent just writing it myself. Clear input, better output. 2. Resist the extra sections. These tools happily generate a features grid, a testimonials block, an FAQ, a pricing table. For an MVP I needed maybe two of those. More sections is more to maintain and more for a visitor to wade through. 3. Set up analytics and the email capture first, not last. The page is a measurement tool, not a portfolio piece. 4. Know the ceiling early. Most of these builders are made for a simple one-page site, so if the project gets traction you will migrate to something with more control. That was fine for an MVP as long as I went in expecting it.

The lesson: match the tool to the stage. An afternoon site for an unvalidated idea is the correct trade. Do not build the mansion before you know anyone wants to live there.

For your MVPs, do you build the site first or validate first, and has that order ever burned you?

For months I insisted on hand coding my marketing site because I am a developer and it felt wrong to use a builder. That pride cost me time I did not have. I finally caved, moved the whole marketing side to an AI website builder, and reclaimed roughly a full day a week. I put that day into user calls and SEO, and three months later crossed 800 dollars MRR with 47 paying customers. The site being nicer helped conversion a little, but the real win was just not spending my life on CSS. Sometimes the highest leverage move is admitting the thing you are good at is not where your time belongs. What did you stubbornly do yourself for too long?

I've got a talk coming up and I'm deciding whether to lean on Slides' presenter view with notes or just wing it. For people who present from Google Slides, is the notes/presenter setup reliable enough to trust live? Don't want it glitching on stage.

first one of these. five questions to a member doing real volume, answers lightly edited for length. this week, the ops lead whose quarter-of-numbers post started monday off.

what’s the setup? one master skeleton per client type, blank numbers version after the incident, brand theme locked, two seats.

what took longest to learn? that the tool’s first draft is a draft. the two decks we shipped without rewriting were the two that died. half an hour of human rewrite is in the budget for everything now.

what would you tell the you of six months ago? stop exporting to pptx by default. ask every client once, most say the link is fine, and the cleanup hour disappears.

what breaks most? fonts in export, same as everyone here apparently.

what’s next? automating the paste step through the api, the proposal pipeline post friday made it look closer than I thought.

next week’s spotlight: a teacher who ran a full semester on the free plan. suggest future subjects below, volume not required, interesting usage is the bar.

Need a simple tri-fold for a small business and I'm halfway through the canva brochure maker, but the fold guides are confusing me and I'm worried about panels not lining up. Anyone done a tri-fold in it that actually printed correctly?

Building in public and trying to cut the noise. Every week there's a new AI writing tool that's supposedly going to write my launch copy, my investor updates, my changelog, all of it. I've tried a pile and most got opened once and forgotten.

What actually survived in my workflow, being honest:

- first drafts of anything internal where nobody cares about polish
- turning my messy voice-note ramble into something a human can read
- changelog and update posts, where the structure is repetitive anyway

What didn't survive:

- anything that needed my actual opinion. It writes a confident average take, and my whole edge is not being average.
- landing copy. Every version sounded like every other SaaS page.

So the real question, not a listicle: what's still in your stack after a few months of real use, and what did you drop even though everyone raves about it? Trying to tell the tools that are real from the ones that are just good at launching.

Solo builder, first real MVP. I finally recorded a short demo of it because everyone says "just show the thing," but I've watched my own demo so many times I've lost all judgment on it.

The thing I can't tell from the inside:

- Is it obvious what the product does in the first fifteen seconds, or do I bury the point?
- Is the pace okay, or is it me clicking around while nothing happens?
- Does the actual useful moment land, or do I rush past it because it's obvious to me?

I know the trap. Founders make demos for people who already understand the product, and then real people watch and have no idea what they just saw. I'm almost certainly doing that and can't see it.

If a couple of you are up for watching it cold and telling me, in one sentence, what you think the product does, that alone would tell me whether the demo works. Doesn't need to be kind. I'd genuinely rather find out it's confusing now than after I put it in front of users.

For people who've shipped a good demo: what did you cut to make it land? Mine's currently too long and I know it.

i lost a proposal in march to someone i know charges more than me. mutual contact told me why: "their pitch just looked like a real company."

that stung because my actual work is better. but my proposal was a word doc exported to pdf with a logo slapped on it, and theirs walked the client through a story. same service, different packaging, they got a $9k engagement.

so i treated presenting like a skill instead of a chore and rebuilt how i pitch. what actually changed outcomes for me:

1. the deck is a narrative, not a menu. old version: "services, process, pricing, about me." new version: their problem in their words (from the discovery call), what it's costing them, the fix, proof, price. price comes last because context is what makes a number feel small.

2. one idea per slide. my old slides were dense because i was scared of seeming lightweight. dense reads as junior. sparse reads as confident.

3. i present it live instead of emailing it. even 15 minutes on a call. an emailed pdf gets skimmed on a phone in a lift. a walkthrough gets questions, and questions are buying signals.

4. i stopped hiding that i'm solo. one slide: "it's just me, here's why that's better for you." clients weren't put off by solo. they were put off by solo pretending to be an agency.

since april: 5 proposals presented this way, 3 closed, and the average deal is bigger because the price finally has a story around it. previous 6 months i was closing maybe 1 in 4.

design tools help at the margin but this is mostly a thinking change, which is why it's free.

what got you over the "i'm a builder not a presenter" hump? or are you still emailing pdfs and winning anyway, because i'd like to hear that side too.

Course creator, sell a couple of self-paced courses, list around 4,600, roughly $11k/month. I've been on Brevo for about a year, mostly because it was cheap and did transactional and marketing in one place. The price is still good. The day-to-day is wearing me down.
My specific gripe is the automation builder. Every time I want to change something simple I'm clicking through screens that feel built for someone managing a much bigger operation. I built a fairly basic post-purchase sequence and it took me twice as long as it should have, and editing it later means relearning where everything lives.
So I'm shopping for a Brevo alternative that does most of what I need without the maze. Things I've looked at: Kit, which seems far simpler but I'm not sure about the transactional side. MailerLite, which people keep calling the easy one. ActiveCampaign, which sounds powerful but possibly the same complexity problem in a different coat. One more I keep seeing recommended is Dreamlit, though I genuinely can't tell if it's simpler or if it's aimed at a more technical crowd than me.
For anyone who left Brevo specifically because the interface got exhausting, where did you go and did it actually feel simpler day to day? I don't need more features. I need to spend less time hunting for the button.

auth emails are documented to death. the part i keep wrestling with is how to send emails with Supabase for everything else: onboarding, "your export is ready," failed payment, notifications, none of which routes through Auth. the patterns i know of: pg_net plus a trigger calling the provider directly (minimal but fragile), database webhooks to a queue with a worker (sturdy, more infra), or an edge function per email type (the default, and how you end up with a pile of near-identical functions). i'm leaning toward the webhook-plus-worker approach but i don't love the infra overhead. the other route i'm weighing is a managed layer like dreamlit that reads the db and fires these without me standing up a worker, but i want to know what people actually run. for people past a handful of non-auth emails on Supabase: which pattern did you settle on, and what made you pick it?

my transactional emails worked great until they didn't, and the failures all traced to one thing: incomplete user rows.
the template said "hi {first_name}" and a chunk of users signed up via a flow that never collected a first name. so the merge broke, and depending on how i sent, it either errored out or shipped "hi ,".
what fixed it for me:
default every field before it hits the template. coalesce in the query, fallback in the code, belt and suspenders.
preview the email against real rows, not a clean test user, because your test user always has every field filled and hides exactly this bug.
validate at send time and skip or flag rows that can't render.
the sending was never my problem. the data shape was, every single time.
how are you handling incomplete rows in your transactional templates? this one keeps catching people.

easy to start, annoying to do right. easy start: hardcode a fetch to an email api inside an edge function, ship it. works for the first email. the annoying part shows up around email number 4, when the same boilerplate (auth, retry, template, joining in the user's data) is copy-pasted across functions and one silently fails because a user row had a null first_name and the template choked on it. what helped: keep the data join in one place and preview against real rows before trusting a flow, because the bug is almost always an incomplete user record, not the sending. dreamlit centralizes that join for me since it reads the row directly, which killed most of the null-field surprises. and keep transactional reputation separate from any marketing, so one bad campaign can't sink your receipts. the null-field thing is the one that keeps biting me. how are you handling incomplete user records in your transactional templates?

i was about to add a queue (pgmq or external) when a thread on the supabase discord pointed me at LISTEN/NOTIFY. used it for 4 months now. saved real complexity. also has limits worth knowing.
the pattern:
postgres has built-in pub/sub. one process executes notify channel_name, 'payload' and any process executing listen channel_name immediately receives the payload. zero infrastructure. it's postgres itself.
how i use it:
a trigger on a key table fires pg_notify when a row matching certain criteria gets inserted:
create or replace function notify_on_payment()
returns trigger as $$
begin
  if new.status = 'succeeded' then
perform pg_notify(
'payments',
jsonb_build_object(
'user_id', new.user_id,
'amount_cents', new.amount_cents,
'payment_id', new.id
)::text
);
  end if;
  return new;
end;
$$ language plpgsql;

create trigger payment_notify
  after insert or update on payments
  for each row execute function notify_on_payment();

a small worker (we run it as an edge function with a long-running connection) listens:
const conn = await new Client({ ...connectionConfig }).connect()
await conn.queryArray('LISTEN payments')

conn.connection.addEventListener('notification', async (msg) => {
  const payload = JSON.parse(msg.payload)
  await handlePayment(payload)
})

now the worker reacts to payments immediately. no polling. no queue.
what i use it for:
low-volume real-time-feeling reactions ("when X happens, do Y within a second")

cross-process coordination ("hey other workers, this thing changed, refresh your cache")

triggering edge functions immediately on row changes without going through database webhooks

what i learned the hard way:
1. it's at-most-once delivery. if the listening process is disconnected when the notify fires, it doesn't get queued. you miss the message. for anything where missed messages cause real damage, this is wrong.
mitigation: pair LISTEN/NOTIFY with a "process the row by id" pattern. the notify is just "hey, look at the new row"; the worker actually goes and reads the row, processes it idempotently, marks it done. if the notify is missed, a periodic scan catches the missed row.
2. payload size is limited (~8KB). you can't ship large data. ship an id, the listener fetches the row.
3. the listening connection has to be long-lived. edge functions don't naturally do this. you either need a long-running worker process (railway, fly, render) or you architect around the limit. i ended up doing the latter — supabase edge functions can have a Deno.serve that holds a connection open for the function lifetime, which is bounded but practical.
4. it doesn't scale to "many subscribers." if you have 100 workers all listening on the same channel, the notify fires to all 100. you usually want one of them to process; the others wasted work checking. for fan-out-of-one work, pgmq is better.
5. notify messages from inside a transaction are delivered only after commit. if your code does notify and then rolls back, the notify never fires. good for consistency. confusing if you're not expecting it.
when to use LISTEN/NOTIFY:
you want sub-second reactions to db changes

the volume is low-to-moderate (hundreds/sec, not thousands/sec)

it's fine to occasionally miss a notification if you have a fallback scan

you don't need fan-out to many independent consumers

when not to:
delivery must be guaranteed

you need persistence (queued work that survives restarts)

you have lots of consumers needing fan-out

it's the right tool for a specific shape of problem. it's the wrong tool for most production queues. but for the shape it fits, it's by far the simplest solution.
anyone using LISTEN/NOTIFY at high volume? curious about the practical scale limits.

it was about an architecture review my principal eng had run on monday where he had described one of my design choices as "interesting" four times in 20 minutes. interesting is not a technical category. i had been ruminating on it for two days.

so on wednesday night i wrote a slack message to him. one paragraph. polite. i asked if he could clarify what specifically about the choice he found interesting or whether the word was doing other work in the meeting.

it took me about three minutes to write. it took me nineteen minutes to send.

what i was doing in those nineteen minutes: rereading the message. wondering if it sounded passive aggressive. wondering if it sounded too direct. wondering if asking the question implied that i thought he meant something he didn't mean. wondering if not asking the question meant i'd absorb the "interesting" forever. composing a less direct version and then deleting it. composing a more direct version and then deleting it.

i sent the original version at 11:53. he responded thursday morning. he said "good question, i was hedging because i couldn't decide if i liked the approach, didn't mean anything beyond that, let's talk about it in our 1:1."

we talked about it in our 1:1. it was a productive conversation. he had three specific concerns about my design. i addressed two on the spot and we agreed on the third.

what i am writing about: those nineteen minutes. i don't think the men on my team spend nineteen minutes deciding whether to send a slack message asking for clarification. i think they hit send. and i think i've been so trained to anticipate how my words might land that i've lost some non-trivial portion of my evenings to wordcraft that men in equivalent roles are not doing.

i am still in the middle of figuring out what to do with this. i don't have a takeaway. just wanted to put the nineteen minutes somewhere visible.

B2B SaaS, 4 years old. We have two products. The legacy one (our original build) has 31 customers paying about $8.5k/month combined. The newer one (rebuilt from scratch on better tech) has 47 customers paying about $34k/month. The legacy is harder to maintain and we want to sunset it.

Customer breakdown on legacy.

8 customers have already shown interest in migrating to the new product.

14 use it heavily and would be unhappy about the change.

9 are mostly inactive (still paying, rarely logging in).

The decision to sunset is right. The communication is what I'm wrestling with.

Approaches I'm weighing.

12-month sunset notice. Migration support. Free migration to the new product. Clean shutdown at the end. The straightforward path.

Gradual price increase on the legacy that creates economic pressure to migrate without an explicit shutdown announcement. Indirect. Reads as manipulative if not framed well.

Combination: sunset announcement plus migration support plus a price increase for those who haven't migrated by month 6. Carrot and stick.

What I'm scared of.

Mass churn at the announcement. The legacy revenue is $8.5k/month. The bigger risk is the trust hit if the announcement reads as abandonment.

The 14 heavy users walking to a competitor rather than migrating. Their feedback was part of what built the new product. Losing them has a substantive cost beyond revenue.

The 9 inactive ones will churn at any signal. Expected.

For folks who have sunsetted a product or service line - how did you communicate, what timelines worked, and what was the churn at announcement versus at final shutdown. The migration mechanics I can figure out. The trust mechanics are what I don't know how to handle.

Been at this company since 2020. Fully remote the entire time. Got the email in March. They're calling it "Hybrid Plus" which is a phrase that should not exist. Four days in office, one day "flex remote."

Did the first week. Here's what it actually cost.

The drive is 28 miles each way. With morning traffic that's an hour and ten minutes. Evening traffic it's an hour and a half. Parking in the garage they recommend is $22 a day, which the company "is exploring options to subsidize," which means no. So that's $88 a week, $352 a month, $4,224 a year, money I did not have to spend two weeks ago.

Bought two pairs of office pants from the Banana Republic outlet on Sunday because I had three pairs left from 2019 and they no longer fit in the way pants are supposed to fit. $164.

The first day my badge didn't work and I waited in the lobby for 25 minutes while someone from facilities looked for the spare card. The second day I had a 9am meeting and got there at 9:11 because I underestimated the parking line. The third day I sat at a hot desk next to a woman who took a 90-minute video call about her divorce on speaker for some reason. The fourth day I gave up trying to do focus work and just did Slack.

My manager is in Chicago. Half my team is in Berlin. The work I'm supposed to be collaborating on in person is being done by people who are not in this building and have never been in this building.

I haven't taken the dog for a walk in five days. He sits by the door at 5:15 because thats when I used to come downstairs.

I've been fully remote for six years and I genuinely don't know how people did this every day.

Started a spreadsheet of remote-first companies hiring in my function. It's longer than I expected.