Software products · Sector unrestricted
Built to last, not to launch.
- Incorporated
- 2026
- Companies House
- Jurisdiction
- England and Wales
- Companies House
- Sector
- Unrestricted
- Stated by the company · Register: SIC 62012
- Operators
- One
- Stated by the company
Facts as at 7 October 2026
01 / Company
Pipo Ventures is a UK company that builds and owns software products. It was founded in 2026 and is run by a single operator. Products are built to a documented standard and released when the evidence supports it. There is no fixed sector.
On verification
Every statement of fact on this page names where it can be checked. Where a fact does not yet exist, the page says so rather than filling the space.
Companies House record02 / Product slots
2 of 3 allocated
-
Slot 01
Public
Live
Plyego
Publish a book. Without the publisher.
Book production software for authors. Upload a Word manuscript; get a typeset print PDF and an EPUB, formatted to your chosen pack's conventions for the parts of the manuscript it can identify. Render as many versions as you like, free. You pay once, for the version you download.
Status: Live. Available to UK residents.
Stated by the company
-
Slot 02
Alpha
Allocated
Surfaceplate
Installs into a repository; checks it against what it publishes.
A software delivery standard that installs into a repository and checks the repository against what it publishes: how software is built, reviewed and released, and how AI assistants may take part in that work. One command installs it; a conformance checker, a pre-commit hook and a CI workflow hold the repository to it.
Status: alpha. Not independently audited. Two adopting repositories, both the owner's own. Open source: Apache-2.0 for the software, CC0-1.0 for the documents.
Stated by the product: its README
-
Slot 03
—
Unallocated
Nothing here yet.
The slot stays empty until a product exists. Its sector is not decided in advance.
03 / The documented standard
What gets checked, and why.
Six things are looked at before anything is released, and how each one is actually applied.
Spec
Specification written before implementation
The specification is written first because it is the cheapest place to be wrong. A paragraph is easy to change; a shipped structure is not.
Test
Test suite passes from a clean checkout
From a clean checkout, not from the machine that built it. A suite that only passes where it was written is evidence about that machine, not about the software.
Risk
Failure modes identified and documented
Failure modes are written down before release rather than after an incident. Naming what can go wrong is what makes it possible to notice it happening.
Data
Data recoverable from a verified backup
A backup is not a backup until something has been restored from it. Until then it is an assumption with a filename.
Roll
Rollback path exercised, not assumed
The rollback path is run, not written down and trusted. A procedure nobody has executed is a plan, and a plan is not evidence.
Review
Output reviewed against the standard
Output is checked against the standard rather than against expectation. Work reviewed only by the person who produced it inherits the same blind spots.
04 / Operator
Mario Pipo Sanchez
Quantitative risk professional
CFA charterholder. MSc in Statistics and Financial Mathematics. Nine years in credit risk modelling, model validation and stress testing across financial services.
Stated by the operator