AI development

Practical AI, built into the software you already run.

Four kinds of AI work we take on most: agents that run a multi-step task across your systems, assistants that answer from your own documents, extraction that turns emails and PDFs into records, and LLM features built into the screens your team already uses.

What we offer

Where AI earns its place

01

AI Agents & Workflow Automation

Multi-step assistants that can look things up, call your systems, and complete bounded tasks.

Agents are useful when a task needs several steps and several systems: checking an order, updating a record, drafting a reply, escalating when unsure. We design the tool boundaries, permissions, and logging first, then build the agent to operate inside them.

02

LLM Applications

Custom applications built on large language models, with your data, rules, and interface.

A chat window is rarely the product. We build LLM-backed applications with proper interfaces, prompt and version management, evaluation sets, and cost controls, whether the model comes from OpenAI, Anthropic, Google, or an open-weight option hosted in your own cloud.

03

RAG Knowledge Assistants

Question answering over your own documents and databases, with sources cited.

Retrieval-augmented generation lets a model answer from your policies, manuals, tickets, and records instead of general training data. We handle ingestion, chunking, embeddings, access control, and evaluation so answers are grounded and traceable to a source.

04

Document Extraction & NLP

Classification, extraction, and routing for text that arrives in volume.

Support tickets, reviews, contracts, and forms all carry structure that people currently extract by hand. We build NLP pipelines that classify, tag, extract entities, and route text so downstream systems and teams get clean input.

Also

The work around those four

These usually come up inside one of the offers above rather than as a project of their own.

Generative AI

Drafting, summarising, and content generation features inside the tools your team already uses.

Computer Vision

Detection, classification, and document understanding from images and video.

Machine Learning

Models trained on your data for scoring, classification, and recommendation.

Predictive Analytics

Forecasts and early-warning signals built into the dashboards people already read.

MLOps

Deployment, monitoring, and retraining so models keep working after launch.

How an AI engagement runs

Check the fit first, then build with review and monitoring.

The same four stages as any BizHues engagement, with two additions: a fit assessment before discovery ends, and an evaluation set that the feature is measured against before and after launch.

  1. 01

    Discover

    Working sessions to agree the users, the decisions the software supports, the systems it touches, and what the first release must do.

  2. 02

    Design

    Data model, integration points, and clickable screens for the main flows before any build time is spent.

  3. 03

    Build

    Short cycles with working software on a shared staging environment at the end of each one.

  4. 04

    Launch & scale

    Release with monitoring in place, hand over the code and infrastructure, then use production feedback to decide what changes next.

Questions

Straight answers on AI work

Who owns the code and the infrastructure?
You do. Repositories, cloud accounts, and third-party services are created in your name or transferred to you at handover, along with documentation.
Do you build AI features into existing products?
Yes. Most AI work we take on is a feature inside a system that already exists: a CRM, a helpdesk, an ERP or an internal tool. We check first whether a model is the right tool or whether a rule would do, then design the data access, the review step and the monitoring before the feature ships.
Which models and providers do you work with?
Hosted models from OpenAI, Anthropic, and Google, and open-weight models run in your own cloud. The choice depends on the task, cost, and where your data is allowed to go.
What if AI is not the right answer?
We say so. A rule, a report, or an integration often solves the problem more cheaply and predictably, and we would rather build that.
Fit check · 30 minutes

Not sure whether AI fits the problem? Ask before anything is built.

Describe the task, the data you have, and who would review the output. We tell you honestly whether a model is the right tool and what the first step would be.

Discuss an AI use case

Talk to an engineer

Have a task that AI might take off your team?

Book a 30-minute call with an engineer, at no charge. Tell us the problem and the systems involved, and you leave with questions answered and a suggested first step, not a sales deck.