ISO 27001 Certified badge by A-LIGNNewsWhalemate is ISO/IEC 27001:2022 certifiedSee Trust Center

Let’s talk about your human risk program

Tell us the size of your workforce and what you need to solve. You get a read on your case, not a brochure.

Who is on the other side

  • Mateo BovioCEO & Co-founder
  • Laura SoteloHead of CX
  • Alejandro SanchezHead of Operations

A product team running programs across LATAM, not an outsourced sales floor.

Already running their program with Whalemate

  • Naranja X
  • RappiPay Colombia
  • PROSA
  • Sancor Seguros
Whalemate gives us the local closeness we need to make cybersecurity part of our users' daily culture.
Banco del SolJavier TepedinoCISO, Banco del Sol

Tell us about your organization

The more context you leave, the more concrete the first reply.

Do you measure human risk in your organization?

No commitment: if Whalemate is not the fit you need, we say so.

Every field without “optional” is required.

Contact

A commercial conversation about your program, not a product tour

Write here if you are evaluating Whalemate for your organization: scope, workforce, integrations and what the program has to show when the board or audit asks.

Scope and workforce: how many people are in, in which countries, in which languages and which channels get simulated. Headcount changes the design of the program and the number too, so it is the first question you will get back. If you already have a vendor and you are comparing, say so in the message: the conversation starts at what you are missing today, not at a feature list you already read somewhere else.

Procurement and security: the Trust Center and the DPA are published so your team can review them before talking to us. ISO/IEC 27001:2022 is there. SOC 2 is not. No endpoint agent. If your tender asks for a seal we do not have, you will know in the first exchange and not three meetings later, once the quarter is gone.

Price and proposal: we do not publish a price list because scope drives it. The proposal is built from headcount, service level and timeline, and it comes in writing. What the first reply can give you is what defines the number and the order of magnitude it sits in, so you do not burn a buying cycle finding out.

Reasons

Three conversations that start here

You do not need a closed project to write. These are the three that arrive most.

You are building the program

Nothing is in place beyond the annual course. We define what to measure first, how to calibrate simulations and what evidence the program leaves behind.

You are comparing vendors

You have one and something does not add up: languages, LATAM support, thin analytics or a contract running out. We compare against your gap, not a grid.

You have an audit coming

A tender, a certification or a customer requirement with a date. We review what the framework demands and what the program can show in that window.

How it works

What happens after you send

Reading

A sales specialist reads the message with your context: headcount, industry and what triggered the search.

First reply

It arrives by email, with a read on your case and the questions still missing to size it. It is not an automated sequence.

Conversation

If there is fit, we set up a meeting about your operation. If there is none, that same email says so.

Questions before you write

Do I need an approved budget to write?
No. A good share of messages arrive mid-evaluation, with no number approved. Saying where you stand helps: sizing for the year you will budget is not the same as solving something that expires this quarter.
Will you drop me into an automated email sequence?
No. The first reply is written by a person, about what you sent. If after that reply you would rather not be contacted again, saying so is enough and it stays that way.
Can I ask for pricing in the form?
You can, and you will get what defines the number — headcount, scope, service level — and the order of magnitude it sits in. The closed price goes in a written proposal, not in a first email.