Discovery summary
A readable HTML report explains the go/no-go decision, the strongest workflow candidate, customer questions, and next actions.
LOCAL BACK-OFFICE AUTOMATION / GREATER SAN ANTONIO
Back-office automation that keeps watch on your machine.
APPROVED FILE IN · CLEAN INVOICE OUT
Vigil starts by probing the back-office files your business already uses, then installs one deterministic local workflow at a time. Invoices are a common first pilot, but the same model can cover quotes, reports, reconciliation, reminders, expense categorization, and file monitoring. No hosted portal, no cloud upload, no unpredictable agent.
0 uploads
Data stays local
$750 setup
+ $149/mo support
Your hardware
Installed, not hosted
LOCAL PIPELINE · WATCHDOG CURRENT
Most automation tools ask you to upload your books or trust an agent to decide what happens. Vigil doesn't.
No cloud dependencyThe customer pipeline makes no accounting or bank API calls and no LLM calls. It runs against your local files.
Secrets in the OS keychainMail credentials live in your operating system's keychain where available — not in a config file in plain text.
No unpredictable agentAutomation runs from reviewed rules, accepted files, and customer-approved activation steps.
// EXPLORATION FIRST
The probe is the first deliverable
Before installing anything, Vigil maps the customer's local files, candidate workflows, blocked paths, customer questions, and exact next commands. The result is an exploration report, not a guess from a roaming agent.
Opportunity map
The probe separates ready, needs-review, and blocked automation paths across billing documents, reporting, reconciliation, expenses, follow-up, and monitoring.
Redacted evidence
Support-safe findings can be shared without raw invoices, customer lists, bank rows, source spreadsheets, passwords, or OAuth tokens.
Example exploration report
- Primary candidate: invoice or quote generation from a stable Excel export.
- Expansion candidates: reports, dunning, reconciliation, expense categorization, and file monitoring.
- Customer questions: source of truth, reviewer, send approval, fallback process, and support contact.
- Recommended commands: build config, run dry-run readiness, then create a redacted support bundle.
What the probe prevents
- No broad automation promise before the files prove a repeatable workflow exists.
- No agent deciding what to automate or send.
- No hosted account area, bank feed, QuickBooks connection, or hosted data room required for discovery.
- No live activation until the customer reviews the dry-run evidence.
// WHAT IT DOES
One local runtime, many file-based workflows
Vigil fits the work your business already runs: spreadsheets, exports, reports, statements, folders, emails, archives, and exception review. The pilot starts narrow, then expands only where the probe finds repeatable value.
Billing documents
XLSX / CSV›››PDF · SENT
Generate branded PDF invoices, quotes, estimates, and customer documents from the spreadsheets you already maintain, then send approved outputs through your business mailbox.
- Reads approved Excel and CSV rows
- Branded, consistent PDF output
- Sends via your own OAuth mailbox
Reports & reconciliation
LEDGER›››IMPACT REPORT
Track payment matching, exception queues, expense categories, and monthly impact summaries so the admin time you save is visible at review.
- Payment matching and categorization
- Monthly impact report for review
- Built from your local records
Follow-up & monitoring
WATCH FOLDER›››ARCHIVED
Vigil can watch folders, archive processed files, generate controlled follow-up, and surface failed jobs so nothing slips through silently.
- Folder watching with a watchdog
- Processed files archived automatically
- Failed jobs isolated for support
Discovery-backed handoff
RECEIPT›››ACTIVATED
Setup walks through the probe report, install receipt, first-workflow dry run, readiness gate, and customer-approved activation. There's no hosted upload form to trust.
- Receipt-driven setup on site
- Non-destructive dry run first
- Monitoring only after you approve
// THE PIPELINE
From exploration to filed evidence
The service starts by mapping the workflow, then runs deterministic local steps. Each stage is non-destructive and leaves a trace, so you can always see what happened.
01
Explore
The probe maps local files, workflow candidates, customer questions, and next commands.
02
Scope
You choose one approved workflow, one input shape, and one reviewer before activation.
03
Run
Vigil executes the reviewed local rule path against approved files.
04
Deliver
Outputs are saved locally, optionally sent through your mailbox, and archived with evidence.
05
Evidence
Status, logs, and impact data are ready if you need support.
DEPLOYMENT HANDOFF · SIX REVIEW-GATED STEPS
1
Install receipt
The setup package records exactly what was installed and where, with a receipt you keep.
2
First-workflow dry run
The first approved workflow runs non-destructively so you can confirm the output.
3
Readiness gate
Generated PDFs are checked against loaded rows before anything is scheduled.
4
Approved activation
Monitoring is enabled only after you review the activation artifacts and approve.
5
Progress check
A run confirms the live pipeline is behaving the way the dry run did.
6
Support bundle
If you need help, a redacted bundle becomes a case on the operator dashboard.
LOCAL-FIRST BY DESIGN
Your books stay where your books belong
The customer pipeline has no LLM calls, no unpredictable agent, and no accounting or bank API dependency. Diagnostics are summarized into redacted bundles for an operator to review. Raw customer files are not included by default.
- Secrets in the OS keychain
Where the operating system supports it, credentials are stored in the keychain rather than plain text.
- Dashboard binds to localhost
The operator dashboard listens on your machine by default and is not exposed publicly.
- Security scans & SBOM in release
Releases run security scans and ship a software bill of materials so you know what's inside.
- Customer-visible action stays human-approved
Support evidence helps the operator diagnose the issue. It does not send replies or change customer workflows on its own.
- READ THE CUSTOMER SECURITY OVERVIEW →
// OPERATOR VIEW
Support that starts with evidence
Every session opens with status, doctor checks, error-queue summaries, log counts, and impact data. You send one redacted support bundle; the operator dashboard turns it into a case — no screen-sharing your books.
Watchdog
Current
Dead letters
0
SMTP
OAuth
Support bundle
Redacted
// CHARTER PILOT PRICING
Start with one local billing workflow this month
One assisted charter pilot, then managed support that keeps it healthy. Begin with the pilot offer or review the demo flow first.
CHARTER PILOT
Setup$750 setup
Managed support$149/mo support
Includes the exploration report, monthly support monitoring, a progress check, release checks, and evidence review. Pilot is scoped to one workflow first, then expanded as the probe and dry-run evidence justify it.
BOOK A DEPLOYMENTFAQ
Straight answers
The things small businesses ask before they let anything near their back-office workflows.
No. The v1 deployment runs locally on your machine. There's no hosted portal and no required cloud service for the customer pipeline.
No raw invoices, bank rows, customer lists, or source spreadsheets are included in the default support bundle. Diagnostics are redacted into a summary an operator can work from without seeing your customers' data.
No. Vigil runs deterministic workflows from reviewed rules and approved files. Customer-visible sends, template changes, and activation steps stay human-approved.
Approved Excel and CSV files that you place in the inbox folder. Vigil works from the spreadsheets you already keep — you don't have to change your source of truth.
Through an assisted package handoff: an exploration report, install receipt, non-destructive first-workflow dry run, readiness gate, and customer-approved activation. Monitoring switches on only after you've reviewed and approved.
Vigil is built in Texas and deploys for small businesses in the Texas Hill Country and the San Antonio area. Reach out and we'll set up a deployment.
Put a vigilant pair of eyes on your busywork
Book a deployment and we'll probe the workflow, choose the first local automation, and keep the evidence visible before anything expands.