About the company
Small, specific, and answerable for the seam.
VEXBE LTD holds company number 17005285 on the register for England and Wales, incorporated there as a private limited company. It does one narrow thing well: make two or more systems agree with each other, in writing first and in code second, then hand the result to somebody who does not need us in the room.
Three things sit on this page: the statutory record, the remit, and the principles the company can be held to. Particulars of the officers are filed at Companies House under 17005285 and readable at source, so this site does not restate them.
Why a practice narrowed to the seam
Integration is unusual among software problems in that the cost of getting it wrong is almost never paid by the people who caused it. A field is repurposed in one system on a Tuesday. Six weeks later a downstream report is quietly wrong, and the finance team spends a quarter reconciling by hand. Nobody logs a defect, because from every individual system's point of view nothing failed.
Consultancies that do everything tend to treat the seam as plumbing, something to be got through on the way to the interesting part. This practice runs on the opposite assumption. The seam is the interesting part, it is where the money leaks, and it deserves a written contract with the same seriousness a commercial agreement gets.
That focus also decides the size of the work we take on. One seam at a time: specified properly, delivered, proved and handed to somebody on your side who can run it. That is the offer, and it is the whole of it.
Remit
Summary of remit
Interfaces, data contracts, migrations, reconciliation and the small pieces of software that surround them. Under SIC 62012 and 62020, being business and domestic software development and information technology consultancy activities respectively.
Everything outside that is out of scope, including managed IT support, desktop and network administration, hardware supply, and any regulated activity.
Statutory record
What the public register says.
Transcribed from the filings held against 17005285. Should the table below and the filings ever diverge, treat the filings as authoritative and this page as stale.
| Field | Value | Note |
|---|---|---|
| Registered name | VEXBE LTD | The full legal name. There is no separate trading name. |
| Company number | 17005285 | Quote this on any correspondence or procurement document. |
| Jurisdiction | England and Wales | Registered under the Companies Act 2006. |
| Company type | Private limited company | Limited by shares. |
| Status | Active | As shown on the register at the date this page was written. |
| Registered office | On the public register | The registered office is the statutory address for service. It is not a client meeting address. |
| SIC codes | 62012, 62020 | Business and domestic software development; information technology consultancy activities. |
| Officers | On the public register | Published at source by the registrar. Deliberately not restated on these pages. |
Searching the register costs nothing. Verification you perform beats a table published by the company being verified, which is why the number sits in the masthead of every page here.
Operating principles
Five commitments that are testable rather than aspirational.
A value is only worth publishing if a client could catch us breaking it. Each of these is written so that you could.
01
The exclusions are written before the price
Every proposal states what is not included, and it is drafted before the number is. If you find something in a proposal from us where the scope is ambiguous enough to argue about later, that is a defect in our document and we will correct it at our cost, not yours.
02
Estimates move in public
If an estimate changes, you hear it in the weekly written note in the week it changes, not at the end. On a fixed price engagement a change in our estimate is our problem financially, and you still get told, because you may want to change the scope in response.
03
Handover is a deliverable, not a favour
An engagement is not complete until a named person on your side has operated the thing, including at least one failure path, with us present but not touching it. If we cannot get that session scheduled, the engagement stays open rather than being quietly declared finished.
04
Access is the minimum that works
We ask for the narrowest access that lets the work proceed, we ask for it in writing, and we ask you to revoke it on the day the engagement ends. Where personal data belonging to you passes through our hands, interface IF-05 in the privacy notice specifies the arrangement, and a written processing agreement is signed before any credential exists.
05
We say no in the first week
If the work falls outside our remit, or the estate needs something we cannot supply, that lands in your inbox during the enquiry rather than three invoices later. Declining work we could technically have billed for is the thing that gives the other four commitments any weight.
Next
Name the two systems that won't talk.
One paragraph about one broken seam to [email protected], and you get a written answer inside three working days on whether this is work we can do.