---
title: "Insurer tenders: what we've learned answering RFIs and RFPs"
url: "https://getcurium.com/news/insurer-tender-rfi-rfp-lessons/"
published: "18 November 2026"
author: "Laura Thomas, Head of Operations & Customer Experience"
publisher: "Curium"
description: "Lessons from answering insurer RFIs and RFPs: why problem-first tenders work, who should be in the room, and why honest feedback matters."
---

# Insurer tenders: what we've learned answering RFIs and RFPs

Lessons from answering insurer RFIs and RFPs: why problem-first tenders work, who should be in the room, and why honest feedback matters.

Answering insurer tenders has been a huge part of my role since joining Curium. A tender usually starts with an RFI (a 'request for information', basically a long questionnaire about who you are and what you do), and can then move to an RFP (a 'request for proposal', where you set out how you'd actually solve the insurer's problem). Each one can take our team days, sometimes weeks.

We've now answered enough of them to see what works and what doesn't, for us and for the insurers running them, so I wanted to share a few lessons for insurers running tenders and insurtechs answering them. I think there's a lot both sides can do to make this easier.

Insurtech Australia has also just published Building Bridges, its guide to how insurers and insurtechs can work better together, and a lot of it really struck a chord with what we've seen first-hand.

## Getting our own house in order: building an answers library

Building our RFI and RFP library has been one of my biggest jobs at Curium. It now holds over 700 questions and answers from the tenders and security questionnaires we've completed, sorted into 12 topics (claims handling, complaints, security, data, implementation and so on), so when a new tender comes in, we search for the same or a similar question and adapt the answer, rather than starting from scratch every time.

It took real effort to get there, and it's never 'done'. Answers go out of date quickly, especially anything touching security, so we check each one before we reuse it, and we never commit to anything that isn't actually in place today.

In short, the library hasn't made tenders quicker overall, but it means we can juggle several at once while still supporting new clients. Without it, answering RFIs and RFPs could easily become one person's entire day job.

## Two very different tenders: problem first or paperwork first

The first, with a large insurer, was structured from the get-go and started with the problem. We met the people who actually live with it, over several rounds, and each round got more specific. Their questions in demos led us to improve parts of the system, and those improvements have since gone out to other clients too! As far as I can tell they're now down to a couple of suppliers, and whatever happens, we've come out of it with a better product.

The second started the other way round. Before I joined the business, the team had received a very large request for information, and they tell me it took weeks to pull together. By the first meeting, there were a considerable number of people in the room, each from a different part of the business with their own agenda, which made it really tricky to prepare a focused demo.

The difference wasn't the size of the insurer or the quality of the people involved. It was how the process started, namely problem first or paperwork first.

## Why it matters beyond us

Insurers are already carrying a huge compliance load. The Insurance Council of Australia's [Cost of Regulatory Burden report](https://insurancecouncil.com.au/wp-content/uploads/2025/11/20251107_ICA-Report-The-Cost-of-Regulatory-Burden_Final.pdf) (November 2025) put the cost of compliance at $2.5 to $3.5 billion a year, or 4 to 6% of gross written premium, and the people running tenders are often the same compliance, risk and claims people carrying that load.

So a long tender process ultimately costs the insurer too. Every question sent to 10 suppliers means 10 answers someone has to read and score, and when a request for information runs to 100+ questions per form, plus supporting documentation, it becomes very clear where the time is really being spent.

Whilst I understand why insurers ask for everything up front (nobody wants to get to the end of a tender and find an issue that rules a supplier out), the reality is that it drags the whole process out, for them and for us. A lot of the detailed checks, like security and due diligence, make more sense after you've shortlisted, so you're only reading answers from the couple of suppliers you'd actually love to have in the room.

## Who's in the room

Who's in the room makes a huge difference, and it's so different between smaller and larger insurers.

With smaller insurers, it's usually the head of claims and the claims manager at the table, the people who'll actually use the system day to day, so the questions are all about how their work gets done, making for a really useful conversation.

Larger insurers have more people with a stake in the decision, which makes sense, but the trouble starts when everyone comes to the first meeting at once, before anyone has agreed what problem they're trying to solve.

## Feedback is part of the process

A tender is a massive investment on both sides. For a supplier, it can mean months of work, sometimes four or five rounds and 15 or more meetings, so when it ends with a short note saying the quality of candidates was really strong (a bit like after a job interview), it's really hard to take anything away from it.

Constructive feedback helps us all grow, and ultimately we learn from our failures, not our successes. I appreciate everyone is tired by the end of a long tender (we've had some run for 6+ months), but taking the time to give that feedback really matters, and to be frank, it's just respectful.

Part of the beauty of being the business we are is that we're agile and always adapting, so we're able to adjust our product quickly, and clear feedback this month can change what we build next month. Without it, the whole process can feel like wasted time, for both sides.

## What helps if you're an insurer

- **Start with the problem.** Tell suppliers what's going wrong, and for whom, before asking them to describe everything they do.
- **Get the problem owners in the room.** The people who live with the problem ask the best questions, and they can tell 'fluff' from substance in seconds.
- **Use knockout questions, then shortlist.** Ask a handful of must-haves up front (certifications, where data is hosted and so on), then save the long security and due diligence questions for the suppliers you're seriously considering.
- **Ask each question once.** We're often asked the same thing several times in one tender, so one shared set of questions really does save everyone time.
- **Give a clear brief.** 'Exploring our AI strategy' is really hard to respond to. We're all for insurers using AI (we use it in our own product!), but a specific problem gets you a much better answer than a broad one.
- **Keep demo audiences focused.** Bring the people who'll use the system and whoever needs to sign off, and bring the wider group in during later rounds.
- **Give honest, specific feedback.** Being told everyone was really strong doesn't help anyone improve. When we've phoned to ask, the real reason has sometimes been something we could have solved, like an integration we were able to build, so a straight answer gives suppliers a fair chance and keeps the relationship in good shape for next time.

## What helps if you're an insurtech

Not all of this sits with insurers, and there's plenty we can do on our side too. A few things that have helped us:

- **Build an answers library early.** Give someone the job of keeping it current, otherwise it quietly goes stale.
- **Ask who owns the problem.** If nobody can tell you, I think that says a lot about where the tender is heading.
- **Treat demo feedback as product input.** Some of our most useful improvements started as a question in a prospect's demo.
- **Ask for feedback, even when it's awkward.** If the written decline is vague, pick up the phone. We've had far more useful answers from a quick call than from an email.
- **Offer a way to try, on your terms.** Live demos go a long way. Beyond that, we've offered a time-limited sandbox under an NDA, and for our [File Audit tool](https://getcurium.com/products/compliance-audit/), a small paid trial on a prospect's own files. We're also rolling out a self-service version of our platform for anyone who wants a 'flavour' of what we do. What we can't do is hand over a fully configured system for free, as implementation is a real investment for us.
- **Protect your time.** No supplier can answer every tender, so it's worth asking whether there's a real problem and a real chance before committing weeks to one.

## Tenders don't need to be painful

I don't think tenders need to be painful for either side, and we've seen just how quick they can be when it works.

One business we've been working with recently came in knowing exactly what problem they wanted to solve, so going into the demo, everyone knew why we were there. They came back with a few questions, and an idea for how the software could help with something else too, so we adjusted our proposal to cover those points. From our first demo to contract stage took around three weeks.

So if you know what you want, it can be an incredibly quick process.

If you haven't read it yet, I think Insurtech Australia's [Building Bridges guide](https://insurtechaustralia.org/reports-research/) is really worth a look, with practical advice for insurers and insurtechs alike.

If you're running a tender for a compliance, risk or claims system and would like to see how Curium could fit, [get in touch](mailto:sales@getcurium.com?cc=louise@getcurium.com).

**Author:**

Laura Thomas, Head of Operations & Customer Experience, Curium. [LinkedIn Profile](https://www.linkedin.com/in/laurathomaslawyer/).
