saascode
project & workflow operations·run 062 · May 2026

Laurelite

A user-controlled work-recall assistant that proposes client and matter candidates from minimal signals, then requires confirmation before billing.

Genesis score6.43/10
Make Laurelite real.0/500
500 more votes and Laurelite 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

Solo consultants and very small development shops can forget short client work when they rely on timers or end-of-week memory. Calendar, email and chat can help reconstruct context, but passive capture becomes surveillance if it reads more content than necessary or treats activity as proof of time worked.

Laurelite lets each user connect selected sources with narrow scopes and visible retention. It creates work-event candidates from permitted metadata and, only where authorized, bounded excerpts. The system proposes client, matter, date, duration and memo with confidence. The user confirms or corrects every entry and may delete source-derived evidence.

An event does not establish duration or billability. Rate, retainer, expense and tax rules come from versioned agreements maintained by the consultant. Confirmed time, invoice-line draft, invoice approval, provider request, acknowledgment, client receipt and payment remain separate.

The product is a recall assistant, not passive timekeeping. It does not score productivity, monitor staff, issue invoices automatically or infer client work from private communication without explicit user control.

Who pays — and why

Solo consultant or owner of a one-to-five-person professional-services shop who loses billable context between manual time entries

What it unlocks
A permission register separating source, account, scope, metadata or content access, purpose, retention, revocation and deletion
A work-recall lane separating calendar or communication event, client candidate, matter candidate, date, duration assertion, confidence, user correction and exclusion
A billing workflow separating confirmed time, agreement version, billability, rate, invoice-line draft, approval, delivery acknowledgment, client receipt and payment
How Genesis scored it
6.43across seven criteria
tension 6temporal 7blindspot 7buyer 8leverage 6convergence 5why-not 5
8
Buyer persona

Solo consultants and very small shops are precise, with a recognizable lost-time problem.

7
Temporal window

Current agent and integration interest supports feasibility rather than a hard deadline.

5
Why nobody did it

The source gap is clearer than the reason it remained unbuilt.

Why it scored well

The supplied research confirms enterprise passive-capture demand, low-cost manual alternatives and a small-shop gap with invoice-draft integration.

What's holding it back

Passive capture is privacy-sensitive, source activity cannot prove hours, the historical barrier is unclear, interface access has cost, and self-serve economics are not established.

Signals detected3 sources crossed
SignalSupplied competitor research

SignalSupplied competitor research

SignalSupplied interface research

Direction brieflaurelite.md
laurelite.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.