After the build, we stay.
Every system we build is registered on our monitoring before its first visitor arrives, and it stays there. Care keeps what we built working. Care Operating watches the rest of your stack, and your AI policy with it.
Month to month, thirty days’ notice either way.
A month of Care, as it runs
Each week we check vendor changes, the connector list, and your AI policy against the tools your team uses. If nothing changed, you hear nothing. If something did, you get one line.
Illustrative. A month of Care Operating, as the firm receives it.
Care watches what we built. Care Operating watches your stack.
Hosting, the five-minute health check, security upkeep, version safety, one hour of changes.
Each month, how often AI assistants read your site while answering someone.
Care, plus four hours of build time a month and a quarterly review.
Health check, patching, version safety, one hour of small changes.
Four hours a month. Open to any firm; the first month is the read.
A month of Care never quietly becomes a project.
Anything that needs more than an hour is scoped and quoted as its own piece.
A watch on something we have never read is a guess.
Care follows a build. Care Operating begins with a read, inside the same price, unless you have completed AI Foundations or The Written-Down Firm.
What your compliance officer will ask about hosting and access is answered on Trust.