Request a walkthrough

A screen-share on a working tenant, with the person who built it. Tell us what you would want to see.

Your name is missing. Add it and send again.

Email address is missing an @. Check it and send again.

Organisation is longer than 200 characters. Shorten it and send again.

The message is empty, or longer than 5,000 characters.

The verification check did not pass. Try again, or write to contact@daxiadata.com.

Too many messages from this connection in the last minute. Wait a moment and try again.

We could not send that. The message is still in the box — try again, or write to contact@daxiadata.com.

The form was sent in a format the server does not read. Try again, or write to contact@daxiadata.com.

What happens next

1
Your message goes to contact@daxiadata.com. We read it, not a queue.
2
You hear back within two working days with a proposed time and a short list of what the walkthrough will cover, based on what you asked.
3
The walkthrough is a screen-share on a working tenant. If you can name a source system and a table or two, it is run on something that looks like yours.

Prefer email? contact@daxiadata.com. No sales sequence follows either route.

What we do with what you send

Three claims, each of which is the behaviour of the code that receives the form.

The message is stored in a database in our own Cloudflare account.

One row: name, email, organisation, message, the time, and whether the browser passed the verification check. Nothing is forwarded to a third-party CRM.

We keep a salted hash of your IP address, never the address.

The hash lets us see repeated abuse from one connection; it cannot be turned back into the address. The user-agent string is kept for the same reason.

This site sets no cookies.

Analytics are Cloudflare Web Analytics, which is cookieless. The theme preference lives in your browser’s local storage and is never sent to us. The verification widget loads only on this page.