Background

There is only one reason for new enterprise software failing, and that is because it doesn’t meet expectations.

There is only one reason why software doesn’t meet expectations and that is because buyers make assumptions about the software they later find out are false.

If a company buys software knowing it does A to Z but doesn’t do X, there is no problem. They accepted that compromise when they purchased the software. But if they buy the software thinking it does X and later find out it does not, the software fails to meet that expectation. Too many unmet expectations, and you have a disaster on your hands.

Wayferry solves this problem by documenting these assumptions as detailed requirements. When the buyer looks at the gap analysis they can see exactly what compromises they are making if they purchase your software.

Our approach means there are lots of requirements on Wayferry RFPs. The aim of this page is to help you respond to those requirements as fast as possible.

Reuse you work

We realize responding to an RFP is significant work.

Avoid adding comments to your responses

When responding to a requirement you:

• Rate how well your software meets the requirement in the “Rating” field, e.g. “Fully meets”, “Partly meets”, “Does not meet”, etc.
• Enter HOW your software meets the requirement in the “How is the requirement met?” field, e.g. “Base product”, “With 3rd party product”, etc.

<aside> 💡 If your software “Fully meets” or “Does not meet” the requirement, the rating field says it all. DO NOT ADD COMMENTS to these responses.

</aside>

The only time you need to add comments to a product rating is:

• When the “How is the requirement met?” field is “Other vendor product” or “With 3rd part product” please add the name of the product to the comments field.
• When the rating is “Mostly meets”, “Party meets”, or “Slightly meets” you may want to qualify your answer with an explanation.

Navigate directly to the next requirement

<aside> 💡 The fastest way to respond to requirements is to go directly from one requirement to the next, without going back to the previous view.

</aside>

After responding to the first requirement use the [Save & verify] button (2 below) to save your response and stay on the current requirement (rather than returning to the previous view),

Then click on the next unrated requirement in the list (3 below). The next requirement can be in the sibling list or the child list. Repeat this for each unrated requirement on the list and use the [Save, verify & close] button (4 below) until you have responded to all of them. Each time you will return to the first requirement. When you have rated all of them and you are back on the first requirement click the [Cancel] button to return to the previous view.