← All demos
THE McBURNEY GROUP
People-centered. AI-forward.
Build Your Own Digital Coworker
You've hired before. You wrote down what the role does, what they can touch, and what stays your call. Do that here. Pick one role, fill the nine fields, paste a starter into Claude.ai, and you've got a coworker by lunch. Swap anything in [brackets] for your own details.
Which role to build first
Think about last week. Where did the hours go? Probably not the work you're proud of. Your first hire is the stuff you keep doing yourself and quietly resent. Look for work that is all three of these:
It eats your timeHours a week, or the same small task over and over.
It's repeatableThere's a clear input and a clear output. You could explain the steps.
It isn't the part only you can doTaste, relationships, the final call, those stay with you.
The test: if you wrote down exactly how you do it, could someone else follow it? If yes, hire it out. Start with capture and triage, Echo and Command touch everything, so the time you get back shows up in the first week.
How to use this
- Pick one role. The work you keep doing yourself and wish you didn't.
- Write the job description. The nine fields below. Same questions you'd ask of a person.
- Write the baseline down first. The five numbers. Ten minutes now, and you'll know later whether it worked.
- Build it where it fits. Claude.ai to start. Cowork when it lives in your week. Claude Code when it has to plug into your systems. Don't overbuild.
- Read everything it sends. You own the output. Always. (More on that below, it cost me once.)
The template, nine fields
Baseline the five numbers
Here's the catch: if you don't write the number down before you deploy, you can't measure anything after. So write it down first. Even a rough one.
Three starters, copy and adapt
Each one is a full job description. Tap to open it. "Copy job description" gives you the text to keep. "Copy setup prompt" gives you a message to paste straight into Claude.ai and start working. Replace anything in [brackets] with your own details.
Before you leave
A confession. Early on, I skipped the review step and sent garbage to a thousand people. Once. You only do that once. Here's the other side of it: Echo, my meeting coworker, has gone six months without missing a single action item. Before Echo, I'd walk out of a call sure I had it all, and find the thing I dropped a week later, usually from the client. That gap, what I was losing versus what I lose now, is the number worth measuring.
You own the output. A digital coworker drafts. You decide. Keep the review step, write your baseline down, and check the numbers again in 30 days. If they moved, you've got a coworker. If they didn't, the job description needs work. Either way you'll know, which beats a feeling.