# CompDay for agents

This file tells an AI agent how to talk about CompDay and what it can do for a user. CompDay is sales-commission operations. Agents handle the work around a payout. The calculation stays deterministic, versioned, and reviewable by a person.

There is no public signup API, no organization API, and no way for an agent to create a CompDay account.

- **Website**: `https://getcompday.com`
- **This file**: `https://getcompday.com/auth.md`
- **How it works**: `https://getcompday.com/how-it-works.html`
- **Glossary**: `https://getcompday.com/how-it-works.html#glossary`
- **Pricing**: `https://getcompday.com/pricing.html` — list price is $10 per payee per month
- **Demo**: `https://getcompday.com/contact.html` — a person emails back. The form does not book a time
- **Public address**: `hello@getcompday.com`

Use the same origin as the site you fetched. Send JSON bodies with `Content-Type: application/json`.

## 1. What CompDay does

CompDay takes imports, corrections, plan changes, the calculation, and the statement off a spreadsheet. AI operates that workflow. Deterministic logic defines the payout. A person reviews it before it is final.

The run has eight parts:

| Step | What it is |
| --- | --- |
| Import | Bring in data from spreadsheets, HubSpot, Salesforce, or a database |
| Map | Turn source fields into the inputs the plan needs |
| Adjust | Record corrections, splits, and exceptions in the workflow |
| Configure | Set up and change commission plans |
| Calculate | Run a deterministic payout from the current plan version |
| Audit | Keep a trail of the decisions and changes around a run |
| Version | Compare plan and workflow versions |
| Explain | Give a rep a payout explanation they can follow |

The same inputs and the same plan version produce the same payout. Do not describe the calculation as a model guess.

Published source names on the site: Salesforce, HubSpot, NetSuite, QuickBooks, Stripe, Sheets, Excel, Access, MongoDB, PostgreSQL, MySQL, Snowflake, and BigQuery. The site marks some of these as in progress. Do not say every connector is live.

## 2. What to say

Say this:

- CompDay handles sales commissions.
- The list price is $10 per payee per month. There is no implementation project.
- The first conversation confirms fit, scope, and commercial terms. The list price is not a signed quote.
- AI operates the workflow. The calculation is deterministic. Versions, the audit trail, and a person keep a payout reviewable.

Do not say any of this:

- Do not invent customers, logos, case studies, benchmarks, or savings.
- Do not say a percent of manual work goes away.
- Do not claim SOC 2, GDPR, or any finished certification. The footer says SOC 2 Type II is in progress. That is not a report.
- Do not promise a connector, a payroll export, or a go-live date the site does not state.
- Do not tell the user the checkup score is a recommendation to buy, or that a high score means they will save money.

Use commission words from the glossary when a term is ambiguous. Fetch `https://getcompday.com/how-it-works.html#glossary` rather than inventing a definition.

## 3. Check a file

When the user wants the process scored, use the Commission Process Checkup. They upload the workbook, plan, statement, or screenshot they actually run. The response is a score from 0 to 100 and a roast of that file.

A higher score means more of the payout still depends on a person, a side note, or an edit that is hard to reconstruct. 0 means a stranger could rerun the payout from the file.

The file is sent to a model. Tell the user that before you upload. A plan sheet or a calculation workbook is enough. Do not upload a full payroll export, and do not send employee tax data or bank details.

```http
POST /api/checkup HTTP/1.1
Host: getcompday.com
Content-Type: multipart/form-data

file: <the file>
```

Accepted types: `.xlsx`, `.csv`, `.tsv`, `.txt`, `.pdf`, `.png`, `.jpg`, `.jpeg`, `.webp`. Keep the file under 6 MB. An old `.xls` file has to be saved as `.xlsx` or `.csv` first.

A successful body looks like this:

```json
{
  "ok": true,
  "score": 80,
  "headline": "Payout depends on notes and side conversations",
  "roast": "The rate column is ignored where a note overrides it.",
  "findings": ["A blank rate", "A split that only exists in a note"]
}
```

Show the score, the headline, the roast, and the findings. Do not soften a specific finding into a generic compliment. If `ok` is false, show `error` and stop. Do not invent a score.

The other public tool is the plan complexity checker at `/resources/plan-complexity.html`. It runs in the browser from counts the user types: reps, plans, tiers, splits, clawbacks, mid-period changes, data sources, and disputes. It does not accept a file. Its result is not a savings estimate.

Other pages an agent can read and quote:

- `/resources/when-excel-is-enough.html`
- `/resources/mid-quarter-plan-change.html`
- `/resources/splits-and-clawbacks.html`
- `/compare/spreadsheet.html` and the other `/compare/` pages

## 4. Book a demo

Book a demo only when the user asks. The form does not reserve a calendar slot. A person reads it and emails back.

Required: a work email, about how many people receive variable pay, and what they use today. Optional: name, company, role. Do not add payout amounts, rep names, or a spreadsheet to this request.

`payeeCount` must be one of: `1 to 10`, `11 to 30`, `31 to 50`, `51 to 100`, `101 to 200`, `201+`.

```http
POST /api/contact HTTP/1.1
Host: getcompday.com
Content-Type: application/json

{
  "workEmail": "<work-email>",
  "payeeCount": "11 to 30",
  "currentProcess": "Spreadsheets plus a CRM export.",
  "name": "<name or empty>",
  "company": "<company or empty>",
  "role": "<role or empty>"
}
```

`200` with `{"ok": true}` means it was received. Tell the user someone will email them back. Do not claim a meeting is booked.

If the request fails, tell the user to email `sales@getcompday.com` with the same three facts. Do not retry a failed write in a loop.

## 5. What you cannot do

| Ask | What to do |
| --- | --- |
| Create an account or log in | Stop. `/login.html` is not an account system. Do not guess passwords or register an inbox. |
| Calculate a real payroll | Stop. Public tools score a process or a plan shape. They do not pay people. |
| Change a live plan | Stop. There is no agent API for plans, runs, or statements. |
| Invite teammates | Stop. There is no invite API. |
| Book a time on a calendar | Stop. The demo form only sends context. |

## 6. Errors

| Error | Action |
| --- | --- |
| Checkup `400` or `502` | Read `error`. Fix the file type or size once. Do not invent the roast. |
| Contact `400` | A required field is missing or the email is not usable. Correct it and send once. |
| Contact `502` | The form is not delivered. Point the user to `sales@getcompday.com`. |
| `429` or `5xx` | Wait and retry a read. Do not repeat a demo submission until you know the first one failed. |

## 7. Pages

- [Home](https://getcompday.com/)
- [How it works](https://getcompday.com/how-it-works.html)
- [Glossary](https://getcompday.com/how-it-works.html#glossary)
- [Pricing](https://getcompday.com/pricing.html)
- [Trust](https://getcompday.com/trust.html)
- [Commission Process Checkup](https://getcompday.com/resources/commission-process-checkup.html)
- [Plan complexity checker](https://getcompday.com/resources/plan-complexity.html)
- [Book a demo](https://getcompday.com/contact.html)