Source prospects (engineers, students, schools)
No sourcing prompt or grammar is written for byCaliber. The CRM database exists in Notion and is read twice a week by ROUTINE1 (CRM brief), nothing fills it automatically.
Architecture
Part A · Acquisition system · cold name to signed client · skeleton
Red
Orange
Yellow
Green
Select any text to mark it. Clear restores the page colour. Dots in the right margin face your marks.
Scope of this page
Only the skeleton exists today. Same sections A.1 to A.9 as tools.byforja.com/architecture (rule 15, one template per page type). Each section states what is known for byCaliber on 2026-09-10 and says "not written yet" where the doctrine does not exist. Nothing below is invented.
This is live state, not doctrine. Doctrine lives in Notion: byCaliber — Claude Code HQ — specifics (posture, brand, the 13 h / 1 800 € offer, contract CTR-V2, CM2C compliance, vocabulary restrictions), byCaliber hub.
On this page
- A.1 The chain at a glance
- A.1b AL's daily operating loop
- A.2 The staircase
- A.3 Automation map
- A.4 Open loops and contradictions
- A.5 The two audiences
- A.6 What AL delivers, and at what cadence
- A.7 The delivery staircase
- A.8 What makes a prospect feel understood
- A.9 The firing map: step → deliverable → prompt → client
A.1 The chain at a glance · read back 2026-09-10
Four stages, one direction. No number below was measured: the byCaliber CRM lives in Notion (one of the three CRM databases read by ROUTINE1 on /crons) and has not been read for this page. The D1 database bycaliber holds contacts, events and the auth tables only.
Prospect rows
—
Not measured. Source: the byCaliber CRM database in Notion.
Calls booked
—
Not measured. Source: Cal.com event
career-move (id 5471203).Contracts signed
—
Not measured. Contract model CTR-V2, offer 13 h / 1 800 € TTC (HQ specifics).
School talks booked
—
Not measured. Second audience of the Cal.com questionnaire (schools and universities, free talk).
The three degrees of automation
Automatic
Runs on its own. No human triggers it, no human reviews it before it happens.
1step
Semi-automatic
An agent or a script does the work. AL triggers it, validates it, or both.
1step
Manual
AL does all of it, by hand, one prospect at a time. No tool carries any of it.
3steps
Only what is wired today is counted: the Cal.com booking (automatic), the twice-weekly CRM brief (semi-automatic, ROUTINE1), and the three human steps around them. The rest of the chain is not written.
A.1b AL's daily operating loop · not written yet, 2026-09-10
Not written yet for byCaliber. On byForja this section holds the 4-step loop AL runs every batch underneath the staircase. It gets filled when AL writes the byCaliber doctrine (Notion HQ specifics), not before: nothing here is invented.
A.2 The staircase, 5 known steps · read back 2026-09-10
Read it top to bottom. Each stage steps one notch to the right, each step inside a stage steps one notch further. The colour of the left edge is the degree of automation, the pill on the right names it. Only steps with a wired tool or a documented fact appear; the empty stages say so.
STAGE 1
Source
I want new names in the pipe.
STAGE 2
Reach out
I want a reply.
Message the prospect
No outreach sequence, no follow-up robot (byForja has CRON9). Channel and cadence not written.
STAGE 3
Close
I want a signature.
Prospect books the call
Cal.com event
career-move, 45 min discovery call, id 5471203. Two questions since 07/09/2026: You are (engineer / student / school or university / other) and one open question. The price question (1 800 € TTC) was removed the same day.Run the call
Call structure not written. A school or university is booking a free talk, an engineer or a student is a coaching prospect: the Q1 answer splits the two before the call.
Contract and payment
Contract model CTR-V2, offer 13 h for 1 800 € TTC, CM2C compliance rules (HQ specifics). Signature tool and payment path not written on this page.
STAGE 4
Hand over
I want the client served.
Not written yet
No onboarding page, no discovery questionnaire, no plan generator exists on tools.bycaliber.work (byForja has all three). The 13 hours are delivered by hand.
A.3 Automation map · read back 2026-09-10
The same five steps, laid flat. One block per step, in order, coloured by degree. One green block in a violet wall: the booking is the only thing that happens without AL.
01
02
03
04
05
Source
Reach out
Close
How to read the wall
ROUTINE1 (CRM brief, Monday and Thursday 08:00 local) is the one semi-automatic piece and sits beside the chain, not on it: it reads, it does not move a prospect.
A.4 Open loops and contradictions · read back 2026-09-10
- Entry price. The Cal.com price question (1 800 € TTC, options Oui / Pas maintenant mais possible / Pas dans mon budget) was removed on 07/09/2026: 1 800 € is now the upsell, not the entry point, and the question made no sense to a university booking a free talk. No new entry price is recorded anywhere. Do not reinstate the question without one.
- Conditional questionnaire. The target design splits Q2 in three according to Q1 (engineer or student / school or university / other). The Cal.com v2 API exposes no conditional-logic property on booking fields, so one open question stands in until the conditions can be set in the Cal.com interface. The three target labels are kept on /cal-questionnaires.
- No outreach path. Stage 2 has no channel, no cadence, no robot. Every other byCaliber number depends on it.
A.5 The two audiences · summary of the questionnaire, read 2026-09-10
The Cal.com Q1 You are splits the two audiences before the call. An engineer or a student is a coaching prospect (the 13 h / 1 800 € engagement, contract CTR-V2). A school or a university is booking a free talk. other catches HR, press and anything unforeseen, so nobody is forced into a wrong answer. Profiles inside the coaching audience, if any, are not written.
A.6 What AL delivers, and at what cadence · read back 2026-09-10
Known: the engagement is 13 hours for 1 800 € TTC under contract CTR-V2, with CM2C compliance and vocabulary restrictions documented in the HQ specifics. Not written: the session cadence, the deliverables per session, the rules that keep AL protected, what the client leaves with.
A.7 The delivery staircase · not written yet, 2026-09-10
Not written yet for byCaliber. On byForja this section holds the 6-week launch wall, step by step, with hours per step measured against the first client. It gets filled when AL writes the byCaliber doctrine (Notion HQ specifics), not before: nothing here is invented.
A.8 What makes a prospect feel understood · not written yet, 2026-09-10
Not written yet for byCaliber. On byForja this section holds the writing rule for every outreach script: four tensions, a three-beat structure, five openers, the three things never to do. It gets filled when AL writes the byCaliber doctrine (Notion HQ specifics), not before: nothing here is invented.
A.9 The firing map: step → deliverable → prompt → what the client receives · not written yet, 2026-09-10
Not written yet for byCaliber. On byForja this section holds the table that says which prompt fires each deliverable and what artifact the client actually holds. It gets filled when AL writes the byCaliber doctrine (Notion HQ specifics), not before: nothing here is invented.