> ## Documentation Index
> Fetch the complete documentation index at: https://docs.apollospace.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Professional services

> Law, accounting, and consulting firms: proposals, deadlines, document drafting, and client relationships under pressure — with the opinion and the signature always a professional's.

It's 6pm and the partner still hasn't sent the proposal he promised for today.
A client is asking on WhatsApp where their case stands, a filing is due the day
after tomorrow and nobody remembered, and the draft opinion has been open on
the same sentence for three days. The firm isn't idle — it's drowning in things
that only need hands, not judgment.

**What leaves your plate:** drafting the first version of proposals and
recurring documents, watching deadlines and obligations, keeping every matter
and file in its place, and answering "where does my case stand?" all start
happening on their own — with context, within budget, and with **the technical
opinion, the filing of record, and the contract always in a professional's
hands.**

## How it works, in one line

Professional service is, at bottom, **qualified time that can't be spent on
busywork.** The agent doesn't issue an opinion or sign anything — it takes the
friction out of everything around the work (draft, deadline, organization,
status) so the lawyer's, accountant's, or consultant's hours are freed for
what only they can do.

```mermaid theme={null}
flowchart LR
    A[Trigger<br/>proposal request, deadline nearing,<br/>meeting ended, client asks] --> B[Agent pulls context<br/>from Company Brain + CRM + Folders]
    B --> C[Decides + uses tools<br/>Documents, Boards, Routines, Chats]
    C --> D{Opinion, filing,<br/>contract or fee?}
    D -->|No| E[Drafts / organizes / reminds / answers status]
    D -->|Yes| F[Proposes + calls the professional<br/>with the piece ready for review]
    E --> G[Becomes memory<br/>the next matter starts faster]
    F --> G
```

## Concrete flows

### 1. Draft proposals and recurring documents from templates + Brain

**Trigger:** a proposal request comes in — a new lead in the
[pipeline](/en/features/crm), a prospecting meeting that just ended, or the
partner saying "put together the proposal for client X."

[Athena](/en/agents/athena), the organization's operator, pulls from the
[Company Brain](/en/features/brain) the template for that kind of work — the
proposal structure, the standard scope, the clauses the firm always uses — and
cross-references the client context that already lives in the
[CRM](/en/features/crm) and the meeting notes. It then assembles the **first
version** in a [document](/en/features/documentos): scope, deliverables,
suggested timelines, and the fee structure **left blank for the partner to
fill in.** The same pattern serves recurring documents — a standard draft, a
set of minutes, a monthly report, a routine notice — where 80% is repetition
and 20% is judgment.

<Note>
  The agent delivers a **draft for review**, never the final version. Fee
  amounts, commercial terms, and any clause that becomes a commitment are left
  for the professional to decide and sign — the agent prepares the frame, you
  fill in what requires judgment.
</Note>

### 2. A deadline-watcher for filings and obligations

**Trigger:** a [routine](/en/features/rotinas) the agent schedules for itself —
every morning, it sweeps matters and obligations with a date approaching.

On each run, the agent cross-references what's in the
[Company Brain](/en/features/brain) and on the boards (procedural deadlines,
compliance and filing due dates, contracted deliverables, renewal dates)
against the calendar, and surfaces **what's due in the next few days and still
has no owner or movement.** It opens a [task](/en/features/boards) assigned to
the person responsible, logs the activity on the matter, and raises a
[proactive notification](/en/features/rotinas) on the bell of whoever needs to
act — before the deadline turns into a fire.

<Warning>
  The watcher **reminds and organizes** — it doesn't file, doesn't petition,
  and doesn't meet the obligation for you. The filing of record, meeting the
  deadline, and the technical responsibility are always a professional's. A
  reminder on the right day is a relief; an automatic filing without review is
  a risk.
</Warning>

### 3. Keep every matter and document organized — and answer the client's status question

**Trigger:** any movement on a matter — a document arrives, a stage changes,
the client replies — or a direct question: "where does my case stand?"

The agent files every document in the client's and the matter's
[folder](/en/features/pastas), keeps the [CRM](/en/features/crm) current with
the stage and activities, and keeps the history alive — whoever opens the panel
sees today's truth, not yesterday's snapshot. And when the client asks in
[chat](/en/features/chats) or on [WhatsApp](/en/integrations/whatsapp) where the
work stands, the agent answers **from what already exists** in the Brain and the
CRM — the logged progress, the next step, what's pending and from whom.

<Info>
  **Why this matters:** much of the dissatisfaction in a firm doesn't come from
  the technical result — it comes from silence. A client who doesn't know where
  things stand assumes they've been forgotten. A status answered on the spot,
  from information that already exists, holds the relationship without consuming
  the partner's hours. If the question calls for technical interpretation ("so
  does that mean I won?"), the agent **doesn't opine**: it logs it and escalates
  to the professional.
</Info>

### 4. Turn a meeting outcome into tasks

**Trigger:** a client meeting ends and the notes (or the summary) enter the
[Company Brain](/en/features/brain).

The agent reads the decisions and the commitments, identifies **who agreed to
do what and by when**, and turns each commitment into a
[task](/en/features/boards) on the board — assigned to a person or an agent,
with a due date, linked to the right matter. What was a "we agreed to send the
draft by Friday" buried in the minutes becomes a trackable item that doesn't
depend on anyone remembering.

```mermaid theme={null}
flowchart TD
    A[Meeting ends<br/>notes enter the Brain] --> B[Agent extracts<br/>decisions + commitments + dates]
    B --> C[Creates tasks on the board<br/>with owner and due date]
    C --> D{Commitment is a technical<br/>or commercial deliverable?}
    D -->|Operational| E[Agent runs / reminds / follows up]
    D -->|Opinion / proposal / contract| F[Task for the professional<br/>to review and sign]
```

## What stays human

<Warning>
  In professional services, responsibility has a name. The agent **proposes and
  prepares, never decides or signs on its own**, when it comes to:

  * **Opinion and technical advice** — legal, accounting, or strategic
    interpretation. Always a qualified professional's.
  * **Filing of record and registered acts** — petition, defense, declaration,
    compliance filing, any act that binds the firm or the client.
  * **Fees and contracts** — amount, terms, billed scope, any term that becomes
    a financial or service commitment.
  * **A commercial proposal sent to the client** — the draft is the agent's; the
    send is yours.
  * **Regulatory or legal communication**, governance decisions, and destructive
    actions.

  In these cases the agent prepares everything — the draft, the reminder, the
  context, the document — and **waits for a person's approval**. Every action
  stays in the auditable trail, with author and rationale, isolated per
  organization and LGPD-aligned.
</Warning>

## Where to start

<Steps>
  <Step title="Teach your templates to the Brain">
    Upload to the [Company Brain](/en/features/brain) the templates your firm
    repeats — proposal structure, standard drafts, obligation checklists, the
    process answers you give every week. That's where the agent pulls what to
    draft and what to watch.
  </Step>

  <Step title="Schedule the deadline-watcher">
    Create a [routine](/en/features/rotinas) that sweeps matters and obligations
    and surfaces what's due. One agent, one cadence, one channel — and autonomy
    grows like a ratchet, never a leap.
  </Step>

  <Step title="Let the agent prepare the first version">
    On the next proposal request or recurring document, ask the agent for the
    draft and review it instead of starting from scratch. Start with human
    approval before any external send.
  </Step>
</Steps>

## Next steps

<CardGroup cols={2}>
  <Card title="Back office & operations" icon="folder-tree" href="/en/use-cases/backoffice">
    The same pattern of collection, checking, and organization applied to the
    everyday paperwork.
  </Card>

  <Card title="Documents" icon="file-lines" href="/en/features/documentos">
    Where agents draft and edit proposals, drafts, and reports for your review.
  </Card>

  <Card title="Routines" icon="clock-rotate-left" href="/en/features/rotinas">
    The proactive daemon that watches deadlines and chases what's stalled,
    without a frantic Friday.
  </Card>

  <Card title="Management & coordination" icon="users-gear" href="/en/use-cases/management">
    How each matter's work becomes a board, a task, and a follow-up.
  </Card>
</CardGroup>