Only in SEQUESTO · Any process
Your bid process, set up your way. No code, no waiting.
SEQUESTO adapts to each team's own bid process: custom stages, fields, document types and workflows, without code. A public tender, a DDQ and a security questionnaire can each run the way your team already runs them.
A bid tool should take the shape of your team, not the other way round. When your process changes, you tell James and nothing waits for a release.
YOUR PROCESS
Why does my team have to change its process for a tool?
Most bid tools come with their own stages, their own fields and their own idea of what a bid is.
01
Boxes set by the vendor
Your team fits its process into the vendor's boxes, or waits months for the vendor to add a field.
02
Custom still means waiting
Even "custom" often means a project run by the vendor's own team, with weeks before anything changes.
03
Built around your process
SEQUESTO adapts to the team's process instead. You decide which stages a bid goes through, which fields every bid carries, what a requirement or a clarification question looks like, and what James, SEQUESTO's AI bid agent, does at each step. You change it yourself, in the product, when your process changes. Simple on day one, as deep as your team needs.
Before / With SEQUESTO
Before
- The vendor's stages, renamed in a spreadsheet on the side
- A ticket to the vendor for every new field
- One set-up for every kind of bid
- AI prompts kept in someone's notes
With SEQUESTO
- Your own stages, as a status field
- Add the field yourself, in the product
- A set-up per bid type
- Shared workflows James runs for the whole team
BID FIELDS
Which fields can I add to a bid?
Any field your bid register needs. Each bid carries the fields your team defines, for example:
01
Value, deadline and period
Contract value in euros, and the win probability your bid director estimates.
Submission deadline, and the contract period from start to end.
02
Sector, lots and stages
Sector, country and lots, such as "Rail", "Belgium" and "Lots 2 and 3".
Your bid stages, from "Qualifying" to "Submitted", "Won" or "Lost".
03
People and tick-boxes
Bid manager, sales lead and legal reviewer, as people from your team.
"Site visit required" or "Framework agreement", ticked or not.
04
Portal link and dashboards
The buyer's portal link and the tender reference.
The same fields feed the dashboards you report on across your bids.
TEMPLATES
Can I decide how requirements and questions look?
Yes. A tender pack is full of things your team handles one by one: requirements, questions, clarification questions, risks, red flags.
01
One template for each item
In SEQUESTO you decide what each item looks like, with its own template.
02
James writes in your template
When James extracts items from the tender, each one is written in your template, with your headings and your fields.
03
Different fields for each
A requirement can carry "Source page", "Owner" and "Compliance", while a clarification question for the nota van inlichtingen carries "Question to the buyer" and "Reason". You decide.
SET-UPS
One set-up for each type of bid
A set-up is everything a new bid starts with, in one go:
01
Folder structure
Folders such as tender documents, clarifications, drafts and final files.
02
Fields
Information the bid carries, such as contract value, deadline and stage.
03
Your templates
They cover requirements, questions and clarification questions.
04
Your workflows
They are the step-by-step instructions James runs.
Start a new public tender from your public-tender set-up, and everything is in place on day one. A public tender (aanbesteding, Ausschreibung, appel d'offres) needs different folders and fields from a DDQ or a security questionnaire, so keep one set-up for each.
WORKFLOWS
Workflows: teach James your way of doing things
A workflow is a reusable, multi-step instruction for James that your team writes and shares. For example: "Analyse a tender and write our bid/no-bid brief", with the steps your bid director expects: read the full tender pack, list scope, key dates and award criteria, flag the risks against our criteria, fill the bid/no-bid fields.
01
The same structure for everyone
Anyone on the team runs the same workflow and gets the same structure.
02
Edit it, no developer
When the process changes, you edit the workflow. No developer involved.
An example: one company, three set-ups
A software company answers French and Belgian public tenders, private RFPs and security questionnaires.
Public tender (appel d'offres)
Folders for the DCE, the CCTP (technical specifications), the mémoire technique and the final submission; templates for requirements and clarification questions; fields for contract value, award date and lot.
Security questionnaire
A single folder for the buyer's Excel; one template, "Question"; fields for buyer, deadline and owner.
Private RFP
A status field with the team's own stages, and a workflow that drafts the executive summary from past bids.
How they were built
For public tenders and private RFPs, the bid manager explained to James how the team already worked, and James built both set-ups. For security questionnaires they had no process yet, so they started from the ready-made set-up and adapted it.
FOUR STEPS
How it works
You already have a bid process:
01
Brief James
Explain to James how your team works, in plain language, as you would brief a new colleague: how you file a bid, what you track, what a requirement or a question looks like, and the steps you follow.
02
A set-up built for you
James builds your set-up for you: the folder structure, the fields, the templates and the workflows.
03
Review the result
Check it and adjust, by asking James or by changing it yourself.
04
Use it on every bid
Start every new bid from your set-up. When your process changes, tell James. No release to wait for, no vendor ticket.
No process yet? Start from a ready-made set-up instead, as explained below.
BEST PRACTICE
No process yet? Start from best practice.
Not every team has a written bid process, and that's fine. SEQUESTO comes with ready-made set-ups, built on how experienced bid teams work: a simple tender, a complex tender with lots, a questionnaire, forms to fill, a public tender, a private RFP, a security questionnaire, a DDQ and more.
01
What each one includes
Each one comes with a proven folder structure, the fields worth tracking, templates for requirements and questions, and the workflows James runs for that type of bid, such as the bid/no-bid brief or the check of every requirement before submission.
02
Start close, then adapt
Pick the one closest to your bid, use it as it is, and change it as your team learns what works.
03
Or just tell James
Explain to James how you work, and he sets it up for you.
See the full list in the workflow library.
Related features
Workflow library
Ready-made set-ups for public tenders, private RFPs, security questionnaires, DDQs and more. Copy one into your workspace in a click, then make it yours.
Learn more →Your reports, in your format
The board pack, the monthly pipeline e-mail, the win rate per business unit: build them inside SEQUESTO. From then on there is nothing to maintain. Every number stays current, one click from the bids behind it.
Learn more →James, your AI bid agent
From the first read of the tender pack to the final file, James, SEQUESTO's AI bid agent, takes work off the bid manager's plate: summaries, drafts, contracts, forms, task assignments and follow-ups. You direct, he does the work, several tasks at once.
Learn more →Requirements & clarifications
James, SEQUESTO's AI bid agent, turns the buyer's requirements and questions into structured items built from your own templates. Unclear points become clarification questions you can send before the buyer's Q&A deadline.
Learn more →Analyse & qualify
James, SEQUESTO's AI bid agent, reads every file in the tender pack and tells you what is asked, by when, how it is scored and where the risks are. Then he helps you qualify it: is this one worth your team's next three weeks? The output follows your team's own format, so it fits the way you already decide.
Learn more →Frequently asked questions
Yes. SEQUESTO adapts to each team's own bid process: custom stages, fields, document types and workflows, without code. You set up your stages as a status field, add the fields your bid register tracks, set up your templates and write workflows for James. You change all of it yourself, in the product.
No. Fields, templates, folder structures, set-ups and workflows are all created and edited in the product by your team. There is no code and no release to wait for. When your bid process changes, an admin on your team updates the set-up the same day.
Whatever your bid register tracks today: contract value, deadline, contract period, sector, country, lots, stage, bid manager, win probability, buyer's portal link. Every field can be used in the dashboards you build across your bids.
Yes. Keep a separate template for each bid type, with its own folders, fields and templates. A public tender, a DDQ and a security questionnaire can each start from the set-up that suits them. Teams that answer different kinds of bids do not have to squeeze them into one process.
A workflow is a reusable, multi-step instruction for James, SEQUESTO's AI bid agent. Your team writes it once and shares it. For example: "Analyse a tender and write our bid/no-bid brief." Everyone who runs it gets the same steps and the same structure, so the quality of the work does not depend on who wrote the prompt.
Yes, built around your way of deciding. Your team writes its bid/no-bid brief once as a workflow, and records the outcome in fields such as "Bid decision" and "Decision date". You keep the decision process you already have, and James runs it on every tender.
Start from the workflow library. It holds ready-made set-ups for common bid types. Preview what a set-up contains, import it, then change it to match how your team works.