Not every piece of work is a platform. These are the small ones — and collectively they show the working style better than any single big project does: recurring chores become scheduled agents, and one-off investigations get closed the same day with something concrete.
Weekly 1:1 briefing agent
A scheduled Tuesday-morning cloud agent that prepares my 1:1 with the CEO. It sweeps Jira across two projects, Slack channels and DMs, email, and Lovable across five active projects, then produces a single short, phone-readable Slack DM: "Top 3 to discuss", plus 2–4 plain-language bullets per project.
Deliberately no ticket keys and no links. The output constraint was the actual design problem.
The engineering here was all in prompt iteration: classification rules for what counts as discussion-worthy, and formatting constraints tight enough that it reads on a phone in the hallway thirty seconds before the meeting. A brief you have to sit down and study is a brief you don't read.
Nightly acceptance-environment E2E suite
A Playwright end-to-end regression suite against the acceptance environment, run nightly in CI with a morning Slack report — and a hard rule encoded that it may never target production. Caught regressions in the externally-developed site before releases reached anyone.
Search Console triage → dev-ready ticket in an hour
Google Search Console flagged "LCP longer than 2.5s (mobile)" across 101 URLs. One short session: analyze the GSC exports, root-cause against the live site, produce a ticket the dev team could pick up immediately.
A good template for export → root cause → actionable ticket turnarounds. The value isn't the analysis, it's that it left the session as something someone could act on.
HubSpot CLI workflow investigation
Set up the HubSpot CLI to audit workflows tied to email subscriptions. Notable side-quest: diagnosing and working around Git Bash's MSYS path-mangling on Windows.
Ended blocked on a missing automation API scope — and documented as blocked, with the exact scope needed, so whoever picks it up starts where I stopped rather than rediscovering it.
Phone validation for prospect mobiles
Evaluated a validation vendor for scraped prospect mobile numbers, feeding the scraper and CRM pipeline. Gotchas documented rather than discovered twice: the unique customer_id requirement, and a demo environment that isn't actually isolated.
What these have in common
- Recurring chores become scheduled agents with tightly-designed outputs — the 1:1 brief, the nightly E2E report. The output format is the product.
- One-off investigations get closed out same-day with a concrete artifact — a ticket, a report, a documented blocker — rather than lingering as a half-remembered thread.
- Even the blocked ones ship something. A documented blocker is a deliverable.