Generative AI for Business.

Generative AI describes models that produce new artefacts — language, images, audio, video, or code — rather than only classifying existing ones. For a business, the practical framing is narrower: it is a way to apply judgement-light language work at a volume and speed that headcount cannot match.

The technology only becomes commercially interesting when it is wired into your own systems. A general model answering general questions is a novelty. The same model grounded in your contracts, product data, and ticket history — with permission to act inside your tools — changes unit economics. That difference between demo and deployment is the entire subject of this guide.

Most organisations arrive at generative AI through three doors: content production, knowledge retrieval, and process automation. They look like separate initiatives but share one dependency — clean, reachable, permissioned data.

Returns concentrate in high-volume work that already has a clear definition of a correct outcome. In our engagements the recurring winners are:

• Support operations — triage, classification, and drafted resolutions reviewed by an agent rather than written from scratch.
• Document intake — contracts, invoices, claims, and compliance filings converted into structured records.
• Knowledge retrieval — grounded answers across wikis, drives, and ticket systems that no one person has read.
• Revenue operations — account research, enrichment, CRM hygiene, and personalised outbound drafting.
• Content production — first drafts, variants, translations, and asset resizing at campaign scale.

Value that fails to materialise usually shares a signature: no baseline metric, no owner, and an outcome nobody can score. Before any build, define the number that should move — hours returned, cycle time, error rate, cost per ticket — and record it today.

Read our companion piece on what an AI agent is if the workflow needs to take action rather than only produce text.

A production generative AI system in an enterprise almost always contains the same layers:

• Model layer — one or more hosted models, routed by task complexity and cost.
• Retrieval layer — indexed internal content with permission filtering applied at query time.
• Tool layer — typed functions that read from and write to your systems of record.
• Orchestration — the control loop handling prompts, retries, budgets, and fallbacks.
• Evaluation and observability — regression suites, traces, and cost dashboards.

Treat the model as replaceable. Model quality improves on a cadence you do not control, so the durable investment is everything around it: retrieval quality, tool design, evaluation coverage, and the guardrails that make the output safe to use unattended.

Multi-model routing is worth building early. Simple classification and extraction steps run well on small, cheap models; only genuine reasoning needs frontier capacity. Systems that send every request to the largest available model typically overspend several-fold.

Retrieval quality sets the ceiling on output quality. Before a pilot, confirm the basics:

• The source content is current, and stale documents are identifiable.
• Access permissions are represented in metadata, not assumed.
• Content is reachable by API rather than locked in exports and screenshots.
• There is an owner for each corpus who can arbitrate conflicts.

The most common failure we are asked to repair is not a model problem — it is an index built over contradictory documents, where the system confidently cites the version nobody follows any more. Cleaning a narrow, high-traffic corpus beats indexing everything.

Generative systems introduce failure modes that traditional software does not have: fabricated claims, prompt injection through retrieved or user-supplied content, data leakage into prompts, and inconsistent outputs across runs.

• Ground answers in retrieved sources and surface citations to the user.
• Treat every retrieved document and user message as untrusted input.
• Keep irreversible or externally visible actions behind human approval.
• Log every prompt, tool call, and output for audit and incident review.
• Run regression evaluations before any prompt, model, or index change ships.
• Document where data is processed and retained, and align it to your obligations.

Governance is cheaper designed in than retrofitted. The teams that scale fastest are the ones that could answer an auditor's questions from day one.

Costs fall into three buckets: inference, engineering, and change management. Inference is usually the smallest and the most visible; engineering and adoption dominate the real total.

• Set per-workflow token and spend budgets with hard termination.
• Cache repeated retrievals and deterministic sub-steps.
• Route simple steps to smaller models and reserve frontier calls for reasoning.
• Track cost per completed task, not cost per request.

Build the ROI case on hours returned and error rate reduced against a baseline you measured before launch. Projects that report volume of generated output rather than business outcome are the ones that get cancelled at renewal.

A sequence that consistently works:

• Phase 1 — Prove. One workflow, one team, measurable baseline, four to six weeks.
• Phase 2 — Harden. Add evaluations, guardrails, observability, and cost controls.
• Phase 3 — Extend. Reuse the retrieval and tool layer across adjacent workflows.
• Phase 4 — Operate. Assign ownership, review metrics monthly, retire what underperforms.

Resist a platform-first programme. The organisations that shipped fastest built one useful thing, kept it running, and let the shared infrastructure emerge from the second and third use case.