Book a working session
Menu
ServicesApproachWorkJournalAboutBook a working session

AI where it
earns its keep.

Rules, software or a person everywhere else.

We embed with your team, map how the work really moves, and route every job to the right tool, then build it and hand it over for you to own.

Book a working session See the work

  1. Supplier invoice · PDFfields read, matched to the PO

    Verdict: Model

    scanned documents, every layout different

  2. Dealer reorderapproved against contract pricing

    Verdict: Rule

    the rule fits on an index card

  3. Quote requestpriced by the configurator

    Verdict: Software

    the logic belongs in the system, not an inbox

  4. Warranty claimsent to a person, with the history attached

    Verdict: Person

    a wrong call is hard to undo

  5. Customer emailreply drafted, queued for review

    Verdict: Model

    plain language, high volume, a person signs off

  6. Compliance deadlinedate computed, reminder scheduled

    Verdict: Rule

    the regulation is the rule, no guessing

Every job leaves with a verdict

Six illustrative entries, not client records.

When to use AI,
and when not to

Eight situations that come up, and the verdict we usually reach for each.

  1. The decision fits on an index card.

    Write the rule

    If a person can explain it in two sentences, code can do it the same way every time, at almost no cost.

  2. The input is messy: scans, emails, photos, free text.

    Use a model

    Reading and sorting unstructured input is where models earn their place.

  3. It’s the same judgment across a very large pile of similar cases.

    Model, with review

    Consistent first drafts at volume, sampled and checked by the people who own the outcome.

  4. A wrong answer is costly and hard to catch.

    Keep a person

    The decision stays human. A model can gather the facts and draft the options.

  5. It happens a handful of times a month.

    A checklist

    Automation pays back on volume. A clear checklist and a capable person win here.

  6. The data lives in several places and they disagree.

    Fix the system first

    A model reasoning over conflicting records gives confident wrong answers. Settle the source of truth.

  7. The tool you already rent mostly fits.

    Integrate it

    Connect what works and build only what it can’t do. Rebuilding for its own sake is waste.

Nobody can describe how it’s done today.

Map it first

We don’t automate a process no one can explain. We sit with the people who do it and draw it.

What we build,
and the lanes it uses

  • AI & operations assessment

    Where AI belongs in your operation, and where it doesn’t.

    • Rule
    • Model
    • Software
    • Person

  • Workflow automation

    The rules, integrations and scheduled jobs that end re-keying.

    • Rule
    • Software

  • AI agents & copilots

    Models in production, with guardrails and a person where it counts.

    • Model
    • Person

  • Systems modernization

    Retire the rented tool, the spreadsheet and the swivel chair.

    • Rule
    • Software

  • Custom applications

    Internal tools, portals, configurators and native apps.

    • Software

  • Embedded engineering

    Engineers inside your operation until it runs.

    • Rule
    • Model
    • Software
    • Person

What you get from each

The work,
shown as built

WellState

Private early access

WellState work queues: the questions an operator asks, each with the wells that answer it
Work queues: each question an operator asks, with the wells that answer it.shell.wellstatelabs.comOpen full size
Sector
Upstream oil & gas
Role
Product, data engineering and AI
Status
Private early access
Verdicts
RuleModelSoftwarePerson

Well retirement infrastructure for operators: every well screened against the rule, every figure traceable to the regulator’s own records.

WellState is its own company, WellState Labs. Auzi designed and engineered the platform.

Read the case

Where AI is, and isn’t

  1. Does a well meet the statutory test?Rule
  2. The source records disagreePerson
  3. Questions about the portfolio, in plain languageModel
  4. Tracing any figure to its sourceSoftware

Leggero

Live

The Leggero home page: the Enzo wheelchair beside the headline Every angle, considered
The public site: every model, every angle.Open full size

A manufacturer’s whole dealer stack: the public site, an online configurator, a dealer portal, an operations console and an AI advisor.

RuleModelSoftwarePersonRead the case

TintBay

Pilot build

TintBay on iPad: the tint editor, a top-down car with each window’s film and shade
The tint editor on iPad: every window, its film and its shade.Open full size

Native iPhone and iPad software that runs a tint shop’s day, from VIN check-in to the finished invoice.

RuleSoftwarePersonRead the case

Tyler Sites

Live

The Lalo’s Mexican Grill & Cantina website
Lalo’s Mexican Grill & Cantina
The C & E Construction and More website
C & E Construction and More
The Marquez Concrete website
Marquez Concrete
The Shade Customs website
Shade Customs
The Go2Guy Party Bus & Shuttle Service website
Go2Guy Party Bus & Shuttle Service

Custom websites for contractors, restaurants and shops, each with its own look, fast on a phone and built to get the call.

Read the case Visit Tyler Sites

Five stations.
Each leaves a document behind

  1. 1Embed

    We start where the work happens.

    Field notes

  2. 2Map

    Every workflow, drawn as it actually runs.

    Workflow map

  3. 3Route

    Each job gets a verdict and a reason.

    Routing memo

  4. 4Build

    Small pieces, in use early.

    Working software

  5. 5Hand over

    You own it. We stay reachable.

    Runbook

The third document is the one you can take anywhere: every job, its verdict and the reasoning.

A specimen of the kind of document, not a client record.

How each station works

Routing memoSpecimen · For review
To
Operations
From
Auzi
Re
How each job is routed
JobVerdictBecause
Dealer reorderRuleThe rule fits on an index card.
Supplier invoiceModelEvery layout is different.
Warranty claimPersonA wrong call is costly.

Build order: the rule first, then the model, with a person reviewing it.

Bring us one job.
We’ll give it a verdict

Book a working session

Or write to ushello@auzi.ai