Legal nameVIVAN LABS LTD
Company number17061582
TypePrivate limited company
JurisdictionEngland and Wales
D-U-N-S number234619233
There is a version of this page that would tell you a founding story, name a leadership team and imply a decade of experience. We are not writing that one. VIVAN LABS LTD is five months old at the time of writing and everything below can be checked against a public register or is clearly labelled as an intention rather than a fact.
This is what the register says. If any line here disagrees with the register, the register is correct and this page is out of date, so please tell us.
| Field | Value on the register |
|---|---|
| Registered company name | VIVAN LABS LTD |
| Company number | 17061582 |
| Company type | Private limited company |
| Company status | Active |
| Registered office | |
| Registered in | England and Wales |
| Nature of business (SIC) | 62012 business and domestic software development; 62020 information technology consultancy activities; 62090 other information technology service activities; 63110 data processing, hosting and related activities |
| Officers and persons with significant control | Published on the public Companies House register against company number 17061582. We do not reproduce personal details of individuals on this website. |
| Accounts filed | None yet. The first accounting reference period has not ended. |
| VAT registration | [TO CONFIRM: VAT number, or a statement that the company is below the registration threshold] |
Why we print this. A UK limited company is legally required to disclose its registered name, number, place of registration and registered office. Most sites bury that in six point type at the bottom. We would rather put it in a table you can read, because for a company with no trading history the register is the only independently verifiable thing about us.
The phrase gets used for four or five different jobs. Here is the one we do, so that nobody buys the wrong thing.
We do this
Extraction, landing, modelling, testing, scheduling, lineage, access control and cost. The output is infrastructure and code in your repository plus documentation somebody else could pick up.
We do this
Taking a warehouse that grew organically and giving it ownership, contracts, tests and a lineage graph, without a rebuild. This is usually cheaper and always less risky than starting again, and it is the engagement we expect to be asked for most.
We do this
Classification, retention that actually deletes, deletion that propagates to downstream copies and backups, access reviews, and the technical evidence a data protection officer needs when the ICO asks a question.
Not this
We will make sure the numbers underneath your dashboards are right and traceable. We are not the right supplier for the visual design, the metric strategy or the reporting rollout, and we will say so rather than take the work.
Not this
We build the feature stores, training data pipelines and reproducibility around models. We do not build the models. A supplier who claims both at this size is stretching.
Not this
We are not a contractor supply business. Work is scoped, priced and delivered against a written outcome, or we decline it.
The right question for a supplier this young is not who else have you done this for. It is show me how you would fail, and what happens to me when you do.
We would rather be assessed on that than on a reference list. Ask us what happens if the engagement stalls, if a key person becomes unavailable, or if the company ceases to trade partway through a piece of work. The answers are the same ones we put in our terms: your code stays in your repository, your credentials are scoped and revocable, and nothing critical to your platform runs on infrastructure we control.
These are structural decisions made at incorporation. They are the reason we can make some of the commitments on this site, and the reason we cannot make others.
C1
We do not operate a SaaS component that a client platform depends on. Everything we build runs in the client's own cloud account, under the client's own billing and identity. That removes an entire category of supplier risk, and it also means we have no recurring product revenue, which is a real commercial constraint we accept.
C2
The company is registered in England and Wales, contracts under the law of England and Wales, and defaults to UK or EU cloud regions for anything it touches. Where a client's chosen tooling forces a transfer outside the UK, we say so before the work starts and handle it under the IDTA or the UK Addendum rather than after the fact.
C3
The first engagement with any client is fixed scope and fixed fee. Retainers, if they happen at all, come after both sides have seen how the other works. This is slower and less profitable than the alternative and it is the arrangement we would want if the positions were reversed.
C4
Scopes, findings, estimates, risks and bad news go in writing before they are discussed on a call. A written record is what protects a client from a supplier's memory, and it is the only way an engagement can be handed to someone else halfway through without loss.
Every line below is a limitation. They are collected in one place so that nobody has to go looking for them.
General enquiries get general answers. A described problem gets a considered technical reply, usually within two working days, and it costs you nothing to find out whether we are any good before you commit to anything.