You tell us the problem
The more specific, the better. “Our reception has a queue at 08:45 and the visitor book is illegible” produces a far better demo than “we would like to see the platform”.
Book a demo
Bring us one process
Bring us one process
you want to fix.
Not a feature list. A specific Tuesday-morning problem: the reception queue, the absence chase, the trip approval that took five weeks, the fire drill, the month-end reconciliation. We will build the demo around that one thing.
Forty-five minutes, not a marathonYou will be talking to the people who build the platform, not to a presenter. If we are the wrong fit for what you need, we would rather say so in the first ten minutes.
What happens to what you sendIt goes to the ISA Bridge team so we can prepare. We reply within one working day. We do not add you to a mailing list and we do not pass it on. See our privacy notice.
Bringing your IT lead?Ask for the technical call instead, or as well. Thirty minutes on hosting, permissions, audit and exit terms, with no sales content. See the security page first.
What happens nextFour steps,
Four steps,
and none of them is a proposal you did not ask for.
We will not put you into a sequence of follow-up emails. If the first conversation says we are not right for you, that is where it ends and we will tell you who might be.
A short call before the demo
Fifteen minutes to understand how your school actually does that thing today, and which of your current systems are involved. This is what stops the demo being generic.
The demo, built around your case
We use your scenario, not ours, including the awkward version of it. Bring the person who does the job daily; they ask better questions than anyone else in the room.
A written scope, or a straight no
If it fits, you get a scope you can take to your governors with each part itemised. If it does not, you get a sentence explaining why rather than a follow-up call.