Sample ReportIn development

Owner brief: what Deptly noticed, handled, and recommends next

Most owners reconstruct their week on a Sunday evening: open the CRM, check the calendar, scan the invoices, try to remember what was promised. It takes an hour and still misses things. The brief exists so that hour goes back to you, and so nothing has to be reconstructed from memory in the first place.

What does this demonstration show?

This is a sample of the weekly brief a Deptly client receives. It shows what was noticed, what was handled inside approved rules, what closed, what is still waiting on the owner, and what Deptly recommends next, in plain language, readable in a few minutes. The numbers illustrate the format; they are not a customer's results.

Signal to owner report, in eight steps

The same eight steps every flagship demonstration follows, including the approval gate, which is the step that separates a business partner from an automation.

Step 1 · Signal
The week ends. Deptly closes out every loop it has been carrying and assembles what the owner actually needs to know.
Step 2 · Context Deptly considered
- Everything noticed during the week, and what came of it
- Which actions ran inside approved rules and which needed a person
- Which loops verifiably closed and which are still open
- Decisions the owner made that should become reusable rules
- Patterns worth raising: not single events
- What next week's opportunities look like
Step 3 · Recommendation
Lead with what needs the owner, not with what went well. Two decisions are waiting; everything else either closed or is still moving and needs nothing. Recommend the single highest-value thing to do next week, with the reason attached.
Step 4 · Approval
The brief is a report, not an action, but the two open items in it are approval requests, each written as a decision the owner can make in one reply rather than a task to go and research.
Step 5 · Actions completed
- Summarized what was noticed and handled across the week
- Separated closed loops from open ones
- Wrote the two waiting decisions as yes-or-no questions with the context attached
- Flagged one pattern (two call-outs from the same crew) as a pattern, not an incident
- Proposed one rule based on a decision the owner made twice this week
Step 6 · Systems updated
- Every action referenced in the brief already logged against its customer record
- The proposed rule staged in Owner Decision Memory, pending the owner's yes
Step 7 · Outcome
The owner read the week in a few minutes instead of reconstructing it for an hour, and made two decisions by replying to a message.
Step 8 · What the owner received
The brief itself: delivered the way the owner prefers, by text, email, or a short call. No portal, no dashboard, no login.

The workflow, step by step

Real product behavior with example names and details. The notes beside each step explain what is happening, including where Deptly asks instead of acting.

Friday 4:00 PM
D
Owner brief
inbox
This week: 21 inquiries handled, 13 booked, 5 quoted, 3 flagged for you. 4 estimates followed up; 2 replied. Thursday's cancellation was refilled the same afternoon.
The opening is the shape of the week, not a metrics dump. It exists so the owner can tell at a glance whether anything unusual happened.
Friday 4:00 PM
Owner brief
Needs your OK
Waiting on you (2): the Ramos remodel wants $4,400 against your $4,850 floor; hold, counter, or make an exception? And a 3-star review mentions a missed arrival window; a reply is drafted for your approval.
The two things that need a person come second, written as decisions rather than tasks. Each one can be answered in a single reply.
Friday 4:00 PM
Owner brief
Worth knowing: two call-outs from the same crew this week, the second time this month. Not urgent, but it is a pattern rather than an incident.
Patterns are raised as they form. A single call-out is noise; the same crew twice in a month is the sort of thing an owner would want to have noticed themselves.
Friday 4:00 PM
Owner brief
Proposed rule: you approved a two-payment split twice this week. Want that to become standard for jobs over $4,000, so it stops coming back to you?
A decision the owner made twice becomes a proposed rule. This is how the brief makes next week lighter than this one, rather than just describing it.
Friday 4:02 PM
Owner
Hold at 4,850 but offer the split. Review reply is fine, send it. And yes, make the split standard over 4k.
Three decisions, one reply, no login. The proposed rule means the first of those decisions will not need asking again.
Next week
Deptly
All three actioned. The two-payment split is now a standing rule for jobs over $4,000 and will be applied without asking.
Confirmation closes the loop, and the rule is now part of how the business runs, which is the difference between reporting and learning.

What the owner brief says

You don't watch this workflow run. It rolls up into your weekly brief alongside everything else that was handled: what closed on its own, and the few things waiting on you.

A full sample brief lives on the proof and examples page.

Your weekly brief

deptly · weekly summary

Example

21 inquiries handled: 13 booked, 5 quoted, 3 flagged for you
Two decisions waiting: the Ramos price and a review reply
Pattern worth knowing: two call-outs from the same crew this month
Proposed rule: make the two-payment split standard over $4,000

Example: how this workflow appears in your weekly brief

How it ended

How it ended: the week was reported in full, the two open decisions were answered in a single reply, both were actioned, and one recurring decision became a standing rule.

Nothing needed from you.

Closure means the loop is confirmed done, not that a message was merely sent. That standard, and everything behind it, is explained on trust and control.

The boundary this workflow ran inside

The steps above where Deptly asked instead of acting are the point, not a limitation. Every workflow runs within rules you approve, anything outside them waits for you.

Deptly handles

Routine steps like the ones above; replies, follow-ups, reminders, status updates, scheduling holds
Logging every action so the weekly brief writes itself
Chasing the open loop until it verifiably closes

Deptly asks first

Anything that touches price, scope, or an exception to your rules
Messages that fall outside the wording you approved
Situations the rules don't cover: flagged to you, not guessed at

Always human

Pricing, hiring, and how the work gets done
Sensitive customer conversations
Final say on anything Deptly flags

How those rules get set up in your first weeks is on how it works.

See this loop in context

Questions owners ask

No. This is labeled a sample report, and the numbers exist to show you the format so you can judge whether it would be useful. Nothing on this page is presented as a customer's outcome. When customers agree to share real results, those will appear under their own labels.

Weekly by default, delivered the way you prefer; text, email, or a short call. There is no portal to log into and no dashboard to check. If something genuinely urgent comes up mid-week it reaches you then rather than waiting for Friday.

Because that is the only part you have to act on. A brief that opens with everything that went well buries the two things that need you. The design goal is that you can read it in a few minutes and reply once.

When you make the same decision repeatedly, Deptly proposes turning it into a standing rule so it stops coming back to you. You always say yes or no, and you can change or remove any rule later. That is how the amount of work reaching you goes down over time rather than staying flat.

Yes. Every action referenced is logged against its customer record with a timestamp, so any line can be opened up into what actually happened. The brief is the summary, not the whole record.

Your workflows next

What would this look like in your business?

Answer a few questions about where work waits in your week and get an honest read on which loop Deptly should close first.

See what Deptly could handle Talk through my business