HOW A BUILD HAPPENS
From Requirements to Release
We assess the business case before committing to an application design. The work then covers development, testing, release and the application’s daily operation.
The home page describes how we built Podium, the Conductor's Office and the first partner app, and what each project taught us.
From the Idea to the Plan
Today: We begin by assessing whether to buy existing software or build an application. We establish the specific need and who benefits before expanding the scope. We agree on what to build before design starts, then review the design for ethical concerns before writing code.
Tomorrow: We plan to automate these questions and their records, with a person reviewing the answers.
Trio Themes
Today: We specify the design once and build screens in three complete themes users can switch while the app runs. The thirty-six-theme library runs in production, and two of our own screens were built directly from their designs.
Tomorrow: We plan to build every screen directly from its design, for iPhone, Android and the web.
From "OK" to "Wow".
The factory takes us from "idea, brief or concept" to "working at more than a Minimum Viable Product level" because of the automation, internal testing and application of pre-approved style catalogs. This then allows the human being to focus on all the little things that take the experience from "OK" to "Wow".
Today: Every change must compile and pass its tests before we accept it. Failed tests guide repairs, and alerts explain the problem alongside the results. A person decides what looks and feels right before the application ships.
Tomorrow: We plan to automate complete builds, including native screens, with the same tests at every step.
On September 22nd, 2026, an alert identifies 20 monitors reporting late or remaining quiet. Its dossier lists the supporting results for each monitor.
Release and Upkeep
Today: Every production release records what was tested and who approved it. Seven releases shipped with their records in September 2026 through this process. Health, spend and decisions share one screen; partner notes enter the same work queue as our own.
Tomorrow: We plan to schedule releases and reviews from the record and assess progress against goals each week.
On September 23rd, 2026 the logs page shows 3,846 entries in seven days and opening one row groups the run with 27 jobs scanned in the drawer.
On September 23rd, 2026 the deliveries page maps work from first conversation through ship and charts eight weeks ending September 22nd to September 28th.
The nine roles responsible for development, their current work and their planned capabilities appear on the Designosaurs page.