|
Wayferry |
External Consultants |
Software Resellers |
Internal Team |
Specialize exclusively in minimizing enterprise software purchase risks To avoid bias and conflict of interest we do not sell, implement or support software. Rather, we manage the entire purchase process from idea to execution, and ensure that, once in production, the new software meets user, management and investor expectations. |
Yes |
No |
No |
No |
Unbiased At Wayferry we are paid by our clients, and never accept payments from vendors when the software is purchased. Other companies only recommend software they sell or implement, which means you get what they want to sell, not what you need to buy! |
Yes |
No [1] |
No [1] |
Yes [2] |
Purchase software aligned with business vision, goals and strategy We start a project by working with your team to define the ideal future state of your new software. Everything we do is designed to get your software delivering what you need to achieve your business goals. |
Yes |
No |
No |
Very rarely |
Wayferry Navigator software Our proprietary cloud application that manages the entire software purchase, saving you time and money. |
Yes |
No |
No |
No |
Objective, data-driven selection Our analysis objectively measures how well potential software products meet your particular needs. Others offer subjective opinions and are limited to what they know. |
Yes |
Sometimes |
No |
Sometimes |
Selection process designed to capture implementation information Avoid the unnecessary costs and delays of the implementation team repeating this work. |
Yes |
No |
No |
No |
Requirements library
- Our library of thousands of requirements shaves months off software selection projects.
- For international clients, requirements can be viewed in 20 languages.
- Well written requirements complete with examples and reasons remove ambiguity which reduces the risks of software being misrepresented in the RFP.
- Requirements are organized in a hierarchical tree structure. Save time by only going down to the level of detail you need. Compare this to typical lists of requirements in spreadsheets.
|
Yes |
Sometimes |
No |
No |
Discover unknown requirements Our goal is finding no significant new requirements during implementation. It's requirements that should have been found earlier that cause implementation schedules to slip, costs to increase and business disruption on going live. |
Yes |
No |
No |
No |
Weight requirements You decide what matters most to your organization, and measure potential software products against this standard. |
Yes |
Usually |
Usually |
Sometimes |
Traceability matrix built in Trace every requirement back to who wants it, why they want it, and how important it is to them. This information is referenced during implementation and User Acceptance Tests. Traceability is also very important to companies in regulated industries. |
Yes |
Sometimes |
No |
No |
Nurture user buy-in
The Wayferry process is designed so employees take ownership of the purchasing decision. And when they know their needs were factored into that decision, they can't wait to start using the new software! |
Yes |
No |
No |
No |
Actively manage user expectations All software purchases have compromises. When expectations are matched with what the software provides, users are not disappointed. |
Yes |
No |
No |
No |
Scope check Verify that your requirements are matched to software features the market can provide. All software systems have functional boundaries. Have the tools to decide what functionality should be inside the system, and what should be in other systems. |
Yes |
No |
No |
No |
Verify RFP Design demo scripts to verify functionality claimed on the RFP. After the demo verify further selected RFP responses to ensure the software was not misrepresented. |
Yes |
No |
No |
No |
Reference checks We use our reference call scripts to help you check references. |
Yes |
Sometimes |
No |
Yes |
Implementation project WBS export Our hierarchical requirements are exported in WBS (Work Breakdown Structure) format as the first draft of the implementation project plan. This keeps the project on schedule and minimizes scope creep risks. |
Yes |
No |
No |
No |
UATs – User Acceptance Tests Our requirements are used for UATs. When detailed tests are passed, go-live risks are minimized and the software is ready for a successful launch into production. |
Yes |
No |
No |
Yes |
Maximize software value Purchase software to maximize the value that flows from the benefits of using the new software. |
Yes |
No |
No |
No |