Jul 1, 2026 • 3 min read
The Model Is Only One Part of the Interface
AI product quality depends on the full interface around the model: inputs, controls, evidence, state, review paths, and recovery behavior.
AIProductSystems
Dev Blog
Building systems that survive real use.
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
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.
OperationsSystemsDelivery
Jun 5, 2026 • 5 min read
Source of Truth Is a Workflow Decision
Systems stay easier to operate when teams decide source of truth by workflow state and correction path instead of letting multiple tools feel authoritative at once.
ArchitectureDataSystems
Jun 1, 2026 • 6 min read
Documentation Is Part of the AI Stack
AI systems get more reliable when documentation defines the terms, states, tool behavior, and exception handling the workflow depends on.
AIDocumentationSystems
May 26, 2026 • 8 min read
Most AI Product Problems Are Context Problems
AI features improve when teams treat context assembly as product and systems design work instead of assuming the model can infer its way past noisy, stale, or incomplete inputs.
AISystemsArchitecture
May 24, 2026 • 5 min read
Recovery Paths Are Part of the Product
Systems feel reliable when retry, rollback, reprocessing, and operator recovery paths are designed before failure forces them into existence.
OperationsArchitectureSystems
May 22, 2026 • 4 min read
Good Workflows Make Ownership Obvious
Workflow quality depends on whether each state has a clear owner, a clear next action, and a clear escalation path.
SystemsDeliveryArchitecture
May 20, 2026 • 4 min read
Operational Simplicity Is a Product Feature
Operational simplicity lets teams publish, recover, and change systems without constant escalation or hidden process drag.
OperationsDeliverySystems
May 18, 2026 • 4 min read
Why Internal Tools Fail After the Demo
Internal tools succeed when they reduce operator friction in real queue work, not just when they look polished in demos.
OperationsSystemsDelivery
May 16, 2026 • 4 min read
The Case for Boring Integrations
Boring integrations stay reliable because their contracts, ownership, and failure handling are explicit from the start.
ArchitectureSystemsDelivery
May 12, 2026 • 4 min read
Content Models Outlast Page Templates
Content models matter more than page templates once campaigns, channels, and teams need the system to reuse content cleanly.
HubSpotArchitectureSystems
May 10, 2026 • 5 min read
AI Workflows That Survive Contact With Reality
Durable AI systems win by structuring decisions, preserving evidence, and designing the workflow around the model for operators.
AIAutomationSystems
May 4, 2026 • 4 min read
Shipping Fast Without Building Fragile Systems
Fast delivery only lasts when teams keep change cheap and refuse to let temporary shortcuts harden into architecture.
DeliveryArchitectureSystems
May 1, 2026 • 5 min read
Why This Dev Blog Exists
This dev blog is where I write about the architectural, operational, and delivery decisions that determine whether systems keep working after launch.
ArchitectureDeliverySystems