Naseem, 24 hours later: #21 and first customer

Yesterday, Naseem finished its first day on Product Hunt:

#21 Product of the Day · 76 upvotes · 57 followers

And today, Naseem got its first paying customer at the $29 launch price.

What surprised me: the first customer was a company, not an indie developer. I wasn’t expecting that this early.

And development continues.

Today I shipped Rules (Beta).

Rules let you schedule Naseem to run agent tasks automatically:

  • On launch

  • Hourly

  • Daily

  • Weekly

This moves Naseem beyond “ask the agent to do something” toward “give the agent recurring work and let it handle it.”

Now I’m curious:

If you had an AI agent working on your Mac every day, what would you automate first?

27 views

Add a comment

Replies

Best

we already run this, scheduled agent tasks on a mac every day. the one i'd start with is the reading not the writing.

finding which 5 threads out of 200 are worth answering is what eats the morning. drafting the reply takes 2 mins once u know where to put it.

 Agreed, the ranking is the hard part — “worth answering” isn’t a filter anyone can write. That’s exactly the kind of work I want Rules to handle: read through the pile, understand the context, and surface only the few that actually deserve your attention.

Where do those 200 threads live for you — email, GitHub, Slack? That helps me decide which integration to build first.

Watching for the thing that didn't happen. Most of what I'd hand to a daily agent is really a check that fires when something quietly stopped, a nightly job that exits 0 but produces nothing anyone opens, a webhook 200ing into a dead handler for a week. Recurring work I can already schedule, what I can't schedule is the noticing.

 Built it. A Rule can now be "quiet unless it matters": it runs the check, stays silent when all is well, and reaches you on Telegram only when something's off. It also refuses to say "all clear" without actually running the check, which was the exact failure you described. Screenshots are from this morning: the rule, and the alert it sent to my phone when the nightly job hadn't produced anything. Ships in the next update.

Here is the telegram notification when uncheck the "Only notify whensomething needs attentions"

  The thing that'll bite you is that a dead rule and a healthy system now look identical. Both are silence. Add a low frequency heartbeat, something like "ran 168 checks this week, nothing to report", or nobody notices the rule itself stopped firing three weeks ago. On our side the heartbeat has caught more breakage than the alerts have.

 You were right. Built it. 🙂
Quiet Rules now have a weekly heartbeat that reports which rules actually ran and flags any that didn’t. If the heartbeat itself stops arriving, you know Naseem isn’t running its rules either. Thanks for the idea.