The jobs nobody assigned you
Helio Team
Patterns from user interviews: the recurring work that never appears in a job description, has no ticket, and reliably comes back next week.
Four people, one shape
We have been running interviews with people using Helio, and the same silhouette keeps showing up in completely different jobs. Nobody described it in these terms. It only becomes visible when you line the conversations up next to each other.
The consultant handed an unfamiliar industry
One is a consultant a few years into the work. Every few months a project lands in an industry she has never worked in. Before she can produce anything a client would pay for, she has to build a picture of that industry from nothing: the policy environment, who the customers are and what they can afford, who is already competing, where the whole thing is heading. That research is not the deliverable. It is the thing standing between her and starting. It happens again with the next project, in a different industry, from scratch.
The grad student building a table of professors
Another is applying to PhD programs. What he needs is a table: for each professor on his list, where they are, which lab, what they have published in the last three years, whether the group is funded, and where their students ended up afterward. Every cell of that table is a small research task, and there are a lot of cells. Nobody assigned this. It exists because he decided to apply.
The analyst whose month has a fixed shape
A third works in business analysis. Her month has a rhythm: targets broken down and tracked, an incentive scheme designed and then reconciled at payout, the same report assembled from the same places, and a presentation her manager cares about a great deal. She told us her baseline work takes an hour or two a day. The rest of the month is that recurring shape.
What they have in common
None of this is in a job description as a discrete deliverable. There is no ticket, and no obvious person to hand it to, so it stays where it landed. It repeats on a cycle you could set a calendar to. And critically, the shape is identical each time while the contents are completely different, which is exactly the combination that defeats a script. A macro can pull the same five fields every month. It cannot notice that this month one of them means something different.
Why this category was skipped
Software has been good at tasks for a long time and good at workflows for about a decade. This category sits in the gap: too irregular to script, too repetitive to keep doing by hand, too small to hire for. So it defaults to whoever noticed it first. That person is usually competent and busy, which is precisely why the work is invisible in any plan. It never shows up as a line item. It shows up as your week being gone.
The test we use now
When someone asks what Helio is for, this is the filter we suggest. Think of something you did last month that you will do again this month, that nobody explicitly asked you to do, and that you would struggle to write down as a set of steps because half of it is judgment. That is the shape. If you cannot think of one, you probably do not need an AI teammate yet.
Frequently asked questions
How is this different from ordinary task automation?
Task automation handles work where the steps are stable. These jobs have a stable shape but different contents every cycle, so the same steps produce a wrong answer roughly as often as a right one.
Why not just hire someone for this work?
Individually each job is too small to justify a hire, which is why it defaults to whoever noticed it. Collectively they eat a serious portion of a week, but they rarely add up in anyone's planning because none of them have an owner on paper.
What kinds of work do not fit this pattern?
One-off projects, anything with no repeat cycle, and work where being wrong on the first attempt is expensive. Those need a person, and often a person who already knows the domain.
How do I find mine?
Look for something you did last month and will do again this month that nobody assigned, and that you would find awkward to write down as steps because a good chunk of it is deciding rather than doing.