Vollou: Empowering User Experience of a Music Royalty Platform
How a royalty-tracking AI platform for musicians engaged a Frontend Engineer.
Challenge
Vollou sells against a problem most people have never heard of. Licence fees get collected from venues and festivals every night, but when nobody records what was actually played, the money never finds the people who made the music. Vollou closes that gap with recognition technology and automated reporting into performing rights organisations. Explaining it is a marketing problem of an unusual shape: the site has to establish that a gap exists at all, then describe a solution spanning phone apps, track recognition and submission formats, and do it for two audiences who share nothing. Rights organisations are institutions that move slowly and decide on evidence. Artists want to know whether they are owed money. Both arrive on the same homepage.
The tech stack was a React rather than a CMS builder. Built by engineers, which suits a technical team and brings its own problem: marketing pages rendered in the browser have to be made fast and findable. The request was for one frontend engineer: React and TypeScript with real depth, a component structure the team could live with afterwards, responsive layout, performance work, the search considerations a client-rendered site demands, and the demo-request flow wired through to wherever those leads are handled. Vollou’s two founders include a technical one, so the engineer joined an established direction rather than setting one.
Most React engineers build applications. Far fewer have built marketing sites in React, where the measures are load time, indexing and conversion rather than state management, and where a page that renders beautifully but arrives late has already failed. Shortlisting went to that narrower group. Timing also leaves no room to learn a project, so candidates needed evidence of joining an existing codebase and being useful inside the first day. The CEO and the CTO interviewed together, and the engagement was confirmed 36 hours after the request opened.
Outcome
Not every engagement is a team. This was one engineer, at a company that already had technical leadership and a clear view of what needed doing. The measure here is what the month did not have to include: no search, no onboarding overhead, and no permanent role created.
- One request, matched in 36 hours.
- The company’s main site and demo funnel, serving two kinds of buyer who need entirely different things from the same pages.
- Added under a technical co-founder, so direction stayed in-house and the engagement was purely capacity.
- One month of engagement with regular releases of a live site.
A Strategic, Multi-Phase Hiring Approach
Phase: Request
A single request for a frontend engineer on React, scoped to the marketing site and its demo-request flow.
Phase: Matching
Shortlisting went to 3 React engineers who had built marketing sites rather than only applications, where load time, indexing and conversion are the measures, and who had joined existing codebases and become productive inside the first week.
Phase: Interviews
The CEO and the CTO interviewed all of them together and agreed on 1, with the match confirmed 36 hours after the request opened.
Phase: Engagement
Part-time workload and an hour cap was set before the start, with the daily time tracker, and monthly reports with hour commitments.
Phase: Support
Throughout the month of site updates, extra hours were requested and approved from the account.
