Customers · People

The record of each person, from first touch to payment.

Everything a person did arrives as events from any system, the stage comes from what they did, and agents take the next step, on their own or through you.

You sign in with a code sent to your e-mail. One base per account, no workspace and no context switcher. The dashboard is in Portuguese for now.

Why this exists

Knowing who a person is is easy. The hard part is knowing WHERE THEY ARE NOW.

Lead, prospect and customer are the same person at three moments, and the market sells one tool for each. The result is the same story split across three places, with a stage someone has to remember to type.

  • The "stage" column in the spreadsheet is right on the day someone updates it
  • The same person shows up twice, with different e-mails
  • Someone who paid and never started using it only shows up when they ask for a refund

The whole path

Events come in, the record builds itself, the agent proposes.

Four blocks, and only the first one needs you in the dashboard.

1 · Create the source

Each of your systems gets an address and a secret

You create the source in the dashboard with a name and a declared legal basis: contract, legitimate interest or consent. The secret is shown once. When you rotate it, the old one keeps working for 24 hours, so nothing stops halfway.

dashboard
Dashboard › Data › Sources › New source

name          Class platform
legal basis   contract

-> address    https://people.worker.mycustomers.click
             /events/<source-id>
-> secret     whsec_…   (shown once)

2 · Send the signed event

Any language that can compute an HMAC can send to People

Standard Webhooks with the x-ccm headers, and the body is always {type, timestamp, data}. Outside the 5-minute window, the delivery is refused. The same id again is a resend and does not duplicate. The type is your system’s own vocabulary.

javascript
import { createHmac, randomUUID } from 'node:crypto'

const id = randomUUID()
const timestamp = Math.floor(Date.now() / 1000)
const body = JSON.stringify({
  type: 'aula.concluida',
  timestamp: new Date().toISOString(),
  data: {
    person: { email: 'ana@escola.exemplo' },
    channel: 'web',
    properties: { aula: 'Primeira aula' },
  },
})
const key = Buffer.from(SECRET.slice(6), 'base64')
const sig = createHmac('sha256', key)
  .update(`${id}.${timestamp}.${body}`)
  .digest('base64')

await fetch(SOURCE_URL, {
  method: 'POST',
  headers: {
    'x-ccm-id': id,
    'x-ccm-timestamp': String(timestamp),
    'x-ccm-signature': `v1,${sig}`,
  },
  body,
})

-> 200 { accepted: 1, duplicates: 0,
        events: [{ personId, stage: 'lead',
          type: 'aula.concluida',
          translated: false, … }] }

3 · Or import the spreadsheet

The list you already have comes in as it is

An import source takes CSV through the dashboard, with headers in Portuguese or English. Each row becomes the person’s first touch, with identity, company and origin.

csv
nome,email,telefone,empresa,utm_source
Ana Souza,ana@escola.exemplo,,Escola Exemplo,instagram
Bruno Lima,,+55 11 90000-0000,,indicacao
Carla Dias,,,,

-> 2 people, each with their first touch
-> line 4 skipped: no e-mail and no phone
-> import again: nothing changes

4 · Check the record

The object you check: the record, with the timeline

Each event lands on the right person’s record and the stage is recalculated. If you choose the first class as activation, the first time it happens becomes account.activated at that moment.

record
Ana Souza                        prospect
ana@escola.exemplo · Escola Exemplo

timeline
  person.touched      import       lead
  account.created     web          prospect
  aula.concluida      web
  account.activated   1st class    activated

next step
  Help with the second module
  [Done]  [Change]

Model Context Protocol

Your agent reads the record and writes the next action. The check comes before everything.

There are five tools, authenticated by OAuth 2.1 with the same login as the dashboard. For reading, people_list_people, people_get_person and people_get_timeline. For writing, people_add_note and people_propose_action, which go into the same queue and through the same check.

What the server does NOT offer

  • No tool talks to a person there is no sending through the MCP, and there will not be: an agent proposes, and the message goes out only after the check and your approval.
  • The account is never an argument it comes from the token. Malicious text the agent reads cannot point a tool at another account’s base.
  • Deleting does not exist as a tool neither does creating a source or reading a secret. Deleting a person stays with you, in the dashboard, by typing their name.

In Team, the dashboard shows who is connected every MCP client the account has seen, with revoke and restore. Once revoked, each of its calls answers 401 until someone allows it again.

What it does not do

Said Up Front, So Nobody Finds Out Later

The lines that count against it stay in the table. That is what makes the others worth something.

Phone messages, calls or live conversation

No

The message goes out by e-mail through your account, or to a destination of yours by signed webhook. What happens on the other side is up to you.

Ready-made connector for another tool

No. One open protocol

No third-party tool is "integrated". Any system that signs the delivery can send, and its vocabulary is translated at the source.

Interest score or data bought from outside

No

The stage comes from events. There is no score calculated by a model, no data bought from third parties and no fingerprinting.

API key that runs the account

No

The read key only reads. The agent key reads, proposes actions and adds notes through the same checks as every agent, and approves nothing. Creating, changing and approving need a person’s login.

Automatic record merge

Never

It becomes a merge suggestion, and you decide.

Agent that sends a price offer

You choose

In Automatic approval it goes out on its own. In "Goes through you", it waits for your approval.

If any of these lines does not match what you found in practice, tell us through the channels on the contact page. The line gets checked and fixed.

Price

Start free. Pay for sources, not for people.

Free

No cost

1 source · no card · does not expire

Starter

R$ 29,99 per month

3 sources · R$ 299,99 yearly

Pro

R$ 49,99 per month

9 sources · R$ 499,99 yearly

Scale

R$ 99,99 per month

99 sources · R$ 999,99 yearly

A source is each system that sends events or each imported spreadsheet. People, events, imports, agents, strategies and the MCP have no plan limit. At the limit, the sources you already have keep receiving; only the next one waits for the plan. Prices are in Brazilian reais (BRL), charged by Stripe.

Questions

The objections, in the order they come up

Found a limit that is not written here?

The channels are on the contact page. If you found where it breaks, the line goes on this page before the next visitor finds it alone.

Create the first source and watch the first record build itself.

You sign in with a code sent to your e-mail. The source, the import, the Manual and the approval queue are in the dashboard.