This session ran a /small-council on the delegated question "kill it or continue?" for the FIFO SaaS validation track, and then executed the verdict. Three fresh, blind advisors (Pragmatist, Skeptic, Long-game) reached 3/3 consensus: CONTINUE, single-threaded, with an early reachability tripwire. I wrote that decision into the ticket and fixed a stale status field. Earlier in the session I also generated the prior session-report and refreshed the CEO dashboard.
This report exists because you asked for all the files + all the actions in one place to track how to proceed — so the centrepiece below is the Action tracker: the dial-sprint plan, the Day-7 tripwire, the Day-21 GO/KILL gate, the exact prospect call order, and the Mom-Test script. Everything is copied from the ticket you can now run against.
Recap reflects available context + git facts; a long/compacted session may omit earlier steps. File lists are derived from git, not memory. Note: a large batch of new tickets (TASK-00027 → TASK-00053) appeared in git status from other concurrent sessions (content-agency, omnictx micro-SaaS, faceless-studio) — those are not this session's work and are excluded from the tables below.
Action tracker — how we proceed (FIFO dial sprint)
Single source of truth for the go-forward. Full copy lives in TASK-00010/notes.md.
The one rule
FIFO is the SOLE active venture-validation track until the Day-21 gate resolves. Freeze net-new tracks (Questionnaire SaaS, Vibe-to-Prod, Higgsfield, grants, content-agency): no new prep, no new tickets. The bottleneck is dialing, not idea selection.
Do next (this week)
Dial prospect #1 — Ranger Drilling (IN-BAND, textbook ICP). This is the single next physical action.
Dial #2 Topdrill (IN-BAND), then work down the call order below, size-qualifying the UNKNOWNs at the top of each call.
Log each call's outcome against C1 / C2 / C3 as you go (append to TASK-00010/notes.md or a simple tracker).
Gate 1 — Day-7 reachability tripwire
≥ 3 ICP interviews BOOKED (calls on the calendar) by Day 7.
Miss → the failure is the channel, not the product. Do not extend silently and do not kill the idea — pivot reach to warm intros (AMEC · CME WA · Austmine · WA Mining Club · events) and re-check. Minority note (Skeptic): if booking proves easy, harden this to "≥ 3 conversations completed by Day-5."
Gate 2 — Day-21 GO / KILL (the market test)
GO requires ALL of:
C1 — ≥ 3 of ~8 name the multi-portal / mobilisation pain unprompted as a top-few admin headache.
C2 — ≥ 2 give their own gate-rejection frequency + $ cost (independent of any marketing figure).
C3 — ≥ 1–2 credible paid commitments: refundable deposit or signed pilot LOI ≥ $299/mo (commitment, not compliments).
Desk half — no competitor owns the subcontractor-side multi-portal wedge (cleared in TASK-00009).
FAIL → clean KILL, reallocate hours to Homeward. Also kill if a portal ships self-serve bulk import, or MyPass proves to own the wedge. On GO → unblock TASK-00011 (concierge MVP for 1–2 real subs); TASK-00012 is the synthesis/gate ticket.
The Mom-Test script (don't lead with anyone's dollar figures)
"Walk me through the last crew you mobilised — what actually ate the time?" → pain, unprompted (C1)
"When did a worker last get turned back at the gate? What did that cost you, exactly?" → their number (C2)
"Which portals are you in? What do you pay for today? Tried DrilLedger — why / why not?" → incumbent reality
"Would you hand an outside tool your workers' medicals?" → trust gate (F5)
Close: "I'm building exactly this — want to be a paid pilot, set up this month for $X?" → then shut up and watch for a commitment (C3)
Verified call-first order (size-checked 2026-07-14, top 11)
#
Prospect
Size band
Note
1
Ranger Drilling
IN-BAND
WA drilling, textbook ICP. Call first.
2
Topdrill
IN-BAND
~100–133; national exploration driller, large FIFO field workforce.
3
Raglan Drilling
likely
21 rigs (weak proxy, could tip >200) — confirm crew headcount on the call.
4
Hicks Civil & Mining
unknown
3-depot Pilbara civil/mining, heavy fleet; high ICP relevance.
5
MineMech Mechanical
unknown
Perth workshop + Goldfields field crews + labour-hire arm.
6
Marlu Group
unknown
Diversified; qualify which arm carries the 50–200 workforce.
7
Jarahfire Drilling
unknown
Likely smaller — size-qualify before spending a full slot.
8
RecruitWest
labour-hire
Internal <50 but places 22k+ — only if ICP = "mobilises 50–200 placed FIFO workers."
White-collar/professional recruiter, weak FIFO fit.
11
Tekk Group
drop
Recruitment + payroll, weakest ICP signal.
Full ~40-company starter list + warm-intro channels: see TASK-00010/notes.md. Confirm size on LinkedIn (51–200 band) before dialing; target the "mobilisation coordinator / compliance / HSE admin."
Your step-by-step — do this, in order
This is the part only you can run. Durable copy: TASK-00010/knowledge/outreach-kit.md.
Mindset: first call = research, not a demo. Get THEIR gate-rejection number before you say any of yours. The pilot ask is a commitment test (money / signature), not a compliments test. This industry is time-poor and phone-first — short and direct wins.
Step 0 — Setup (once, ~30 min). Open a tracker sheet: company · contact · role · channel · first-touch · reply? · booked? · call date · C1 · C2 · C3 · next step. Lock your identity line: "Perth founder researching how mining subs handle worker compliance across client portals."
Step 1 — Find the person (~10 min, start with Ranger Drilling). Confirm size on the company's LinkedIn page (51–200 band). Search LinkedIn: "[Company]" mobilisation / compliance / HSE / admin coordinator. Grab the office phone from their site.
Step 2 — First touch, two channels same week. (a) Phone the office and ask for the mobilisation/compliance coordinator; (b) LinkedIn connection + note; (c) email if you can find it.
Step 3 — Book the call. Ask for 15–20 min, framed as research. Offer two specific times. Work around their roster.
Step 4 — On the call, run the Mom-Test script (above). Extract C1 + C2 before describing anything. Ask the medicals-trust question. Close with the pilot ask (C3), then stop talking.
Step 5 — Log + follow up. Update the tracker right after. Send Monday, follow up Thursday.
Step 6 — Day-7 check. ≥3 booked? If not → the channel is the problem, not the idea: pivot to warm intros (AMEC / CME WA / Austmine / WA Mining Club) before burning the sprint.
What to tell people — copy you can send
Drafts for you to send yourself; nothing here has been sent. Swap [Name] / [Company] / [$X] before sending.
A · Phone — getting past reception
"Hi, I'm Valter — a Perth-based founder doing research on how drilling and mining subcontractors handle worker compliance across all the client portals, like Avetta and ISNetworld. Could I speak to whoever looks after mobilisation or compliance for your crews? I'm not selling anything — just after 15 minutes on how it actually works for you."
B · Phone — once you've got the coordinator
"Thanks for taking a sec. I'm Valter, a Perth founder — I'm researching the admin side of mobilising FIFO crews, specifically the pain of getting every worker's tickets and medicals into the different client portals. You're exactly the person who'd know. Could I grab 15–20 minutes this week to hear how it actually works for you? Genuinely research, not a pitch."
C · LinkedIn connection note (≤300 chars)
"Hi [Name] — Perth founder here, researching how mining subcontractors handle worker compliance across client portals (Avetta/ISNetworld/etc). Looks like you're exactly the right person to learn from — could I ask you a couple of questions sometime? Not selling anything."
D · LinkedIn message / cold email
Subject: Quick question on mobilising crews through client portals
Hi [Name], I'm Valter, a Perth-based founder. I'm trying to understand one specific headache for WA mining subcontractors: re-entering every worker's tickets, medicals and inductions into several different client portals (Avetta, ISNetworld, Cm3, BHP Enable) — and what it costs when a doc's expired and someone gets turned back at the gate.
You're at [Company], so you'd know this cold. I'm not selling anything — I'm doing about 10 conversations to learn whether this is a real problem worth solving. Could I grab 15–20 minutes this week or next? Happy to work around your roster.
Cheers, Valter
E · The booking ask (close of any first touch)
"Would Tuesday or Thursday work for a quick 15 minutes?"
F · The pilot ask (end of call — only if the pain is real; this is C3)
"Honestly, this is exactly what I'm building — a tool that keeps one master record per worker and generates the upload package for each portal, so you enter once, not six times. I'm setting up one or two subcontractors this month as paid pilots at [$X/mo]. Would you want to be one? I'd need a [refundable deposit / signed one-pager] to hold your spot." → then stop talking and watch what they do.
G · Warm-intro ask (Day-7 fallback — to associations / your network)
"Quick favour — I'm doing founder research on how WA mining subcontractors handle worker compliance across client portals. Do you know anyone who runs mobilisation or compliance at a drilling, labour-hire or maintenance sub (50–200 FIFO workers)? A 2-line intro would mean a lot."
How you can help me take action
Where I'm blocked without you, and what unblocks each step.
I can do
I need you to
Draft/refine all outreach copy, the tracker, the pilot one-pager, the LOI/deposit wording.
Decide the pilot price [$X/mo] and whether the hold is a refundable deposit or a signed one-pager.
Build the per-prospect research (verify size, find the named contact, draft a personalized opener) — one prospect at a time.
Say "go" and I'll start with Ranger Drilling: confirm size, find the mobilisation/compliance contact, and hand you a ready-to-send message.
Stand up the tracking sheet + a follow-up cadence reminder.
Tell me where you want it (a repo file, or a Google Sheet).
Draft warm-intro emails to AMEC / CME WA / Austmine for the Day-7 fallback.
Confirm you're OK sending them, and from which address.
Everything except the human contact.
Make the actual calls / send the messages — the one thing that can't be delegated.
Timeline (this session)
Session report #1 — generated reports/session-report-2026-07-15-2156.html (TASK-00010-labeled recap), then regenerated the CEO dashboard front door.
/small-council convened — 3 fresh blind advisors on "kill or continue?", run concurrently.
Verdict: 3/3 CONTINUE — consensus, no ballot needed; synthesized a Day-7 tripwire from the majority.
Executed the decision — wrote the mandate + tripwire into TASK-00010, recorded the decision, and synced the stale status.yaml.
Session report #2 — this consolidated tracker (your request: "all files + actions in one place").
Artifacts produced (this session)
File
What it is
reports/session-report-2026-07-15-2156.html
First session recap this session — a fact-anchored, honesty-flagged snapshot of the workspace state.
reports/session-report-2026-07-16-0828.html
This report — the consolidated decision + dial-sprint action tracker.
Files edited (this session)
The concrete execution of the council verdict. Confirmed against git diff --stat.
File
Change
TASK-00010/status.yaml
Synced status: backlog → in_progress + bumped updated_at (fixes the stale-state discrepancy vs backlog.yaml/adb; this is what the session was named for).
TASK-00010/notes.md
+18 lines: the Day-7 reachability tripwire, the single-thread council mandate (freeze other tracks), and the next physical action.
TASK-00010/knowledge/decisions.yaml
Recorded the 2026-07-15 small-council decision: method (3/3 consensus), rationale, actions, minority report, next action.
reports/index.html
CEO dashboard front door regenerated to index the new report(s).
Other modified files in git status (ADR/backlog/debt, TASK-00016/00019 designs, the 90-day plan, TASK-00005 Serena notes) are from earlier or concurrent sessions — not edited here.
Key decisions
CONTINUE FIFO validation — do not kill; make it the sole active venture track (/small-council, 3/3 consensus). Why: the founder's binding constraint is prep-hoarding instead of dialing, not idea selection. FIFO is the one track where the call kit is 100% built and recon is favorable, so the only remaining action is the behavior to learn — dialing. Killing it just frees hours to prep a sixth track; switching to the "further-along" Questionnaire track rewards the prep-hoarding.
Add a Day-7 reachability tripwire ahead of the Day-21 market gate (majority synthesis). Why: the real risk is cold outreach with no warm mining network. A Day-7 "≥3 booked" check converts a channel failure into a fast, cheap signal (pivot to warm intros) instead of burning all 21 days.
Freeze net-new tracks until the gate resolves.Why: single-threading is the intervention that breaks the parallel-motion habit; the board already reflects it (FIFO is the only in-progress venture track).
Tasks (FIFO validation line)
From adb task status. This is the dependency chain the tracker runs on.
ID
Role in the sprint
Status
TASK-00010
The 8–10 ICP interviews (this ticket) — active now
in_progress
TASK-00009
Competitor recon (DrilLedger + portals) — desk half of the gate
done
TASK-00011
Concierge MVP for 1–2 real subs — unblocks on a GO
blocked
TASK-00012
Synthesize + Day-21 go/no-go gate
backlog
Sources & caveats
Fact sources used this run:
git ✓adb ✓ticket files ✓this session's own actions ✓gstack — thintranscript — not relied on.
No commits in the last 8 hours — all TASK-00010 changes are in the working tree, uncommitted. Consider a commit sweep.
Attribution: the TASK-00010 edits + the two reports are this session's work. The TASK-00027–00053 tickets and other modified files come from concurrent sessions and are excluded from the tables.
The Action tracker is a faithful copy of the ticket kit built on 2026-07-14 (recon + prospect list) plus the 2026-07-15 council additions — anchored to files, not memory.
Recap reflects available context + git facts; a long/compacted session may omit earlier steps. File lists are derived from git, not memory.