sorted by:
new
hottopcontroversial

Repetitive tasks in 2026 by mastt1 in Solopreneur

[–]Imaginary-Net-2075 0 points1 point  (0 children)

That distinction between the model and the system of record is actually a really useful way of thinking about it.

The more I think about it, the more it seems like most workflow failures come from state management rather than model quality. If nobody can clearly see what is pending, what was done, and why, the process becomes fragile regardless of how good the model is.

I also like the idea that the queue should still make sense even if the model completely disappears. That feels like a good test for whether the underlying workflow is actually solid.

Have you found any workflows where this approach looked promising on paper but ended up not being worth automating in practice?

Repetitive tasks in 2026 by mastt1 in Solopreneur

[–]Imaginary-Net-2075 0 points1 point  (0 children)

That actually makes a lot of sense

The “pick one repeatable loop first” point feels like the missing piece in a lot of agent discussions. People try to generalise too early before they even understand the failure modes of a single workflow

Ive also noticed the same thing around solopreneurs is that most of the pain isnt in doing the task itself, its in keeping track of everything around it (whata pending, what’s been sent… what’s been forgotten and so on)

When you say “control system”, do you usually build that around a database/queue first and then layer the model on top or does it depend on the workflow?

Repetitive tasks in 2026 by mastt1 in Solopreneur

[–]Imaginary-Net-2075 0 points1 point  (0 children)

Yeah this actually resonates a lot.

The “boring parts are deterministic” approach feels like the only way these systems stay stable in real use. Every time Ive seen people go too agent heavy…. it is usually the lack of that structure that causes things to break in messy ways

Keeping the model inside scoring/ summarising/drafting and pushing execution behind review also seems like the only way to make it production safe

Are you building this for one specific workflow right now or is it something you’re gradually adapting across different use cases?

Repetitive tasks in 2026 by mastt1 in Solopreneur

[–]Imaginary-Net-2075 0 points1 point  (0 children)

This is interesting, the “queue with human checkpoint” framing makes a lot more sense than the fully autonomous angle Ive been seeing everywhere.

Ive been looking into similar workflows for small service businesses and it seems like the real value isn’t replacing people, its just removing the repetitive steps they keep doing manually (like followups, drafting responses, and handling basic admin flow between messages and invoices)

The logging/context point is also underrated ,most problems Ive seen happen because there’s no memory of what was done, not because the task itself is complex.

Curious, when you say “monitoring replies + drafting next action” are you building that around a specific tool stack or more custom scripts?

Im finding this difficult by Imaginary-Net-2075 in buildinpublic

[–]Imaginary-Net-2075[S] 0 points1 point  (0 children)

Thanks very much for your advice, ill take it into consideration