Extracting Value from Data

Just another computer company. The difference is what we leave behind.

We are senior engineers in Norfolk who turn neglected data into systems you can trust, and teach your developers to build with Claude properly while we do it. Then we hand everything over and get out of the way.

Based in
Norfolk, UK
Engineering since
2016
Team you get
Senior only

Flagship service

Anthropic Development Guidance & Tutoring

We train your developers to build with Claude properly, then step back. Hands-on mentoring in agentic workflows, prompt and context engineering, and the Anthropic API, taught against your real codebase.

How the tutoring works

What we do

Six things, done by people who have done them before

Every engagement starts with the data and ends with your team holding the keys. We would rather tell you the work is unnecessary than invent a project.

Flagship service

Anthropic Development Guidance & Tutoring

We train your developers to build with Claude properly, then step back. Hands-on mentoring in agentic workflows, prompt and context engineering, and the Anthropic API, taught against your real codebase.

Most teams adopting Claude get a productivity bump and then plateau, because the hard part was never the API. It is knowing how to decompose work for an agent, how to engineer context, where to put guardrails and evaluations, and when not to reach for a model at all. We embed with your developers and work through those judgements on the code you actually ship: pairing sessions, code review, workshops and an agreed set of conventions your team owns after we leave.

  • Developers fluent in agentic patterns, not just chat prompting
  • Context and prompt engineering practices written into your standards
  • Evaluation and review habits that keep model output trustworthy
  • Tooling, MCP integrations and automation tuned to your stack
  • A team that no longer needs us
Talk about training your team
Abstract illustration of branching agent workflows guided by a mentor figure, rendered in JADC teal and lime
Tangled data strands resolving into ordered, aligned rows, in JADC teal and lime

Data Cleaning & Augmentation

Messy, duplicated, half-typed data turned into something you can actually build on, then enriched with the context it was missing.

  • Deduplicated, validated, consistently shaped records
  • Repeatable pipelines instead of a single rescued spreadsheet
  • Enrichment from authoritative and geospatial sources
  • A documented audit trail of every transformation applied
Discuss this
Modular blocks assembling into a coherent structure, in JADC teal and lime

Bespoke Software Development

Software built for the way your organisation actually works, when the off-the-shelf option would mean bending the business to fit the tool.

  • Working software in front of real users early and often
  • Tested, documented and deployable from day one
  • Built on mainstream technology your team can hire for
  • Full ownership of the source and the pipeline, no lock-in
Discuss this
Weathered architectural columns transitioning into clean modern structure, in JADC teal and lime

Upgrading Existing Code Bases

Incremental modernisation of systems that still earn their keep: off end-of-life runtimes and back into support, without a rewrite.

  • Supported, patchable runtimes and dependencies
  • Characterisation tests before anything is touched
  • Reversible, incremental steps rather than a risky rewrite
  • Containerised builds and automated deployment
Discuss this
Magnified inspection of layered code structure with highlighted findings, in JADC teal and lime

Code Quality Analysis

An evidence-based read on the health of your codebase, and a prioritised plan you can hand straight to your team.

  • Risk-ranked findings, not an undifferentiated linter dump
  • Dependency and vulnerability exposure made explicit
  • Hotspot analysis showing where defects actually cluster
  • Quality gates running in your pipeline afterwards
Discuss this
Stylised contour and boundary map with plotted data points, in JADC teal and lime

GIS & Mapping Software

Spatial data put to work: web mapping, geocoding, routing and spatial analysis built on open standards and open data.

  • Responsive web maps that cope with real data volumes
  • Accurate UK address matching and geocoding
  • Spatial analysis built on PostGIS and open standards
  • Field capture that survives poor rural connectivity
Discuss this

How we work

Three habits, applied to everything

We have no methodology to sell you. These are simply the things that decide whether a software engagement is worth what you paid for it.

Senior people only

You get the engineers who scoped the work. Nothing is quietly handed to a junior once the contract is signed.

No lock-in by design

Mainstream technology, your repositories, your infrastructure, full handover. Leaving us should be easy and we build on that basis.

Data-first engineering

Most software problems are data problems wearing a costume. We start with the data and the systems tend to follow.

Plain-English reporting

Findings and progress written so that both your developers and your finance director can act on the same document.

  1. Understand before proposing

    We start by reading the code and talking to the people who use the system. No proposal until we can describe your problem back to you in your own terms.

  2. Smallest useful increment

    Something real and reversible in front of you early, rather than a six-month reveal. You can change direction while changing direction is still cheap.

  3. Leave the capability behind

    Tests, documentation and deployment are part of the work, and your developers are in the room while it happens. The measure of the engagement is what your team can do once it ends.

About JADC

A deliberately unglamorous name

We called ourselves Just Another Computer Company because the industry has enough companies promising transformation. What organisations usually need is someone competent to read the code, fix the data and explain honestly what is going on.

We work from Half Moon Farm in Rushall, Norfolk. That means low overheads, no sales floor, and the person who scopes your work being the person who does it. Our clients are UK organisations with real systems and real constraints: the thing in the corner that nobody wants to touch, the dataset that three departments disagree about, the development team that wants to use Claude well rather than just quickly.

Our tagline is not decoration. Almost every problem we are called about turns out to be a data problem wearing a software costume, and that is where we start.

JADC's working base at Half Moon Farm in Rushall, Norfolk: a
                  converted rural building housing a small senior engineering team

Find us

Half Moon Farm Rushall Norfolk IP21 4QD

Questions

Before you get in touch

If what you need is not covered here, call +44 (0) 330 043 2099 and ask. You will get an engineer, not a switchboard.

Hands-on work against your own codebase rather than a generic course. A typical engagement mixes pairing sessions, focused workshops on agentic patterns and context engineering, review of your team's AI-assisted pull requests, and an agreed set of written conventions your team owns afterwards. It is usually a few days a week over a handful of weeks, scaled to the size of the team.

We are based at Half Moon Farm in Rushall and Norfolk is our home patch, so we are on site easily across East Anglia. The work itself is delivered remotely for clients across the United Kingdom, with travel for workshops, discovery and the sessions that genuinely benefit from being in a room together.

A code quality analysis or a short discovery is a perfectly sensible way to start, and it is how a lot of our longer relationships began. If a couple of days of review is all you need, we will tell you that rather than manufacture a project.

You do, outright, in your own repositories, along with the tests, documentation and deployment pipeline. We use mainstream technology you can hire for, and handover is part of the engagement rather than an afterthought.

That is the arrangement we prefer. Embedding with your developers is how the capability actually transfers, and it means the decisions we make together survive our departure.

Under a signed NDA where you want one, with access limited to what the work requires and removed when it ends. We are a UK data controller for our own records and act as a processor under written instruction when handling yours. Our privacy notice sets out the detail.

Tell us what is not working

A short conversation with a senior engineer, no obligation and no sales script. If we are not the right people for the job we will say so, and point you at who is.