Internal briefing
The same Iris, with a second role. Partners get help selling and a direct line into our pipeline. Nothing else.
Not a second assistant. The same Iris with a partner role, which decides what is mounted into her container and which tools exist. The limits are the room, not a rule she is asked to follow.
We hand out one partner code. Nothing is set up in advance.
A welcome written for partners. It offers nothing they cannot have.
We are told who joined and from what number. A leaked code is visible, and we bar the number. Barred numbers cannot return under a new name.
Before any lead exists. They get the line to say, not a paragraph to memorise.
People text in fragments. She confirms the company name before recording anything, then claims it on the spot.
The client is theirs from that second.
Written to their file before anything is sent. A second partner naming it now is blocked, and never told who holds it.
"Toyota Lipa" and "Toyota Shaw" are already two companies. The hard case is a partner who writes only "Toyota" when a different Toyota is claimed.
"Let me check this one with the team." Nothing is decided while the question is open.
Iris asks Pat: same company or different. A person decides. She only ever reports a clash.
Held about five minutes so everything they add arrives as one thread. One client, one line in the channel. The headline mentions nobody; the detail and the ping go inside.
Family-run steel fabricator, 400 staff. They find out about material shortages only after the machine is set up. Readiness review next Tuesday.
@Rolan @Patrick
Iris does not create the ClickUp card. Pat reads the thread and adds it himself.
Deliberate for v1. Deciding whether a lead belongs in the pipeline is a judgement call, and cards created straight from a partner's enthusiasm would fill the board. The relay is the automation. The decision stays human.
Every update is a reply under the original, pinging us again. Each one also resets the 60-day clock, so a deal they are working stays theirs.
Update from Juan Reyes
Tuesday 2pm confirmed. They asked whether DrawScan reads scanned PDFs.
@Rolan @Patrick
Fifteen tools, chosen one at a time. Anything added to Iris later is denied to partners until somebody names it on purpose.
Confirms the name, records it under them, claims it, carries it to our channel.
"Is Tanglaw taken?" answers in seconds. Finding out after the trip is worth nothing.
Every client, days left on each claim, and what is still on its way to us.
Which of the six products answers the complaint they just heard, and the words to say.
Reminders, follow-ups, their calendar and mail. Their accounts, never ours.
A photo of a business card becomes a lead. Half of them arrive that way.
Not rules she is asked to respect. Every instruction-only safeguard in this codebase has eventually failed, so these are enforced in code.
Asking her anything, any time, is unlimited. What costs us money is standing jobs that run on their own, so those are where the line sits.
| What | Partner account |
|---|---|
| Asking her anything, any time | Unlimited |
| Reminders ("tell me X at 2pm") | Up to 25, hourly at most. These cost nothing to run. |
| Standing jobs that go and check something | Once a day, two at a time |
| "Watch my inbox every hour" | Not included. We can build it for them. |
Every standing job used to run a full model. Nothing stopped one firing every minute, which is 1,440 runs a day from one sentence. Plain reminders now cost nothing at all.
She names what they can have, says standing jobs are capped, and offers to have us build it properly. An ask like inbox monitoring is a signal of what someone would pay for, so it reaches the team.
228 automated tests pass, 36 against the live ClickUp API. None can test a human on WhatsApp, which is next.
| Piece | State |
|---|---|
| Role separation, mounts and tools | Live |
| Self-enrolment and revoke | Live |
| Lead capture, 60-day claim | Live |
| Relay, threaded updates | Live |
| Pipeline view for the team | Live |
| Cost limits on scheduled jobs | Live |
| Pat settling an ambiguous name | Needs a decision |
| Warning before a claim lapses | Not built |
| Creating the ClickUp card | By hand, on purpose |
| Tested with a real partner | Pending |
Commissions. Whether client names can appear in proof stories. First wave of partners. Offboarding.
The product descriptions she quotes to prospects are not signed off: Maestro, ForecastIQ, Diagnostik.