Evolutions

As the founder of Requirement Yogi, I’m always amazed at the speed of loading a new requirement in our app. You click on the treeview, the requirement is here. It is instant. No spinner, no loading time. It makes a world of difference. End-users care, even if license purchasers are insensitive to the everyday-UX criteria.

This is what we’re born to do. We polish a UX that end-users love, estimating our success on the altar of our users’ speed and efficiency at work. We’re making people productive by caring about keyboard navigation, loading times, etc.

Of course, on the Atlassian platform… our speed and flexibility are naturally linked to Atlassian’s ecosystem.

We’re announcing it now, so that customers can renew within 60 days and still benefit from the old pricing. In fact, they renew for 2 years within 60 days.

It’s also important to build accurate price expectations for new customers, so they don’t have unexpected expenses later on.

Requirement Yogi is not expensive: Going from $1400 to $1820 for a team of 100 people for an entire year, while spending $18k on Atlassian, remains a small expense for the right product. We’re writing these justifications because we take our customers' expenses very seriously.

We’ve noticed that customers purchase testing products at the same time as requirement management. It can be a significant expense: The two most popular testing plugins on the Marketplace are 7 times more expensive than Requirement Yogi for Confluence. We’re building testing inside our app so that customers can avoid extended costs, in addition to our integrations with Xray and Zephyr.

Please fill in this Google Form to apply to the Testing experiment group.

Let’s talk about the elephant in the room: Google Docs. The end goal of the standalone app is to be able to integrate with other document management platforms. Is Google Docs the best first platform to integrate with?

Please fill in this Google Form to apply to the Standalone experiment group.

Our plan is to deliver features faster on the standalone app. It’s an engineering decision. It’s a governance decision. Practically every blocking bug for our customers is due to platform choices outside our control.

We’ve heard that customers value the in-app experience of Jira and Confluence. Our plan^[1] involves:

• Keeping the in-app experience that customers have today,

• Decoupling our software from Atlassian’s constraints, so we can achieve a best-in-class design,

• Opening the platform to non-Atlassian users, with its own payment platform (while keeping the paid-through-Atlassian possibility), especially enabling the collaboration with clients,

• Open the API so customers can declare their own documents. We hope to see open-source implementations of JUnit or source-code links to requirements, and perhaps integration with industrial tools.

We’ll be working with a few select customers for the initial steps, please declare your interest.

Atlassian has announced tremendous changes this year. We’re of the opinion^[2] that Atlassian has basically pivoted, they’re outputting results at the speed of AI and the quality of AI. All vendors face the same changes, and the rate of changes has been higher for a year. In the end, it makes maintaining apps more expensive. This is the price of operating on the Atlassian Cloud.

We’re passing real costs to customers and asking both employees and customers to contribute to the pivot. In the meantime, we’re offering an open door in the future to migrate to other platforms, which will compensate price-sensitive customers.