Book a demo
Half an hour, your own companies, no slides.
We will show you the parts that do not work yet as well as the parts that do. That is not modesty. You would find them in week three anyway, and week three is a much more expensive place to find them.
There is no calendar here to pick a slot from, because there is no scheduling system behind this page and we would rather not pretend there is. You tell us roughly when suits; a person reads your request and replies to agree a time.
30 min
The whole session, questions included
Four blocks, and the last five minutes are yours. If it needs to be shorter, say so and we will cut the middle.
2–3
Company numbers, from your own portfolio
The reconstruction reads public Companies House filings, so a number is enough to run it on a company you actually know.
0
Documents, logins or exports we need
Nothing confidential leaves your practice to make this demo work, and there is nothing to install or connect.
The running order
What half an hour actually looks like.
It is the product on a screen, driven by whoever asks the question. There is no deck, no roadmap slide, and no section where we describe something that is being built.
0–5 min
You talk, we listen
How the compliance side of your practice runs today: what lives in a spreadsheet, what lives in one person's head, and which deadline you most recently came close to missing. Nothing we show afterwards is useful until we know that.
5–20 min
The product, on companies you named
The share register reconstructed from the public filings of your own client companies, with the filing behind each figure named; the statutory register with its as-at view; the worklist a Monday actually runs on; and a Companies House filing prepared to the edge, with every field marked as one the records supply or one only a person can.
20–25 min
Where it stops
The boundary, in the product's own words rather than ours: what is prepared, what is sealed into a package, and what a person at your practice has to do next. This is also where we show you the flags — an over-allocated register, filings that contradict each other — because a product that stops is only worth having if you can see why it stopped.
25–30 min
Your questions
Including the awkward ones. If they are about data handling, say so when you ask for the session and we will bring the technical due diligence and the company secretary's review with us.
One honest split, so it is not a surprise on the day: the ownership reconstruction runs on yourcompanies, because it needs nothing but their public filings. The parts that depend on a year of a practice’s work being in the system — a prepared filing with its approvals behind it, a document pack, a client approval recorded in the portal — are shown on our own demo data, because we cannot manufacture your practice’s history in fifteen minutes and would not want you to think we had.
Who should be there
Three people, and none of them need to be technical.
If those three are one person in your practice, then it is one person. We would rather run the session than spend a fortnight aligning diaries.
The partner who owns compliance risk
The person who signs off, and who would be answering the question if a register turned out to be wrong. They should hear where the product stops from the product, not from a salesperson.
Whoever actually does the company secretarial work
They will find the gaps in five minutes that a partner would take a month to notice, and they are the person who decides whether this is genuinely quicker than what they do now. If they are not in the room, the session is a presentation.
Whoever answers your firm's data questions
Pilot software holding client data is something your own supervisory obligations make you ask about. Bring that person, or send them to the security page first — including the section headed what we do not claim.
If your data questions want answering before anybody gives up half an hour, read how we handle your data — every claim on it names the control and the file it lives in, and the limits are listed in the same detail as the controls.
What to bring
Two or three company numbers. Genuinely nothing else.
The reconstruction reads the public register — incorporation documents, returns of allotment, transfers and confirmation statements — so a company number is enough to run it. That is what lets the demo use companies you actually know without your practice sending us anything confidential.
Bring these
- Two or three company numbers from your own portfolio. Pick the awkward ones: twenty years of filings, a corporate shareholder in the chain, or the register you inherited and cannot evidence.
- A rough portfolio size, so we show the screens that matter at your scale rather than the ones that demo well.
- The two or three questions you actually want answered. The running order bends around them; it is not a script we are attached to.
- Roughly when in the week suits you, and how long you can give it.
We will not ask you for these
- No client documents, exports or spreadsheets. Nothing confidential needs to leave your practice for this.
- No Companies House authentication codes. Nothing in a demo needs one.
- No logins to your own systems, and no integration to set up beforehand.
- No card details. There is nothing to pay for at this stage and no trial to cancel.
The pilot environment holds synthetic data, and pilot firms are asked not to upload real client documents. A demo does not change that — which is exactly why the reconstruction runs from the public register instead.
Stated before you ask
The parts that do not work yet.
Naming these on a public page costs us some demos. It saves us the ones where a firm discovers them in week three, and those cost considerably more — to them as well as to us.
Nothing is transmitted to Companies House
This one is deliberate and permanent rather than unfinished. The filing client throws and opens no socket — you can check it in about a minute by searching the module for a fetch. We prepare the form, the data, the statutory deadline and a sealed, content-hashed package, and somebody at your practice submits it.
The pilot cannot submit a VAT return
The pilot deployment omits the HMRC credentials entirely, so the connection resolves to not connected and no submission is possible. Sandbox mode generates its sample data locally and labels it on screen; we will not show you a sandbox receipt and call it a filing.
Nothing runs on a timer yet
The scheduled jobs exist and run on demand, and nothing in the pilot environment runs them overnight. If you are imagining a chaser that goes out at seven in the morning without anyone pressing anything, it does not, yet. The due diligence names this as the largest unaddressed operational gap, and so do we.
The conflict wall is not yet on every screen
Restrict which staff see which clients and the restriction holds in the database query across the client list, companies, deadlines, search and the company secretarial work. It does not yet hold on the compliance worklist, the compliance reports or the VAT client picker, which still show every client’s name. We will show you exactly those screens if you ask.
The second reader is architecture, not a feature
An independent document reader can run behind the main one and compare what the two extract. It is off unless an operator turns it on, it has no user interface, and it never overrides your data. On demo data the extraction counters read zero, so we will not open an empty panel and describe it as intelligence.
No certification, and no penetration test
We hold no SOC 2 report and no ISO 27001 certificate, neither is in progress, and no external penetration test has been commissioned. A twelve-attack cross-tenant suite runs on every change and is our own code — useful, and not the same thing. This is pre-1.0 software in controlled pilot.
Ask for a demo
Tell us who you are and what you want to see.
Five fields. A person reads every one of them, and replies to agree a time that suits your practice.
What happens when you press send
- Nothing is e-mailed. There is no mail transport configured for this site, so it cannot send you an automatic acknowledgement — and telling you it had would be the first untrue thing we said to you.
- Your request is written to a private file on our server and given a reference, which appears on this page the moment it is saved. That reference is the acknowledgement.
- A person reads the file and replies by e-mail to the address you give, to agree a time.
- What is kept is what you type and when. No IP address, no user agent, no tracking profile.
- There is no customer-relationship system behind this form and no marketing list to be added to, because neither exists.
Not ready to talk to anybody?
Reasonable. There is more written down here than most products give you before a call — including the parts we would rather you did not find on your own.
Compliance Cockpit prepares Companies House filings and stops. A person at your practice submits them, and no statutory register moves until somebody approves the change.