Time tracker that writes the invoice for translators

Start a timer per language pair and client. When you stop, it drafts the invoice in their template, with word counts if you drop the file. Emails it. Done.

For Freelance translators and interpreters

Riff on @T_Zahil niched idea list

The problem, sharper

Freelance translators and interpreters already tried the generic version and bounced. Start a timer per language pair and client. When you stop, it drafts the invoice in their template, with word counts if you drop the file. Emails it. Done. The wedge is the constraint, not another feature list.

Features that make the pitch true

01Capture the job in one screen: Start a timer per language pair and client. When you stop, it drafts the invoice in their…
02Audience-aware defaults for freelance translators and interpreters.
03Shareable artifact you can send to a teammate in one tap.
04Honest empty states. No fake social proof, no infinite onboarding.
05Export: the user can leave with their data on day one.

This weekend

Friday: landing page, one happy path, seed data.
Saturday: the core loop that makes the pitch true.
Sunday: share link, ugly-but-working export, tell ten people.

Stack

— Next.js + TypeScript
— Local-first persistence, server later
— role-based access
— audit log
— CSV in / CSV out
— double-entry basics

User stories

As a person in this group: Freelance translators and interpreters, I can describe the job in one sentence and get a usable first result.
As a skeptic, I can try it without creating an account.
As someone who might build this, I can copy a spec and start this weekend.

Paste into Cursor, Claude Code, or Codex

Build a working product called VoltLine.

Tagline: Time tracker that writes the invoice for translators — without the usual product theater.

One-liner: Start a timer per language pair and client. When you stop, it drafts the invoice in their template, with word counts if you drop the file. Emails it. Done.

Who it is for: Freelance translators and interpreters

Non-goals: do not build a generic work app. Do not add auth until the core loop works. Do not invent extra personas.

Must-have features:
1. Capture the job in one screen: Start a timer per language pair and client. When you stop, it drafts the invoice in their…
2. Audience-aware defaults for freelance translators and interpreters.
3. Shareable artifact you can send to a teammate in one tap.
4. Honest empty states. No fake social proof, no infinite onboarding.
5. Export: the user can leave with their data on day one.

Suggested stack:
- Next.js + TypeScript
- Local-first persistence, server later
- role-based access
- audit log
- CSV in / CSV out
- double-entry basics

UX:
- Distinctive, editorial, not purple-gradient SaaS
- Works on a phone
- Empty states teach the product
- One primary action per screen

Ship this weekend:
1. A landing page that states the job in one breath
2. The core loop end to end with sample data
3. A shareable output
4. A README that explains what was intentionally left out

Constraints: TypeScript. Keep the first version local-first if a database would slow you down. Name the product VoltLine unless you have a clearly better one.