Read this page first if you are new. It is a day-by-day plan for your first 30 days that you can follow alone. Each day names the page to open, the quota to hit, and the artifact that proves it is done. If a day's artifact does not exist, the day is not done; carry it to tomorrow and say so in your weekly report.
What the month is for: moving labs through the five pipeline stages on page 00 — qualified workflow → frames + metadata → reference measurement → budget owner → signed pilot. Signups are counted as a diagnostic, not a goal. This page expires on November 12, 2026; the operator replaces it with the next month's plan.
Month targets (each one is a [HYPOTHESIS]: a planning guess to test, never something to say to a prospect):
| Stage | Month target | Artifact |
|---|---|---|
| 1. Qualified workflows | 25 | 25 saved workflow-fit responses + qualified log rows |
| 2. Frames received | 10 labs, each returned inside 48 h | 10 result ZIPs + time-to-result |
| 3. Reference measurements secured | 3 | 3 reference files or dated commitments |
| 4. Budget owners identified | 5 | 5 rows with budget columns + decision_date |
| 5. Pilots signed | 1 | 1 countersigned Software or Hardware Design Partnership |
| Talks + clinics booked | 2 talks, 1 clinic held | calendar invites; clinic sign-up sheet |
Escalation, any time: email
system@apertureapi.com with the page and
step number in the subject (e.g. 23 / Day 6 — workflow-fit 422). That is the
IT Desk. You never wait on a person to continue: if a step is blocked, log the
block, email the desk, and move to the next day's work.
| Account | How | Artifact |
|---|---|---|
| Company mailbox | issued by the operator; plain-text sending, no tracking pixel, signature = your name + https://api.apertureapi.com/signup?ref=<your-handle> |
a test email received at system@apertureapi.com |
| Your referral handle | a short lowercase handle (letters, digits, ., -, _; up to 40 characters); tell the desk |
your signup?ref=<handle> link opens the signup page |
| Sales-flock sign-in | ask the sales manager for the password to the data/ downloads |
you can open design-partner-targets.csv |
| A trial API account for demos | sign up at api.apertureapi.com/signup with the company mailbox | an API key in your password manager |
Company accounts (@apertureapi.com) are excluded from every count.
| Activity | Quota | Page | Artifact |
|---|---|---|---|
| Qualified conversations | 2 new conversations where a named person describes a real workflow | 24 | log rows with the use in one sentence |
| Workflow-fit checks run | every described workflow, same day | 24 | saved JSON response per lab |
| Researched outreach | 10 message-test emails + 3 design-partner emails (one at a time) | 16, 22 | rows at contacted |
| Frames worked | all, each returned inside 48 hours | 17 | result ZIP + time-to-result |
| Next-stage ask | every lab at stage 2 asked for its reference measurement; every lab at stage 3 asked who owns the budget | 22, 31 | the ask, logged with date |
| Log update | end of every day | 09 | logs saved |
Weekly quotas: 2 guest-talk pitches sent (25); clinic invitations to every stage-1 lab (26); 5 budget-owner rows researched (31); one referral ask to each satisfied researcher (28).
| Day | Do this | Artifact |
|---|---|---|
| 1 | Rules; accounts; read pages 00, 14, 15, 24; run a practice workflow-fit check on the sample setup | accounts exist; one saved practice response |
| 2 | Claim your rows (page 12, design-partner targets); read the three segment buyer pages and page 22 | claimed rows; a note of which buyer page fits each row |
| 3 | First 10 + 3 researched emails; book the date of this month's clinic with the operator (page 26) | 13 sends; clinic date fixed |
| 4 | 10 + 3; run workflow-fit on every reply; draft one guest-talk pitch using the group's own papers (page 25) | saved fit responses; pitch draft |
| 5 | 10 + 3; send the first 2 talk pitches; first weekly report | 2 pitches sent; report sent |
| Day | Do this | Artifact |
|---|---|---|
| 6–8 | Daily quotas; every stage-1 lab gets the clinic invitation and an ask for one frame with its metadata | invitations logged; frame asks logged |
| 9 | Work every frame through page 17 inside 48 h; send the methods supplement with each result | result ZIPs; time-to-result |
| 10 | Budget-owner research on your top 5 rows (page 31); weekly report | 5 rows with budget columns filled or marked unknown |
| Day | Do this | Artifact |
|---|---|---|
| 11–12 | Ask every stage-2 lab for its reference measurement; offer the Software Design Partnership to labs that have one, the Hardware one to labs with no rig (page 22) | asks logged; proposals sent |
| 13 | Hold the monthly lab clinic (page 26) or a guest talk (page 25) | sign-up sheet; follow-up emails sent within 24 h |
| 14 | Confirm budget owner + decision window on every proposal (page 31) | decision_date filled |
| 15 | Industrial inbound review (page 29): route or log every one; weekly report | page 21 log current |
| Day | Do this | Artifact |
|---|---|---|
| 16–19 | Daily quotas; chase each open proposal for its decision date; send the procurement packet when asked | decision dates logged |
| 20 | Hand any "yes" to the operator for countersignature (page 22) | operator ack |
| 21–22 | Close trials to paid where ready (page 20); ask satisfied researchers for one referral (page 28) | plan chosen per account; referral asks logged |
| 23–29 | Repeat; fix whatever the KPI table says is behind | daily logs |
| 30 | Month-end report with stage counts and the next month's proposal | report sent |
Every Friday put the real count beside each month target ÷ 4. A stage under half its weekly share is behind. Fix the earliest behind stage first: no qualified workflows → more talks, clinic invitations and researched emails; no frames → shorten the ask to one frame plus three numbers; no references → lead with the design partnership; no budget owner → page 31 before the next call.
The previous plan set a 400-signup goal; that math was a [HYPOTHESIS] and
is kept here only as a health check. The only [MEASURED] baseline: on
2026-10-12 scripts/count_customers.py reported 0 outside accounts.
| Source | Diagnostic expectation (hypothesis) | If it reads zero for a week |
|---|---|---|
| Discovery plumbing 01–08 | a trickle of ?ref=<handle>-pypi / -hf signups once listings are live |
check the listing still resolves |
| No-account upload form | some form uses convert to signups | check /public/form_token and the form page load |
| Your outreach | signups follow frames, not the other way round | nothing to fix — read the stage counts instead |
Use https://api.apertureapi.com/signup?ref=<your-handle> in every email and
signature; sub-tags (-dp, -talk, -clinic, -ref) show which channel
worked. Counts come from data/scoreboard.csv
(sign-in; refreshed hourly): signups_total, signups_by_ref,
customers_ge1_run, paid_accounts. A signup is not a customer; never round
one into the other.
Plain-text email, subject Weekly report — <your-handle> — week N:
1. Pipeline (new this week / month to date / month target)
Qualified workflows: __ / __ / 25
Frames received (labs): __ / __ / 10 returned < 48 h: __
Reference measurements secured: __ / __ / 3
Budget owners identified: __ / __ / 5
Pilots signed: __ / __ / 1
2. Activity: conversations __, workflow-fit checks __ (tested __ /
needs_review __ / unsupported __), talks pitched/booked __/__,
clinic sign-ups __, referral asks __
3. Open proposals: lab, stage, decision date, signer role
4. Industrial inbound: routed __, logged on page 21 __
5. Diagnostic: signups this week __, with my ref __, customers __, paid __
6. Blocks: what stopped me, which desk email I sent, what I did instead
7. Next week: the one thing I will change because of the numbers
Attached: prospect log, design-partner log
| File | What it is |
|---|---|
| design-partner-targets.csv | 29 researched labs with budget-owner columns (sign-in) |
| design-partner-log-template.csv | design-partnership pipeline log (sign-in) |
| prospect-log-template.csv | outreach log (sign-in) |
| industrial-inquiry-log-template.csv | page 21's sheet (sign-in) |
| workflow fit | the public checker and checklist |
| design partnership brief · procurement · validation docket | the buyer pages to send |