Managed services for Run on Claude.
We build it. Then we run it with you. Managed services covers support, skill updates, new releases and new workflows, so the build keeps getting more useful after the handover.
Customers stay because the work keeps paying off, not because they are locked in.
Why managed services is the default
A build needs updates after the handover. Your sales stages change. A rep joins with a new territory. You add a product. Claude gets new releases. Your database vendor changes how a feature works. Each change means somebody has to update a skill file, a dashboard or the data model.
You can have one of your own people do that. Many teams do not have someone whose job is keeping an AI build current. Under managed services, we do it, and the person who built your system is the team that updates it.
What the retainer covers
Support.
You ask a question or report a problem, and a person on our team answers. Critical production issues are acknowledged within 2 hours. Response times for other issues are set in your contract.
Skill updates.
When your process changes, we update your skill files to match.
New releases.
When we improve how our builds work, we apply the changes that fit your build. Our engineers test each release internally, then your team runs user acceptance testing and signs off before it goes live.
Ongoing operation.
We watch that the system is doing its job: records are being filled, dashboards are current, and your Claude and database accounts work together as built.
New workflows as needs come up.
When you want Claude to do a new job, such as quoting or hiring, we scope and build it as part of the relationship.
We do not publish retainer prices. We tell you the build price and the retainer price before you commit.
The retainer does not include your Claude or database licenses. You buy those directly.
How it starts: the build, then operation
Request a demo.
You tell us how your team works today and which workflow to show you. You can upload one redacted deal, a process doc or a screenshot.
Your recorded walkthrough, then a live session if you want one.
We build the demo on your workflow and email you a recorded walkthrough within 3 business days. Our team can then walk through it live with you.
The build.
We build your skill files, data model and dashboards in your accounts.
The handover.
At handover you get: your data exported from the database as CSV files (one per table) plus a full workspace export in Markdown; documentation of the data model (every table, field and relationship, and what each one is for); the skill files we built for you; and the dashboard files. The data stays in your own database account the whole time; the export is so you can move it if you choose.
Operation.
Managed services starts. We support the system, update it and add workflows with you.
Why you can leave
Everything runs in your accounts.
We picked the best agent harness and the best database. You own what we build for you: the skill files, the dashboards, the data model and your data. If you ever want to move one or both, you can. Every handover includes an export of your data in open formats and documentation of the data model. Our own methods and tools stay ours.
What you give up when you stop is the service: support, updates, new releases and new workflows.
Who does the work
A US-based team. The people who run the demo and the build are the people who support the system.