Morning brief

Start the day with a written point of view.

This is the surface the homepage is talking about: a client-ready morning brief that tells the team what changed, what to trust, and what should happen next.

01

Findings

What moved overnight, what looks unusual, and which clients need attention first.

02

Trust notes

Freshness, missing inputs, and confidence cues so nobody mistakes incomplete data for clean data.

03

Next actions

The exact follow-through the team should take while the context is still warm.

Overnight · 22:00 → 06:40

How the brief gets assembled while the firm sleeps.

Six stages, running automatically overnight. Hover to pause, or click a stage to focus it.

22:00 · Stage 01

Day closes

The record freezes on today's state. Open tasks, flagged items, and unresolved observations are captured as the baseline.

Baseline captured · 312 open items

Auto-advancing · hover to pause22:00 → 06:40 · 8h 40m window

Novatrai workflow

One operating system, two sides of the same record.

Practices and business owners see different work, but the workflow is one shared loop: context comes in, AI prepares, humans decide, and follow-through stays attached to the same operating trail.

For practices

The firm starts with context, not reconstruction.

This is the practice-side operating loop: intake, prepared review, active service work, filing pressure, and follow-through staying in one system.

  1. 01

    Client record opens the operating trail

    Contacts, documents, billing posture, open work, and trust notes start in one record instead of across disconnected tools.

  2. 02

    Data and documents arrive before review begins

    Bank feeds, ledger syncs, uploads, and workflow status create a usable picture before anyone starts asking around.

  3. 03

    AI prepares the first pass

    Extraction, categorization, and prep artifacts arrive already assembled so human judgment can start higher up the stack.

  4. 04

    The Morning Brief writes the point of view

    The team sees what moved, what is reliable, what is blocked, and what should happen next while the context is still warm.

  5. 05

    Cases keep service work attached to the file

    Requests, replies, tasks, and drafts stay tied to the same client record so ownership and handoff stay obvious.

  6. 06

    Filing, billing, and follow-through close the loop

    Preparation, approvals, invoicing, and collections stay visible inside the same rhythm instead of leaking into side systems.

For business owners

The owner, the AI, and the accountant stop working from fragments.

This is the business-side loop: run the company, let the AI keep the books moving, and let the accountant step into the same operating context.

  1. 01

    The business connects once

    Bank accounts, accounting software, documents, and the core business record are set up in one place.

  2. 02

    AI keeps the background work moving

    Transactions are categorized, documents are read, and anomalies are flagged without turning the owner into the bookkeeping layer.

  3. 03

    Requests and approvals stay visible

    When the accountant needs something, the owner sees the request clearly and can answer it inside the same record.

  4. 04

    Client work, support, and invoicing stay attached

    Cases, customer follow-up, and receivables live next to the operating picture instead of in separate inboxes and spreadsheets.

  5. 05

    The accountant reviews and files behind the scenes

    The accountant works from AI-prepared context, verifies what matters, and completes compliance work without rebuilding the file.

  6. 06

    Reports and advice come back through the same system

    The owner sees outcomes, recommendations, and next moves in the same operating trail the work came from.

What the brief looks like

Findings, trust notes, and next actions - one screen.

The interactive mock below is the same brief that lands on the practitioner's desk at 06:40. Click Expand brief to see the full list.

Inbox / Morning Brief
Fresh at 06:40
Inbox
Clients
Briefs
Tasks
Portal

Good morning

3 clients need attention today

MC

Morrison Construction Ltd

Overnight brief with findings, trust notes, and next actions

review before send

Travel spend rose 40% this month and is materially above recent baseline, driven mostly by project-coded expenses.

Three invoices are now more than 15 days overdue. Combined exposure is $12,400.

The First National bank feed has not synced since Tuesday, so the brief is partially stale.

Confirm whether the travel spike is project-related, request the missing supplier invoices, and reconnect the bank feed before month-end close.

Trust layer

Brief confidence is adjusted automatically when bank feeds, ledger syncs, or required documents are stale.

Action layer

Findings turn into tasks, document requests, and client-ready drafts without leaving the workflow.

Why it works

The brief has to do three jobs, in the right order.

01

Written before the team logs in

The first handoff is already assembled from synced books, documents, workflow state, and open follow-through.

02

Clear about trust, not just change

The brief says when a bank feed is stale, when supporting documents are missing, and where confidence should drop.

03

Ready to act on immediately

Every finding stays close to the next move: task creation, document requests, draft follow-up, and review.

Result

The team sees the read, the trust limit, and the next action on the same screen.

Why this matters

The brief stops the first hour from turning into a scavenger hunt.

Instead of reconstructing client status across inboxes, ledger tabs, and memory, the team walks into prepared context and moves straight into review and follow-up.