saascode
project & workflow operations·run 260 · Jun 2026

Billrook

A user-triggered engagement-note workflow that proposes time and scope records, cites the source, and requires contract-aware approval before billing.

Genesis score6.45/10
Make Billrook real.0/500
500 more votes and Billrook is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The case

Agencies and professional-services firms lose context when staff postpone time entry or forget small scope-change conversations. Voice can make a post-call debrief easier to capture, but always-on ambient listening would collect coworkers and clients beyond the intended purpose. A transcript also cannot establish duration, billability, scope or client acceptance.

Billrook uses explicit, user-triggered voice notes after an authorized interaction. It preserves the recording, transcript candidate and source spans, then proposes matter, activity, duration, billable status, scope-change question and follow-up owner. The user corrects the note; an authorized engagement owner applies the current agreement, rate and change-control policy.

Work assertion, approved time entry, change-request draft, client approval, invoice line and payment remain separate. A signed or hashed ledger proves which version was preserved, not that the hours are true, billable or accepted by the client.

The product excludes passive listening, worker productivity scoring and automatic billing. It helps teams prepare a source-linked engagement history while preserving consent, contract authority and dispute corrections.

Who pays — and why

Agency or professional-services operations, finance or engagement leader responsible for time capture, scope control and client billing

What it unlocks
A consented capture record separating authorized interaction, user-triggered note, recording, transcript candidate, source span, correction and retention
An engagement layer separating client, matter, activity, duration assertion, billability candidate, agreement version, scope-change question and reviewer finding
A commercial ledger separating approved time, change request, client response, approval, invoice line, delivery, correction, dispute and payment
How Genesis scored it
6.45across seven criteria
tension 6temporal 7blindspot 5buyer 7leverage 7convergence 5why-not 7
7
Temporal window

Active entrants validate demand, while the main broad competitor is not fully launched.

7
Buyer persona

Agency operations and finance owners are concrete, while size, budget and current alternative need validation.

5
Convergence

The supplied record has two cross-references and no inbound connections.

Why it scored well

The supplied research confirms voice-to-time products and a reported gap around contract-aware scope-change provenance.

What's holding it back

The proposed ambient capture is unacceptable without explicit triggering, a broad competitor is approaching the workflow, billability remains contract-specific, and signed history does not prove truth.

Signals detected3 sources crossed
SignalSupplied competitor research

SignalSupplied competitor research

SignalSupplied interface research

Direction briefbillrook.md
billrook.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.

Discussion

?

No comments yet — be the first to weigh in.