Use cases

Where a model is worth its cost.

Kinds of work where AI is worth building in, grouped by the three questions we ask first. Some are built into Lina or Lina Terminal. The rest are what we build to order.

Patterns to start a conversation from. None of them is a case study.

Why the order matters

Three ways AI spend goes to waste.

The model is rarely the problem. Each one comes from skipping one of the three questions.

A demo without a job

Impressive in a meeting and unused a month later, because it was never attached to work anyone owns.

Avoidable

A tool beside the work

Another tab and another place to paste context, so whatever time it saves is spent switching to it.

Avoidable

A bill without a ceiling

Every request sent to the largest model available, whether the task needed it or not.

Avoidable
The alternative

Start from the work, then choose the model.

Find the steps that need judgement, build the model into the application where they happen, and size it to what the work is worth. Pick a question to see what that looks like.

01Discover

Finding the use case.

Which steps need a model, and which need a rule.

Most of the value is decided before anything is built. These are the situations where the first job is working out what the AI is for.

The pilot that never reached production

A team that has tried AI tools and has a demo or two to show for it.

The work today

Nothing is attached to a workflow anyone owns, so usage fades while the subscriptions stay.

Where AI fits

Map how the team works today, pick the one use case worth shipping, and decide whether to build it, buy it or leave it alone.

More ideas than capacity

A business with a long list of places AI might help, and no way to rank them.

The work today

Every idea looks promising on its own, and building them all would cost more than they return.

Where AI fits

Weigh each use case by how often the work happens, what it costs today and how bad a mistake would be. Then start with the one that clears all three.

OperationsBuilt to order

The process that does not need a model

An operations team asked to “add AI” to a process that runs the same way every time.

The work today

A model would add cost and unpredictability to work that a rule already describes.

Where AI fits

Automate it with ordinary software, and keep AI for any step that needs judgement.

Start from the workRequests, handoffs and repeat tasks show where the time goes. Look there first.
Rules before modelsIf a step runs the same way every time, ordinary software does it more cheaply and more predictably.
One workflow, properlyOne workflow understood properly is worth more than a shelf of shallow pilots.

Bring us a workflow. We’ll tell you which parts need AI.

Tell us how it runs today and where it gets stuck. If none of it needs AI, we’ll say so.

Start a conversation