Skip to content
Contact sales

Talk to us about fit, cost and rollout

For plan structure, procurement questions and scoped rollouts. If you would rather see the product working first, a demo is the better starting point.

Send an enquiry

We only ask for what we need to route your enquiry and prepare a useful answer.

So we can reply and send the meeting link.

Helps us prepare the right setup — a range is enough.

The more specific the scenario, the more useful the conversation.

We use these details to route your enquiry and prepare for the conversation. We do not sell them or use them for advertising. Read the privacy policy, security practices or documentation first — none of it is gated.

Your enquiry is stored and visible to the RapidRoot admin team at /admin/enquiries — we reply within 1 business day.

What happens next

No drip sequence, no repeated follow-ups. One reply from a person, then whatever you ask for next.

  1. 01

    We read it and route it

    Commercial questions go to sales, technical ones to an engineer. You get one reply, not a hand-off chain.

  2. 02

    We reply within one business day

    That is a target we can hold, not a contractual guarantee. If your enquiry needs research we will say so rather than stall.

  3. 03

    You choose the next step

    A written answer, a demo, a security review pack, or nothing at all. We do not chase enquiries that have gone quiet.

For larger organisations

Most of what a review team needs is already published. Start here, then bring us the gaps.

Security review

Trust centre documentation covering data protection, access control, encryption and our compliance position — including what is not yet certified.

Open the trust centre

Procurement questions

Plan structure, billing model and the commercial terms we can discuss. Pricing is quoted on usage rather than published per seat.

Review pricing structure

Technical discussion

Architecture, integration surface, webhooks and the API roadmap, with an engineer in the room rather than a summary afterwards.

Developer documentation

Custom onboarding

Scoped rollout across teams or locations, with roles, reporting and the first workflows agreed before launch.

See onboarding

Not a sales question?