Sec. 04 — Operating plan
The request queue
The posting: “the whole queue lives in Notion — requests logged and triaged, specs where developers can find them, a visible priority order and release calendar.” Here's the board I'd stand up, so anyone who asked for something can see where it stands.
Intake3
Triaged · spec'd2
In build2
Released2
Every request comes through one door: reproduce it, classify config vs code, resolve it or write the spec — nothing reaches the dev partner without going through the queue.
Owning site health
Stop the bleeding
- Lock staging (password + noindex)
- Fix robots.txt and the duplicate title/canonical
- Reconcile the $36 / $49 price card
Stand up the deck
- Full 40-item pre-relaunch checklist with evidence
- App-stack audit with keep/remove calls
- Notion queue live for CS, Brand, Growth, Product
First health review
- Speed, error rates, conversion by funnel step
- Recharge failed-payment / dunning watch
- Relaunch readiness scored and reported to Growth
Method & scope
Findings come from public data pulled Sep 19, 2026: page source (duplicate title/canonical, invalid Product JSON-LD, 77-script PDP), robots.txt, /products.json, the public staging.biotrust.com store, and a Lighthouse mobile audit. TruSkin and BioTRUST are sister brands under Wellbeam Consumer Health; the posting describes BioTRUST.com. Recharge is the one named tool I'd be learning at configuration level in week one; everything here I'd validate against the real theme and admin before shipping.