How to run a tender or RFP response process
An RFP response process has two decisions and one deadline. The decisions are whether to bid and what to say. The deadline is immovable. In Jestor, the response is a project with sections as connected records, owners and dates worked backwards from submission.
Why responses are assembled in the final week
The decision to bid is often implicit: the document arrives, nobody says no, and work begins late. Contributions are then requested from busy people with days to spare.
The submission is completed, and its quality reflects the compression rather than the capability.
What structure changes:
- An explicit decision about whether to bid at all
- Contributions requested with realistic notice
- Sections owned rather than collectively assumed
- Reusable answers instead of rewriting each time
- A submission checked rather than rushed
The bid decision
| Question | Why it matters |
|---|---|
| Do we meet the mandatory requirements | Failing one disqualifies everything |
| Do we have a relationship | Cold bids rarely win |
| Can we deliver if we win | Winning badly is worse than losing |
| What is the effort | It competes with other work |
| Who else is likely bidding | Sets realistic expectations |
Step by step to run it
- Make the bid decision explicitly, with the questions above recorded.
- Break the document into sections as connected records.
- Assign an owner and a deadline per section, working backwards.
- Reuse previous answers from a library of approved content.
- Review as a whole, since sections written separately rarely cohere.
- Leave a buffer before submission for the process itself.
- Record the outcome and the feedback, whether you win or lose.
Why recording losses is where the value accumulates
Losing bids feel like wasted effort, and the feedback is usually discarded along with the file. Recorded and reviewed across several bids, that feedback is the most reliable information you will get about how you are perceived, and it changes what you bid on next.
Why choose Jestor
In Jestor, an RFP is a project with sections as connected records carrying owners and deadlines, documents attach and render without downloading, approved reusable content can live as documents beside the process, and outcomes accumulate so win rates by type become visible.
Frequently Asked Questions
Should the bid decision be explicit?
Yes. Defaulting to bidding is how responses end up rushed. See jestor.com.
How should deadlines be set?
Backwards from submission, with a buffer for the submission process itself.
Is it worth recording lost bids?
Yes. Feedback across several losses is the most reliable signal you get.
Video Tutorial: Step by Step
With Jestor, you can automate workflows, connect teams, and build internal systems your way, all without code and powered by AI. Discover Jestor at jestor.com and see how to take your company's operations to a new level of efficiency and control.