Contact
Ask the awkward question first.
Whether it can file anything (it cannot), what happens to your client data, whether it earns its place at your portfolio size. You will get a straight answer from a person, and a screen to look at rather than a slide.
Where each enquiry goes
Five reasons to get in touch.
Most of them end at the form below. Two do not — a security disclosure and an existing pilot practice both have a faster route, and it is worth using it.
A demo
Half an hour, no slides, against a portfolio the size of yours. We will show you a confirmation statement prepared to the point of filing — and then show you that the software refuses to send it, because that refusal is the design rather than a gap.
A pilot enquiry
Compliance Cockpit is in a closed pilot. That deployment holds synthetic data only, testers are asked not to upload real client documents, and the HMRC credentials are left out of it entirely so that no VAT return can leave the build. If you would like your practice considered, choose Pilot enquiry below and tell us what you work on.
A security disclosure
Tell us before you tell anyone else and we will work with you. Email security@compliancecockpit.co.uk with the steps to reproduce it, the URL affected and roughly when it happened. Please do not post it publicly first.
The same address is published at /.well-known/security.txt. Our policy is on the security page.
Support, if you already use it
Pilot practices are given a named support contact when their pilot starts. Use it in preference to this page: it reaches the people who can look at your actual deployment, and it will not wait behind a general enquiry. If you have mislaid it, ask below and we will send it back to you.
Press and analysts
We keep a media kit: boilerplate, product screenshots and a plain statement of what the software does and does not do. Choose General question below, say you are writing about us, and we will send it over. What you will not find in it is a customer name, a logo or a number we cannot evidence — we do not publish those, and we would rather say so now than disappoint you at deadline.
Get in touch
Send us an enquiry.
What happens when you press send
- No email is sent. There is no CRM behind this form and no email provider configured in this build, so nothing is delivered automatically — including an acknowledgement to you. There is none to wait for.
- Your enquiry is recorded. It is written to the private area of our server that the application uses for anything that must not be public, and you get a reference on screen.
- A person replies. Someone here reads what was recorded and writes back, from a real mailbox, to the address you gave. We are a small team and will not promise a response time we have not measured.
- Nothing you type reaches a URL. The form posts its values and the page does not navigate, so your details cannot end up in your browser history, a referrer header or a web-server access log.
We keep what you typed and the time you sent it, and nothing else. Your IP address is not stored with the enquiry — it is used only by an in-memory counter that stops the form being flooded, and it is never written to disk. The rest is in the privacy notice.
There is no general mailbox published on this site yet. We would rather leave that blank than print an address nobody is watching.
Would rather see it than read about it?
A demo answers more in half an hour than a page of copy will, including the parts that do not work yet. Bring the client company you find hardest to keep straight.