Sections, extracted
Drop in the issuer's .docx, .pdf, .xlsx or .txt and ProposalOne reads it, finds the questions, and creates a section per requirement — so the response outline matches the RFP instead of somebody's best guess.
RFP Management Platform
Respond to more RFPs using the answers you already have.
ProposalOne takes an issuer's documents apart, drafts each response from your own approved answer library, routes the gaps to the people who own them, and assembles the submission package. Eight phases, one system of record, every company you operate kept straight.
Your own isolated database·Microsoft Entra SSO or magic link·AI included at every tier
8
Phase workflow, gated
1:1
Database per customer
5
Seats included per entity
$0
AI add-ons, ever
The workflow
From "we should bid this" to a filed submission.
Every RFP moves through the same eight phases, and a phase won't close until its work is actually done. Nobody has to remember what happens next, and nothing gets submitted with a section still open.
1
Intake
Email or upload
2
Cover Sheet
Key dates & terms
3
Go / No-Go
Recorded decision
4
Auto-Fill
Drafted from your repo
5
Team Setup
Owners per section
6
Review
SME & approval
7
Submit
Document & package
8
Archive
Filed & searchable
What you get
Built for the parts of an RFP nobody enjoys.
Drafted from your own words
Auto-Fill matches each question against your approved answer repository first, then uses Claude to adapt the closest answers to what was actually asked. Every draft shows its confidence and its source.
Gaps routed to owners
Unanswered sections go to the department that owns them. Subject-matter experts see only their queue, reviewers see what's waiting on them, and the notification schedule does the nagging.
A repository that compounds
Good answers get promoted back into the repository after review, tagged and department-owned. The tenth RFP is materially easier than the first, because it is answering with the first nine.
Multi-company by design
Bid as several operating entities from one workspace, each with its own companies, customers, service types and filing structure — with seats pooled across all of them.
Your data, your database
Every customer runs on a dedicated Postgres database — not a shared table with a tenant column. Competitive pricing and win themes never share a row with anyone else's.
The math
Most of the work is answering the same questions again.
These are industry benchmarks, not our results — but they are the reason ProposalOne is built the way it is. The expensive part of an RFP is rarely the thinking. It is re-typing what your team already knows, chasing the people who know it, and paying senior salaries to do both.
33 hrs
Average time per response
Industry average across proposal teams, down from 35 the prior year. Loopio 2026 benchmarks
60–80%
Of questions are repeats
Share of RFP questions that restate something the team has already answered well. Iris AI benchmarks
$8–15k
Cost of one response
Direct labour and SME time on a defined-scope commercial RFP. Complex bids run far higher. Steerlab
<5 hrs
Reported with AI tooling
What teams using AI-assisted proposal software report for a full response. Their figure, not a ProposalOne guarantee. Pifini
The reuse number is the one that matters most here. If most of a bid is questions you have answered before, the fix is not drafting faster — it is never drafting twice. That is what the answer repository below is for.
The answer repository
Your best answer, found in seconds.
Most RFP questions are variations on questions you have already answered well. ProposalOne keeps those answers in one reviewed, tagged, searchable repository — and reaches for them before it reaches for the model.
- Text matching first, AI second. Candidate answers are found by matching the question against your repository, then adapted to the wording the issuer used.
- Review before reuse. Answers enter the repository through a promotion queue that the owning department signs off on, so nothing self-published makes it into the next bid.
- Department ownership. Safety, Legal, HR, Operations — each answer has an owner, and their queue is theirs alone.
- Reference documents. Certificates, insurance, licences and standard attachments live alongside the answers and travel with the package.
- Ask your own history. Reports and "Ask ProposalOne" run against your data — win rates, volumes, what you promised last time.
Access & isolation
Bid data is the last thing you want in a shared table.
One database per customer
A dedicated Postgres database per customer, provisioned at signup. Isolation is the architecture, not a filter in a query.
Sign in the way you already do
Microsoft Entra ID single sign-on for your directory, or emailed sign-in links for the people who aren't in it. One email field, no wrong button.
Roles that match the room
Admin, response lead, SME, requestor, reviewer, approver — plus per-person capability grants when someone needs exactly one more thing.
Everything is on the record
Phase changes, approvals, promotions and submissions are all logged against a person and a time, per RFP.
Pricing
Priced by entity, not by headcount.
A platform fee per operating entity, with five producer seats included for each one and pooled across your whole workspace. Reviewers, approvers and the person who forwards you the RFP are free.
Starter
One entity
$499/mo
5 seats · 200-answer repository
Business
Up to 3 entities
$1,200/mo
5 seats each · unlimited repository
Multi-Entity
Up to 8 entities
$2,200/mo
5 seats each · unlimited repository
Enterprise
Unlimited entities
Custom
Negotiated seats · Opus models
See it against a real RFP.
Start a trial on your own private workspace, or walk through one of your recent bids with us and we'll show you where the hours actually go.