| Role | Create | Review | Match | Accept | Respond | Compare |
|---|---|---|---|---|---|---|
| Buyer | Writes brief | Reviews changes | Sets priorities | Reviews access | Compares answers | Chooses next step |
| Consultant | Edits in scope | Supports review | Reviews fit | Supports buyer | Reviews answers | Prepares handover |
| Finlane | Structures | Reviews brief | Matches categories | Controls access | Keeps responses private | Keeps record |
| Provider | — | — | Reviews brief | Accepts or declines | Answers rows | — |
Illustrative example.
How it works
1. Create a structured brief
Guided template
Build the RFP section by section, mark requirements as want to have or optional, and add the deadline, context, files and links.
AI RFP advisor
Use a staged conversation to capture the company context, use case and product needs, then hand the result into the same editable RFP format.
Learn moreConsultant-assisted
An invited consultant can continue work in the client's context when their organisation, project or RFP access covers it.
Quality control
2. Review before the market sees it
Card issuing processor
Illustrative example.
Relevant reach
3. Match without revealing the buyer
Category eligibility
The RFP is visible only to approved providers whose assigned categories overlap the brief.
Capability fit
Confirmed provider capabilities are compared with weighted want-to-have and optional requirements to explain fit and surface gaps.
Incumbent blocking
A buyer can exclude a specific incumbent provider from a specific RFP before distribution.
Gaps to review
- • Local settlement coverage
- • Offline card controls
Illustrative example.
Controlled disclosure
4. Accept before identities are shared
Before acceptance
Use case, region and requirements remain visible.
Accepted brief
Company name · Contact
2 files · 1 link
Use case, region and requirements remain visible.
Illustrative example.
Structured answers
5. Build a private response
Structured coverage
The provider answers the same requirements the buyer asked, using full, partial or not-offered coverage with supporting notes.
Evidence and contacts
Attachments, links, company fit, a response summary and mandatory contact details travel with the response.
Autosave and AI assist
Drafts autosave. Optional AI assistance maps requirements to confirmed capabilities, fills only empty fields and still requires provider review.
Buyer requirement
Real-time card controls
Confirmed capability
Controls supported
Suggested coverage
Illustrative example.
Comparable evidence
6. Review, clarify and hand over
| Requirement | Provider A | Provider B | Provider C |
|---|---|---|---|
| Virtual card issuing | Full | Full | Partial |
| EEA programme support | Full | Partial | Full |
| Real-time controls | Partial | Full | Not offered |
| Migration support | Full | Needs your answer | Partial |
Illustrative example.
Visibility
Who sees what, stage by stage
| Party | Before acceptance | During response | After submission |
|---|---|---|---|
| Matched provider | Sees brief | Doesn’t see identity | Sees accepted buyer details |
| Buyer | Sees own draft | Sees response status | Sees submitted responses |
| Consultant | Sees named scope | Sees submitted responses | Doesn’t see unrelated work |
| Other providers | Doesn’t see brief | Doesn’t see responses | Doesn’t see messages |
Illustrative example.
How it works
What stays outside Finlane
Contracting
The buyer negotiates and signs directly with the selected provider.
Due diligence
Provider approval and structured evidence support evaluation but do not replace legal, regulatory, technical or commercial checks.
The final decision
Finlane structures and documents the market process; the buyer remains responsible for selection.
Useful details