The Road to UNBOUND Office Hours - Build Your Own Harness, or Outsource Your Understanding?

The first Office Hours on the road to Boston, and it belonged to the guest.

Shubham Nigam arrived having genuinely wondered whether this was a bus trip. "Maybe some five co-hosts will be there, they will be entertaining on during this bus journey." Ten years in the HubSpot ecosystem, three trips to the event, and he came with two real questions and the nerve to ask both.

The first is the one every architect is circling. Business users are building their own tools now, so, in his words, "there are less inquiries come to me." His own answer was to move up: build the more complex things, the logic nobody vibe-codes on a Tuesday. But he pushed further than that. If your workflow calls out to an agent, you have taken on a second dependency on top of HubSpot, and when that agent's servers go down your workflow goes with it. So why not spend the tokens once, build your own app with the same logic, and own the thing outright?

Rob Jones reframed it into the sentence the room needed: how come humans aren't using Claude Code to build their own Claude Code harness so they don't need the harness anymore? Then he answered it with a boat. Better to have a friend with one than to own one, because ownership is maintenance, and every hour spent maintaining the thing you built is an hour not spent on the customer it was built for.

Chris Carolan took it somewhere less comfortable. We have been here before, and we did not cover ourselves in glory: fifty percent CRM adoption, PLG plug-and-play, big agency money, all of it spent trying to buy our way out of human-led dysfunction. No technology solves change management. What AI does is reveal the problem faster and far more cheaply, which is the same lesson arriving in a new outfit.

George B. Thomas declined the premise entirely. He is not passionate about harnesses, he is passionate about content, education, and entertaining the humans who are bored out of their minds keeping up with HubSpot, so that is what he points AI at. Then he and Chris spent a genuinely good five minutes disagreeing about what the word even means.

Casey Hawkins found the load-bearing question underneath all of it. The risk is not outsourcing the building. It is outsourcing the understanding. You can hand AI your ability to think and to communicate, and the day the model is down or wrong you have to explain a thing you never understood. She put herself on the wrong side of it on purpose: she is the average person who wants AI for convenience, and she regularly spends thirty minutes getting AI to find a workflow she could have opened herself.

That produced the most practical moment in the hour. On live client work this week the team was two hundred steps ahead, weighing a custom agent that would read the record and write a note, before a fourth human said: what if we just made it visible? A CRM index page. No credits, no agent, problem solved. An index page still goes a long way.

It closes where it started, with Shubham. He is building a monitoring tool on weekends because he has spent years afraid of what a rogue access token quietly did to a property, and a broken property breaks every workflow behind it. Chris's read: all of it comes back to visibility, because you cannot pay attention to what you cannot see, and fear is what fills the gap. Rob's parting advice was to enjoy the struggle, because that particular frustration is where most good things in this ecosystem came from.

And the last word is Shubham's, a decade in, saying he is moving toward training and toward building the tools he wishes he had had. "I haven't discussed anything about this with anyone." That is why the show exists. It accepts hitchhikers.