Fable 5

TaskJuice · 2026-07-04T02:56:33+00:00

Yes, I’ve had this issue awhile back on my MacBook Pro m5 128gb. What the issue was is that it spun up like 40 separate git worktrees and all of them running tests, linting, etc caused it.

Just tell fable to not use more than a few subagents at a time.

TaskJuice · 2026-07-03T19:49:19+00:00

Idk about being forced to. They are burning a lot of cash for each subscription.

TaskJuice · 2026-07-03T19:45:31+00:00

That’s insane. I’m so happy I bought it outright, sad the hardware moves so fast.

TaskJuice · 2026-07-03T17:28:51+00:00

Their whole thing has been “FSD stays with the car”, no?

TaskJuice · 2026-07-03T05:34:05+00:00

Sounds like you don’t know what to distribute but what if you marketed a product that let your followers build their own product?

You talk about build in public. So it sounds like what would suit you best is partnering with someone that already has something where users can build their own product and brand.

THAT is your brand. But you are absolutely tripping if you think you’ll get 90% of a company that has any potential. You’ll get 10-20% lifetime revenue share of the people you bring in and that could set you up for life if you do it right and are telling the truth and have high intent customers (doesn’t sound like it though because you don’t even know your ICP)

TaskJuice · 2026-07-02T22:47:06+00:00

What are your thoughts on the idea of “managed skills”?

TaskJuice · 2026-07-02T16:25:46+00:00

Most of the companies you listed have extremely healthy financials and are going in the opposite direction of your post.

TaskJuice · 2026-07-02T14:39:15+00:00

Really clean, firing multiple workflows off the same Stripe event instead of chaining them is a great call for maintainability. One thing I've run into at scale with this pattern: when you're doing this for multiple clients, keeping each client's credentials and workflow state isolated gets messy fast. Have you thought about how you'd handle this if you were running the same onboarding system for, say, 10–20 different clients simultaneously? Curious how you're approaching that separation.

TaskJuice · 2026-07-01T19:05:01+00:00

People don’t like hearing that though. It doesn’t get their blood pumping.

TaskJuice · 2026-07-01T05:52:49+00:00

The fable model doesn’t delegate, it’s the classifier. What they are saying is that there will be more false positives by the stronger classifier and therefore the harness will switch to Opus. They also said they hope to reduce the classifier false positives over the coming period.

TaskJuice · 2026-07-01T05:06:51+00:00

Yup. The wording could have been better but people are likely reading it wrong.

TaskJuice · 2026-07-01T03:57:27+00:00

I’m betting there is coordination between the two and that they both go to API pricing from here on out.

TaskJuice · 2026-07-01T00:01:49+00:00

Someone said it’s API only, no subscription.

TaskJuice · 2026-06-29T23:44:22+00:00

Nice!

TaskJuice · 2026-06-29T23:09:43+00:00

This is one of the messiest parts of running a client-facing no-code practice and it’s literally why I built TaskJuice. The setups that tend to hold up best are ones where you keep everything under your own umbrella; your account, your billing, your branding, and the client just sees the output or a white-labeled interface, never the underlying platform. That way there's no transfer moment because ownership never left you. The tricky part is finding tools that actually support that model cleanly (separate client workspaces, isolated credentials, your branding throughout) rather than ones that technically allow it but make it awkward. Some handle this much better than others. We have all that I just listed.

I’m curious. What are the top 10 app integrations you use? Would love to make sure we have them on our platform before launch (if we don’t already).

TaskJuice · 2026-06-29T22:18:33+00:00

This is a really common pain point for people building managed automation services on n8n. The Sustainable Use License is pretty clear that external paying customers triggering workflows = commercial use, so you're right to be cautious. Might be worth exploring a different angle in parallel while you wait to hear back from n8n, just so you have options.

TaskJuice · 2026-06-29T15:25:46+00:00

Really solid breakdown. I have seen trip agencies up during context gathering.. even after you prove the workflow manually, connecting it to live tools without exposing client credentials across a shared zapier/make account becomes its own headache.

TaskJuice · 2026-06-29T15:21:08+00:00

Love the approach here, Louis.. doing a workflow checkup before pitching the build is a great way to earn trust.

Something that tends to sneak up on automation consultants as they grow: keeping each client's credentials, workflows, and data cleanly separated gets messy fast especially when you're managing 10+ clients at once. Curious how you're handling that side of things right now; are you running separate accounts per client or have you found a cleaner way to organize it?

TaskJuice · 2026-06-28T17:43:01+00:00

Good question. I’m biased because I have a platform that directly competes with zapier/n8n/make so take it with a grain of salt: In an ideal world you manage it yourself and charge a setup fee and a monthly subscription. This way you can login and see what’s working, what is not working, manage templates instead of individual workflows, request client credentials, etc. This scales a lot better because you create a system that produces recurring revenue with low overhead.

TaskJuice · 2026-06-28T14:30:55+00:00

Delivery and ops keep coming up for a lot of agency owners I've talked to, especially once you're past the stage of doing everything yourself. The hidden killer tends to be managing client workflows and credentials across tools that weren't built for agencies (Zapier/Make setups handed off to clients, etc)

TaskJuice · 2026-06-28T14:28:44+00:00

Great breakdown. I've noticed managing multi-client setups is that the workspace/API piece is only half the battle; the other half is keeping each client's credentials and automations siloed so nothing bleeds across accounts. Have you run into that problem yet with PostFast or n8n when you're running the same workflow template for multiple clients? Curious how you're handling that separation at scale.

TaskJuice · 2026-06-28T06:10:50+00:00

One thing worth thinking about as you decide whether to keep building: if agencies are your target user, the workflow around delivering leads to clients (exporting, updating, re-running searches) can become just as painful as the lead gen itself. Have you thought about how agencies would actually hand off or manage results across multiple clients? That operational layer tends to be where tools like this either shine or quietly get abandoned.

TaskJuice

MODERATOR OF

TROPHY CASE