Soloop

I designed almost exactly this for my own company — departments instead of loose agents, each with a manager, shared memory, daily reviews. The one place I landed differently is approval. I started approval-first and moved to "execute and report, stop only at what's irreversible", because the approval queue became the bottleneck it was meant to remove. As a solo founder my scarcest resource is attention, and a system that asks me twelve times a day is a slower version of doing it myself. Curious how you're drawing that line — is "requires approval" a fixed category, or does it widen as the founder builds trust?

rodrigo_baigorria · Imported from Product Hunt

I have built my site already. Can I use your product CMO to put together a marketing plan, find and get users and sell? Or is your solution only usable from the onset of an idea?

brent_kilner · Imported from Product Hunt

Congrats on the launch.. Is there a level of autonomy planned to baked in? Also is the product only meant for solo folks - or in future can also accomodate co founders. Last connected issue is that our calendars, emails and usually slack - are filled with discussions and clutter - could those be connected and baked into the plan. Last but not the least -- can real product signals from say feedback widgets, posthog, newrelic/sentry, langfuse traces etc automatically be parsed to create and suggest product stories (sorry having been a PM for so many years - this is something I keep thinking about, product discovery). Have signed up will try to take this out for a spin soon :-)

himanshu_garg · Imported from Product Hunt

Approval-first is the hill I’ve been dying on all year, so congrats, you built my argument. I’m a solo founder running 25 AI marketing agents, and the two rules that keep that sane are exactly your premise: agents produce drafts, not actions, and when they’re missing information they ask instead of inventing. (Mine once invented an employee named Teri and assigned her support tickets. Approval-first is why Teri lasted one document review instead of reaching a customer.) So here’s the question I’d ask before subscribing, because it’s where I’ve watched this model strain: how do you fight approval fatigue? At some volume, “approve” stops being a decision and becomes a reflex, and a human rubber-stamping fifty prompts a day is arguably worse than no gate at all, because now there’s an audit trail saying someone reviewed it. Do you do anything structural to keep approvals meaningful: batching, risk-tiering, surfacing only diffs, anything? Genuinely asking. This is the design problem I think decides whether approval-first scales or becomes approval theater.

tiffany_trboyevich · Imported from Product Hunt