2
55 Comments

I asked AI tools to do my actual work for 2 weeks. Most failed at step one.

I've been an AI skeptic inside my own AI company. Awkward place to stand.

For the past two weeks I gave specific AI tools one job each. Not "help me with X." Actual tasks with a measurable output. A draft that needed to go out. A report that needed filing. A piece of copy that needed to convert.

Here's what I found, and it'll probably annoy the AI hype crowd.

7 out of 12 tasks required more time with AI than without.

Not because AI is bad. Because most AI tools are optimised for conversation, not for completion.

The gap between "generates decent text" and "does the actual thing in the actual app in the way you actually need" is enormous. Almost nobody is shipping across that gap yet.

The 5 that worked had one thing in common. They didn't just generate something and hand it back. They completed the action in the context where the action lived.

That's the distinction that matters. A tool that writes an email is not the same as a tool that writes and sends the email. Sounds obvious. Most tools stop at step one and call it AI.

This is actually why I built Genie 007 (genie007.com). Not to make a smarter text generator. To close the gap between "here's your draft" and "the thing is done." Voice-to-action, not voice-to-text. You say what you want, it does it everywhere on your computer. No integrations, no setup.

The 2 weeks taught me something I didn't expect: the useful AI tools right now are not the ones with the best models. They're the ones where someone thought hard about where the task actually lives and built all the way to done.

What AI tools have actually completed tasks for you, not just helped with them?


Building Genie 007 (genie007.com) — voice-to-action for everything you do on a computer.

on September 24, 2026
  1. 1

    For coding, the line I've noticed: tools that verify their own work complete tasks, tools that don't just chat about them. An agent that writes code AND runs the tests, reads the failures, and iterates will finish the job. One that just generates a diff leaves me holding the bag. Same model, totally different outcome depending on whether the loop is closed.

  2. 1

    Clear and practical, thanks. Did anything surprise you along the way?

  3. 1

    How did you decide this was worth building in the first place?

  4. 1

    Interesting take. Would you still recommend this approach to someone starting today?

  5. 1

    Appreciate the honesty here, most people only share the wins.

  6. 1

    Interesting take. Would you still recommend this approach to someone starting today?

  7. 1

    Appreciate the honesty here, most people only share the wins.

  8. 1

    Clear and practical, thanks. Did anything surprise you along the way?

  9. 1

    How did you decide this was worth building in the first place?

  10. 1

    Appreciate the honesty here, most people only share the wins.

  11. 1

    How did you decide this was worth building in the first place?

  12. 1

    Interesting take. Would you still recommend this approach to someone starting today?

  13. 1

    Clear and practical, thanks. Did anything surprise you along the way?

  14. 1

    Appreciate the honesty here, most people only share the wins.

  15. 1

    Clear and practical, thanks. Did anything surprise you along the way?

  16. 1

    How did you decide this was worth building in the first place?

  17. 1

    Interesting take. Would you still recommend this approach to someone starting today?

  18. 1

    Interesting approach. What was the hardest part to get right?

  19. 1

    Solid lesson. Which channel has worked best for you so far?

  20. 1

    What made you pick this stack over the alternatives?

  21. 1

    This is useful. How are you finding your first users so far?

  22. 1

    Interesting approach. What was the hardest part to get right?

  23. 1

    Good write-up. What would you do differently if you started again?

  24. 1

    Good point. Did you test that with users before committing to it?

  25. 1

    Nice progress. What is the next thing you are focusing on?

  26. 1

    Good point. Did you test that with users before committing to it?

  27. 1

    Appreciate the honesty here, most people only share the wins.

  28. 1

    Clear and practical, thanks. Did anything surprise you along the way?

  29. 1

    Interesting take. Would you still recommend this approach to someone starting today?

  30. 1

    How did you decide this was worth building in the first place?

  31. 1

    Clear and practical, thanks. Did anything surprise you along the way?

  32. 1

    Interesting take. Would you still recommend this approach to someone starting today?

  33. 1

    How did you decide this was worth building in the first place?

  34. 1

    Appreciate the honesty here, most people only share the wins.

  35. 1

    How did you decide this was worth building in the first place?

  36. 1

    Appreciate the honesty here, most people only share the wins.

  37. 1

    Interesting take. Would you still recommend this approach to someone starting today?

  38. 1

    Clear and practical, thanks. Did anything surprise you along the way?

  39. 1

    Nice progress. What is the next thing you are focusing on?

  40. 1

    What made you pick this stack over the alternatives?

  41. 1

    Clear and practical, thanks. Did anything surprise you along the way?

  42. 1

    How did you decide this was worth building in the first place?

  43. 1

    Thanks for writing this up. Bookmarking it for later.

  44. 1

    Nice progress. What is the next thing you are focusing on?

  45. 1

    Appreciate the honesty here, most people only share the wins.

  46. 1

    Totally agree with the “where the task lives” point. For writing, the failure mode I keep seeing is forcing people to leave Mail/Notion/Docs, generate text elsewhere, then paste/edit it back in. The better UX is assistance inside the field: autocomplete when you are already composing, rewrite selected text in place, and keep sensitive drafts local when possible.

    I’m working on DraftKey for that exact Mac-native/on-device slice: https://www.getdraftkey.com/ . It does not try to complete the whole workflow, but it removes a bunch of the copy/paste/context switching around founder writing.

  47. 1

    How did you decide this was worth building in the first place?

  48. 1

    Appreciate the honesty here, most people only share the wins.

  49. 1

    Interesting take. Would you still recommend this approach to someone starting today?

  50. 1

    Clear and practical, thanks. Did anything surprise you along the way?

  51. 1

    Clear and practical, thanks. Did anything surprise you along the way?

  52. 1

    How did you decide this was worth building in the first place?

  53. 1

    Interesting take. Would you still recommend this approach to someone starting today?

  54. 1

    Appreciate the honesty here, most people only share the wins.

  55. 1

    Really solid approach — I'm juggling something similar myself (building Xstream4K on the side), what's been the hardest part for you so far?