01home02about03services04now05hire me06cv
— work

Method overlogos.

No client names here, that's a rule. Three systems worth reading about, two more for range, and the actual artifacts of how I work. Click a case to open it.

Problem

A lean delivery team coordinating a growing portfolio through recurring meetings, three separate spreadsheets, and a daily pile of admin. Every status update was manual. The 14-build spreadsheet was the breaking point.

Approach

An agent-based operations platform instead of another tool subscription. Specialised agents watch channels, read meetings, draft updates, and escalate only what needs a human. Phase-lock discipline and approval gates built in from day one, so nothing reaches a client without sign-off.

Outcome

322 agents in production running daily briefs, end-of-day summaries, and weekly forecasts. The recurring meetings and the three spreadsheets are gone. The system runs after the laptop closes, which was the whole brief.

StackClaude API · Node.js · MongoDB · Slack + Gmail + meeting-intelligence webhooks

Problem

Twenty-plus concurrent builds tracked in a shared spreadsheet that broke every time someone touched it. Phases lived at "almost done" for weeks because nothing forced a decision.

Approach

A phase-locked delivery hub: Discovery, Architect, Build, Validate, Handover, AMC. Each phase has entry and exit gates, owners, and review windows. A phase cannot be half-closed. Done means done, or it isn't this phase.

Outcome

Every build visible end-to-end in one place: phase, gate status, blockers, finances, handover stage. The spreadsheet is retired, and "almost done" stopped being an acceptable status.

StackNode.js · MongoDB · review-gate + change-request workflow · Slack integration

Problem

An inbox of unsorted maintenance emails. Urgent issues buried under routine requests, out-of-scope asks quietly absorbed instead of flagged, and triage eating senior time every single day.

Approach

An AI classifier in front of the inbox. Every incoming request is read, classified by type and urgency, routed to the right owner, and tagged against its SLA. Out-of-scope requests get flagged as opportunities instead of disappearing into goodwill.

Outcome

The manual triage queue is gone. Requests arrive pre-sorted with SLA tags, nothing urgent waits behind routine noise, and scope creep became visible enough to charge for.

StackClaude API · email webhooks · SLA rules engine · CMS integration

AI sitemap generator

Drop in a discovery doc, get back a sitemap and wireframe spec. Hours of architecting per project, now a paste and a coffee.

mini

Client comms layer

Auth-protected portal for feedback, approvals, and signed-off scope. Lost email threads, retired.

mini

"Good delivery is 80% deciding, 20% doing."

— under the hood

The artifacts,phase by phase.

Twelve anonymised snippets of the actual working documents, walking Discovery through AMC. Sensitive content redacted.

Discovery
Sample discovery brief
redacted
Decision-rights matrix
stakeholder communication plan
Architect
Agent system prompt structure
redacted
Risk register example
live format
Build
Daily brief sample
anonymised agent output
Phase-locked dashboard
blurred, 20+ builds
Validate
Eval framework / QA checklist
live format
Agent eval / accuracy report
sample
Handover
Handover runbook sample
redacted
Weekly delivery brief
sample
AMC
Monitoring dashboard
triage classification view, anonymised
Maintenance log / iteration tracker
sample