Use cases

Business workflows that become conversations.

Every workflow here shares a shape: a customer with an intent, a business process with rules, and systems that must be called correctly. Each pattern shows which parts the AI handles, which parts stay deterministic, and the outcome the application completes.

Flagship flows and proven patterns

Use AI for perception and ambiguity. Use explicit steps for decisions.

The engineering knowledge that matters is knowing which responsibilities belong to an LLM and which must be deterministic: where validation lives, how failures recover, and when a human must review. Each pattern below encodes that division for one class of workflow — and the flows are ordinary PicoFlow steps, so a new project starts from a proven envelope instead of inventing its architecture from scratch.

Insurance quoting

Home insurance quote

Qualify → collect → rate → compare → correct → consent

Guide a prospective customer through a preliminary quote while code owns eligibility, referral reasons, premiums, quote IDs, re-rating, and consent. The model collects and explains; it never fabricates a price or binds coverage.

Built as a complete tutorial — walk through it

Benefits enrollment

Employee benefits enrollment

Verify → cover → compare → elect → review → submit

Verify eligibility, collect household coverage, compare plan options, validate account limits and beneficiaries, disclose pending requirements, and submit only after review. Policy code owns plan terms, limits, payroll totals, and the final enrollment record.

Built as a complete tutorial — walk through it

Reservations & commerce

Hotel reservation

Discover → select → quote → confirm → commit → verify

Understand the request, check availability, capture preferences, present priced options, and book. The model conducts the conversation; the flow guarantees no booking before explicit confirmation, no double charge, and quoted terms preserved through commit.

Built as a complete tutorial — walk through it

Support resolution

Customer support that executes

Diagnose → retrieve → propose → authorize → execute → confirm

Understand the issue, inspect account data, propose approved actions, place approval holds where policy requires, execute, and confirm. When human help is needed, the hand-off carries the complete case record instead of a transcript dump.

Built as a complete tutorial — walk through it

Claims & document intake

Claims intake and document processing

Intake → classify → extract → validate → route → adjudicate

Collect incident details in conversation, receive documents, use AI for perception — classification, OCR, extraction — then apply deterministic validation and business rules in codified steps. Exceptions route to human review instead of silently passing.

The document-processing tutorial shows the extraction half

Customer onboarding

Onboarding without the form maze

Gather → verify → enrich → approve → activate

Guide setup in one conversation: gather missing information, verify identity and eligibility, call backend services, handle exceptions, and activate. Durable session state means an interrupted customer resumes mid-onboarding instead of starting over.

Start from the first-flow guide

Procurement

Procurement requests with policy

Capture intent → policy check → approval → order → reconcile

Capture purchase intent conversationally, apply vendor and policy rules deterministically, route approvals with holds, create the request in your systems, and track status. Policy is enforced in typed handlers — not requested of the model.

See how approval holds are modelled

Financial operations

Extraction, reconciliation, and posting

Extract → reconcile → detect anomaly → approve → post

Use AI for perception over invoices and statements, normalise into structured facts, reconcile deterministically, surface anomalies for review, and post only after approval. One-shot and batch execution use the same flow model as conversations.

Explore the invoice tutorial

What every pattern specifies

A pattern is an engineering playbook, not a prompt snippet.

01

AI / deterministic boundaries

Which stages use an LLM for perception and conversation, and which are codified steps for interpretation, validation, and business decisions.

02

State and checkpoints

The durable state each stage requires, the sensitive actions that demand explicit confirmation, and the tool and data-access boundaries around them.

03

Failure and escalation

Retry and recovery behaviour, exception detection, and the points where a human must review before the application proceeds.

04

Evaluation scenarios

Deterministic transition tests and live scenarios that keep the application honest as prompts, models, and business rules evolve.

Which workflow costs your customers the most effort today?

Start there. Bring the business outcome, the systems it must call, and the rules it must never break — we can help you assess the fit.