A great thing about ROI Hunter is that we build our own product. We started from scratch and everyone in the company is continuously shaping the platform we build and the experience our clients have.
What we value is drive and genuine care for our clients. You can read more here
That is why instead of receiving a pixel-perfect design, the developers are paired with designers to iterate and build together. And instead of exact feature specifications, they are presented with the business context and the boundaries given by product managers, always with enough space for interpretation and creative thinking.
<aside> 💡 A big portion of how we operate is inspired by Shape Up framework used at Basecamp. Bonus points for you if you're already familiar with it!
</aside>
The product and engineering departments work in cycles of 6+2 weeks in sort of a dual-track system. During the six weeks the engineering teams focus on building and delivering, while the product team research topics for the next cycle.
The remaining two weeks are a cooldown. There are no plans for this period and the developers are free to work on whatever they feel is important. During that time we take a look at what was delivered, discuss the inputs from the product team, agree on the next steps and commit to another six weeks of building.
The job of our product managers is finding ways of making ROI Hunter a better product. They talk to our clients, experiment, dig in the data and eventually come up with their ideas of what we should build.
Those ideas are written down in a brief document. Describing the business context, the problem, the key elements of the solution and few other things.
And this is where developers come to play. We usually have some idea of who could work on what, based on their field of expertise. So we ask those devs to give their feedback on the proposal. They are usually the smartest people in the room and their questions and notes are super valuable.
Only when we feel that we've sorted everything out and there are no surprises or blank spots, we proceed to actually commiting. The CEO and other stakeholders greenlight the plans for the upcoming six weeks and we get to work.
The core of building things is writing code - no surprise there 😀