Stack · 08Tokyo · Incoming Cambridge HSPS

The stack

The systems I run solo across investing (PriorMoves), distribution, and an agency layer (ElevateOS). Built for near-zero cost: free and local first, every outward action gated and dry-run before it sends.

08.1Distribution + outreach
01

LinkedIn growth engine

A headless connect and DM lane over my own session, paced on the limits that real CDR tools (gojiberry, Expandi, PhantomBuster) publish, with human gaps and warmup. It discovers my account's true weekly ceiling by watching for the block instead of guessing a number.

02

Commenter to DM flywheel

A post asks for a keyword, people comment, a responder DMs them the asset and sends a connect to the ones who are not connections yet. Warm inbound instead of cold outreach.

03

One 9am pipeline

Sync (Gmail, WhatsApp, reconcile), reach snapshot, source-of-truth doc sync, warm DMs, cold connects, and content fan-out chained into a single scheduled run. Nothing sends without an explicit enable flag.

04

Multi-platform fan-out

One canonical post adapted natively for X, Bluesky, Telegram, Threads, and newsletters, each re-linted before it ships. A platform turns on the moment its credential lands in the keychain.

08.2Investing engine — PriorMoves
05

58 investors, next-buy model

Each investor's disclosed 13F holdings plus a per-investor model of the stocks they are most likely to buy next, roughly six weeks before the filing. Walk-forward gated, so a market only ships a prediction when it clears the test.

06

Global registers

Japan, UK, Korea, and EU large-shareholding surfaces alongside the US book, plus Congress trades, activist 13D drift, and federal contract awards. All local, all zero cost, live at priormoves.com.

08.3Operating doctrine
  • Free or local first. Local models for text transforms, Codex for web discovery, paid APIs only when they are the only thing that works and the cost is stated up front.
  • Secrets live in the OS keychain, never in a file. Around 150 wired keys, each mapped to a use case.
  • Verify before claiming. No asserting a limit or a result from memory; check the source, then state it.
  • Everything reversible. Dry-run is the default, sends are gated, and every deploy has a one-command rollback.
Connect on LinkedInhappy to walk through any part of it