Example workflow · Finished job → Sent invoice

Document intake

The job is finished. The invoice is waiting for hours nobody wrote down.

6 steps by hand → 1 approval

Before 6 steps, all by hand

MayaReads the completed job sheet
MayaFinds the booking
MayaCopies the details across
MayaEmails the team about missing hours
MayaWaits, then comes back to the reply
MayaPrepares and sends the invoice

After 1 step for a person

AIReads the job sheet
AIAsks the team for the missing hours
AIReads their reply
AIPrepares the invoice with its sources
MayaMaya checks it and approves — then it’s sent

Watch it happen · Document intake

Completed job → AI follow-up → team reply → invoice draft → owner approval → customer send. Source connections appear at the final review. Invented business and sample data; playback sends nothing.

Film transcript and visual description

The finished job, waiting invoice

The job is finished. Why is the invoice still waiting? Because someone still has to turn the paperwork into something you can bill. Open the sheet. Find the job. Copy the details. Chase the hours. And when the reply arrives, start again.

On screen: The completed CL-204 job sheet sits beside an invoice blocked by blank hours. The owner searches bookings, copies the customer into a draft and returns to the paperwork when the reply arrives.

AI asks for the missing hours

An AI workflow can carry that whole loop forward. First, it reads the job sheet and matches it to the booking. The customer, completed work, and agreed pricing are ready. But the final hours are missing. The AI emails the team with the job reference and the exact question.

On screen: A scan reads the sheet; its job, customer and work become structured fields. The blank hours expand into focus. The AI composes and sends a targeted email asking the assigned team for the cleaner count and each person’s working time.

The reply resumes the workflow

This job waits for a reply while the other jobs continue. Later, the team replies with the missing hours. The AI reads the message and matches it to the waiting job. The missing detail is resolved. The workflow continues automatically. It prepares the invoice and brings the finished draft to you.

On screen: CL-204 waits beside another job that continues processing. Later, the AI scans the team’s reply and matches CL-204 to the waiting job. Cleaner count, working time and break information become usable fields, the job resumes, and the invoice assembles for final review.

The owner checks the evidence

Only now do you step in, to review the final output. Start with the customer and the work. The job sheet and booking support both. The hours link directly to the team's reply. Two cleaners. Two hours each. Four cleaner hours. The rate comes from the accepted booking: twenty-five pounds per cleaner hour. Four times twenty-five gives a line subtotal of one hundred pounds.

On screen: The owner sees the finished invoice before its source connections appear. Job sheet and booking support the work; the reply supports two cleaners with two hour tiles each. Those tiles regroup into four cleaner-hours. The booking supplies £25 per cleaner-hour, and four priced units give the £100 line subtotal.

Approve the invoice and recipient

The question, reply, and calculation are all available beside the invoice. The billing contact comes from the customer record. Check where it will go. You approve this invoice and recipient, or return it for correction.

On screen: The question, reply and calculation remain available beside the invoice. The customer record supplies the billing contact. The owner can approve this invoice and recipient or return the draft for correction.

From completed job to sent invoice

After approval, the system issues the invoice, sends it, and records the outcome. From completed job to sent invoice. AI carries the workflow. You approve the result. Bring your workflow to Eniks.ai.

On screen: The approved invoice is issued, folds into an envelope and travels to the customer’s Accounts team. The send outcome is recorded. The closing composition pairs the completed job with its sent invoice, followed by the invitation at eniks.ai/free-poc.

What happens at each step

AI prepares and checks the work. Maya reviews the final output, its sources and where it’s going before anything is sent.

1. Input
Completed job sheet
The team submits a completed cleaning job sheet. The work is done, but the final hours needed for billing are blank.
Reference
CL-204
Customer
Cedar Offices
Work
Office clean
Date
16 June 2026
Status
Completed
Final hours
Missing
The invoice cannot be prepared until the missing hours are supplied.
2. Processing
The reply restarts the job
AI matches the job to its booking, emails the team for the missing facts and waits. It reads the reply, matches it to CL-204 and automatically resumes invoice preparation.
Question
Please confirm the number of cleaners and the time each worked on the 16 June clean.
Team reply
There were two of us on CL-204, 9am to 11am each, no break. Work completed as booked.
Reply matched to
CL-204 · Cedar Offices
Workflow
Resumed automatically
Draft invoice
Ready for final owner review
Other jobs continue while CL-204 waits for the team. Routine follow-up does not require the owner to intervene.
3. Human review
One final owner review
The owner checks the finished invoice with its evidence beside it. The job sheet, booking, email thread, calculation and customer record support the final output and recipient.
Work and customer
Job sheet and accepted booking · CL-204 · Cedar Offices
Hours
Team reply · 2 cleaners × 2 hours = 4 cleaner-hours
Rate
Accepted booking · £25 per cleaner-hour
Line subtotal
Calculation · 4 × £25 = £100
Billing recipient
Customer record · Accounts team
Decision
Approve & send, or return for correction
Source connections are revealed at this final review. Approval applies to the reviewed invoice and recipient.
4. Output
Sent customer invoice
After the owner approves, the workflow issues the invoice, sends it to the recorded billing contact and records the outcome.
Job
CL-204 · Cedar Offices
Invoice line
Office clean · 4 cleaner-hours at £25
Line subtotal
£100
Approval
Maya · final invoice and recipient
Delivery
Issued and sent to Accounts team
History
Sources, question, reply, calculation and approval retained
The completed job now has a recorded invoice and send outcome.

What would your proof measure?

Time from completed job to a correctly approved and sent invoice, including reply matching, quantity checks and final review. Track waiting for the team separately from active handling time.

This example uses an invented business and reports no measured saving. Your call would agree your own baseline and the one result that matters.