One machine, many doors

The engine under the products.

AVNZ runs the parts a small business never wants to build. Checkout and billing, the funnel that leads to it, every lead that comes in, the customer service that answers, the ads that buy the traffic, and the mail that starts the whole thing. Each product below is a door into the same machine.

AVNZ is a GG Consulting company.

The intelligence

Never let a model invent a number.

Every other product in this category leads with how much its AI reads. Ours leads with what it is forbidden to touch. A vision model that reads $54.99 as $549.90 with total confidence poisons a tax return silently, and nobody finds out for a year. That single failure is what the whole architecture is built to make impossible.

StepWhat runs itWhy
Amounts, dates, vendorsPurpose built extractionNot a language model. It reads layout and returns typed fields with per field confidence, so it does not generate a figure and structurally cannot invent one.
Arithmetic validationNo modelLine items sum to the total, tax is plausible, dates fall in period. Deterministic and testable.
CategorizationSmall classifierGenuine judgment, so a model earns its place here. Constrained to a fixed taxonomy and the practice's own history, which is where the accuracy actually comes from.
Findings and detectionNo modelDuplicate charges, price creep, stale subscriptions. Found by arithmetic with thresholds you can read, which is why every finding can be defended.
Phrasing the findingLanguage modelLanguage only, over a result that is already true. It never sees a raw transaction and never decides whether a finding is real.
Hard pages, low confidenceVision modelFallback only, never the default path, and every document that takes it is flagged as having done so.

Tier scales with judgment required rather than with importance. The most important step in the chain gets the least generative treatment, which is the opposite of how most of this is built.

The ledger

Every call on the record

Prompt version, tokens, cost, latency, and outcome, written for every single call. It is how prompts get tuned without guessing, how a bill is explained line by line, and what an auditor is shown when they ask how a number was reached.

The ladder

Nothing fails silently

Work that cannot complete lands in a tiered queue rather than vanishing, retried, escalated, and finally put in front of a person. Each step carries forward why the one below it could not finish, so an escalation arrives as evidence rather than as a shrug.

The breaker

A vendor's bad afternoon stays small

If the cheap tier starts failing at scale, the ladder stops escalating and pages instead. Without that circuit breaker an upstream outage quietly converts every document into an expensive call, and one bad afternoon becomes a runaway spend event.

The rule

Computed, never generated

The machine computes and the model speaks. Findings come from arithmetic over the ledger; the model writes the sentence that explains one. It is the difference between a number you can defend to an auditor and a number that sounded right.

Running in production

Eight systems, one spine.

Not a roadmap. These are the modules the products above are built on, described by what they do rather than what they are called.

Payment rails

Take the money

Checkout, subscriptions, and recurring billing, with refunds that route through an approval step and chargebacks handled before they turn into write offs. Four gateways sit behind one interface, Stripe, PayPal, NMI, and Authorize.Net, so a card declined in one place can be retried in another.

Funnels

Build the path to the sale

Multi stage flows from a first click to a paid order, with A/B variants, session tracking, and recovery for the carts that get abandoned along the way. Assembled and changed without a developer.

Lead OS

Catch every lead

Web forms, text in keywords, and printed QR codes all land in one inbox, deduplicated, with the ad click that produced them attached. Every lead carries a status until it reaches a real outcome, and anything that sits untouched for three business days gets flagged rather than quietly forgotten.

Customer service AI

Answer the phone

Voice and chat handled by an AI representative that escalates to an AI manager, and then to a person when the situation earns it. Wired through Twilio, so the number rings for real and the transcript is kept.

Adley paid search

Buy the traffic

Google Ads campaigns built and managed, with a copy lab for headlines and descriptions, and offline conversion upload wired back to Google so bidding is built to train on what actually closed rather than on what merely got clicked.

Communications

Send the message

Transactional email on a queued and logged sender, SMS keyword capture that turns a printed code into a contact, and lifecycle sequences that fire on their own schedule and then stay out of the way.

Integrations framework

Hold the keys

Every third party credential encrypted with AES-256-GCM and configured per provider in one place, never scattered through environment files. The server refuses to start without its encryption key, which is the point.

Evidence mail

Put it on paper

Personalized letters with a unique code for each recipient, a print pipeline that renders and sorts them for postage, and per code scan tracking so a piece of paper becomes something measurable instead of something hoped for.

The doors

Every product is a door into the machine.

Each one is built for a trade that would never shop for software. The machine underneath is the same.

Live now

SheetTamer

For accounting practices and the businesses they serve. Documents land in a shared room sorted by month, the practice asks for whatever is missing with one click, and a checker reads the workbook for duplicate charges, price creep, and invoices past due.

sheettamer.com

Open SheetTamer

Free for accounting practices.

Built, not yet open

AVNZ Leads

For local service businesses. Ads managed, every lead captured and answered, and a weekly report that shows the cost of a booked job rather than the cost of a click. The software is finished and deliberately closed until the first door reads out.

leads.avnz.io

Ask about your county

Goes to a person, not a list.

Live now

ShipKeeper

For anyone who ships. A customer portal for filing a claim, a workflow that moves it without email, risk scoring on the claims that do not add up, and billing that reconciles itself. Software for handling what goes wrong in transit, sold as software.

shipkeeper.io

Open ShipKeeper

Runs standalone or inside a store.

Live now

Commerce

The original spine, and still the largest. Funnels, checkout, subscriptions, orders, refunds, fulfillment, and the routing that decides which processor sees a card. Every other door is built on parts of it.

admin.avnz.io

Open the console

Sign in required.

cpa.avnz.io · payments.avnz.io · sb.avnz.io are divisions on the same machine. They open when there is something behind them worth walking through, and not before.

Why one spine

Shared underneath, separate at the door.

A business that uses two of these never sets up billing twice, and a lead that turns into a customer keeps its history instead of starting over.

One set of rails. The gateway that takes the first payment is the gateway that takes the hundredth, whichever door it came through.
One record. A lead, an order, and a support conversation belong to the same customer rather than to three disconnected tools.
One login, coming. Today each product signs in on its own. That is a known gap and it closes as the second door opens.
One place for keys. Credentials live in the integrations framework, so adding a gateway or a provider is configuration rather than a deploy.
Partners

Building something that belongs on these rails?

If you run a trade, an agency, or a book of clients that needs the machine rather than another dashboard, say so plainly and we will answer the same way.