odel-labs

01The overnight drafts waiting for approval, each one showing what it was written from.

Module

yixxoo

Shape

SaaS, AI

Parts

Drafting, approval, stack

Runs

Overnight

Built for

Trades and services

State

Available

Nothing is sent until you approve it. That one rule set the whole design. A tool that emails a customer on your behalf has to be trusted before it is useful, and trust is not something you can add in a later version, so the approval step came first and everything else was built behind it.

Every draft shows what it was written from: the job sheet, the thread it is replying to, the quote it is chasing. You read the draft, not the source, and the source is one click away when a number looks wrong. Approving is a button. Rewriting is a sentence, and what you change is kept, so the next draft of that kind starts closer.

It is modular. Invoicing, quoting and replies are separate parts, and you add the ones you need to your stack and leave the rest alone. Most firms start with the one that is costing them evenings, which is usually invoicing, and add the second after a month of watching the first.

Built for the firm where the person doing the work is the person doing the paperwork, and the paperwork always loses. It is our own product rather than a commission, which is why it is the one we can show in full.

One draft on a phone, with the source it was written from and a single approve.

A tool that emails a customer on your behalf has to be trusted before it is useful.

Screens

Drawn, not photographed. The captions say what each screen shows.

02The draft against the job sheet it was written from, with the figures it carried over marked.
03The parts in use and the parts available, priced separately.
04What was rewritten last week, and what the next draft of that kind will do differently.

What next

If the paperwork is being done after the work, that is the first module.

Send an email