AI Consultant or Build It In House?
Somebody has to scope the job, set up the runtime, write the agent's files, connect the tools, rehearse it and train the team. The question is whether that somebody already works for you. Here is how the two routes compare for an owner-led business.
The Install Is the Easy Part
The runtime an Apollo Claw agent runs on is open source. A capable technical person can install it in an afternoon, and that is where most in-house projects start and stall. The hard parts are the ones that look soft: deciding which job the agent owns first, writing its persona and rules in your words, connecting the tools with the right permissions, running it through real situations before it touches a live inbox, and teaching the team what to trust.
A consultant who has done this for a law firm, a medical practice and an insurance agency has made those decisions before and knows which ones bite. In-house staff know your business better than any consultant will. The right answer depends on which of those two kinds of knowledge you are short of.
What Each Route Costs You
Measured in time, attention and what you keep, since those are the costs an owner feels first.
| Build in house | Apollo Claw | |
|---|---|---|
| Who does the work | Your IT person, a developer, or you, around the day job. | A consultant who has set up agents for firms like yours, with your team in the room. |
| Time to a useful agent | Weeks to months, most of it learning the runtime and deciding scope. | The first week for a scoped job: about 15 minutes to build online, then rehearsal and training. |
| Scope | Often everything at once, which is how an agent ends up doing each job poorly. | One job first, named rules, then the second and third jobs on a schedule. |
| The agent's files | Written by whoever installed it, in whatever shape they chose. | Written from your intake in your words, and yours to read and change. |
| Where it runs | Wherever your person put it. Often a laptop at first. | A Mac Mini on your network or a private virtual server, encrypted and locked down from day one. |
| Permissions and rules | Decided as you go, usually after something goes out that should have been a draft. | Decided before anything is connected, written down, and enforced by the runtime. |
| The first 30 days | Whatever time your person has left over. | Hands-on onboarding and co-training with every custom build, with support a message away after. |
| When something breaks | Your person reads the logs, if they still work for you. | We read the logs; it is the job. |
| What you keep if you part ways | Everything, and the knowledge in one person's head. | Everything: the hardware or server, the files, the agent and its memory. |
Build It Yourself If
Some companies should keep this inside. These are the signs.
You Have a Real IT Team
An engineering or IT group with time on the roadmap can own the runtime, the permissions and the rehearsals, and will know the systems better than we will.
The Agent Is the Product
If what you are building is something you will sell or run for thousands of users, that is software development, and it belongs with your developers.
Policy Rules Out Outsiders
Some organizations cannot let a third party near their systems during setup. The runtime is open source; we are happy to point you at it.
Bring Us In If
The Owner Is the Bottleneck
You want an agent on your own inbox and calendar this month, and the person who would build it is you.
There Is No Technical Bench
A practice or firm with an outsourced IT vendor and no developer has nobody to learn a runtime on the side.
The Data Is Sensitive
Client files, patient records, financials. The permissions and the rules have to be right the first time, and that is experience rather than cleverness.
You Already Tried
A stalled build with a weak scope is the most common thing we are asked to look at, and the quickest to fix.
The Questions Owners Ask
If we hire you, do we end up dependent on you?
The agent runs on hardware reserved for you, and every file that defines it is plain text you can read and change. If you leave, the agent stays. We would rather be the people you call for the next job than the people you cannot leave.
Can our IT person work alongside you?
Yes, and it goes faster when they do. They know the systems and the permissions; we know the runtime and the agent files. The 30 days of hands-on onboarding is where that handover happens.
What if we already started in house and got stuck?
Common, and fixable. Most stalled builds have a working runtime and a weak scope: the agent was asked to do everything and does each job poorly. A scoping call usually finds the one job to give it first.
How long until an agent is useful?
With a scoped first job, the first week. The online build takes about 15 minutes; the rehearsal with real scenarios and the team's first days with it are what make it useful, and that is what the first month is for.
Unsure Which Route Fits?
A discovery call is a scoping session either way. If in house is the right answer for you, we will say so.