PitchAI Agent Engine Define a process

PitchAI Agent Engine

Automate one office process. Prove it works. Then choose the next.

PitchAI handles recurring administration across inboxes, documents, calendars, CRM and project records. Start with one defined process at zero initial cost. Pay when the agreed work is completed and validated.

Define your first process See the five steps
  • 01No setup fee
  • 02One process to start
  • 03Human checkpoints for sensitive actions

Example process

Inbox follow-up

Working
Run0148
OwnerOffice admin
Started byInbox event
  1. New reply receivedSource message attached
    Checked
  2. Account record reconciledContact and open item matched
    Checked
  3. Follow-up preparedOne open decision highlighted
    Review
  4. Calendar and reminder updateRuns after the checkpoint
    Waiting
  5. Completion receiptResult and evidence returned
    Waiting
P
Next checkpointApprove the prepared follow-up

Example interface Your process uses its own steps, evidence and authority.

A small first decision
01

Zero initial cost

There is no setup fee for the standard first-process start.

02

One process

Agree a clear beginning, end and completion rule before work starts.

03

Pay for completed work

Review the result and its evidence. Only completed and validated work is billable.

How it starts 01

Start with work you can point to.

Choose a process that happens often, takes time and has a result your team can recognize.

  1. 01

    Define

    Name what starts the process, what done means and where a person must decide.

    Completion rule
  2. 02

    Connect

    Give the process approved access to the inbox, document, calendar, CRM or project record it needs. The first process can begin inside your current operating setup.

    Approved sources
  3. 03

    Run

    The Engine checks the source, completes the agreed steps and keeps the work visible. Recurring work keeps its place while urgent work takes priority.

    Visible work
  4. 04

    Validate

    Review the returned update, document, record or evidence against the completion rule. Sensitive and external actions stop at the agreed checkpoint.

    Result + evidence
  5. 05

    Repeat or expand

    Keep the process, adjust it, stop it or choose the next one. You choose when to expand.

    Your decision

Processes 02

The office work that keeps returning.

Start where your team copies, checks, chases or rebuilds the same context every week.

Process 01 Good first process

Inbox follow-up

Check for the authoritative reply, update the working record, prepare the next action and stop the reminder when the loop is closed.

Source
Shared inbox and open follow-up
Work
Match the reply, update the record and prepare the next action
Returned
Updated case, reviewed follow-up and closed reminder
Checkpoint
Approval before an external reply

Returned with the workResult, source and completion evidence

A completed loop 03

What “done” looks like.

One example shows where the Engine works, where a person decides and what comes back for validation.

  1. 01

    Trigger

    A reply and two attachments arrive.

    The shared inbox event opens the follow-up process with the source attached.

    Received
  2. 02

    Check the source

    Match the reply to the open case.

    The expected documents are checked. One missing field is recorded.

    Checked
  3. 03

    Prepare the work

    Reconcile the files and update the checklist.

    A focused follow-up is prepared around the one open field.

    Prepared
  4. P

    Human checkpoint

    The owner decides whether to send.

    The process waits for that decision and keeps the open field visible.

    Approved
  5. 04

    Close the loop

    Update the case and close the old reminder.

    The next date is recorded with the result so stale follow-up stops.

    Completed

Working context 04

Most office processes live between systems.

The email starts the work. A document holds the evidence. The calendar carries the deadline. CRM needs the decision. The project record needs the handoff.

01InboxTrigger
02DocumentsEvidence
03CalendarDeadline
04CRMDecision
05Project recordHandoff

PitchAI works across the approved sources needed for the first process. Your team keeps its working systems while the Engine carries the context from one step to the next.

We agree the exact access while defining the process. When a source cannot be reached reliably or safely, that step stays visible for a person.

Control and evidence 05

See the work, including the exceptions.

Every process has the operating details your team needs to review what happened and decide what happens next.

01

Visible state

See what is waiting, working, ready for review or finished.

02

Source and owner

Keep the incoming item, responsible lane and next handoff attached to the work.

03

Evidence at completion

Return the document, update, record or receipt that shows the agreed step was completed.

04

Human checkpoints

Keep sending, submission, signature, purchase and sensitive record changes under the authority your process requires.

05

Durable schedules

Recurring checks and reminders wait safely when urgent work takes priority.

06

Controlled improvement

Repeated work can suggest a better procedure. A person reviews the suggestion before it becomes the operating rule.

Commercial model 06

Pay for the result you defined.

The first process begins with a completion rule. The standard start has no setup fee.

Before the run

We agree the trigger, required steps, evidence, human checkpoints, result that counts as complete and price for that result.

After the run

You review the returned result against that rule. Only completed and validated work is billable. An incomplete run stays visible with its current state.

After it proves useful

Keep running the process, adjust it, stop it or scope the next one. You can choose a custom implementation or broader commercial arrangement later.

Practical questions 07

Before the first process.

A useful process has a recognizable finish, a current owner and a clear line for human authority.

01Which process should we start with?

Choose a repeated process with a clear trigger, a recognizable finish and a current owner. Good first candidates involve checking, reconciling, preparing, updating or reminding.

02Do we need to replace our current software?

No. The first process uses approved access to the sources it needs. When a source cannot be used reliably, that step remains with a person.

03Will the Engine send emails or submit documents by itself?

Only when that authority has been explicitly agreed for the process. Sending, submission, signature, purchase and sensitive changes can remain human checkpoints.

04What happens when information is incomplete?

The process records the missing fact or exception and routes it for review. An unresolved case stays open.

05What exactly gets validated?

The returned result is checked against the completion rule agreed before the run. That may be an updated record, a reconciled document set, a prepared follow-up, a closed reminder or another observable result.

06Can we stop after the first process?

Yes. The first process stands on its own. Keep it, change it, stop it or expand when the result justifies the next decision.

07What if we later need custom integration?

That can be scoped separately after the process and its value are understood. The standard first-process start can begin without it.

Your first process 08

Start with the process your team keeps doing by hand.

Tell us what starts it, where the work happens and what a correct result looks like. We will define a practical first run with no setup fee.

Define your first process One process. One completion rule. A result you can review.