The most surprising thing about hiring your first AI teammate is what you don't have to do. No prompt engineering. No workflow diagrams. No blank canvas asking you to configure an "agent" from scratch. You start Dock on your Mac, and your first hire, a Chief of Staff, arrives already working.
"Already working" is literal, and it's the part worth slowing down on.
What arrives with your first hire
A new Chief of Staff comes with standing routines provisioned from the start: a daily brief on weekday mornings, an end-of-day wrap-up, a nightly self-review. You didn't schedule any of them. They're the baseline of the job, the way a human chief of staff wouldn't ask you whether they should prepare for the morning.
It also arrives with the machinery of a real teammate rather than a chat window: a name, an address you can message directly, memory that starts learning you and your company from the first conversation, and the ability to hire specialist teammates under it as your goals grow. Later specialists start leaner, with one standing routine rather than a handful, and pick up responsibilities as you hand them over.
The first message from your Chief of Staff isn't "how can I help?" It's a report on work that's already in motion.
Your accounts, your machine
The step people expect to be painful, giving the agent access to tools, mostly isn't a step at all. Your teammates run on your own machine, through your own Claude account, using the connectors you've already set up there: your email, your calendar, your docs. Dock doesn't sit between you and those accounts; the credentials stay yours. If Claude can reach it, your Chief of Staff can work with it.
The first hour, honestly
The first hour looks like this: "30 seconds" gets you a working teammate, not a finished relationship. In the first minutes, you'll get the introduction and see the routines that are live. In the first conversation, the Chief of Staff starts building its understanding of you and your company, and the fastest thing you can do is give it a real objective rather than a test question. "Keep an eye on my inbox" beats "what can you do?"
By the end of week one, the pattern that matters has usually emerged: the second hire. Most teams add a specialist shortly after the first teammate proves out, because the Chief of Staff surfaces exactly which standing responsibility deserves its own owner. That's the actual on-ramp to running a team rather than operating a tool: one generalist, fast, then specialists, deliberately.
The 30 seconds is real, but it's not the point. The point is what's on the other side of it: not a configured product, a staffed role. Here's what that first teammate can actually do.