How Signet works

One process runs underneath everything we sell.

We built it delivering attested policy and governance programs where being wrong had consequences, and it is the reason our output holds up when someone pushes on it.

Why Circle Square

We already run the environments we are automating.

We run it on ourselves first

Every agent we sell, we operate internally before we offer it. Our own operating brief is written by one. We are the first reference.

Compliance is home field

We deliver attested security policy programs mapped to NIST CSF 2.0 and CIS Controls v8.1. Governance is not bolted on afterward; it is the delivery method, whatever we are building.

We ship real software

Beyond services, we design, build, and operate commercial products of our own. When a workflow needs an application rather than an agent, that is not a subcontract for us.

The method

The Harness

AI does the typing. A named human makes the judgment calls. The harness is everything that keeps that sentence true.

  1. Context pack

    We encode how your business actually works: your systems, your rules, your obligations, your house style. This is the asset. It is yours, it is written down, and it compounds.

  2. The agent drafts

    AI does the volume work: reading, classifying, routing, drafting, reconciling, summarizing. The part that is repetitive, rule-bound, and eats your team's week.

  3. A person reviews

    Every output that carries consequence passes a named human, against a written checklist, not a spot check, and not a vibe. Low-stakes work runs unattended; we tell you which is which.

  4. We sign

    Attestation, logging, and a defined escalation path. You can always answer who decided what, on what basis, and where the record lives.

  5. Two strikes and it's law

    Anything a reviewer corrects twice gets promoted into the context pack permanently. The agent gets more accurate every month, and cheaper to run.

  6. You keep the asset

    The context pack, the policies, the governance record. If you ever bring this in-house, you are not starting over. That is the point.

What you are buying

One agent does one job. Here is what that means.

An agent is not a chat window somebody has to remember to open. It is a process that runs on its own inside a system you already use, and hands work to a person only when it should. Six parts, every time.

  1. A trigger

    Something happens in your stack. An email lands, a ticket opens, an invoice ages past thirty days, a form gets submitted. No one has to start it.

  2. Your context pack

    The written rules for this workflow: your categories, your thresholds, your tone, your obligations. This is what makes it yours instead of generic, and it is the asset you keep.

  3. It reads and drafts

    Classifies, extracts, matches against your history, and writes the response or the record. The repetitive judgment-light work that currently eats somebody's morning.

  4. It writes back into your system

    A note on the ticket, a draft in the mailbox, a row in the ledger, a status change. This is the part most stalled AI pilots skip, and the reason they stall.

  5. An escalation path

    A written list of what it must never decide alone. Those are drafted and handed to a named person with the reasoning attached. Never sent.

  6. A log and a review queue

    Every action recorded. Review rate and override rate tracked. When a client or a carrier asks how it is governed, you have the answer in a report.

A worked example: Frontdesk at a 40-person law firm

  • Email to the general inbox and transcribed voicemail arrive around the clock
  • It decides which of five things this is: new matter inquiry, existing client, vendor, spam, or conflict-check needed
  • New inquiries get the firm’s standard acknowledgement and an intake record, with the conflict check flagged for a person
  • Existing clients route to the responsible attorney with a one-line summary and a link to the file
  • Anything touching a deadline, a fee quote, or legal advice is never sent, always drafted and escalated

What the managing partner actually notices

The inbox is already triaged before the first person arrives, and nothing went out unreviewed that shouldn't have.

Blueprint, then Build

WhenWhat happens
Weeks 1–2
Blueprint
Workflow spec and data-readiness check. What it does, what it never does, what good looks like, and a fixed quote for the build. You approve this before anything is written.
Week 3Context pack written, and read/write access wired into your system of record
Weeks 4–5Build and test against your real historical data, not synthetic examples
Week 6Pilot on a live subset with every output reviewed by a person. Tune against what actually comes back
Week 7Launch, runbook, and training for the internal owner
AfterThirty days of tuning included. Then Care at $750/month, or you run it yourself

What you own at the end

The workflow spec, the context pack, the runbook, and the governance record. If you ever take this in-house or move on, you leave with all of it.

See one work

This is Frontdesk at that law firm, handling a morning.

Six things arrive the way they arrive on any Monday. Step through them one at a time: the agent explains each move as it makes it. Watch the two it refuses to touch.

Simulated with sample data. The real agent runs on your systems, with your rules.
How to read this: the left panel is the inbox as it arrived. The right panel is the agent’s own log. The panel underneath is what it refused to decide alone. Click Walk through it and it will take the first email, slowly, and explain each move as it makes it.
Inbox6 waiting
What the agent did–
Click Walk through it to start.
Escalated to a person0
Nothing yet.
0Handled
0Escalated
0Human touches
0Minutes returned

The two it refused are the whole point

A proposed deadline change and a request for a fee and an opinion never got an automatic reply. They were read, classified, summarized, and put in front of a named person with the reasoning attached. Any vendor can show you the four it handled. Ask them to show you the two it wouldn't.

Signet · A division of Circle Square

AI does the typing. A named human makes the judgment calls.

Book an AI Readiness Check

Thirty minutes, no obligation. You keep the assessment either way.