VIRGIL · DIGITAL BUSINESS ASSISTANT SETUP

Your digital business assistant. Set up around the work you need help with.

Kova configures and tests Virgil around the information, supported tools and review rules you approve. Use it to prepare a brief, research a question, compare options, draft a message or turn notes into next steps. You decide what it can access and review important output before using it.

Review before sendingDefined approval stepsApproved information sourcesScope agreed before build
See Virgil at work in four steps
Virgil at work: Approve the context. Retrieve notes. Prepare the work. Hold for approval.
Approve the context. Retrieve notes. Prepare the work. Hold for approval. This is an illustrative workflow, not a client result or a live system.

Prepare the information, drafts and next steps.

01

Find Relevant Notes

Choose the documents and client records the system may use. It brings relevant notes together to help prepare a reply or proposal. Check details against those records before using or sharing the output.

02

Use voice when it helps

Where voice is part of the agreed setup, use it to capture a note, prepare for a meeting or ask for relevant context. The scope defines the supported channels and access rules.

03

Keep Approval With You

Draft replies, proposals, and follow-ups are prepared for review. Sending a message or making another consequential change requires an approval step. We test those boundaries before enabling the connection.

04

Know What You Control

The handoff identifies your source files, accounts, access controls, and operating notes. We document which providers handle information and their applicable terms before connecting your records.

AGREE THE BOUNDARIES

What it prepares. What you approve.

PREPARES WITH APPROVED ACCESS

  • Finds relevant client records and notes
  • Prepares drafts for you to review
  • Turns approved voice notes into action lists
  • Summarizes recorded tasks and due dates

ASKS FIRST

  • Sending any external email or SMS
  • Modifying CRM pipeline stages
  • Transferring money or processing refunds
  • Committing founder time or calendar slots

These are approval boundaries, not a promise that every connection is included. The scope defines which actions the build can support.

SET UP AND TEST

  • The business rules it must follow
  • The providers allowed to process information
  • Which tools and records it may access
  • Records of approved actions and their results

BEFORE CONNECTING YOUR INFORMATION

Bring one task, an example with private details removed, and a list of the tools involved. We define the approved sources, supported channels, access and review rules before connecting records.

This is not permission to send confidential information to any provider, nor a guarantee that every draft is correct. You review important details before using the output. Passwords and access keys do not belong in a public inquiry.

What you receive: the configured assistant, the connections and review steps agreed for the setup, and operating notes explaining the sources, accounts and access rules. Want Kova to stay involved? We can review the setup and make agreed updates as your needs change. Ongoing scope and cost are agreed separately.

START WITH ONE TASK

What are you always looking up or drafting again?

Name one recurring question, where its answer lives, and the tools involved. Keep private records out.

Talk to Al about your Virgil

Want the recommendation in writing before a build? The optional $1,500 Build Plan sets out the information, connections, approval rules and work to do first.

See the optional $1,500 Build Plan