Crewdle AI

Very interesting for a new product, some onboarding and UI work could help make this a gem.

I love the idea. This sounds similar to invideo Agent One for video production, correct?

Hey - Congrats on what looks like a strong launch. The subscription sprawl angle really resonates. This is something that has annoyed me for a while too, especially when you end up with a bunch of AI tools that are useful in theory, but not used enough to justify another monthly subscription.So I can definitely see the value potential here for small businesses. One quick question: when someone signs up, do they usually know what they want to delegate first, or do you need to guide them toward the right first use case? With AI tools I often feel the harder part isn’t access, it’s knowing what work should actually be handed off first.

"Stop juggling five AI subscriptions" hits hard. I'm running 4 right now and the monthly bill compounds quickly. Pay-as-you-go is the right pricing model for this category.Curious how you handle the model-switching cost, when I move from Claude to GPT in a workflow, does Crewdle abstract that or do I manage it?

The pay-as-you-go model is what actually sets this apart. I think Thomas's point about a flat subscription pressuring owners to justify the cost every month names a tax most small businesses never articulate. And $20–40 is a believable number, which lands better than a flashy one. One question on the shared context: each component keeps its own memory but can share knowledge. When Forge builds an automation that depends on what Create produced, does the user have to pass that context between crew members manually, or do they find each other's outputs on their own?

How do you handle context between models? Is there a source of truth where I can store all instructions and reference documents/knowledge base?

I like the usage based pricing model. The subscription fatigue is real, especially for small businesses. Have you found your customers actually replace their existing subscriptions with Crewdle AI ? Does it become an additional tool in their workflow?

The "stop juggling five AI subscriptions" framing is relatable. most small teams are paying for separate chat, agent, content, and automation tools that barely talk to each other. honest question though, when you bundle everything into one platform, how do you keep each piece from being a watered down version of the standalone tools? that's usually where all-in-one platforms struggle. the breadth is nice but depth is what keeps people from churning back to point solutions.

Consolidating AI tool access into a single billing and auth layer is genuinely hard. The context isolation problem alone gets messy when users switch tools. We've dealt with similar multiplexing challenges routing between different model providers. How do you handle session state when a user's workflow spans multiple tools with different context windows?

Solid concept. How's the billing handled when one month suddenly spikes compared to others?

The subscription consolidation angle makes sense on paper, but I'd push back on the "one platform for everything" promise a bit. Every all-in-one tool I've used covers ~80% of each individual tool's functionality - and the 20% gap is usually the exact feature the team was relying on. The risk isn't the price, it's the capability ceiling.What's the honest answer when a user needs something Crewdle's automation layer can't do that Make or Zapier could? Do they export and move on, or are they stuck? The lock-in risk of an all-in-one tends to show up 6 months in, not at signup.

With usage-based billing, is there a way to set a hard monthly spend cap or alerts? For a small business, an autonomous agent running around the clock could get unpredictable, so I'd want guardrails.

Most founders I know are not looking for more AI features. They want fewer tabs open and fewer invoices to track. The positioning here seems much stronger than simply calling it an AI platform.

Interesting! Will test

Interesting launch 🚀The biggest challenge I've seen with all-in-one AI platforms is context sharing between different tools and agents.I'm curious: if one agent creates content, another builds an automation, and another updates a website, how do you maintain shared context and prevent conflicting actions across the workspace?Congrats on the launch!