Choose a treasury system on evidence, not on who demoed best
Most corporates run a treasury system selection on spreadsheets and email. The requirements are rarely grounded in how the treasury actually works today, the answers cannot be compared like for like, and the shortlist comes down to a good demonstration. TenderEval is the structured version: build the requirements, invite the bidders, collect and compare the responses, score them against a rubric you published first, and defend the decision afterwards.
How a selection runs
- 01
Describe the treasury you have now
Entities, banks and accounts, payment and transaction volumes, how long a cash position takes to produce, how many hours reconciliation costs each month. Answered per region or legal entity rather than once for the whole group, and it decides which areas are in scope at all.
- 02
Build the requirements
From a library of 672 questions across 40 functional areas of corporate treasury, or your own. Switch an area off and its questions are never put to bidders and its weight is redistributed across what remains, rather than quietly penalising everybody equally.
- 03
Invite the bidders
Each bidder sees only its own workspace and a completeness bar for the questions that actually apply to it. They state how each requirement is met, propose workarounds with effort and cost, and price into your cost categories rather than their own.
- 04
Score against a rubric set beforehand
Rank what matters and the weights follow, because people are poor at typing percentages that sum to a hundred and then standing behind them. Scores run 0 to 10 with a written meaning at each band. Price is reported beside the score and never blended into it.
- 05
Defend the decision afterwards
Every change to a score, a weight, a scope decision or a stage outcome is written to a log that cannot be edited or deleted, with who made it and when. Weight changes made after the RFP was issued are surfaced separately, because that is the first thing a challenge looks for.
The field narrows in stages
Writing a three hundred question RFP before you know who can credibly serve you wastes everybody's time. Each stage gates entry to the next, a bidder cut at one stage cannot see the next, and scores from an earlier stage are kept for the record but never move a later stage's ranking.
Stage 1
RFI
A short capability screen. Its answers shape which areas the RFP asks about in depth.
Stage 2
RFP
The detailed requirement set, weighted and scored. The bulk of the evidence.
Stage 3
Demo
Scripted demonstrations against your own scenarios, re-scored with the reasoning recorded.
Stage 4
Best and final
Final commercial and contractual positions from whoever is still in.
What a bidder never sees
Enforced in the database rather than by hiding buttons, so it holds even for a bidder who asks for the underlying data directly. Weights are withheld deliberately: a bidder who knows that reporting carries fifteen per cent and treasury transactions two writes to the weighting rather than to the requirement.
- Any other bidder's answers, prices or proposals
- That any other bidder exists, or how many are bidding
- Every weight, at all three levels
- Any score, comment or ranking
- Internal notes, and what a referee said about them
Each client's data sits in its own separate database, and a workspace lives at an address that is a random code rather than the client's name, so nobody can confirm who is running a selection by guessing.
Already have a workspace
Follow the link you were sent. That link is the normal way in and these addresses are not meant to be typed or remembered. If you still have the short code from the front of it, the box at the top of this page takes you there. If you do not, ask whoever invited you rather than guessing: we cannot tell you whether an address is real, and nothing here will.
Ask about access
The portal is used by invitation, so there is no sign up. Tell us who you are and what you are trying to do and we will come back to you. Nothing you write here is stored: it is sent to us as a message and that is all.
Prefer email? Write to hello@elevaition.solutions.