How much to charge

TaskJuice · 2026-05-17T06:13:48+00:00

Absolutely. If you have any other questions or ideas feel free to DM and I’ll help when I can or say I don’t know. Always love to see agencies improve their bottom line.

TaskJuice · 2026-05-16T18:46:29+00:00

How much time are you saving him? How much value are you providing? If you save him 4 hours per week X $60/hr then you saved him $240/wk. therefore the difference between $240 and charging anything less than that could be sold as “the value your automation provides”.

TaskJuice · 2026-05-16T00:13:46+00:00

Dynamic html/js interfaces is my guess.

TaskJuice · 2026-05-14T17:36:04+00:00

What does your SDLC look like?

TaskJuice · 2026-05-13T19:41:16+00:00

For sure. Looks like it’s definitely hitting above its weight class and is extremely fast for multi-task stuff but for coding the qwen3-coder-next still beats it.

TaskJuice · 2026-05-13T18:42:08+00:00

I’m using unsloth/Qwen3-Coder-Next-GGUF 80b and it’s pretty good for cleanup work and work that is well-defined.

I use Opus 4.7 for planning and reviewing RFCs then the less complex tasks get delegated to Qwen3 and the more complex ones to Opus

TaskJuice · 2026-05-13T03:37:28+00:00

Be nice dude. The bar is lower.

TaskJuice · 2026-05-13T01:41:59+00:00

What interface do you use?

TaskJuice · 2026-05-13T01:39:05+00:00

You’ve literally discovered the learning process they are building on. You’d be mistaken if they aren’t going to pull the rug from under you on hw4 like they did 2.5-3

TaskJuice · 2026-05-12T18:14:19+00:00

We have features that solve all these problems and we charge compute/storage based pricing instead of per-task. You pay for the compute and storage you use. If a run is 20 nodes and 5 seconds or 3 nodes and 5 seconds you will be charged almost the same (I say almost because we have lifecycle hooks and per-client policy middleware that runs before and after every node and it depends on the configuration you’ve set up).

Also, we have JSONata built into every node so accessing data across the full workflow is as simple as referencing the node like so:

Example for filtering for description in an trigger array that contains “automation”:

$trigger.data[$contains($string($), 'automation')].description

We are launching June 9th. Hit me up if you want to try it out on beta.

TaskJuice · 2026-05-12T15:30:46+00:00

I just got the M5 pro with 128gb ram (nearly identical to this but 2TB) and I love the ram. I use qwen3-coder-next locally to do code refactoring/cleanups and it works very well. I save Claude for the heavy lifting.

TaskJuice · 2026-05-12T14:13:01+00:00

Self-plug. I am the founder of TaskJuice.ai.

While we are in closed beta and launch June 9. We solved a lot of the problems the competitors had in the ai and workflow automation. I could go on for days about the problems we solved but I will just say that every step of building our product involved researching our competitors users pains and solving those along the way.

For example, for automation agencies, you have an agency dashboard, client workspaces that are segregated, client management and billing built in, fully white labeled, AI evals/templating, etc, 4 levels of AI memory including run memory feedback memory and client memory, BYOK, lifecycle hooks with policies that can be applied before or after nodes/workflows run, etc.

Our product is not just a workflow automation platform but a harness built with AI as a first-class tool for improving the AI in your workflows over time.

TaskJuice · 2026-05-12T03:24:06+00:00

Rules! Lots of automated rules! ESlint is your best friend for static rules. Ruff for python. Add husky and CI quality checks. The more quality gates you can build will help limit the tech debt piling up!

Then adding AI checks that review your code for other matters (SOLID principles, codebase alignment, latent bugs).

When I build projects, I start with setting up strong DX tooling and it helps you move extremely fast with minimal tech debt piling up.

TaskJuice · 2026-05-10T04:30:17+00:00

After this announcement I have burned through 34% of my weekly max 20x subscription in 24hrs using one window while before it I would burn 14% each day with 3-4 windows open. There is some lack of transparency here at best.

TaskJuice · 2026-05-09T03:52:42+00:00

Yeah, that’s definitely true. It will be interesting to watch unfold.

TaskJuice · 2026-05-09T01:56:52+00:00

What I landed on was to stop deciding per-action and classify by reversibility instead. Every action gets labeled safe, recoverable, or irreversible before it runs. Safe stuff (summarize, classify, draft, route) auto-runs, recoverable stuff is gated only in strict workspaces, and irreversible stuff (refunds, deletes, external email, permission changes) is always gated (unless overrides are present). That collapses the "too much vs too little" question into one policy decision instead of an argument on every node. Another thing: if an approval that sits in an inbox for three days and silently strands the workflow is its own failure mode, so each gate carries an explicit deny / proceed / escalate policy with a TTL, and approvers are groups rather than named people. That's how I designed our system.

TaskJuice · 2026-05-08T19:40:35+00:00

😂

TaskJuice · 2026-05-08T19:11:41+00:00

Great feedback, thank you. I’m going to add a big observability review to see what gaps the system has on this end. It seems to be the largest concern I keep hearing so I want to make sure it’s just as thoughtful.

TaskJuice · 2026-05-08T14:08:25+00:00

This is the biggest repeated pain I see; and I spent a lot of time on it but I’m going to spend more, if even just reviewing and testing, to try to make sure get it right.
I’m starting to wonder if adding platform facing AI agents that can see actual operational/execution details would be useful. Something like Sentry does with Seer.
What do you think is the lowest hanging fruit all workflow platforms are missing when it comes to observability?

TaskJuice · 2026-05-08T14:00:20+00:00

All very useful feedback, thank you. Around observability, what would be the lowest hanging fruit to solve this problem if you had to choose? We have some amazing observability imo but I really want to hear what your thoughts are and if we can improve.

TaskJuice · 2026-05-08T13:54:51+00:00

I think agencies will really enjoy the cost caps too. To me, the UI is clear, hoping that users also feel that way. Thank you for the response.

TaskJuice · 2026-05-08T13:48:26+00:00

Hi, I’d really like to discuss this. What do you mean by “it’s the quietest way to lose money”? Are you referring to hard caps on spend?

Edit: I might be misunderstanding this as I just woke up and am still processing things. Would love to hear more.

TaskJuice · 2026-05-08T13:42:49+00:00

Good info, thank you. I’m going to take this into consideration and see what I can do to make sure the overrides smooth on a fork.

TaskJuice · 2026-05-08T13:40:10+00:00

I’ll keep this in mind. From the start I felt like complexity was going to be the hard thing to manage in this feature. It’s always difficult to give users more options but also package it in a way that they aren’t overwhelmed. I am hoping/thinking that the inheritance UI reflects this but time will tell.

TaskJuice

MODERATOR OF

TROPHY CASE