Work
Systems in production, not slideware.
Catalyze Labs builds AI systems that run inside mission-critical workflows — some as our own products, some inside a client's operation. Four are described here in full. Most of the rest sits under client confidentiality.
Published case studies
What we can show in full.
The pattern underneath
Different industries. The same hard problem.
Covenant compliance, urgent care throughput and wildfire response have nothing in common at the surface. Underneath, they are the same six-stage problem — and we solve it the same way every time.
- 01
Complex data
Fragmented, high-volume, in formats nobody chose.
- CovenantFlow
- Loan documents, borrower financials, collateral reports
- Urgent care network
- Practice management, clinical records, fax intake, telephony
- Claritus.One
- Scheduling, billing, workforce and clinical systems
- LucidSky
- Optical imagery, radar, weather feeds, ground sensors
- 02
Semantic understanding
One agreed meaning, encoded once, before anything reasons over it.
- CovenantFlow
- Covenant taxonomy, thresholds, breach definitions
- Urgent care network
- Governed metric definitions, hierarchy, comparison windows
- Claritus.One
- Shared organizational semantics across every domain
- LucidSky
- Scene interpretation against each location's own baseline
- 03
AI and deterministic systems
Judgement where it is needed, rules where they are better.
- CovenantFlow
- Statement extraction, term identification, anomaly detection
- Urgent care network
- Text-to-SQL over governed metrics, narrative synthesis
- Claritus.One
- Domain agents with model routing by task
- LucidSky
- Detection models plus consequence modelling
- 04
Workflow orchestration
The part that turns an insight into something that happens.
- CovenantFlow
- Trigger rules, escalation routing, borrower notification
- Urgent care network
- Scheduled brief generation and agent task execution
- Claritus.One
- Approval gates, escalation routing, action tracking
- LucidSky
- Incident assembly with evidence and change history
- 05
Human decisions
Who is accountable, and what they need in front of them.
- CovenantFlow
- Relationship managers, credit operations, portfolio risk
- Urgent care network
- Executives, regional managers, clinic leads, compliance
- Claritus.One
- Executives, department leads, coordinators
- LucidSky
- Analysts and emergency responders
- 06
Operational outcome
The measure the system exists to move.
- CovenantFlow
- Breaches detected while remediation is still an option
- Urgent care network
- Answers in a session rather than a reporting cycle
- Claritus.One
- Foundation built once rather than per department
- LucidSky
- Observation to actionable incident in hours
This is why we do not describe ourselves by industry. The domain expertise matters and we build it, but the thing we are actually good at is the column on the left — and it transfers.
On confidentiality
Why there are fewer case studies here than engagements.
Our systems sit in regulated and mission-critical workflows, and most clients will not have that described publicly. We do not publish a study, a client name, a quote or a number without written approval for that specific item. Where a result exists but cannot be published, we say so rather than round it into something vague — and we share the detail directly, under NDA.
Tell us about the workflow. We'll tell you whether we have built something like it.