1
2 Comments

Small but important UX update: Added item name + description to my invoice generator

Hi everyone,

I shipped a small but important update to my free invoice generator today.

A few people pointed out that invoices usually need a clear item name, not just a description. For example:

• “Kitchen Sink Repair”
• “Website Design – Phase 1”
• “Roof Inspection”

Previously the tool only had a description field, which made invoices feel less structured.

So I updated the line item system.

Now each line item supports:

• Item Name (main service/product)
• Optional description (extra details if needed)
• Photo attachments per line item
• Automatic totals and PDF export

The description field is now hidden behind a button so the UI stays clean unless you actually need more details.

I also updated the homepage hero to better explain the photo attachment feature, which many contractors and service businesses found useful.

Here are a few screenshots of the updated interface 👇

(attach the screenshots you showed me)

You can try it here:
https://invoice.gen.in

Curious to hear feedback from other builders — especially anyone building tools for freelancers or service businesses.

on March 4, 2026
  1. 1

    Small UX tweaks like this are usually underrated =(

    In many SaaS tools the biggest improvements come from reducing ambiguity, not adding features. When a user sees a clear item name + description, they immediately understand what the invoice represents.

    Did you notice any change in support questions or user confusion after this update?

    1. 1

      Thanks! I completely agree — a lot of SaaS tools focus on adding more features, but sometimes the biggest improvements come from removing ambiguity in the UI.

      In this case, a few early users told me they were unsure what to put in the description field, especially contractors who usually think in terms of clear service names like “Kitchen Sink Repair” or “Roof Inspection”.

      Adding the Item Name + optional description made the invoice structure much clearer.

      It’s still early, but the goal was exactly what you mentioned: reduce confusion and make the invoice feel more professional with minimal input.

      I’m also trying to keep the interface extremely simple — that’s why the description field is hidden unless someone needs it.

      Really appreciate the feedback. If you ever have thoughts on things that feel confusing or unnecessary, I’d love to hear them.

Trending on Indie Hackers
Your AI Product Is Not A Real Business User Avatar 116 comments Stop Building Features: Why 80% of Your Roadmap is a Waste of Time User Avatar 72 comments I built an enterprise AI chatbot platform solo — 6 microservices, 7 channels, and Claude Code as my co-developer User Avatar 38 comments The Clarity Trap: Why “Pretty” Pages Kill Profits (And What To Do Instead) User Avatar 34 comments I got let go, spent 18 months building a productivity app, and now I'm taking it to Kickstarter User Avatar 22 comments I went from 40 support tickets/month to 8 — by stopping the question before it was asked User Avatar 19 comments