Back in 2018, while I was working at Vote.org during the height of midterm elections, I was constantly monitoring our daily traffic and usage patterns, looking for anomalies and preparing for our ever-growing traffic. It wasn’t unusual for our CEO to ask questions about users and for me to develop the SQL query to answer, but I wanted a daily understanding of how our users were using our apps, state by state, tool by tool.

So I did what any engineer would do: I wrote a quick cronjob that would email me at the end of each day with a summary of the day’s activity based on the SQL queries I so often ran.

That’s it. Just a simple email to myself with some usage stats. Each morning it gave me peace of mind to see that the majority of users who started a tool completed their registration form. I loved seeing the spike in users as elections approached and watching adoption grow as we shipped new features.

The Organic Growth

A while later, another engineer became perplexed about how I always seemed to have a quick read on our traffic trends. I told them about the cronjob. They asked to be added. Then another engineer. Then someone from ops. Then our CEO. With each new person added to the email, a few more SQL queries got folded in, answering questions about user behavior, state demographics, and our top partners.

Suddenly, this little hack I’d built for myself had become the daily monitoring ritual for the entire team. Every morning, people were checking that email, asking questions about trends, using it to inform decisions.

It became clear: we needed proper monitoring and dashboards. The scrappy cronjob had done its job; it proved the need. We invested in Geckoboards for real-time usage, integrated more robust analytics to track funnel completion, and built out a proper observability strategy. But the daily email didn’t go away; it had become ritual at that point, a morning check-in the whole team relied on.

And that turned out to matter. One day when the email didn’t arrive, it tipped us off that something was wrong with our scheduled jobs, which led us to improve our PagerDuty setup for real-time alerting and to rerun the jobs manually. One hack revealing the need for the next.

The Lesson

This experience taught me something fundamental about building tools and features:

Start with the simplest thing that could work. Don’t build the dashboard first. Don’t make it configurable or pretty. Write the cronjob, send it to yourself, see if it matters.

Let organic demand prove the need. I wasn’t trying to convince anyone that monitoring was important. I built something for myself, and others gravitated toward it because it was useful. The demand was real, not manufactured.

Use scrappy solutions to justify real investment. That cronjob became the business case for proper tooling. The value was already proven before we spent a dollar.

The best features often start as hacks you build to scratch your own itch. If it solves your problem, chances are it solves someone else’s too.

This pattern hasn’t changed in 2026; if anything, AI makes it more powerful. The gap between scrappy hack and working prototype is smaller than ever. You can get to useful faster. But that just means you should validate the need even sooner, not skip the step. Start simple, prove value, then invest.