logan/server-26
1
0
Fork 0
Code Issues 84 Pull Requests Actions Packages Projects Releases Wiki Activity

OWNER AGENDA: who do we hire to generate interest? The owner is not the growth engine #69

New Issue
Open
opened 2026-08-25 00:07:07 -04:00 by logan · 1 comment
logan commented 2026-08-25 00:07:07 -04:00
Owner
Copy Link
Copy Source

Filed by the owner. For the board to decide and report back.

The ask

The board's current plan has the owner personally doing go-to-market: 12 discovery conversations by 2026-09-22 (#66), 4 by the 2026-09-05 checkpoint. The CMO's draft (#59) concluded that "almost all go-to-market work is owner-only."

The owner rejects that as the permanent answer. Generating interest is not work the owner wants to own.

The question for the board is not whether to do outreach. It is:

Who do we need to hire to do it, and what exactly does that role own?

Decide it and tell the owner. Do not come back asking the owner to choose from a menu of options — the board is expected to form a position and defend it.

What the owner is offering

  • Connections. The owner can make introductions and open doors. That is the owner's contribution to go-to-market, and it is bounded — an introduction is minutes, not hours.
  • Whatever budget the decision justifies, subject to the ruling in GOALS.md that this is a lifestyle-scale company and the owner's time is capped under 5h/week.

What the board must return

  1. The role. What is it actually called, and what does it own end to end? Is this a persona in .claude/agents/ (an agent that drafts outreach, builds target lists, writes sequences), a real human hire, or a contractor/agency? Say which, and why the other two are wrong.
  2. The boundary. What does the role decide alone, what comes to the board, and what still needs the owner. If the answer still requires owner-hours, name the number.
  3. Cost. What it costs in money and in owner-hours, measured against GOALS.md. A role that consumes more owner-time than it saves is a rejection.
  4. The interim. The 2026-09-05 checkpoint (4 conversations) and the 2026-09-22 kill criterion do not pause while this is decided. Say explicitly what happens to those dates — whether they hold, move, or are met a different way.
  5. How the owner's connections get used. Concretely. "The owner makes introductions" is not a plan; who does what with an introduction once it exists?

Constraints the board already ratified

  • GOALS.md (minutes #54): owner time is a hard cap under 5h/week; customers first is the tiebreaker; the commercial track dies if the 12 conversations return nobody paying.
  • Minutes #54 decision 5 suspended the automatic fallback to segment #2 precisely because it costs more owner-hours per deal. Founding agenda item 8 (the scaling channel) is adjacent and may be answered by the same ruling — say so if it is.
  • Gate A blocks publishing any price; Gate B blocks charging anyone. Neither blocks discovery conversations (minutes #54 decision 4).
  • Per the board charter, if the answer is a new persona, that goes through the HIRING flow: the board files the rationale and scope, alerts the owner, and the owner and Claude wire the persona together. An unattended run never creates an agent definition on its own.

Note

If the board's honest conclusion is that no hire fixes this and the owner must do the first conversations personally, it should say that plainly and explain why — but it has to be an argued position, not a default.

**Filed by the owner. For the board to decide and report back.** ## The ask The board's current plan has the owner personally doing go-to-market: 12 discovery conversations by 2026-09-22 (#66), 4 by the 2026-09-05 checkpoint. The CMO's draft (#59) concluded that "almost all go-to-market work is owner-only." **The owner rejects that as the permanent answer.** Generating interest is not work the owner wants to own. The question for the board is not whether to do outreach. It is: > **Who do we need to hire to do it, and what exactly does that role own?** Decide it and tell the owner. Do not come back asking the owner to choose from a menu of options — the board is expected to form a position and defend it. ## What the owner is offering - **Connections.** The owner can make introductions and open doors. That is the owner's contribution to go-to-market, and it is bounded — an introduction is minutes, not hours. - Whatever budget the decision justifies, subject to the ruling in GOALS.md that this is a **lifestyle-scale** company and the owner's time is capped **under 5h/week**. ## What the board must return 1. **The role.** What is it actually called, and what does it own end to end? Is this a persona in `.claude/agents/` (an agent that drafts outreach, builds target lists, writes sequences), a real human hire, or a contractor/agency? Say which, and why the other two are wrong. 2. **The boundary.** What does the role decide alone, what comes to the board, and what still needs the owner. If the answer still requires owner-hours, name the number. 3. **Cost.** What it costs in money and in owner-hours, measured against GOALS.md. A role that consumes more owner-time than it saves is a rejection. 4. **The interim.** The 2026-09-05 checkpoint (4 conversations) and the 2026-09-22 kill criterion do not pause while this is decided. Say explicitly what happens to those dates — whether they hold, move, or are met a different way. 5. **How the owner's connections get used.** Concretely. "The owner makes introductions" is not a plan; who does what with an introduction once it exists? ## Constraints the board already ratified - GOALS.md (minutes #54): owner time is a **hard cap under 5h/week**; **customers first** is the tiebreaker; the commercial track dies if the 12 conversations return nobody paying. - Minutes #54 decision 5 **suspended** the automatic fallback to segment #2 precisely because it costs *more* owner-hours per deal. Founding agenda item 8 (the scaling channel) is adjacent and may be answered by the same ruling — say so if it is. - Gate A blocks publishing any price; Gate B blocks charging anyone. Neither blocks discovery conversations (minutes #54 decision 4). - Per the board charter, if the answer is a new persona, that goes through the **HIRING** flow: the board files the rationale and scope, alerts the owner, and the owner and Claude wire the persona together. An unattended run never creates an agent definition on its own. ## Note If the board's honest conclusion is that no hire fixes this and the owner must do the first conversations personally, it should say that plainly and explain why — but it has to be an argued position, not a default.
logan added the board:agenda label 2026-08-25 00:07:07 -04:00
logan commented 2026-08-25 21:48:43 -04:00
Author
Owner
Copy Link
Copy Source

Ruled. Final minutes: #79. board:agenda removed — this is scoped.

The board formed a position rather than returning a menu. All five things you asked for:

1. The role. growth-ops, an agent persona — not a human hire, not a contractor/agency. Scope filed at #78 (HIRING); the board did not create it, per your own constraint. A hire is wrong because there is no repeatable script at 0 of 12, no entity to employ through (#47), and onboarding costs more owner-hours in 28 days than it saves. An agency is wrong because $3-10k/mo is unjustifiable pre-Gate-B, the domain briefing reproduces the cost we are removing, and — decisively — there is no safe login to hand an outsider: Gate B3 (#43) is fully unimplemented at HEAD, so any account reads real person names on real EMS dispatch, and #4 means even platform-admin is not org-scoped.

2. The boundary. growth-ops decides target-list order and copy wording alone. Price (Gate A), live/named data (Gate B3), and any new outbound channel come to the board. It holds no credential of any kind — not even a Gitea token — and is structurally incapable of sending anything. Residual owner-hours: ~0.5h per phone/video conversation, ~1h per walk-in, ~2 minutes per introduction, plus one 30-60 min wiring session.

3. Cost. $0 marginal money. ~2-3 owner-hours to 2026-09-05; ~6-9 owner-hours to 2026-09-22 — roughly 35-45% of the under-5h/week budget across that window. It fits.

4. The dates. Both hold, unmoved. 4 conversations by 2026-09-05, 12 by 2026-09-22. What changed is method, not deadline: phone and video conversations now count exactly as much as walk-ins, which roughly halves owner-hours per conversation and deletes the "physically visit 40 places" framing you objected to.

5. Your introductions. You forward a name plus one line (under 2 minutes). growth-ops writes, same day, an intro-reply draft in your voice plus a one-page brief on the operator. You send it from your own account — that is where a warm intro gets its value. You take the call. growth-ops drafts the log entry and the 24h follow-up; the CEO posts the log, you send the follow-up.

The honest part of the answer, because you asked for an argued position and not a comfortable one: growth-ops removes roughly 80% of the go-to-market function. It cannot remove the 12 conversations. No hire, contractor or agency can, in the next 28 days, at 0 of 12, with no entity, no NDA and no safe login. You personally hold ~6-9 hours between now and 2026-09-22. The permanent answer to "the owner is not the growth engine" is not a person — it is the self-serve/inbound scaling channel (founding agenda item 8), and that is gated on Gate B, which is gated on these twelve conversations. The fastest route to never doing sales again runs straight through doing these twelve. The human-hire question re-opens on trigger — Gate B open and #43 and #47 both closed — recorded as new founding-agenda item 11.

What you personally do: wire the persona with Claude, 2026-08-26 (#78). Then 4 logged conversations on #66 by 2026-09-05.

**Ruled. Final minutes: #79.** `board:agenda` removed — this is scoped. The board formed a position rather than returning a menu. All five things you asked for: **1. The role.** `growth-ops`, an **agent persona** — not a human hire, not a contractor/agency. Scope filed at **#78 (HIRING)**; the board did **not** create it, per your own constraint. A hire is wrong because there is no repeatable script at 0 of 12, no entity to employ through (#47), and onboarding costs more owner-hours in 28 days than it saves. An agency is wrong because $3-10k/mo is unjustifiable pre-Gate-B, the domain briefing reproduces the cost we are removing, and — decisively — **there is no safe login to hand an outsider**: Gate B3 (#43) is fully unimplemented at HEAD, so any account reads real person names on real EMS dispatch, and #4 means even platform-admin is not org-scoped. **2. The boundary.** growth-ops decides target-list order and copy wording alone. Price (Gate A), live/named data (Gate B3), and any new outbound channel come to the board. It holds **no credential of any kind** — not even a Gitea token — and is structurally incapable of sending anything. **Residual owner-hours: ~0.5h per phone/video conversation, ~1h per walk-in, ~2 minutes per introduction, plus one 30-60 min wiring session.** **3. Cost.** **$0 marginal money.** **~2-3 owner-hours to 2026-09-05; ~6-9 owner-hours to 2026-09-22** — roughly 35-45% of the under-5h/week budget across that window. It fits. **4. The dates.** **Both hold, unmoved.** 4 conversations by 2026-09-05, 12 by 2026-09-22. What changed is method, not deadline: phone and video conversations now count exactly as much as walk-ins, which roughly halves owner-hours per conversation and deletes the "physically visit 40 places" framing you objected to. **5. Your introductions.** You forward a name plus one line (under 2 minutes). growth-ops writes, same day, an intro-reply draft in your voice plus a one-page brief on the operator. **You send it from your own account** — that is where a warm intro gets its value. You take the call. growth-ops drafts the log entry and the 24h follow-up; the CEO posts the log, you send the follow-up. **The honest part of the answer**, because you asked for an argued position and not a comfortable one: growth-ops removes roughly 80% of the go-to-market function. **It cannot remove the 12 conversations.** No hire, contractor or agency can, in the next 28 days, at 0 of 12, with no entity, no NDA and no safe login. You personally hold ~6-9 hours between now and 2026-09-22. The permanent answer to "the owner is not the growth engine" is not a person — it is the self-serve/inbound scaling channel (founding agenda item 8), and that is gated on Gate B, which is gated on these twelve conversations. **The fastest route to never doing sales again runs straight through doing these twelve.** The human-hire question re-opens on trigger — Gate B open and #43 and #47 both closed — recorded as new founding-agenda item 11. **What you personally do: wire the persona with Claude, 2026-08-26 (#78). Then 4 logged conversations on #66 by 2026-09-05.**
logan removed the board:agenda label 2026-08-25 21:48:44 -04:00
logan added the area/governancearea/growth
priority
p3
type
decision
 labels 2026-10-05 02:04:35 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/ai-pipeline
Scene/entity extraction, summarizer, AI providers, embeddings
 area/auth
AuthN/Z, roles, tenancy/org scoping, API keys, credentials
 area/billing
Plans, entitlements, AI spend accounting and caps
 area/correlation
Incident correlation, linking, lifecycle, severity, corr_debug
 area/discord
Discord bot, radio bots, voice streams, bot tokens, webhooks
 area/frontend
Web UI: Next.js app and the edge-node local dashboard
 area/governance
Board process, minutes, unattended runner, agent tooling
 area/growth
Go-to-market, outreach, cold email, discovery conversations
 area/infra-deploy
CI/CD, VM, registry, Firestore rules/indexes deploy, Terraform/Caddy
 area/legal
ToS, retention, licences/DAAs, CAN-SPAM, E&O, name suppression
 area/map
Live map: pins, paths, tiles, legend, geocoding
 area/mqtt
Node-C2 MQTT, checkins, commands, node sweeper, dynsec
 area/node-ota
Node install, enrollment, OTA updater, image skew
 area/osint
External feeds: cameras, 511, ADS-B, AIS, outages, and their licences
 area/recording-audio
Call capture, boundaries, PulseAudio, ring buffer, trimming, attribution
 area/sdr-radio
OP25 decode, SDR hardware/tuning, conventional, second SDR, mesh radio
 area/transcription
STT, transcript correction, place verification, name accuracy
 board
Board process: minutes and board-filed items
 board:agenda
Needs board scoping at the next sitting; CEO removes the label once scoped
 minutes:draft
One exec pre-read, closed by CEO
 minutes:final
CEO ruling; open until enacted
 role:ceo
Filed by the CEO
 role:cfo
Filed by the CFO
 role:cio
Filed by the CIO
 role:ciso
Filed by the CISO
 role:cmo
Filed by the CMO
 role:coo
Filed by the COO
 role:cto
Filed by the CTO
kind
behavior-bug
Wrong product behavior; the instrument reads it correctly
kind
measurement-bug
Corrupts the recording/instrument (debug data, evals, health checks), not behavior
priority
p0
Drop everything: prod broken, live exposure, or owner-ruled P0
priority
p1
Next up: blocks a gate, a customer, or core incident quality
priority
p2
Normal: real defect or planned work, schedule in turn
priority
p3
Low: minor, cosmetic, or someday
status
blocked
Waiting on an external party, spend, or another issue
status
in-progress
Branch or PR open against it
status
needs-decision
Waiting on an owner or board ruling before work
status
needs-info
Root cause or repro unknown; needs a reading first
type
bug
Something built is wrong: code, data, or a measurement
type
chore
Maintenance, refactor, tests, pinning, cleanup: no user-visible change
type
decision
A ruling to make or record: board minutes, owner calls, legal reviews
type
docs
Docs, runbooks, CLAUDE.md, skills, SOPs
type
feature
New capability or an extension of an existing one
type
security
Security, privacy, credential or tenant-isolation exposure
type
tracking
Tracker, checklist, initiative or punch-list spanning several changes
No labels area/governance area/growth
priority
p3
type
decision
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
logan
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: logan/server-26#69