AI for UK Healthtech_
Production AI for UK healthtech founders — built so DTAC v2, investor diligence, and your clinical-safety officer all sign off on the same artefact.
Book a 30-min readiness callYour next round's lead investor will ask how the model handles patient data, where it lives, who can see prompts, and what happens when it hallucinates. Their technical due-diligence partner will ask harder questions, in writing, and want the evidence file.
Reviewers — MHRA, your CSO, the procuring NHS trust — will want evidence the AI is safe by design, not safe by hope. DTAC v2 went live on 6 April. Pre-v2 evidence packs no longer pass.
NHS trusts run an evidence checklist that wasn't written with AI startups in mind. Founders who navigate it ship. Founders who improvise stall — at the procurement stage, after the trust is sold on the product.
Teque builds production AI for UK healthtech — RAG over clinical and patient text, agentic workflows, classification, summarisation, decision support. Shipped behind audit logs, with governance baked in upstream, not retrofitted under a deadline.
What "governance baked in" means in practice:
Why "baked in" beats retrofitted → how we build AI with governance from day one

Teque ships production AI for UK healthtech — RAG, agentic workflows, classification, summarisation — built against Article 9 data, with governance dossiers shipped as deliverables, not retrofitted under a deadline.
Article 9-class data; retrieval over their proprietary clinical dataset; governance dossier shipped as part of delivery — so their next investor and reviewer conversation has artefacts, not promises.
A production agentic AI tool we built and shipped for the UK charity sector. Live, clickable, recursive proof of the same architecture discipline that ships here.
Try the Charity Health CheckTeque engagements are designed and delivered by a small core team led by founder Saleem Beg, plus named specialist contributors brought in per brief — clinical-safety officer support, security audit, frontend, infrastructure. The contract names every contributor; their work shows up in the arc42 documentation your fractional CTO can verify. No anonymous offshore pool; no surprise sub-contracting.
Saleem's 12 years of regulated-data architecture work — Article 9-class beneficiary records at Embrace and HHUGS, NGO financial PII at scale, the Go-binary PII obfuscation library still running in production — underpins every Teque build.
Saleem on LinkedInWe can produce the documentation your reviewers ask for — because we work to those standards before the diligence call, not in scramble mode after it.
30 min · free
We map your AI surface against DTAC v2, your data class, and your investor / clinical-safety risk surface.
Deliverable: a written summary of what's in scope, what's missing, and what we'd build first. No deck, no follow-up sequence.
1–2 weeks · fixed fee
We produce the architecture, governance dossier, evidence plan, and a shipped slice — a runnable proof of the AI behaviour against your real data class.
Deliverable: all four artefacts — you own them whether or not we build the rest.
4–12 weeks · fixed scope
RAG, agentic workflows, audit logs, retention controls, clinical-safety scaffolding.
Deliverable: production AI delivered with the documentation your next reviewer will ask for.
your call
Hand to your CTO or fractional CTO with full arc42 docs — or we keep operating it with you on a defined run rate.
Deliverable: a clean handover or a defined run rate — documented either way.
Yes. We've aligned to the v2 standard since the 6 April cut-over and can produce the evidence pack your trust procurement or investor reviewer will ask for.
It stays in your environment. Tenant isolation, prompt and response logging under your control, retention you set, sub-processors documented and approved before use. No training data flows back to us or to a model vendor.
Teque is a boutique — a small core team led by founder Saleem Beg, with named specialist contributors (clinical-safety, security audit, frontend, infrastructure) brought in per brief. Every contributor is named in the engagement contract; no anonymous offshore pool.
Yes; most engagements do. We document everything arc42-style so your fractional CTO can verify the system's behaviour without taking our word for it.
Three layers — retrieval grounded in named sources, response logging with provenance, fail-safe defaults for clinically-relevant outputs. We document the model behaviour envelope so your CSO and reviewers can read it.
More on the engagement model: how a Teque project runs →
Bring your data class, your current reviewer pressure, and what you've shipped so far. Leave with a written summary of what's missing and what to build first. No deck. No pitch. No follow-up email sequence — we treat your inbox the way we'd want ours treated.
Book a readiness call