Flopinio logoFlopinio

Request-to-invoice walkthrough

See how Flopinio handles client work from intake to invoice.

Follow one sample Northstar Health Labs request in four steps. This overview uses Acme Research Demo records. It does not create work or send invoices.

Read the four-step overview Try the sandbox after sign-in
1Capture request 2Plan delivery 3Track and review 4Invoice evidence

Step 1 of 4

External Inbox to urgent request

A connected Gmail item enters External Inbox with its source intact. The operator reviews the client, project, urgency, and suggested destination before creating work.

Why it matters

Incoming context stays reviewable instead of silently becoming a task with missing details.

What to check
Confirm the client signal and choose what record should exist.
What happens next
Source evidence remains linked when the item becomes a request.
Next: Plan delivery

Acme Research Demo

External Inbox

Sample data — not a customer account

Gmail · received today at 09:12

Urgent

Northstar needs rollback guidance before the 3 PM steering call

The appointment-confirmation flow is blocked. Preserve the client message, confirm the affected launch project, and route it for review.

Suggested record

Request

Client

Northstar Health Labs

Project

Patient portal launch

Step 2 of 4

Project hub & active work

The accepted request is connected to the Northstar launch project and a priority task, alongside current health and delivery evidence.

Why it matters

The project becomes a live execution hub instead of a passive folder.

What to check
See the blocker, owner gap, and next task together.
What happens next
The request, project, task, and note retain their relationships.
Next: Track and review

Acme Research Demo

Delivery

Sample data — not a customer account

Project health · needs attention

Northstar patient portal launch

Same-day coordination is active and the rollback checklist still has owner gaps.

Priority task

Close rollback-checklist ownership gaps

Linked to the originating request, delivery note, and launch project.

Step 3 of 4

Track work and review AI suggestions

Tracked time and an AI review use the same linked requests, tasks, and notes. Review the suggested client action before approving it.

Why it matters

Check the source records and proposed action before deciding.

What to check
Review the evidence and decide whether the client-facing action should proceed.
What happens next
The review and approval history stay attached to the work.
Next: Invoice evidence

Acme Research Demo

Execution

Sample data — not a customer account

Tracked time

01:18:42

Northstar launch coordination

AI review · complete

Fallback release plan prepared from linked evidence

The suggested client update uses the request, task, delivery note, and tracked time. Sending remains an explicit approval step.

Pending human approval

Step 4 of 4

Invoice & billing evidence

Tracked launch work becomes invoice evidence without losing the tasks, notes, or request that explain it.

Why it matters

Billing is more reliable when it follows delivery evidence instead of month-end reconstruction.

What to check
Review included work and confirm the evidence before sending.
What happens next
Time, invoice preparation, and delivery provenance remain connected.
Try this in a sandbox

Acme Research Demo

Billing

Sample data — not a customer account

Draft invoice evidence

Northstar Health Labs · July

Portal launch coordination12.5h
Rollback preparation4.0h

Invoice evidence

16.5h

Time is linked to tasks, notes, and the originating request. Final invoice review and send remain explicit.

Trace the sample invoice evidence

Run the same flow with your own client work.

Sign in, open Workspace setup, and choose Try a sandbox demo. This creates a separate workspace with sample tasks and a sandbox invoice. Your real client workspace stays separate.

Open workspace setupBack to homepage