Built for the portals UK buyers use
TenderSwift drives a real browser, so it works with the portals bid teams use every day, including Delta eSourcing, In-Tend, ProContract, Jaggaer, Atamis, EU-Supply and Proactis.
The right login for each portal
You don't pick a login for each job. When a portal asks it to sign in, TenderSwift matches the site's address to your saved logins and uses the one that fits. Passwords are encrypted and never shown again after you save them.
Two-step verification
Many portals ask for an authenticator code. TenderSwift can keep its own authenticator for a login, so nobody has to read a code off their phone. Where a portal needs a person, such as a code sent by email, it pauses and asks your team.
Online questionnaires
Some buyers ask the questions on the portal itself rather than in a document. "Find questions to answer" collects every question with its guidance, word limit and weighting into a spreadsheet, which TenderSwift then answers like any other document.
It never submits
The portal agent downloads documents and reads questions. It doesn't submit responses, send messages to the buyer, accept contracts or change account settings.
Frequently asked questions
Will it submit my bid on the portal?
No. It downloads documents and reads the questions. Your team submits.
How are our passwords kept?
They're encrypted when you save them and never shown again. They're only decrypted for the run that needs them.
What if the portal asks for a one-time code?
TenderSwift uses its own authenticator for that login where the portal allows it. Otherwise it pauses and asks your team for the code.