UtilityCheck

Inspiration Utility bills are something most people have to pay every month, but they can be confusing to understand. A bill might suddenly increase, and it can be hard to tell whether the change came from higher usage, a rate increase, a one-time fee, or a possible mistake.

I wanted to build a simple tool that helps people keep track of those changes and know when it might be worth asking their provider questions.

What it does UtilityCheck helps users track their electricity, water, gas, internet, and other utility bills in one place. Users can add their provider, billing month, amount, and usage if it’s available.

The app compares a bill with previous bills from the same provider and flags unusual increases. If usage information is available, it can also compare the average cost per unit. When something looks unusual, UtilityCheck explains the comparison and suggests steps the user can take to review the bill.

A higher bill doesn’t automatically mean someone was overcharged, so the app highlights charges that are worth reviewing rather than claiming there is definitely an error.

How I built it I built UtilityCheck as a web app with a dashboard for viewing bills, a form for adding new ones, and a history section for reviewing past charges. The app uses the information users enter to calculate averages and identify increases. Bill data is stored locally so users can return to their information after refreshing the page.

I used Claude to help with development, and I focused on the idea, the user experience, and making sure the comparisons were understandable.

Challenges I faced One challenge was figuring out how to flag a potentially unusual bill without making a misleading claim. Utility bills can change for many reasons, including the time of year, how much someone uses, or changes in their provider’s rates.

I also had to account for incomplete information. Not every user will know their usage, and someone adding their first bill won’t have enough history for a comparison. I designed the app to work with the information available and explain when more history is needed.

What I learned I learned that a useful financial tool doesn’t have to solve every part of a problem. Sometimes, helping someone organize their information and notice a change is a valuable first step.

I also learned how important it is to explain what a calculation means and be clear about what it cannot prove.

What’s next I’d like to add the ability to upload a bill and automatically extract its information, along with reminders for upcoming due dates. In the future, I’d also like to explore using reliable local rate information to help users better understand their charges.

Built With

• claude
• codex
• github
• higgsfield
• render