
01
The problem
- Demos that don't hold up: an AI demo works in a meeting but gives inconsistent answers with real data.
- Unmeasured quality: nobody can say whether a prompt or model change made things better or worse.
- Untrustworthy answers: the assistant makes up facts, or retrieval returns the wrong documents.
- Agents out of control: they call the wrong tools, loop, or take actions they shouldn't.
- Costs and speed: costs and latency grow with usage.
- Data exposure: sensitive data is sent to model providers without anyone deciding it should be.
02
What we do
Use-case and model selection
- Use-case definition: we define the task, the success criteria and the risks.
- Model comparison: we compare hosted and open-weight models on quality, latency, cost, data residency and licensing for *your* use case, using your own evaluation set.
Model deployment
- Hosted APIs: set up with gateways, retries, fallbacks, caching and cost controls.
- Self-hosted and open-weight models: on vLLM, TGI or similar, deployed on GPU infrastructure in AWS, Google Cloud (Vertex AI) or Kubernetes.
- Autoscaling and serving: autoscaling, batching, quantisation where suitable, and observability for latency, throughput and cost per request.
Fine-tuning
- When it's worth it: we tell you when fine-tuning is worth doing and when better prompts or retrieval would do the job.
- Data and training: we prepare datasets, train (LoRA/QLoRA or full), and evaluate against a held-out set.
- Versioning and rollback: every model version is tracked and can be rolled back.
RAG and context engineering
- Ingestion pipelines: parsing, chunking strategies and metadata.
- Embedding and vector store choices: pgvector, OpenSearch, Pinecone, Vertex AI Vector Search.
- Retrieval quality: hybrid search (keyword plus vector), re-ranking and query rewriting.
- Context assembly: what goes into the prompt, in what order, and within what token budget. This includes conversation memory and per-user access filtering, so users only ever retrieve documents they are allowed to see.
- Citations and grounding: answers point back to their sources.
Agents and tool use (LangGraph)
- Agent workflows: stateful agents in LangGraph with explicit graphs, checkpoints and human-in-the-loop steps.
- Tool design: a small, well-described set of tools, structured inputs and outputs, and tool selection and routing that we test.
- Guardrails:
- tools run with the end user's permissions
- actions that change state require confirmation
- step and cost limits
- prompt injection defences
Evaluations
- Eval datasets built from real or representative queries.
- Measures:
- answer correctness and groundedness
- retrieval precision and recall
- tool-call accuracy
- latency and cost
- How quality is checked: automated scoring (rule-based and LLM-as-judge, calibrated against human review), plus regression evals in CI so prompt or model changes can't quietly lower quality.
- Production monitoring: tracing, feedback capture and drift checks.
Safety and data protection
- PII handling: minimised and masked before model calls.
- Retention: prompts are logged with redaction, and retention settings are reviewed.
- Testing: against the OWASP Top 10 for LLM Applications. See also Security Testing.
03
How it works
- Scoping call. We discuss the use case, data, constraints and success criteria.
- Discovery and eval set. We define "good" before building.
- Prototype. We compare approaches (prompting, RAG, fine-tuning, agents) against the eval set.
- Production build. Deployment, monitoring, guardrails and cost controls.
- Launch and iterate. Staged rollout, with evals and feedback guiding improvements.
- Handover. Documentation, runbooks and training for your team.
04
What you receive
- Solution design: architecture, model choice and the reasoning behind it.
- Evaluation suite and baseline results.
- Production code:
- RAG pipelines
- agents (LangGraph)
- model serving infrastructure as code
- Observability dashboards for quality, latency and cost.
- Security and data-flow review of the AI feature.
- Runbooks and handover sessions.
05
Standards and tools
Aligned with: the OWASP Top 10 for LLM Applications, the NIST AI Risk Management Framework, and provider responsible-use guidelines.
Tools:
- Agents and orchestration: LangGraph, LangChain, LlamaIndex
- Tracing and evals: LangSmith / Langfuse, Ragas, promptfoo
- Model serving and platforms: vLLM, Hugging Face, AWS Bedrock, SageMaker, Google Vertex AI
- Vector search: pgvector, OpenSearch
- Pipelines and models: Python and TypeScript, MLflow
06
Packages
We offer fixed-price packages for businesses with different needs. Scope, timeline and deliverables are agreed in writing after the scoping call.
07
Next step
Book a 30-minute call to talk through your product and what you need.
FAQ
Questions
Should we fine-tune a model or use RAG?
Most products that answer questions from your own data start with RAG and good context engineering. Fine-tuning suits a consistent style, format or a narrow task. We test both against your eval set before recommending one.
Can we keep our data private?
Yes. Options include: - **Hosted APIs:** set up with zero or limited data retention. - **Cloud-hosted models:** running inside your own cloud account (Bedrock, Vertex AI). - **Self-hosted:** open-weight models on your own infrastructure.
How do you stop the assistant from making things up?
- **Grounding:** answers are based on retrieved sources, with citations. - **Admitting uncertainty:** the assistant is told to say when it doesn't know. - **Measurement:** groundedness is part of the evals, so we can see when it slips.
Are agents safe to let take actions?
They can be, with limits: - **Permissions:** tools use the user's own permissions. - **Confirmation:** sensitive actions need it. - **Limits:** step and cost limits stop runaway agents. - **Testing:** every tool is tested against prompt injection.
How do we know if it's working?
Through evals agreed at the start, run automatically on every change, plus monitoring and user feedback in production.
Can you add AI to our existing product?
Yes. Most of our work is adding AI features to existing web and mobile apps and backends.

Start a project
Have a product to ship?
Engagements are fixed-price packages, shaped to the business. Book a call for a quote.
Book a 30-min call ↗