Writing · Execution

Why I don’t take access to your systems

Most consultants ask for admin credentials in week one. It’s the fastest way to build something your team abandons in month six.

Sam Hirbod · September 2026 · 4 min read

Every engagement starts the same way. Somewhere in the second call, someone offers me a login.

I turn it down.

Part of that is the security review. Most of it is what happens eighteen months later, when the thing I built is still running and nobody in the building knows why.

What the login actually costs

Ask for admin access and you’ve put a security review on the critical path. At a company of any size that’s two to six weeks before anyone writes anything. Legal wants to know where the data goes. IT wants to know what’s being connected. Both are right to ask.

The delay isn’t the expensive part. What the arrangement teaches is.

If I build it, I know how it works and your team knows that it works. Those are different states, and the gap stays invisible until something breaks. A field gets renamed. A workflow quietly stops firing. The person who asked for it leaves. Now you’re paying me to maintain something you own on paper and can’t touch in practice.

What I do instead

I write the specification. Your team builds against it.

The specification isn’t a wish list. It names the trigger, the data the system reads, the decision rules it applies, the output it produces, who receives that output, and what should happen when it produces nothing. It’s precise enough that two different people would build roughly the same thing from it.

The person who builds it is the person who can fix it.

Work starts the week we agree scope instead of the week security signs off, because there’s no login to review. Your team learns the system by building it. They choose the field names, they hit the edge cases, and when it breaks the person who wired it is still there.

The specification also outlives the tool. Change CRMs and it still describes what you need. The implementation was never the valuable part.

What this costs you

The first build is slower. I could configure it in an hour. Your team takes a week, because they have other work. If you need something live by Friday, this is the wrong model and I’ll tell you so.

You also need someone who can build. Not an engineer necessarily. An operations person who’s comfortable in your own admin panel is usually enough. If nobody at your company can do that, the specification sits there and we’ve both wasted the quarter. Worth finding out before you pay anyone, including me.

Where I do build

Anything document-shaped I draft myself: scripts, delegation structures, decision maps, board pre-reads, negotiation frames. There’s no team to hand those to. The artifact is the deliverable.

Personal AI workflows for an individual leader I build and hand over. One person’s week isn’t a company stack, and there’s no operations team standing behind it. That’s the end state I’ve written about elsewhere, the AI-augmented executive.

And when a company wants me inside its environment building agents directly, I’ll do that. It needs access and whatever review that triggers, and I’ll be clear about the trade-off. Most pick the other route once they’ve heard the argument about March.

The question worth asking

Ask any consultant, including me: what happens to this if you disappear?

If the answer involves calling them, you didn’t buy a system. You bought a retainer.

Sam Hirbod builds execution systems and AI agents for executives and revenue teams, through TLDR Coaching LLC in New York. He’s shipped ten production AI agents in his role at HubSpot (NYSE: HUBS) and coached more than 1,000 professionals. More about the practice.