referent.lawrecording brief / 06 aug 2026

Three-minute private beta video

Fewer dropped balls.
Less admin stress.

The audience is mostly solo and very small firms. They already know AI can draft. Show the outcome first: Referent turns intake and scattered firm context into controlled work, without taking professional judgment away from the lawyer.

One story
Operational chaos becomes one controlled workflow. AI prepares. The lawyer decides.
01 / Audience

Who is on the other side of the camera

The strongest shared trait is not a practice area. It is an owner-operator carrying legal work and firm operations at the same time.

438People recordsAll CRM leads live in People
89%Solo or up to 10 peopleAmong 281 leads with usable firm size
73%United StatesAmong 181 with country
476Linked notesCovering 425 current People

Shape of the known lead pool

Solo
65.8%
2–5 people
19.6%
US
72.9%
UK
25.4%

Three useful mental models

The overloaded solo

Knows every matter personally, but intake, follow-up, billing prep, and filing keep slipping.

The lean owner

Wants more capacity without hiring an admin layer. Usually decides and pays directly.

The AI-literate skeptic

Has tried generic AI. Wants reliable execution, source context, boundaries, and a human to call.

02 / Demand

What they care about

The richer interviews repeat the same jobs. The wording changes; the operational shape barely does.

Make routine work actually happen

Intake, matter opening, engagement steps, file setup, follow-ups, and reminders should run consistently instead of sinking to the bottom of the list.

7/12 forms · 6/6 usable call summaries · 9/9 debriefs

Put the practice in one context

Email, documents, notes, tasks, calendar, and current matter status should stop living across disconnected tabs and personal memory.

5/6 call summaries · 6/9 debriefs

Surface what was forgotten

Lawyers ask for overdue work, deadlines, missing follow-ups, and a quick answer to “what happened last?”

6/6 call summaries · 8/9 debriefs

Keep authority with the lawyer

Matter-specific context, editable drafts, privacy controls, source-linked summaries, audit history, and approval before client-facing action are trust requirements, not polish.

11 forms with trust answers · editability led at 7/11

Prove fit before asking for rollout

They ask for a real demo, supported integrations, clear beta scope, price-to-value, and a believable first result—not another subscription that adds manual sync.

Demo/scope: 3/6 call summaries · 3/9 debriefs

Close the remaining capture gaps

Phone calls, in-person meetings, billing systems, complex client relationships, and custom workflows are expansion asks. They are confirmed, but not a single universal request.

Medium confidence · several are not complete today
03 / Product

Connect the ask to what is already real

The video should stay on the green path. Mention the gaps only if asked; do not sell roadmap as product.

Lead asks
“Set up the client and matter without retyping everything.”
“Tell me what needs attention today.”
“Turn incoming work into the right matter or task.”
“Give me the whole matter without hunting.”
“Let AI help, but show me why and ask before acting.”
Safe to demonstrate now
Connected-source onboarding and client / matter import
Dashboard: overdue, due today, inbox, triage, schedule, activity
Triage suggestions with Create / Dismiss and destination review
Matter workspace plus State of Play, timeline, notes, email, docs, tasks
Voice/chat with matter context, source accounting, approval, activity trail

Verified against the current checked-out application code, including UI plus API/service or registered agent-tool paths. Rehearse every step in the target demo workspace before recording; code presence is not proof that each integration is enabled there. Phone-to-matter capture, in-person meeting capture, universal PMS migration, Outlook Calendar event sync, and every billing integration remain outside this demo promise.

04 / Run of show

One clean three-minute arc

Speak for roughly 2:20. Use about 35–55 seconds for clicks, loading, pauses, and product response time. Lead with the benefit; do not narrate every control.

0:00

Fewer dropped balls

Open on the outcome: less operational chaos and less admin stress—not another chatbot or a list of features.

On screenFace to camera, then Referent home.
0:20

Start from the real practice

Connect email, calendar, and documents. Show organized client files and intake becoming the right matter.

On screenCompleted import cutaway; no waiting.
0:50

What needs attention

Dashboard: overdue work, today, unlinked email, triage, schedule, time, and recent activity.

On screenOne scan; no detours.
1:15

AI prepares, lawyer decides

Inspect one source and one suggestion. Approve it or dismiss it. Make control visible instead of merely claiming it.

On screenSource → destination → decision.
1:55

One matter, one context

Show email, documents, tasks, calendar, notes, time, timeline, and State of Play together. Say what this prevents.

On screenMatter overview, then timeline.
2:30

Ask, then act

Ask one concrete matter question. If the voice timer is the cleaner rehearsed proof, substitute it here rather than adding another beat.

On screenMatter question or voice time action.
2:55

Private beta

Invite warm beta users to bring the workflow that causes the most admin stress into onboarding.

On screenPrivate beta / hands-on onboarding.
05 / Script

English teleprompter copy

304 spoken words: about 2:20 at 130 words per minute, leaving roughly 35–55 seconds for clicks, pauses, and product response time.

0:00–0:20Fewer dropped balls

Small firms do not need another chatbot. They need fewer dropped balls. Intake, email, deadlines, documents, and time live in different places, while the lawyer carries the real status of the firm in their head. Referent turns that operational chaos into one controlled workflow.

0:20–0:50Real context

Referent connects to the email, calendar, and documents the firm already uses. During onboarding, it builds clients and matters from the context already there. Instead of retyping the practice into a blank CRM, you start with organized client files and an intake flow that can turn incoming work into the right matter.

0:50–1:15What needs attention

This dashboard answers the first question every morning: what needs my attention? I can see overdue work, today's tasks and schedule, unlinked email, triage, time, and recent activity without searching across tabs.

1:15–1:55Lawyer control

Here is one incoming item. Referent reads the source and suggests the next step: file it, create a matter, or turn an obligation into a task. I can inspect the source, choose the destination, approve it, or dismiss it. Nothing high-risk happens silently. AI prepares; the lawyer decides.

1:55–2:30One matter

Now I will open one matter. Email, documents, tasks, calendar events, notes, time, and recent activity sit together. The State of Play and timeline show what changed and what comes next. The benefit is simple: less reconstruction, fewer missed follow-ups, and less administrative stress.

2:30–2:55Ask, then act

I can also ask, “What happened last in this matter, and what needs my attention next?” Referent answers from the firm's live context and prepares the next action—not conversation for its own sake, but useful work ready for review.

2:55–3:15Private beta

Referent is built for small firms that want more capacity without giving up professional judgment. If you are joining the private beta, bring the workflows that create the most admin stress. We will help you set up the first useful version with your firm.

06 / Shot list

Five visual beats worth rehearsing

Use the real application for the recording. These existing brand images are composition references, not substitutes for a working demo.

Auto-created matter card
01 · Intake becomes a matterShow the result of connected-source onboarding. Keep fake data obvious and clean.
Voice command interface with matter context
02 · Voice inside matter contextUse one rehearsed prompt. A start/stop timer command can substitute for the matter question, but should not become an extra beat.
AI suggestion with dismiss and approve controls
03 · Approval is the productPause on the source and decision. The click is more persuasive than a trust claim.
Matter-aware commands
04 · Ask about the actual practiceKeep the question concrete: last event, next action, current state.
Agent action recorded in activity
05 · Leave a traceShow that an agent action is visible in activity rather than disappearing into chat history.
07 / Guardrails

What makes the recording believable

Credibility comes from a narrow working path and clear boundaries, not from saying “AI” more often.

Do

  • Record only in a seeded demo workspace.
  • Preload one matter with email, document, task, event, timeline, and one reviewable suggestion.
  • Make every sentence answer what the feature saves or prevents.
  • Use one approval and one matter thread from start to finish.
  • If import timing varies, use a short cutaway of the completed import.
  • End on the private-beta onboarding prompt.

Do not promise

  • Phone/VXT-style automatic call capture.
  • Granola-style in-person meeting capture.
  • Turnkey migration from every legacy PMS.
  • Outlook Calendar event sync or every accounting/billing integration.
  • Autonomous legal judgment or unreviewed outbound action.
  • A lawyer/paralegal replacement, competitor comparison, or roadmap-only workflow.
Copied