Joshua Hayes

Most developers have the same problem.

They know how to build things. They have spent hundreds of hours learning, practicing, shipping. But when it comes to actually showing that work to the people who matter, they fall back on a resume that says proficient in React and hope for the best.

We just put Buddy on iOS and Android today, and the thing I didn't expect: I capture totally differently on my phone. At my desk I type. Walking to lunch or lying in bed at 11pm, I just talk. Half my best notes now start as me mumbling into my phone.

But I know dictation is divisive. Some people live in voice notes, others would rather do anything than talk to their phone in public

If you're building an AI agency, I think the questions from clients are going to move faster than the excitement around the output itself. At first they care about speed, cost, and whether the agent can do the job. Very quickly, though, they start asking who is checking the agent, what data it can access, and what happens when it gets something wrong.

That is usually where governance comes in. Clients want to know about data privacy, approval workflows, auditability, human-in-the-loop review, and what responsibility looks like when an agent makes a bad call or hallucinates. In practice, they are not just buying automation. They are buying a way to trust the automation.

It's one of the reasons I've been thinking a lot about this while building @OpenBox. Agencies and internal teams usually need a clear record of what the agent did, what it touched, and where human approval happened. That tends to matter more once the workflow is real and clients start asking harder questions.

Are clients asking you about compliance yet, or mostly speed and cost?