Find out what the software should be, before you commit to building it.
Pathfinder Labs Corporation is an applied research and prototyping studio in England. We take an untested product idea, put working software in front of real conditions, and hand you the evidence: a running prototype, a written record of what held up and what did not, and a clear recommendation about what to do next.
Three kinds of question, one kind of answer: something running.
Each of these ends with software you can execute and a document you can hand to somebody who was not in the room.
-
01 · Feasibility probes
Answer the question a document cannot
You have a technical question that a document cannot answer. We build the smallest thing that answers it and write down the result, including the negative one.
-
02 · Product prototypes
A version you can put in front of people
A working, clickable, deployable version of the idea, with real data, real latency and real failure modes. Good enough to test with users and to cost a build against.
-
03 · Technical due diligence by construction
Implement the risky part twice
Before you pick an architecture or a vendor, we implement the risky part twice and report which one survived.
Four stages. Each one timeboxed and priced before it starts.
We take one engagement at a time. These are commitments about how we will work, not a description of work we have already done.
-
01 · 1 week
Frame
We write the question down and agree what would count as an answer. If we cannot agree on that, there is nothing to build yet and we say so.
-
02 · 1 to 2 weeks
Probe
We build the throwaway version. It exists to settle the question, not to survive contact with users.
-
03 · 3 to 5 weeks
Prototype
We build the version you can put in front of people, running on real data with real latency and real failure modes.
-
04 · 1 week
Hand over
Source code, a written findings memo and a recommendation you are free to act on without us.
Two rules that sit above the four stages
You own the code and the findings outright from day one. And if the honest answer at the end of Probe is that you should not build this, we say so and stop billing.
We are new, so instead of a client list we publish our own work.
These are prototypes we start because we want to know something. Status is stated honestly, and where one gets shelved the notes explain why.
Nothing is published here yet, and that is the honest position
THE PATHFINDER LABS CORPORATION LIMITED was incorporated on 1 March 2026. As of 7 August 2026 no experiment has reached a stage where the result is worth reading. We would rather show you an empty record than a full one you cannot check.
Every entry we publish will carry all six of the fields below, including the ones that are uncomfortable.
- Date started
- The real calendar date the work began.
- The question
- Written before the code, in one sentence, with the condition that would count as an answer.
- What we built
- What the prototype actually did, and what it deliberately did not do.
- What happened
- The result, stated plainly. Negative results are published on the same terms as positive ones.
- Status
- In progress, finished, or shelved with the reason for shelving it.
- Where the code is
- A link to the source, or an explanation of why it cannot be published.
If you want to be told when the first entry appears, email us and say so. We will send one message when it happens and nothing else.
We would rather hand you a short memo that says do not build this than a long one that says maybe.
Evidence, not opinion
An opinion about whether something will work is cheap and we have no track record to make ours expensive. A running artefact under real conditions is different: you can point at it, argue with it, and take it to somebody else for a second reading.
Timeboxed and priced before it starts
Every stage has a duration and a price agreed in writing before work begins. If a stage overruns because we misjudged it, that is our cost, not yours. If it finishes early, the next stage starts early.
You own it outright
Source code, findings, notes and any negative results belong to you from day one. There is no licence to renew, no repository we hold the keys to, and nothing that stops you taking the work to a different team the week we finish.
What we do not claim
We do not hold ISO 27001 certification, a SOC 2 report or Cyber Essentials certification, and will not represent otherwise. We have no published client work, no user numbers and no funding history to show you, because the company is new. Anything on this site that is not yet settled is marked rather than smoothed over.
One person is accountable, and you meet them first.
The person who writes the code writes the findings memo and sits in the meeting where the recommendation is delivered. There is no account manager between you and the work, and nobody appears on the invoice who was not in the room.
We are not going to fill this section with biographies of people who do not work here. The company is small and new. The director of THE PATHFINDER LABS CORPORATION LIMITED is on the public register at Companies House against company number 17061706, which you can check without asking us.
[TO CONFIRM: name of the named engagement lead, and a first-person biography covering their own skills and interests. Nothing will be published here until it is written by that person and is true.]
Tell us the question. One paragraph is enough.
hello@pathfinderlabs.co.ukThere is no contact form on this site. Email reaches a person directly, which is faster and leaves you holding a copy of what you sent.
- Response time
- We reply to email within two working days, Monday to Friday, UK time.
- What helps
- The question you want settled, any deadline you are working to, and what you would do differently if the answer turned out to be no.
- Post
- 30 Pettley Gardens, Romford, England, RM7 9AB. Post is slower than email and is not monitored daily.
- Not us
- Several unrelated businesses use similar names. See the note about our name before you write.