RESPONSE TO RFI · REF. AIRFP/COMPANY-OVERVIEW
Before we built AIRFP, answering RFPs was our job. The platform puts that method within reach of any team that answers tenders, with or without a dedicated bid function. This page is written the way we used to write those responses: your questions, in order, each one with its answer and its source.
30 minutes, on an RFP you currently have open.
Describe the origin of your company and the rationale behind your solution.
For fifteen years, our job was to answer. Specifications running to hundreds of pages, questionnaires hundreds of lines long, Excel grids filled in cell by cell, annexes landing two days before the deadline. The response always went out on time. The part that would have made the difference — the angle, the argument, preparing for the final presentation — was always handled last, with whatever time was left.
The frustrating part was not the workload. It was knowing the answers already existed. They had been written, by our own teams, in a response submitted six months earlier. Somewhere in a SharePoint. The work was never the writing. It was the finding.
We looked for the tool that solved it. What we found were content libraries you copy and paste out of. We found no platform that worked inside the Excel grid in its original format, that returned the deliverable with its formatting intact, or that asked the question which comes before all the others: do we bid at all? In the end we wrote it ourselves.
And that method cannot always be hired. That is what AIRFP makes accessible — to organisations that have a bid team, and to the many more where the RFP lands on the desk of a salesperson or a presales lead who already has another job.
Evidence your experience in the relevant field.
Across fifteen years of bid management, AIRFP's founders led responses that won more than €500 million in signed contracts: regulated sectors, public procurement, international accounts, final presentations.
That experience is what the product encodes. The qualification grid, the scored Go/No-Go, the way effort is distributed against the buyer's own scoring grid, the debrief that feeds the next response: these are not features derived from a design workshop; they are practitioner reflexes — reflexes an organisation cannot hire on demand, and that the product applies on its behalf.
The scale of those bids is not a condition of use. What carries over is the method they produced, and it applies to a forty-line questionnaire as readily as to a three-hundred-page specification.
Scope — this figure is the cumulative value of contracts won by the founders during their careers as bid managers, before AIRFP. It does not predict results obtained by customers of the platform.
Introduce the team that will work on our bid.
The person handling your question about an Excel grid spent fifteen years filling them in, and the person who decides what gets built is in the same conversation. You are not explaining your job to a support desk that is discovering it.


What external expertise do you draw on?
David Danino and Joel Bentolila advise AIRFP on strategy and architecture — one after operating at executive level at Capgemini, the other after running engineering at Talentsoft. They are here for one question: what survives contact with a large organisation, and what does not.


Describe the methodology you apply.
AIRFP follows the order of a real bid: qualification and strategy first, production after. That is what separates a compliant response from a winning one, and it is also what separates the platform from a drafting assistant with stages bolted on.
An organisation that qualifies the same way from one bid to the next knows what it is committing to, and why. That is what makes a portfolio of opportunities predictable — not the speed at which a questionnaire gets filled in.
Relevant opportunities surface before anyone forwards them to you.
A Go/No-Go scored on your own criteria. The decision still holds up six months later.
The angle, the differentiators, effort allocated against the scoring grid.
Questionnaires, Excel grids and technical proposals handled in their native format.
The debrief stops being reserved for the big bids. The next response inherits what this one learned.
How is the data we share hosted and protected?
A bid response carries the most sensitive material an organisation holds: its pricing, its technical architecture, its customer references. How those documents are handled is the first thing a security team checks, and it is the subject with the least room to negotiate.
Scope — the AWS Europe infrastructure hosting AIRFP is ISO 27001 certified. AIRFP itself, as a vendor, is not: its certification is in progress. We answer your security team's questionnaire before the demo, not after.
Frankfurt. Your documents are hosted inside the European Union.
Isolation at database level. Your data never sits alongside another client's.
At rest and in transit, with no carve-outs.
Your files train no model — neither ours nor a third party's.
Processing, sub-processing and data subject rights documented.
For organisations whose internal policy requires it, on their own infrastructure.
What set-up and maintenance load does this put on our teams?
A knowledge base that starts with a data-entry project never gets filled. Teams that have already tried a tool say so plainly: the time spent feeding it exceeded the time it saved, and the work had simply moved somewhere else.
AIRFP works the other way round. Material enters through the bids you already handle: the answers approved on one response feed the next, each carrying its source document and its date. The debrief stops being an exercise reserved for the big bids, because it stops being a separate exercise.
The shortest way to judge AIRFP is not a generic demo. It is to take an RFP you have open right now and watch what the platform does with it — the qualification, the grid, the deliverable.
30 minutes. You bring the RFP, we run it through the platform in front of you.