{{ c.title }}
{{ c.body }}
What we do
The same small senior team advises, builds and runs your system. No handover to people you never met.
Architecture, build-or-buy and roadmap decisions, made with people who ship.
Platforms and business applications built to stay in production.
Pipelines, warehouses and semantic layers your reports can trust.
Models trained, evaluated and deployed where they need to run, cloud or edge.
LLMs and agents wired into your systems, secured, governed and audited.
Hands-on courses that leave your teams able to run what we build.
Selected work
Services
We take responsibility for outcomes, not headcount. Every engagement ends with your team able to run and change what we built together.
Architecture reviews, build-or-buy decisions, due diligence and AI readiness, delivered as a written recommendation in three to six weeks.
Architecture review against your quality targets, technical due diligence, cloud and vendor assessments, AI readiness and governance.
Platforms and internal tools built with the people who use them, connected to your ERP and CRM, and looked after for years.
Distributed services, event-driven integration, CI/CD, observability and on-call practice. Legacy systems replaced step by step, each step reversible.
Pipelines, warehouses and reporting your teams can trust, so the same figure means the same thing in every report.
Data contracts between teams, lineage that survives schema changes, governance for GDPR and sector regulators. Warehouse or lakehouse, chosen on evidence.
Forecasting, detection and decision models trained on your data and deployed where they need to run, in the cloud or on the device.
Offline evaluation suites, drift monitoring, retraining pipelines, quantisation and compilation for edge hardware.
Assistants and agents that work with your documents and business systems, with the security and audit controls your compliance team will ask for.
Retrieval-augmented generation, an AI gateway with identity, rate limits and audit logging, evaluation gates and cost tracking per use case.
Hands-on courses in data, AI and software engineering, taught by engineers who do the same work for clients.
Courses adapted to your stack, from one-day introductions to multi-day programmes for engineering teams.
A small senior team, your codebase and your constraints. Ends with a costed plan you own, whether or not we build it.
FP2K engineers working inside your organisation, with your engineers on the same standups and the same pager.
We keep the system healthy under an availability commitment while your team gradually takes the wheel.
Technology Advisory
Independent advice on strategy, architecture and AI, framed in business terms: total cost of ownership, return on investment and risk. From senior engineers who can also build what they recommend.
Advisory work usually starts with one of these situations.
Other services
Software Engineering
When off-the-shelf tools no longer fit, we design, build and run the applications your teams depend on, and connect them to the systems you already have.
Four commitments that apply to every project, whatever its size.
Other services
Data Engineering
We design, build and run the data platforms behind your reporting, analytics and AI, so every team works from the same reliable numbers.
Most companies do not lack data. They lack data they can use: scattered across systems, defined differently in every report, and too unreliable to build AI on.
Other services
Machine Learning
A model in a notebook is not a product. We take your use case from feasibility study to a monitored model running in your operations, in the cloud, on site or on the device.
From idea to production
Other services
AI Integration
We take AI beyond the pilot: assistants and agents that work with your documents, your ERP and your CRM, with the security and audit controls your risk and compliance teams will ask for.
Other services
Training
No catalogue. Tell us the topic and the people in the room, and we design the session around them.
For companies, public bodies and training partners, from a half-day briefing to a multi-day hands-on course.
Other services
FP2K Radar · Autumn 2026
Our opinion on the techniques, tools and platforms we meet in projects, updated twice a year. Each entry is one line of judgement, not a sales pitch.
Free first step
Before any proposal, we study your case and bring two or three concrete hypotheses to a 30-minute call. You keep the thinking, whether or not we work together.
How a system proves where an answer came from, and refuses to answer when it can't.
Benchmarks decay the moment a system meets real traffic. We build evaluation that keeps telling the truth eighteen months after launch.
Sparse failure events, irregular sampling and sensors that lie. Applied to industrial and operational data.
When a 3B model on your own hardware beats a frontier API on cost, latency and data residency — and the honest cases where it doesn't.
The Lab takes on a few missions a year, working directly with the client's own team. These are not staffing arrangements — they are questions we agree to answer.
Propose a mission| Mission | Typical length |
|---|---|
| Feasibility study on your own data | 6–10 weeks |
| Independent model & vendor evaluation | 4–8 weeks |
| Evaluation harness design | 8–12 weeks |
| Technical audit | Case by case |
Case studies
Every figure below was measured against a baseline agreed with the client before we started. Named references available on request.
{{ c.body }}
About
Since 2014, we have been a small team of engineers who watched too many good systems die the moment they were handed to someone else. At FP2K, the people who design a system stay on it.
The median FP2K engineer has eleven years of experience. We do not sell junior time at senior rates, and we do not pad teams.
Architecture decisions are written down with the alternatives we rejected and why. If we were wrong, the record says so.
Success is your team not needing us. Two of our longest engagements ended because the client's own team outgrew the need.
No account layer, no org chart to climb. The people who scope the work are the people who do it.
{{ ro.text }}
Careers
We hire slowly and keep people for a long time. In a small team, your work is visible and your opinion counts.
Every engineer gets one day per fortnight inside the Lab, on Lab problems.
Utilisation is a planning input, not a performance metric. Nobody is measured on it.
Training and conference time for everyone, not only the Lab.
Published internally, reviewed annually against market data we share with you.
| Role | Practice | Location | |
|---|---|---|---|
| {{ ro.title }} | {{ ro.practice }} | {{ ro.loc }} | Apply |
45 minutes with someone who does the job you applied for.
A real problem from our backlog. No whiteboard algorithms, no take-home marathons.
Paid. You sit with the people you'd work with and see the work as it is.
Band and level explained, with the evidence behind the decision.
Blog
Written by the people doing the work. No ghostwriters, no gated downloads.
{{ art.excerpt }}
{{ b.text }}
{{ b.text }}
{{ legal.kicker }}
{{ legal.updated }}
{{ lp }}
Contact
An engineer reads every message and replies within two working days. If we're not the right people, we'll say so and point you somewhere better.
Two working days to a reply, three weeks to a costed plan.