I used WorkBuddy and Qwen Office for three months each: one gets work done, the other just writes text
Community Discussion · General

I used WorkBuddy and Qwen Office for three months each: one gets work done, the other just writes text

Pixel DustPixel Dust5d ago2026/11/13 287 views

If you're only dealing with documents and spreadsheets, Qwen Office is handier, and the interface is much cleaner. But whenever the task needs to step outside documents and touch real files on your computer, of these two only WorkBuddy can get it done. The price is that I still haven't gotten used to its interface.

There's a saying going around the industry now: from AI assistant to digital employee. I've read the reports too—for this 2026 wave, the market size is said to be over 150 billion, with enterprise-level annual growth over 110%. Sounds lively. But sitting at my computer using it for three months, I feel it's another matter—the part that can be called an "employee" is only the hands; the brain is still on probation.

Work within a single file: Qwen Office wins, and wins gracefully

Last month I revised a brand manual for a client, a 60-plus-page docx, needing to unify terminology and swap the color values in tables to a new set. I tried both.

Qwen Office is really solid on this kind of work. Accurate positioning, replacements don't run across lines, and after editing the formatting is basically untouched. It knows where its boundaries are—it stays inside the document and doesn't run around outside. The interface is restrained too; line spacing, whitespace, button hierarchy are all designed, and it doesn't tire your eyes after a while. I have to give it credit for this.

WorkBuddy can do it too, but its habit is to pull the file out, process it in its own workspace, then put it back. Occasionally the intermediate format loses a bit, like table column widths, comment positions. From my testing, for pure document tasks the rework rate is lower with Qwen Office—saves me roughly one full read-through.

And the interface. This isn't a small matter; for me it's a hard requirement. After WorkBuddy finishes organizing files, that directory tree—a whole screen of same-named folders, indentation not even aligned, looks like a misaligned grid. I have to take a deep breath every time.

Cross-software, cross-file work: WorkBuddy wins, and wins ungracefully

The real gap shows on another type of task.

Last week I dropped in all the screenshots from a design project, about forty of them, scattered in the downloads folder with messy names. What I wanted was to sort them by project and by page type, rename them, then extract version numbers and dates into a summary table.

Qwen Office can't do this—it can't get outside the document layer. WorkBuddy can, and the final result is correct.

But the process is ungraceful. After the first run, the folders were sorted, but some of my original files had been moved, and it took me a while to find them back. I wrote a post about this last week; the lesson is that rules must be spelled out one by one, and it's best to manually build the folder skeleton first, then let it fill in. It won't follow your understanding; it follows its own.

Once the rules are spelled out, running the same batch of images again takes about twenty minutes to produce results, much faster than an afternoon of manual organizing. This is where it's valuable, and why I've never uninstalled it.

A week ago I started using its SubAgent, splitting design review into three pipelines—structure, visual, copy—with the main Agent only responsible for splitting tasks and collecting results, the three running queued separately, not crammed into the same context. I think this design is right; the value is in isolation and queuing, not in opening several windows at once to look busy. The downside is the task brief must be written verifiably; write it vaguely and what comes back is vague too.

The term "digital employee": I have reservations

There's a line in the report I agree with: but when it lands in a real enterprise environment, the picture turns sharply—in between lies a POC valley of death.

I believe this. Because I've been in the valley myself. In a demo, WorkBuddy organizes a pile of screenshots into a table in three minutes—very impressive. But in daily life, what you deal with is non-standard naming, directories with historical baggage, the same file in three versions. It won't judge on its own which is the final version; you have to tell it.

I've seen the traffic data too—supposedly in June 2026, a dozen or so mainstream office agents together broke 60 million visits, with WorkBuddy near the front. I believe that; the designers and operations people around me all use it. But high traffic doesn't equal being usable as an employee. At the current level, it's a very useful pair of hands, not someone who can make decisions on their own.

So my judgment is scenario-based. For people who spin around documents and spreadsheets all day and have a unified ecosystem, Qwen Office is enough, and more worry-free. For people who need to cross software, touch local files, and line up a pile of odd jobs into a pipeline, WorkBuddy is the only choice of these two—but you have to accept it's ugly, and accept that you have to think the rules through first.

Over the next year, I guess this track will split in two: the ones that can land will dig into the "execution layer"—doing files, doing systems, doing rollback-able; the ones that write words will retreat to the assistant seat. The watershed isn't how smart the model is, but who first makes solid the ability to roll back after a mistake. What WorkBuddy most lacks right now is exactly this—it dares to touch your files, but rollback isn't detailed enough. Fix this, and it deserves to be called an employee. Fail to fix it, and it'll always be those hands—useful, but you won't dare let go.

2 replies

?
Ctrl + Enter to reply
Amy
Amy5d ago

"It dares to move your files but its undo isn't granular enough"—that's so real. Our reimbursement forms got moved around and it took half a day to find them again.

Ling Xi
Ling Xi5d ago

"Build the folder skeleton first, then let it fill in"—I've hit that same pit. If you don't spell out the rules, it really does move files based on its own understanding.