We are Vector & Frank.
The AI operating layer built for your people and your systems.
Somewhere in your business, a good team is doing by hand what your systems should already be doing for them: matching, rekeying, chasing exceptions, spreadsheet by spreadsheet. It costs your business money, and it costs your people time that would be spent elsewhere. Your current systems can't fix it and overhauling everything doesn't make any sense.
Free workflow audit · nothing to sign until you decide to go
The mid-market gap
Too big for the off-the-shelf tool. Too lean to build an AI team.
If you run between 100 and 5,000+ people, the work that costs you most is handled by hand, because your process has exceptions no vendor ever built a field for. That's exactly the work we take off your plate.
Off-the-shelf leaves a spreadsheet
The system of record holds the data. The judgment lives in a workbook beside it, maintained by one person and understood by one person.
Hiring is the wrong size
Two AI engineers and a year of ramp is not the answer to a nine-minute step that runs twenty times a day.
An overhaul is not on the table
You have watched an eighteen-month replatform before. We touch one workflow and leave the rest alone.
Where it usually sits
- Invoice coding
- Order entry
- Claims intake
- Vendor onboarding
- Renewal quoting
- Scheduling exceptions
- Month-end reconciliation
Movement
01
Evaluate
Two weeks · free
We time how the work runs today, then cost each step.
Our engineers sit with your team, time how the workflow actually runs, and cost each step. You walk away with a ranked list of what's worth automating and the price of an outcome against what it costs you by hand today, before you've spent a cent. This is the workflow audit: free, and nothing to sign until you decide to go.
Baseline, measured
A regional distributor's order desk, timed before we touched it
Timed · costed · ranked
Movement
02
Automate
Three to six weeks
A straight path, and one short loop where the step needs judgment.
We build it on our operating layer: explicit logic for the path, constrained judgment for the one step that needs it, tested against your real historical cases before it ever touches production. No internal project to staff, so your team isn't pulled off their day job to make this happen.
Explicit logic for the path · one short loop for the judgment · tested on your history
Movement
03
Operate
In production · ongoing
The gate, the spur and the log.
We run it and we are answerable for it. Your team works the exception queue; you keep your data and the log.
Held at a gate
Runs without a log
A gate on every run · 1 in 8 held for a person · the rest to the log
Terminus · measured
Sixty hours a month, down to seven.
Every order on that desk was rekeyed into two systems by hand: nine minutes each, twenty a day, twenty working days a month. In production about one run in eight needs a person, which leaves seven hours in the exception queue your team works. Each outcome is billed once, under what the step costs by hand; nothing is billed for a run held at the gate.
In production
One outcome
$1.25
Matched · logged · billed
What it costs
You pay for outcomes, not for access.
Put your own process through the math.
Runs a month · minutes by hand · hours back · what we bill
One invoice matched. One claim checked. Priced under what that step costs your team by hand, from the baseline we timed in the workflow audit, so every run saves you money instead of costing it. No licence, no seats, no subscription. Nothing runs, nothing is billed.
Why we can promise that
An agent that is right nine times out of ten is a process that is wrong four times a day.
Hand a model the whole job and it finds a new way to do it. Fine in a demo; not on an order desk with eleven steps and a customer on the phone.
So we split it. The path is explicit logic and does not move. Judgment is constrained to one step, and where the two meet you put a gate.
Determinism
You can predict what it will do tomorrow and check what it did yesterday.
Explicit logic
Path, branches and exceptions are written down. A change is a version you approve.
Approval gates
Thresholds you set, people you name. Over the line, the run holds and says why.
Replayable log
Every input, decision and write kept in order. Same evidence for your team and your auditor.
Your systems, not ours
There is nothing new for your team to log into.
The workflow reads and writes in the systems your team already uses, with the permissions they already have.
No new tool to log into, no seats to hand out, no onboarding to sit through. The connections, the credentials and the running of it are ours to take care of.
- NetSuiteOrders in · posted
- SAP B1Orders in · posted
- OracleInvoices · matching
- SalesforceAccount context
- SlackGate approvals
- SnowflakeReporting · baseline
- REST · SFTPDirect feeds
- Custom connectorBuilt in the automate phase
Twenty-two connectors in production
Read and write with the permissions your team already has
- Baseline timed
- We build and run it
- Kept correct
- Paid per outcome
Get started
Name the process that is eating your team's week.
The workflow audit times the steps, costs them, and prices the outcome against what you spend today. It is free and there is nothing to sign to get it. If the numbers do not work, you keep the findings and there is nothing to buy.