Start a conversation
Trevanna Tracks · Product engineering

From scattered licensing records to a shared software platform.

Xivic assessed an inherited MVP, rebuilt the application and helped Trevanna Tracks turn product ideas into a development plan.

Context
Music licensing for content production
Xivic’s role
Product planning · Engineering · UX · QA
Story milestones
Client review, 2020 · Product release, 2022
The client’s challenge

Bring the songs and their records together.

In her 2020 review, founder Jennifer Freed described licensing teams working across disconnected spreadsheets and file storage. She wanted a shared place for song information, licensing documents and payment records.

Xivic began by assessing the previous vendor’s MVP and resolving bugs. The team then rebuilt the platform and continued adding functionality.

The client’s perspective · June 5, 2020

“they helped me learn how to run a software company”

Jennifer FreedFounder & CEO, Trevanna Tracks · Role at review date
Read the full client interview on Clutch

Excerpt from an edited phone interview. This review describes the partnership in 2020.

Beyond the build

Help the founder shape the product.

Freed also described learning to organize feature ideas and plan development with Xivic. Architecture, interface guidance and engineering were part of a broader product partnership.

A later delivery example · 2022

A licensing exception should not erase a payment obligation.

The later work shows how detailed business rules became product behavior. Xivic helped Trevanna Tracks separate whether a license was required from whether a fee was due.

The changes connected the interface, track data, imports and document workflow. The Q3 2022 business review records the relevant release as live.

Two decisions. Distinct document rules.

No license required; a fee still applies
Keep the payment workflow available.
No license and no fee required
Disable payment documents.

Quotes and confirmations remain available under the exception rules.

This delivery is documented separately from the 2020 client review.

Inside the same release

Carry the rules into everyday work.

  • Explain the exception.

    Teams can record the reason and see it in the track summary when no fee is required.

  • Classify tracks consistently.

    Track types are available in list management and CSV imports, connecting classification to the ways people manage the data.

  • Bring frequently used information forward.

    People can favorite media-list blocks so the blocks they return to appear at the top.

What this work demonstrates

Product thinking, carried through to released software.

The founder’s account explains the partnership behind the platform. The later release makes the engineering contribution tangible: separate licensing and payment rules, supported by track classification and media-list favorites.

Explore custom software and applications

What does your next release need to handle?

Talk with us about the rules, exceptions and connected systems behind the work.