Summary
Fred built most of the Artemis tool stack in roughly one month using Claude. Half the stack is in production, the rest is in beta. Agents are being given these tools before they're polished because field testing is the fastest path to polish — but only if agents actually engage. This page defines what "engage" means and why disengaging is a competitive liability.
The Mandate
"When these things are in your hands and they are working, you can't completely disengage with this stuff."
Translated: using the tool one time and then going silent is not beta testing. Beta testing means:
- Report breaks in real time — "It's been down" is not acceptable three weeks later. If it's broken, tell Fred when it breaks.
- Flag quality-of-life gaps — "This would be better if it could do X" is the feedback that turns a beta into a winner.
- Use it on real business — Not "I'll try it when I have time." Use it on your next listing, your next buyer consult, your next offer.
- Stay on the list — Accept the Meta Business Suite invite. Get connected. If you're not on the integration list, you're not in the game.
Why Agents Drop Off
The pattern Fred is fighting against:
- Agent tries a tool once, something small doesn't work, they quietly stop using it
- Agent never reports the issue
- Tool sits in the portal going unused, no feedback accumulates, it never improves
- Six months later: "I didn't use that because it was broken"
Fred's response: that's a mutual failure. He builds it, you test it, you tell him what's wrong. If either side drops out, the loop breaks.
Competitive Framing
Fred's positioning to the team:
- Other team leaders are competing with their agents for production. Fred isn't — he doesn't produce. His full-time job is giving the team an unfair advantage.
- What Artemis agents have access to is not available anywhere else in the market.
- Agents who do NOT engage with these tools will be out-competed within a couple of years by agents who do — this is a full-stop, no-qualifier claim.
Comparison to Paid Tools
| Previous Tool | Replaced By | Cost Before | Cost After |
|---|---|---|---|
| Sked | hermes-social-command | ~$1,000/yr per page × 24 | API costs only |
| Curaytor | Spark + Lyra + Hermes stack | $1,800/mo | ~$200/mo target |
| Cloud CMA | iris-tool-suite | Monthly subscription | API costs only |
| PropStream | orion-seller-buyer-intelligence | Monthly subscription | API costs only |
| Geniuslink | lyra-link-intelligence | Paid tier | Free to agents |
| Generic closing calculator | delphi-closing-calculator | Paid subscription Jake found | Free to agents |
If Fred were charging agents for all of this, he says he wouldn't be charging enough.
What Agents Owe Fred
Three behaviors, in this order:
- Commit — decide this matters and put the tools in your workflow
- Learn — read the pages, try the features, know the inputs and outputs
- Engage — report breaks, request features, share what's working
This is not a pitch for optional adoption. It's the minimum viable participation level for agents who want the competitive edge the team is building.
Related
- seneca-adoption — Same adoption gap pattern; same coaching response
- identity-first-coaching — "The Gatekeeper" framework applies — discomfort in learning new tools is confirmation you're doing the right thing
- marketing-stack-migration — The broader economic case for why this stack exists