Soloop - Approval-first Agent OS for solo founders

@brent_kilner Spot on. You’ve highlighted a critical transition phase. Right now, our core focus is taking users from 0 to 1 (ideation). However, scaling from 1 to 100—structuring a GTM plan, driving traffic, and optimizing acquisition for an existing site—is exactly where we are heading next.

We are actively building the infrastructure to onboard existing products for this exact purpose. Since you are facing this bottleneck now, I’d love to connect and hear more about your current site to ensure what we're building solves your specific growth hurdles.

@brent_kilner Thanks for asking! It’s not available yet, but we’re shipping support for existing products within a week. Then the CMO can build your marketing plan, find users, and help sell what you’ve built.

@himanshu_garg Love these questions—this is exactly the kind of PM-level thinking that makes building this fun.

Quick takes on each:

Autonomy: We're building toward "human sets the direction, AI runs the execution." The bar for when something needs your approval will get smarter over time, but you always have final say. Full autonomy without human oversight isn't the goal—reduced decision fatigue is.

Co-founders: Right now we're laser-focused on solo founders (that's where the pain is sharpest), but multi-person teams are definitely on the roadmap. The handoff and coordination problems get even more interesting with 2-3 people.

Calendar / email / Slack integrations: 100% on the list. The whole point is that your company's context shouldn't live only inside Soloop—it should pull from wherever the work actually happens.

Product signals → product discovery: Okay, this one is the most exciting to me. The idea that real user data (feedback, analytics, error traces) could feed directly into the roadmap and suggest what to build next… that's the good stuff. Our product team has been obsessing over this exact thing.

Really stoked you signed up—would love to hear what you think once you've taken it for a spin. PMs are our favorite users to talk to, no bias at all 😄

@sabit_ali 😂😂

@qiwap Thank you so much for taking the time to try Soloop and write all of this!
It honestly helps a lot. You pinpointed something that made sense in our heads, but wasn’t clear enough in the product.

Soloop is built around several agents working together to keep your company moving. The CEO is your home base. You talk through the direction there, and once it’s clear, the CEO turns that conversation into concrete tasks for the Analyst, CTO, and CMO. The Analyst researches the market and users, the CTO builds and ships, and the CMO finds users and gathers feedback. You review and approve each task before it runs.

If you’re ever unsure what to do next, just return to the CEO page and ask. When another role finishes a task or needs your approval, you’ll see a red dot next to that role in the left sidebar.

We really appreciate you calling this out. We’ll make the guidance simpler and clearer so the path forward feels obvious next time. Thank you so much!!🚀

@qiwap Great question, and honestly this is such useful feedback—thank you for taking the time to write this out.

You're totally right that the journey from "talking to an agent" to "shit gets built" isn't clear enough right now. We think about this a lot because one of the core problems we're solving is founders getting stuck mid-build and losing flow.

Here's how it actually works today:

Phase 1 — Refine the idea. This is where you are right now with the CEO agent. You're not just brainstorming—you're pressure-testing the idea until it's sharp enough to execute on. Two agents do most of the heavy lifting here:

• CEO agent breaks your idea down into concrete, actionable tasks and pushes on feasibility. It's the "okay, but how do we actually do this by Friday?" voice.

• Analyst agent is the outside perspective—competitive landscape, gaps you might be missing, opportunities you haven't spotted. The person who'd ask "why hasn't anyone done this yet?" in a good way.

Phase 2 — Actually build it. Once the idea is solid enough, that's where the handoffs happen. The CEO doesn't just keep talking—it kicks off work with CTO and CMO agents who take the plan and start executing. You're not manually switching between agents; the system moves the work forward and brings you back in when a decision is needed.

The feature that ties this all together is called "What's Next." Instead of you figuring out what to do with each agent, the AI proactively suggests the next step—who should work on what, what needs your approval, what's ready to move forward. You stay in flow, the AI handles the transitions.

That said, you're 100% right that we need to make this journey way more obvious from the start. New users shouldn't have to figure out the value—they should feel it within the first few minutes. We're actively working on making this clearer, and your feedback is exactly the kind of thing that helps.

Would love to hear more about what you expected to happen vs. what actually happened. Super useful for us.

@charlenechen_123 Thank you so much, this really means a lot! We believe agents will keep gaining the skills founders need, and we’re all in on helping every solo founder turn an idea into revenue 🚀

@agilek Yep, we do use our own agents to help with the writing and the post. :) We’re a small team and simply don’t have enough hands to do everything manually. It’s also a great way to dogfood Soloop. We still review and approve everything ourselves, and this is exactly how we keep improving our agents’ skills.

@harry_douglas Thanks for flagging this, and I’m really sorry that was your first experience with Soloop. About nine hours ago, a spike in traffic caused roughly an hour of downtime and a few related issues. Everything is back up and running now.

We’d love for you to give Soloop another try. Thanks so much for bearing with us!

@tiffany_trboyevich OK. "Approval theater" is such a perfect way to put it—and you're exactly right that it's worse than no gate at all because it gives you a false sense of security. We've had so many internal debates about this.

Here's what we're working on structurally to fight it:

Risk-tiering first. Not every approval is equal. A copy tweak on a landing page? Low stakes, batch it up and show you the diffs once a day. A pricing change or a new feature direction? High stakes, surface it immediately with full context. The goal is that your attention only goes to decisions that actually need your judgment.

Diff-only approvals. You shouldn't have to re-read a whole document to approve one changed paragraph. We show you what moved, why it moved, and let you say yes/no in seconds.

Batching by default. The default mode isn't "ping me for everything"—it's "here's everything that happened since you last checked, organized by what needs your call." You set the rhythm, not the AI.

That said—this is still the hardest design problem we're working on, and we haven't cracked it perfectly. The line between "meaningful approval" and "rubber stamping" is thinner than people think, and it moves as you scale.

Honestly, I'd love to swap notes with you more on this—someone running 25 agents has way more battle scars than we do. Want to chat sometime?