Why I Built My Own Invoicing App Instead of Paying for Another Subscription

Ottermation
Jun 11
3 min read

Updated: Jun 12

I'm a motion designer, not a software developer. But a few weeks ago I shipped GigsFlow, a time tracking and invoicing app for freelancers. Here's why I built it and how someone with zero backend coding experience pulled it off.

The Problem

After 15+ years of freelancing in animation, I've tried most of the big invoicing platforms. They all have the same issue: I was paying a monthly fee for a feature set built for agencies. Expense reports, team seats, limited clients, payroll, bank connections, project budgeting, integrations I'd never touch. All I actually needed was a way to track hours across multiple clients, see my week at a glance, and turn that time into a clean PDF invoice.

The math bothered me too. $25 a month, every month, forever, to use maybe 10% of an app. Over a few years of freelancing that's well over a thousand dollars for what amounts to a timer and a PDF generator.

So I set a goal: build exactly the tool I needed, nothing more, and charge a single one-time fee so other freelancers could get off the subscription treadmill too.

Building It Without Being a Developer

This is the part that would have been impossible two years ago. I built GigsFlow using AI-assisted development tools, where you describe what you want in plain English and the AI writes, runs, and debugs the actual code.

That doesn't mean it was effortless. The process was closer to being a director than a passenger. I wrote detailed specs for every feature. I caught layout bugs on mobile, state conflicts where edits would vanish and reappear, timezone issues that logged my hours on the wrong day, and a timer that died every time you refreshed the page. Each fix meant clearly describing the problem, understanding why it was happening, and pushing back when the first solution didn't hold up.

My background in animation production actually helped more than I expected. Freelance motion work is constant iteration: client notes, revisions, version control, knowing how to communicate exactly what's wrong with a frame. Building an app turned out to be the same loop. Spot the problem, describe it precisely, review the fix, repeat.

What GigsFlow Does

The app does four things and tries to do them well:

Time tracking. A live timer that survives page refreshes, plus manual entry with start and end times. Every minute lands under the right client and project.

A weekly timesheet. A spreadsheet-style week view where you can review and edit hours before they become an invoice. This was the feature I missed most in other apps.

Invoicing. Clean, professional PDF invoices generated from your tracked time, with custom line items, mixed hourly and day rates, and your own logo and branding.

Unlimited clients. No tiers, no caps, no "upgrade to add more than 3 clients." Every client gets its own rates and its own running balance.

One price, $9.99, one time. A 20-day free trial with no credit card required. That's the whole business model.

What I Learned

A few takeaways for anyone, especially other creatives, thinking about building their own tool:

Your pain point is your spec. I never had to guess what features mattered because I was building for a problem I'd lived with for years.

Precision is the skill. AI tools don't reward vague requests. The better I got at describing exactly what I wanted, down to the breakpoint behavior on a 375px phone screen, the better the output got.

Shipping something small beats planning something big. GigsFlow does less than its competitors on purpose. That constraint is the product.