Watch
$1,500 USD a month
A handful of automations that must keep running. Monitoring, fixes inside the cap, the monthly report, the security re-check.
Someone who runs, fixes, and keeps secure the agents and automations your business already has.
For businesses where the automation exists but nobody owns it: a contractor built it, a tool grew, a workflow runs until it does not. A monthly retainer with hours capped in writing, a written report every month, and a security re-check so it stays as safe as the day it was built.
from$1,500 USD a month
Three tiers: $1,500, $2,500, and $5,000 a month. What moves it: how many agents and automations are in scope and how fast you need a fix when one stops.
Who this is for
You have agents, workflows, or integrations doing real work: reporting, syncing, monitoring, sending. They were built by a contractor, a former employee, an agency, or VXSec. Nobody on the team owns them, and the first sign something broke is a client noticing.
The retainer makes VXSec responsible for them, with a written record of what runs, what changed, and what was checked, every month.
- Scope
- The agents and automations listed in the written scope, on the systems they touch. New builds are quoted separately.
- Hours
- Capped in writing per tier. Unused hours do not roll over; work beyond the cap is agreed first.
- Term
- Month to month. Terms are in the written scope. The runbook stays with you.
What a month looks like
- Monitoring: every automation in scope is watched, and a person is told when one stops or drifts, with the evidence.
- Fixes: broken syncs, expired tokens, changed APIs, failed runs, fixed inside the cap and logged.
- Small changes: a new field, a changed schedule, a new recipient, an extra check, inside the cap.
- Monthly written report: what ran, what broke, what was changed, what to decide next. Short enough to read.
- Security re-check: scopes, secrets, actions, inputs, connectors, and the human gate re-verified, because tools and permissions drift.
- Out of scope: net-new agents and automations, which get their own build quote; infrastructure projects, which get an infrastructure quote.
Three tiers
The hours in each tier are stated in the written scope. Pick by how much is running and how fast you need it fixed.
Run
$2,500 USD a month
Several agents across more than one system. Everything in Watch, more hours for changes, and a standing priority on fixes.
Own
$5,000 USD a month
An operations layer your business depends on daily. Everything in Run, the most hours, and the fastest fix commitment, stated in the scope.
How it starts
A review first, so the retainer covers what is actually there.
- Inventory: every agent, workflow, integration, and the accounts and keys they use, listed with what each one does and touches.
- Findings: what is fragile, what is over-permissioned, what nobody can explain, written down with a fix for each.
- The scope: the tier, the hours, the fix commitment, and what is out, in writing. You approve it, the month starts.
Questions about the retainer
Can you take over something someone else built?
Yes. The review at the start finds out what it does, what it touches, and where it breaks. If it cannot be owned safely as it is, the scope says what has to change first and what that costs.
What counts as a fix and what counts as new work?
Keeping what is in scope doing what it did is a fix. Making it do something new is a change, inside the cap if small, quoted as a build if not. The line is drawn in the monthly report before it is drawn on an invoice.
What access does the retainer need?
Named accounts with the least access that does the job, listed in the scope, with admin actions logged and reported monthly. Keys live in your systems, not VXSec's.
Can we stop?
Yes, with the notice stated in the scope. Everything, including the runbook and the monthly reports, stays with you.
Send the problem in writing.
What you are running, what is wrong or what you want built, and links if you have them. A written scope and a fixed price come back within two business days.
Or email [email protected] directly.
- You send: the tools involved, what should happen, what happens instead.
- You get back: a scope in plain words, a fixed price, what is out, and how it will be verified.
- Then: a call if you want one, or straight to the spec.