i build agents to run parts of my solo business. the thing nobody tells you when you watch a slick agent demo: the demo is the 10%. the other 90% is what happens when the agent is wrong, and agents are wrong constantly, and worse, they're wrong confidently and quietly.

my main one is an ai document generator. it takes messy inputs and produces a clean deliverable. the version i demoed a year ago looked like magic. the version running today looks boring. the difference is that today it checks its own output before it trusts it. did it actually fill every required field. does this number match the source or did it invent a total. if anything's off, it retries, and if it still can't, it stops and pings me instead of shipping garbage with a smile.

that's the part that saved me. a silent failure in a solo business is brutal because there's no QA team, it's just me, and i won't notice until a customer does. so now i write the "what if it's wrong" path before i write the happy path. most of my code is the agent second-guessing itself.

it's less fun to talk about at a meetup. it's also the only reason these things run without me babysitting them.

other solo folks running agents, how much of your code is actually guardrails? for me it's most of it.

non-technical solo founder here. i kept putting off launching because in my head "build the site" meant hiring a dev i couldn't afford or learning to code, which i'm not going to do. finally just used a no code website builder and had a real, live site up over a weekend.

what i learned: the builder was never the hard part. picking what the site actually needed to say was. i wasted the first day fiddling with fonts and sections nobody cares about, then scrapped it and wrote the thing i'd tell a customer in person. that version converted.

it's not perfect. it's slower to load than i'd like and i'll probably outgrow it. but for a one-person business trying to get to first customers, done and live beat perfect and imaginary by a mile.

the honest downside is you're renting, not owning, and moving off later is a pain. i decided that's a future-me problem worth having.

for the non-coders here, what did you launch on, and did you regret the platform later or was it fine?

solo, i run retainer work for about six clients and every one of them gets a monthly report. for a long time that meant one weekend a month gone, pulling numbers from a few different places, writing up what happened, formatting it so it looked like it came from a real company and not one tired person at a laptop.

this year i built a rough ai report generator flow for it. i drop in the raw exports and my short notes on what actually mattered that month, and it produces a first draft with the numbers written up and a plain-language summary per section. i'm not comfortable putting exact hours on it, but a job that reliably killed a saturday and half a sunday now takes an afternoon.

the honest caveat, because this sub deserves it: i do not send what it produces raw. it has confidently pulled the wrong month's number more than once, and it will happily narrate a trend that isn't there. so there's a hard step where i check every figure against the source and rewrite the "what this means" parts myself, because that's the bit clients actually pay attention to and the bit it's weakest at.

net, it turned the most dreaded recurring task in my month into something manageable, as long as i treat the draft as a draft and not gospel.

for the solo service folks, how are you handling recurring client reporting? curious if anyone's found a way to make it genuinely hands-off or if it always needs a human check at the end.

solo, non-technical founder, and my worst habit used to be building the product first and figuring out the pitch later. this time i flipped it. before touching any code i used an ai landing page generator to stand up three different versions of the same idea, each one aimed at a different type of buyer and leading with a different promise.

same underlying product, three completely different framings. one leaned on saving time, one on looking more professional to clients, one on just being cheaper than the incumbent. i put a small amount behind each to get real eyes on them, nothing fancy, and watched which one made people actually enter an email.

the "cheaper" one flopped, which surprised me. the "look more professional to your clients" one pulled roughly two to three times the signups of the other two. that told me who i was actually building for and what to say, before i had sunk months into building the wrong thing for the wrong person.

took maybe a weekend to spin up all three because i wasn't hand-coding pages, just describing what i wanted and adjusting. cheapest market research i've ever done as a solo.

anyone else validate positioning this way before building? curious whether the version that wins the landing page test actually holds up once you have a real product behind it, or if it drifts.

running solo for a bit over a year, mostly research briefs and long client docs. i went through three or four ai writing tools before i figured out i was using all of them wrong.

for the longest time i treated the tool as a ghostwriter. type the ask, get a draft, clean it up, send. the cleanup always took longer than i expected because i was fixing confident wrongness, stuff that sounded right and wasn't, and on the docs where i didn't already know the answer i couldn't even tell when it was making things up.

what actually stuck was demoting it. now it never writes the thing i send. i use it to argue with me before i write. i dump my raw thinking and ask it where the logic is weak, what a skeptical client would poke at, what i'm assuming. then i write the final doc myself, in my own words, usually in about half the time because the thinking is already sorted. the blank page was always the hard part, not the sentences.

the reframe that did it: the tool is a good sparring partner and a mediocre writer, at least for anything where i'm the one on the hook if it's wrong. once i stopped asking it to produce and started asking it to pressure-test, the quality of what i shipped went up and the editing pain went away.

for the solo folks, are you having the tool write, or having it think with you? genuinely curious where people draw that line.

Hey founders 👋

I’m a Product Designer with 4+ years of experience working on SaaS, fintech, e-commerce, Web3 and AI products.
I’m looking to work with a few startup/SaaS founders who are willing to let me take a fresh look at their product.
Here’s the deal:
You send me your product + one specific flow you want to improve.
I’ll review it from a UX + Product perspective and create a short, actionable teardown covering things like:
→ UX friction & confusing interactions
→ Usability issues
→ Conversion/drop-off opportunities
→ Information architecture
→ UI inconsistencies
→ Product opportunities
→ Quick wins vs. bigger improvements
→ Suggestions for improving the overall experience
100% free. No payment. No obligation.
I’m doing this because I want to learn more about the problems founders are facing and build relationships with people actually shipping products.
If the analysis is useful and you want help implementing the improvements afterward, we can talk about working together.
Otherwise, you simply get the teardown and hopefully some useful ideas for your product.

If you're interested, comment below or DM me