---
title: "Customers"
sidebarTitle: "Overview"
description: "Client-specific process documentation — how Profit Builders runs the close, reporting, and recurring services for each engagement."
icon: "building"
---

> **For AI agents:** the complete documentation index is at [llms.txt](/llms.txt). Append `.md` to any page URL for its markdown version.

This section holds **client-specific** process documentation: how Profit Builders actually runs the close, the reporting, and the recurring services for a named engagement.

It is deliberately separate from the rest of the Internal KB:

| Section | What it answers |
|---|---|
| [SOPs](/internal/sops/overview) | What the firm requires, for every client. |
| [How-To Guides](/internal/how-to/overview) | How to operate a system — which buttons to click. |
| **Customers** | How *this* client's engagement is run: their entities, systems, workpapers, calendar, and people. |

<Warning>
  Pages in this section contain client financial detail, account numbers, loan identifiers, and named client contacts. They are for internal PBI staff only and must not be shared outside the firm or copied to a client-facing site.
</Warning>

## Engagements

<Columns cols={2}>
  <Card title="Rackson Restaurants Group" icon="burger" href="/internal/customers/rackson/overview">
    Two entities on Sage Intacct — Burger King (RRS) and Dave's Hot Chicken (RCY). Full-cycle outsourced accounting plus weekly operational reporting.
  </Card>
</Columns>

## What belongs on a client page

Add a client section when the engagement has process detail that is **specific to that client** and would be wrong to generalize into a firm-wide SOP — a bespoke workpaper set, a client-specific close calendar, named client contacts, or a reporting package built for their org structure.

Keep firm-wide method in the SOP library and link to it, rather than restating it per client. A client page should say *what is different here*, not repeat what the firm already documents once.

## Structure to follow

Each client section follows the same shape, so a preparer moving between engagements knows where to look:

<AccordionGroup>
  <Accordion title="Engagement overview">
    The entities, systems, scope, and a map of everything else in the section. This is the page a new team member reads first.
  </Accordion>
  <Accordion title="Key people">
    Who owns what on both sides, and who to contact when a number doesn't tie.
  </Accordion>
  <Accordion title="Close calendar">
    The cadence — what happens on which workday, and what gates what.
  </Accordion>
  <Accordion title="Workpapers">
    One page per workpaper category, each listing the GL accounts, purpose, steps, and source files.
  </Accordion>
  <Accordion title="Review process">
    How the preparer's work gets reviewed, account by account.
  </Accordion>
  <Accordion title="Processes">
    Step-by-step system walkthroughs specific to the client, with screenshots.
  </Accordion>
  <Accordion title="Reference">
    Report inventories, GL mappings, distribution lists, and other lookup material.
  </Accordion>
</AccordionGroup>