Summer Freelance Season: Track Projects by Voice, Not Spreadsheets
Every summer the same thing happens. I pick up two extra projects in June, three more in July, and by August my "simple" Google Sheet has 47 tabs, half of them named "client_FINAL_v3."
I run Inithouse, a small studio that ships AI products. One of them is Voice Tables, a workspace you control by talking to it. It started because I got sick of my own spreadsheet mess during a particularly chaotic freelance summer two years ago.
The freelance summer problem
Summer is when a lot of B2B freelance work lands at once. Clients want things shipped before their teams go on vacation. Budgets need spending before Q3. Everyone's timelines compress.
So you end up juggling more projects than usual, and your tracking system (let's be honest, a spreadsheet you set up in January) starts cracking. Client names in the wrong column. Invoices you forgot to log. That one project you were supposed to follow up on last Tuesday.
I tried Notion, Asana, Monday. They all worked, but they all required me to sit down and type things out. When I'm between calls or walking to grab lunch, I don't want to open a laptop and fill in fields. I just want to say "add a new project for Marketa, due August 15, budget 2000" and have it land in the right place.
What I actually built
Voice Tables takes a voice command and turns it into structured data. You describe what you need (a client tracker, an invoice log, a project timeline) and it builds the tables and columns for you. Then you keep talking to it: add rows, update statuses, ask questions about your data.
Three setups I use every summer:
Client tracker. One table with client name, project scope, status, deadline, and hourly rate. I add new clients by voice when the contract comes in. "Add client: Pavel, website redesign, starts July 1, 40 euro per hour." Done.
Invoice log. Every time I finish a deliverable, I tell Voice Tables to log it. "Invoice Pavel, 12 hours, website homepage." At the end of the month I export the table and send invoices in ten minutes instead of reconstructing what I did from memory and calendar entries.
Project timeline. A simple table with milestones and dates. When a deadline shifts (it always does), I update it by voice. "Move Pavel's homepage review to July 22." No clicking through date pickers.
Why voice actually matters for freelancers
This is not about being lazy. When you're running multiple projects solo, context switching is the real killer. Every time you stop working to update a tracker, you lose focus on the actual deliverable.
Voice input happens in the gaps. Walking between meetings. Waiting for coffee. Sitting in a tram. You say what happened and get back to the work that pays.
Last summer I tracked eight projects this way. The part that surprised me most: I caught two missed deadlines early because I was actually keeping the data current, which I never did when it required opening a spreadsheet on my laptop.
Try it in five minutes
If you're a freelancer gearing up for summer projects, here's what I'd suggest:
- Go to voicetables.com
- Say "create a freelance project tracker with columns: client, project, status, deadline, rate, notes"
- Add your current projects by voice
- Keep it open on your phone and update as things happen
No account required to start. The workspace builds itself from your description in about a minute.
I still use spreadsheets for some things (complex financial modeling, shared reports with accountants). But for the daily chaos of tracking who needs what by when, talking is faster than typing. Especially when you have eight clients and it's July.
If you try it, I'm curious what setup you build first. The freelancer use case is where Voice Tables started, so I'm always interested in how other people organize their work.
The setup I'd build first is a client-loop state table, not a project table.
Projects already tend to have a place to live. The leak is usually the half-open thread: quote sent, waiting on client, invoice sent, nudged once, answer needed, close if no reply by Friday. Those are the loops that quietly turn into inbox archaeology.
The useful fields are pretty plain: state, owner, next date, and close condition. If a row says "waiting" but has no next date attached, it isn't actually waiting, it's dropped. Voice capture seems especially useful there because the update usually happens in the middle of doing something else.
agentisland's point about draft confirmation before committing an invoice number is the one I'd take most seriously — anything that touches money should default to "I'm not sure, confirm this" rather than a confident guess. It's basically the same principle behind why my own invoicing tool (getalisio.com) says "not enough data" instead of showing a number it can't back up — a wrong number that looks right is way more dangerous than an honest blank. Neat idea overall, voice for the fast-capture parts and a confirmation step before anything invoice-shaped gets touched seems like the right split.
The part that stands out is catching missed deadlines early because the data stayed current, not because of the voice format itself. Most tracking systems fail on friction rather than capability, the update never happens because it takes too many steps in the moment it occurs to you. Curious whether a quick text capture would hold up the same way, or if voice removes a specific friction that typing does not.
The 47 tabs named client_FINAL_v3 is way too real. I went a different direction, doubling down on the spreadsheet instead of replacing it, mostly because I didn't want another subscription or my data locked into someone else's app. But the voice angle for invoice logging is smart, that's exactly the kind of thing that gets skipped when you have to stop and open a laptop. Have you run into cases where it mishears a number on something like an invoice?
Context switching being the real killer, so true. I run a few different things at once and get the same summer compression, just with businesses swapped for clients. Voice input for capturing data in the gaps is smart. Where I still get stuck even with a good tracker is the other half, something logged three weeks ago quietly needs a decision today and nothing surfaces it. That's basically what FounderFlow tries to solve, feels complementary to what you built rather than competing. Nice work on Voice Tables.
I totally get the spreadsheet overwhelm; it's so easy to lose track when things scale. I've been using Taskai on my Android to just dump tasks via chat/voice so I don't have to manage complex sheets. It keeps me focused on the work instead of the tracking.
Voice capture fixes update friction, but invoice logging is the dangerous case because speech errors become money errors. I'd make every financial command land as a draft with parsed client, hours, rate, and total shown back before commit. The useful metric is corrected fields per 100 voice entries, not commands completed.