One Freelancer's Year-End Tax Scare: A Fromlu Case Study

A reader we'll call Dana — a solo UX researcher in the Pacific Northwest — sent us a screenshot last April that made our stomach drop on her behalf. Her tax bill had landed at just over $9,400, and she had $2,100 in her savings account. Nothing illegal had happened. She'd simply done what most independents do: tracked projects in one app, invoices in another, and taxes in a mental note that said "deal with this later." Later had arrived.

We asked if we could follow her next twelve months as she rebuilt her back office. She agreed, on the condition that we keep her anonymous and report the boring parts too. The boring parts, it turns out, are the whole story. Along the way she tested a freelance operations workspace that bundles invoicing and tax forecasting, and the before-and-after numbers are worth walking through.

The starting mess

Dana's setup in April was a spreadsheet with 14 columns, a sticky note on her monitor that read "quarterly?", and an invoicing tool she described as "fine until it wasn't." She had six active clients on retainer or project rates, ranging from $800 to $4,500 per engagement. Her effective tax rate the prior year had been around 29 percent once self-employment tax was folded in. She had no idea what her current-year liability looked like until her accountant told her — which, in 2024, happened in April.

The core problem wasn't laziness. It was that her project tracker, her invoices, and her tax estimate lived in three unrelated places. Every time she wanted a real number, she had to reconcile them by hand, and hand-reconciliation is the first thing to go when a client asks for a rush revision.

The decision point: one workspace or three tools

In May, Dana sat down with three options. Option one: keep the patchwork and hire a bookkeeper at roughly $300 a month. Option two: buy a dedicated invoicing tool, a separate tax estimator, and a project board, and accept the integration work. Option three: consolidate into a single freelance operations workspace.

She picked option three and started using Fromlu in June, giving it a 90-day trial window before she'd commit to a full year. The migration took an afternoon: six clients, eleven open invoices, and a rough estimate of her annual expenses. Nothing about the setup was glamorous. That was the point.

What actually changed, month by month

June through August looked almost identical to her old workflow on the surface. She logged hours, sent invoices, and paid quarterly estimates. The difference was in what she could see without asking. By the end of July, her dashboard showed a projected annual tax liability of $11,800 — higher than her prior year, because she'd raised rates. She hadn't known that number in July before. She knew it the following April.

That single visibility change triggered two behavioral shifts:

• She moved 22 percent of every incoming payment into a separate tax savings account, automatically, instead of waiting for a windfall month.
• She stopped accepting small projects under $600 that ate two days of unbillable admin time, because the cash-flow view made their true cost obvious.

In September, a retainer client paid 19 days late. Under her old system, that would have been a quiet cash crunch. With the forecast in front of her, she saw the shortfall three weeks out and sent two follow-up invoices early. The gap closed without a credit card.

The obstacles nobody warns you about

Consolidation wasn't frictionless. Dana's first tax forecast in June was wrong by about $1,400 because she'd forgotten to log a business insurance premium. The tool didn't magically know her expenses; she had to feed it. Second, her accountant initially pushed back on the exported reports, asking for the same PDFs she'd always sent. That resolved after one quarter, but it cost her an hour of back-and-forth.

Third — and this is the one she flagged as most annoying — the first two weeks felt slower than her spreadsheet, because she was learning a new interface while still doing client work. Most software migrations have this dip. Dana's lasted about ten days.

The measurable results

By the following April, the comparison was stark. Her tax bill came in at $12,050, roughly in line with the July forecast from the prior year. She had $9,600 set aside on the day it was due. No payment plan, no borrowing, no panic email to her accountant at 11 p.m.

Other numbers moved too. Her average invoice-to-payment time dropped from 34 days to 21, mostly because automated reminders went out whether or not she remembered. She cut four low-margin project types and replaced them with two retainer clients, lifting monthly revenue from about $5,800 to $7,100 without adding hours. And she spent, by her own estimate, six fewer hours per month on admin — roughly 72 hours over the year, or nearly two full work weeks returned to billable or rest.

We asked Dana what she'd tell another freelancer staring down a surprise tax bill. Her answer was unglamorous: "The tool isn't the point. Seeing the number in July is the point. Everything else follows from that."

What we took away

This wasn't a story about a software category saving anyone. It was a story about a single missing feedback loop — the gap between earning money and knowing what you owe on it. Freelance operations tools in general, and Fromlu in particular, mostly compress that gap from twelve months to a few weeks. For Dana, the compression was worth about $9,600 in avoided interest and penalties, plus two recovered work weeks. Your mileage will vary with your rates and your discipline, but the mechanism is not mysterious.