Freelance Developers: Your Invoicing Workflow Deserves the Same Care as Your Code

Jonathan Devis — Sun, 25 Oct 2026 13:39:42 +0000

You finish the project, push the final changes, and send the handover email. After days of debugging and client feedback, the work is finally done.

Then comes the task you have been putting off: sending the invoice.

For freelance developers, invoicing can feel like a small administrative chore. But an unclear invoice creates another round of questions, interrupts your next project, and leaves you wondering when payment will arrive.

The solution does not need to be complicated. A repeatable workflow can make the business side of freelancing easier to manage.

Start Before You Write the First Line of Code

A smoother invoicing process begins with the project agreement.

Before development starts, confirm the scope, payment schedule, billing contact, and payment method. If you charge hourly, explain how you will record time. If you charge a fixed amount, define what that amount covers.

Imagine building a landing page for a client. Does the price include copywriting? How many revision rounds are included? Is deployment part of the project?

These details matter because an invoice should reflect an agreement that already exists. It should never be the first place a client discovers an additional charge.

For larger projects, consider agreeing on milestones so both sides know when each invoice will be sent.

Describe Work in Language Clients Understand

Developers naturally think in components, endpoints, and pull requests. Clients often think in outcomes.

An invoice item labelled "development work" gives very little context. At the other extreme, a list of internal function names probably will not help the person approving payment.

Aim for descriptions that connect technical work to the agreed deliverable:

Responsive landing page implementation
Checkout integration and testing
Website performance improvements
Monthly maintenance and bug fixes

If you bill hourly, include the hours and rate alongside each relevant item.

The goal is simple: someone who did not attend your project meetings should still understand what the invoice covers.

Make the Next Step Obvious

A client should not have to search through an email thread to work out how to pay you.

Use a consistent invoice number, identify both parties clearly, and include the issue date, due date, currency, itemised charges, and total amount. Add the agreed payment instructions where they are easy to find.

Write an actual due date instead of relying only on wording such as "payment due in two weeks."

Before sending, check the recipient details. Your usual project contact may not be the person who processes invoices. Asking for the correct billing address early can prevent an avoidable handoff later.

Build a Workflow You Can Repeat

Creating every invoice from a blank document introduces unnecessary decisions.

Choose a standard layout and follow the same sequence each time: gather approved work, check the amounts, review client details, send the invoice, and record its status.

Keep a simple register showing what has been drafted, sent, paid, or needs attention. A spreadsheet may be enough when you have a few clients.

When evaluating tools, focus on the steps that take up your time. Check how easily you can prepare an invoice, correct a mistake, and keep your records organised.

My website, Invoiceo, is another resource you can explore while putting together your invoicing workflow. Whatever approach you choose, test it against a realistic client scenario before making it part of your routine.

Treat Follow-Ups as Routine Communication

Following up on payment can feel awkward, especially when you enjoy working with the client.

Prepare a short, polite message in advance. Reference the invoice number, amount, and due date, then ask whether anything is needed to process payment.

Avoid assuming that a delay is intentional. An invoice might be waiting for approval or have reached the wrong inbox.

A calm follow-up gives the client a clear action without turning an administrative issue into a personal disagreement.

Give Your Business Process Some Attention

You do not need a complex finance system to work professionally.

You need clear agreements, understandable invoices, reliable records, and consistent communication.

Review your process after your next project. Notice where you had to repeat yourself or search for missing information, then fix that step.

Your next invoice should be easier to send than your last one.

I Built a Free Online Video Compressor in 1 Week

Jonathan Devis — Tue, 13 Oct 2026 09:59:07 +0000

Hi everyone!
In the last two weeks, I've worked on a tiny side project Video Compress

A fast, free, and simple online video compressor with no watermarks or limits on use.

The Problem

You've got a ton of free online video compressors to choose from, though most of those services will throw a lot of frustrating restrictions on you watermarks, file size limits, and hidden paywalls.
I was looking for something simple: upload, compress, download -no unnecessary things, no tricks.

The Tech Stack

The project is developed with:

Frontend: Next JS, static site generation and an ultra-fast UI.
Backend: Node JS, for handling API requests.
FFmpeg, on server to make compression more efficient.
The Next app is all static - served out on a CDN for near-instant access all over the world – while all the real work happens on the server with the backend API.

Reasons for Moving Compression to the Backend

First, I added compression to the frontend through Web Assembly builds of FFmpeg.
It worked, but performance was not good - CPU load was low and compressing large files took forever.

This allowed me to shift the compression to the server side so that I could take advantage of full CPU and I/O performance of the machine.
And that resulted in faster compression-especially if you were working with a longer video or a higher resolution file (like 1080p or 4K).

It also gave me more flexibility to:

Optimize compression presets dynamically

Manage bigger uploads

Compatibility to various video formats, like MP4, MOV, AVI, etc.

Lessons Learned

Sure, frontend compression sounds neat and all, but when you got some serious grind to do, ain't worth the effort.
No comparison to the quality/size ratio of FFmpeg.
Keep the UI as simple as it can get - users are only interested in getting results, not navigating through loads of settings.
Static building with Next JS + Node JS backend is a power combo for projects like this - quick to build, deploy easily and scalable.

Test It

Get it now or try it here:

https://shrinkvideos.com/

It's totally free, no watermarks, no hidden limits.
Would appreciate your comments or suggestions of improvement!

DEV Community: Jonathan Devis