COMMON QUESTIONS. STRAIGHT ANSWERS.

Vigil is built for owners and small teams that want more value from current tools, more capacity from the people they have, and a practical path to improve everyday work.

Choose AI Office Readiness when your team wants to think, create, research, communicate, or analyze with more confidence. Choose Rule-Based Business Automation when approved inputs should move through the same reviewed rules to a consistent output.

No. Construction is one focused service lane, while AI Office Readiness and Rule-Based Business Automation can help owner-led small businesses in many industries.

Stable office work with recognizable inputs, repeatable steps, a defined output, visible exceptions, and a responsible reviewer is the strongest fit. Invoices, documents, reports, exports, and recurring file handling are useful examples.

No. Vigil removes repeat preparation, makes exceptions visible, and improves handoffs. Judgment, professional responsibility, customer relationships, and final approval remain with the people who own them.

Vigil reviews the problem, current workflow, people involved, tools, representative inputs, exceptions, and desired result. If the work fits, you receive a defined scope that states the deliverable, boundaries, review path, acceptance criteria, and quote.

Yes. Each service lane stands on its own. Start with the problem that costs the most time, money, or attention, then connect another lane only if the first result makes that worthwhile.

Timing depends on the workflow, source quality, access, review requirements, and deliverable. The proposed milestones and dependencies are stated in the scope before work begins rather than estimated with a generic timeline.

Most work is quoted against a defined result and its implementation boundaries. Any fixed pilot price is shown on the relevant service page; broader or custom work receives a scope-specific quote before delivery begins.

Bring one concrete example of the problem: what triggers the work, who touches it, which tools or files are involved, where it tends to stall or fail, and what a useful result would look like. Do not send sensitive files until an approved handling path exists.

The core automation runtime is designed to operate on a customer-controlled machine with local files, predictable rules, exception isolation, and human review. The exact configuration is confirmed during scoping.

It can be when account ownership, provider settings, data boundaries, and human review are clear. Vigil helps define what belongs in the platform, what stays out, and what a person approves before the work is used.

No. The core file-processing and document workflow uses deterministic Python rules that can be tested against representative data. AI Office Readiness is a separate founder-delivered service for teams that want to use a customer-owned AI platform with more confidence.

Customer-visible actions and release decisions require the approval path defined in the scope. Exceptions remain visible, and the system includes a manual or recovery path appropriate to the workflow.

Rule-based automation can keep workflow inputs and outputs on the customer-controlled machine, with approved folders, review points, and redacted support evidence. AI Office Readiness keeps the customer in control of the account, settings, connections, and information choices.

That is a design requirement. Vigil documents the inputs, decisions, exceptions, handoffs, operating steps, and support path so the responsible person can review and operate the system.

It focuses on stable, repeatable office work such as validating approved spreadsheet or export rows, generating consistent documents, isolating exceptions, preparing reports, monitoring folders, and routing approved communications.

They help teams keep plans, budgets, selections, bids, issues, and release decisions tied to the correct project sources. Missing, stale, or conflicting information stays visible instead of being treated as cleared.

Vigil reviews technical eligibility, service and location clarity, content evidence, entity signals, internal paths, and answerability. Findings become an evidence-backed report and an approved fix plan—without ranking or placement guarantees.

It is a practical introduction, setup, and guided practice session for an owner or very small team that wants more from ChatGPT or Claude. The exclusive early adopter package is $399 remote or $499 local on-site and includes one customer-owned platform, up to two attendees, workspace organization, reusable instructions, guided practice, a take-home guide, and 14 days of email questions.

Yes, but they do not have to. A visibility finding can lead to an approved content workflow, or a project-control need can reveal a repeatable office task. Each connection is scoped explicitly so one service never becomes an undefined dependency on another.