AI reports

AI writes the draft. A person signs it off.

Weekly project reports are assembled from active tasks, the Gmail thread, and the Slack channel, then held as a draft. The model proposes a status; approving it is what makes it real. Client update emails skip AI entirely.

context sources
3context sources
human approval
1human approval
AI in client email
0AI in client email

Harborview Logistics — Onboarding

Weekly progress report

Draft
Context 4 active tasks Gmail thread Slack channel

The model proposes a status. It never sets one.

How it works

The path a record actually takes.

  1. 01

    Context is gathered

    Active tasks on the project, the Gmail thread with the customer, and the project's Slack channel.

  2. 02

    A draft is written

    A summary of where things stand, plus a proposed project status and the risks worth naming.

  3. 03

    A person decides

    Approve and the status is written to the project. Reject and the draft is discarded — the project is untouched.

  4. 04

    Clients get the computed version

    Client update emails render from milestone and task state through your own template. No model touches what a customer reads.

Client updates

What the customer reads is computed.

Client update emails render from milestone and task state through your own template. No model touches them, because nothing reviews them before they land in a customer's inbox.

Harborview Logistics — weekly progress

To dana.ruiz@harborview.co

No AI
Source milestone + task stateProject progress · v3

Hi Dana — here is where the onboarding stands this week.

  • Kickoff & discoveryComplete
  • Implementation2 of 3 tasks done
  • HandoverNot started

Training is booked for next Tuesday. Reply here if anything looks off.

Computed, not written. Nothing to review.

Sent 09:00

What you get.

Drafted, never published

The model proposes a status. It never sets one.

Task context

Reads what is actually open on the project right now.

Gmail thread context

Read-only access to the conversation with the customer.

Slack channel context

Pulls the project channel where delivery is actually discussed.

Deterministic client updates

Computed from milestone and task state — nothing to hallucinate.

Weekly or on demand

Run on a schedule, from a button, or from a workflow trigger.

Worth knowing

The model cannot change a project

Project status is only ever written by a person approving a draft. There is no path where generated text updates a record on its own.

Keep going.

Projects & tasks

Built automatically the moment a lead is won.

Read more

Notifications

In-app and browser push from a single dispatch.

Read more

Reports

Leads, tasks, automations, projects, and billing.

Read more
Start hereYour next won deal

Never rebuild the same project twice.

We set up your workspace and your first admin. Your team joins by invite, and the next deal you close arrives as a project that is already moving.

  • We set up your workspace
  • Your team joins by invite
  • Bring the pipeline you have

Prefer to talk first?

  1. Deal marked Closed/Won

    One status change

    01

  2. Project, milestones, 5 tasks

    Drafted from the conversation

    02

  3. #harborview-onboarding

    Channel opened, kickoff posted

    03

  4. Owner notified

    In-app and browser push

    04

Every step above runs from one status change.