EIGHT32 built Lumos Throughline with Serras in 25 days.

Lumos Throughline plans a month of marketing for one organization and its staff. One person at EIGHT32, a Serras development partner, directed Symphony from the first day to the last release.

October 1, 2026 · Serras

Book a demo

July to August 202625 days

Jul 11Setup, discovery, analysis, plan

Jul 12Design approved, build begins

Jul 15First deployment

Jul 29Running at its own address

Aug 5Last release

Build: 211 tasks in 19 runs

The build began 23 hours after setup. A person approved the design before it began.

What it is

A growing organization had no single place to run its marketing across its staff. Lumos Throughline gives it one.

The product turns what the organization knows, its content library and its priorities for the season into a month of promotions, a content calendar and a daily work list for each person. It drafts images and video with AI, and a person reviews and approves each piece. It does not publish for you.

It is a web app for desktop and phone browsers, with five roles: admin, strategist, content producer, reviewer and viewer.

Where to find it

Lumos Throughline is an internal tool, so its address opens a sign-in page. Accounts are by invitation.

The build at a glance

	Lumos Throughline
What was built	A web app for desktop and phone browsers
Built by	EIGHT32, a Serras development partner
Team	One person directing Symphony, in Claude Code
Setup to its own address	18 days, July 11 to July 29, 2026
Setup to the last release	25 days, July 11 to August 5, 2026
Setup to the start of the build	23 hours
Brand	An existing brand, by BetterOff, applied to the product
Approved before the build	76 requirements and 280 acceptance criteria
Designed before the build	53 screens in 89 mockups, with 63 shared components
Planned checks	280, one for each acceptance criterion
Build	211 tasks in 19 runs; 206 complete and 5 still open
Last recorded test run	1,554 server tests passed, July 29, 2026
Decisions made by a person	20 before the build, and 8 more gates during it

How it ran

The same five phases as every Serras delivery.

Shape: two days.Setup, discovery, analysis and the plan all ran on July 11. Discovery raised 68 open questions. Symphony grouped them into 20 themes and put 8 to the person. The design was approved and the checks were written on July 12.
Build: from day two.The build began 23 hours after setup. The six planned phases were complete by July 14, and the first deployment followed on July 15.
Check: by people and by Symphony.Symphony walked the product as five kinds of user. Design checks ran four times. Independent audits read the work the build had already passed.
Release: July 29.The product moved to its own address, lumosmarketing.app, 18 days after setup.
Improve: to August 5.A review of what production still needed added 86 tasks in six runs. The last release in the record is August 5, 25 days after setup.

The brand already existed, and the messaging was settled on July 9. The days on this page count from project setup on July 11.

A line from the product

Ready to review. Nothing is published until a person approves it.

The review card on a generated image in Lumos Throughline

Not every run was smooth.

On day two, an independent audit found security gaps that the build’s own passing tests had missed. They were fixed the same day.

Image and video generation passed its checks on sample data before it had ever run from end to end. A person found that on July 24. Each fix revealed the next fault, and the first video played on July 27.

After the product reached its own address, the person directing the build found three more faults by using it. One fix passed 1,559 tests and changed nothing, so it was done again.

Five tasks are still open. Every fault, and the fix that came from it, is on the record. Nothing is quietly patched.