---
title: Active Priority
created: 2026-05-02
updated: 2026-05-02
type: goal
review-cadence: weekly
status: draft-awaiting-rocky-review
drafted-by: cowork (curator) during HQ design grill session 2026-05-02 ~21:30 AEST
---

# Active Priority

> HQ reads this file at boot every session. The block under `## Active Priority` heading is the priority HQ scores the grill against. Rocky reviews and revises this file weekly (or whenever priority shifts). Read fresh, never pinned.

## Active Priority

**Two-sided marketplace bootstrap for RateRight.**

Both supply (workers) and demand (contractors) need active acquisition. Currently neither side has liquidity — 300+ contractor leads in pipeline but only 1-2 active on site; worker side similarly under-supplied.

> ⚠ **IMMEDIATE BLOCKER (2026-05-02):** rateright.com.au has been DOWN 50 days per claude-code-rr's truth audit. Hermes' WhatsApp bridge is holding port 3000; systemd `rateright-app.service` crash-looping with 47k+ restarts. **Acquisition strategy below cannot convert until the site is back online.** See [[10_RateRight/_Brain/Open-Threads]] item 0.

## Strategies (the Hunt)

Active acquisition, not passive listing. Don't wait for inbound; go get them.

- **Hunt supply** — actively browse Facebook groups, Gumtree, and similar boards for workers looking for jobs. Outreach via email, text, or call.
- **Hunt demand** — same channels, same posture, for businesses/contractors looking for workers. Same outreach.
- **Seek-style bootstrap** — scrape job listings from Seek, Gumtree, etc. Post on RateRight so the platform looks busier than it is. Pattern Seek itself used in early days. Tooling: investigate Claude in Chrome (browser-driven, lower bot-detection risk than headless Playwright). Bulk volume blocked by ToS + rate limits — tactical scraping only.

## Why this and not X

- **Why not just demand-side acquisition (work the 300+ leads):** Susan's pipeline has been cold ~71 days. Even if revived, contractors won't convert without workers available. Supply side has to grow in parallel, not after.
- **Why not product/feature work:** site has been down 50 days and nobody noticed. The product exists; the constraint is liquidity, not features. Once site is restored, re-verify this assumption.
- **Why not waiting for organic growth:** marketplaces with weak network effects don't grow organically. Seek bootstrapped; the same pattern fits here.
- **Why not pivoting:** 14 months of build-up, real codebase, real Stripe integration (live mode configured, charge processing unverified pending site uptime). Pivoting now is sunk-cost panic, not strategy.

## Last Reviewed

2026-05-02 — initial draft, voice-typed strategy captured during HQ design grill. **Awaiting Rocky review.** Rocky should re-read tomorrow morning, edit anything that's wrong, and update `updated:` field in frontmatter.

## Open questions for next review

- Site uptime fix path — see [[10_RateRight/_Brain/Open-Threads]] emergency item.
- Stripe live key authentication unverified per truth audit.
- Pawel + Susan's lead pipeline — 71 days cold. Drop or revive? Decide.
- Seek/Gumtree/Facebook ToS for browser-driven scraping — investigate before scaling.
- Routines feature in Claude Code Desktop (per 2026-05-02 research) — potential replacement for Hermes-as-COO. Investigate.
- Decide: PR project as new top-level `13_PR/` folder or sub-folder under `20_Personal/`. Approval required per no-new-folders rule.
- "Horror project" voice-typed entry from grill — clarify what this actually is.