Lume
A new digital format for albums.
- Brand, UX and UI by Daylight. We built to it.
- Architecture, delivery plan and trade-offs as fractional CTO
- The platform, store and apps for iOS, Android and web, on the fixed date
- Payments, partners, release process and monitoring
- 17 July 2026, trading with paying customers
The client
Lume is an early-stage consumer media startup with an ambitious product and a lean team. A Lume is the album plus everything the artist chooses to put around it: alternate versions, live recordings, handwritten lyrics, photography, film. Fans buy it once and keep it, online or off, and 80% of net revenue goes to the artist and their rights partners.
They needed senior engineering leadership and the engineers to go with it: a team to take the platform from build to launch, without the cost and commitment of a full-time executive hire or an in-house engineering department.
The challenge
The launch date was fixed. The product was still evolving. The founders were learning from customers and refining what they wanted to build, and engineering had to keep pace without losing the date.
A consumer launch leaves little margin. Payments have to work, the experience has to hold up across iOS, Android and the web, and the platform has to carry real customers from the first day. The risk in that position is building fast in the wrong direction, or stalling while decisions settle.
How we worked
Voidforge embedded as Lume's engineering lead and engineering team, accountable for the technical build from planning through to launch. Brand, UX and UI came from Daylight; we set the technical direction and wrote the code. It is the same approach we bring to every large build.
- Leadership from day one
- We were the senior technical voice in the business: owning the architecture, the delivery plan and the trade-offs, and giving the founders a straight answer on what is possible, what it costs and how long it takes. The same people then built it, so there was no gap between the plan and the code.
- Decisions in the right order
- When a product is still in flight, sequencing matters. We locked in the decisions that are expensive to change later and left the rest until the business knew more, so the team kept shipping and the early work stayed useful.
- Architecture that can absorb change
- Solid enough to carry paying customers, flexible enough to evolve after launch. Purchased albums have to play offline, on a phone, years from now. That is a licensing, media and distribution problem as much as an app problem.
- Choosing the right partners
- Payments, hosting, analytics and media all lean on third-party platforms. We assessed the options against Lume's needs, budget and growth plans, and avoided lock-in that would limit them later.
- Delivery and release discipline
- Infrastructure, release process and monitoring in place so the team could ship often and with confidence. Small teams move faster when deployment is routine and problems are caught early.
- Evidence over instinct
- We tested research findings, questioned assumptions and made sure the team built what fans actually value. Engineering time is expensive, and we treat it that way.
The outcome
Lume launched on iOS, Android and the web on 17 July 2026 and is trading with paying customers, with a launch roster of established New Zealand artists and reissues.
Lume had senior technical leadership and a senior engineering team through the most demanding phase of the business, at a fraction of the cost of hiring both, and a platform built to keep evolving after launch.