Jun 7, 2026 • 5 min read
Queues Are a Product Surface
Internal systems work better when teams design the queue itself as a product surface instead of focusing only on the single-record happy path.
Dev Blog
Essays on HubSpot architecture, AI workflow design, and engineering delivery for teams that care about what happens after launch, when operators, edge cases, and changing requirements put the real system on display.
Jun 7, 2026 • 5 min read
Internal systems work better when teams design the queue itself as a product surface instead of focusing only on the single-record happy path.
Jun 4, 2026 • 5 min read
Prompt edits can change routing, escalation, and decision quality in production, so they deserve versioning, evaluation, and rollback.
May 22, 2026 • 4 min read
Workflow quality depends on whether each state has a clear owner, a clear next action, and a clear escalation path.
May 21, 2026 • 5 min read
Useful documentation reduces coordination drag by making state, ownership, and recovery legible without extra meetings.
May 20, 2026 • 4 min read
Operational simplicity lets teams publish, recover, and change systems without constant escalation or hidden process drag.
May 18, 2026 • 4 min read
Internal tools succeed when they reduce operator friction in real queue work, not just when they look polished in demos.
May 16, 2026 • 4 min read
Boring integrations stay reliable because their contracts, ownership, and failure handling are explicit from the start.
May 6, 2026 • 4 min read
Launches go better when teams instrument critical workflow states, delays, failures, and human intervention before go-live.
May 4, 2026 • 4 min read
Fast delivery only lasts when teams keep change cheap and refuse to let temporary shortcuts harden into architecture.
May 1, 2026 • 5 min read
This dev blog is where I write about the architectural, operational, and delivery decisions that determine whether systems keep working after launch.