We're using the factory to build the factory. First, we built and refined each agent (aka Designosaur) to do its job, like tuning each robotic system on a modern physical automobile factory. The first apps went through its steps, at first largely by hand (like trundling each part of the car from machine to machine), then adding more internal automation, building from the inside steps out. Each correction became learning for the next cycle. Cycle times are getting faster. Here's how it worked to create Podium, and the Conductor's Office, and here's how we're using it to create a fitness app.
In the software world, the concept of "Eating your own dogfood", or for the fancy people "Drinking your own Champagne", is the idea that you become your own first customer. Here's how we did it.
Podium, Our Business and Factory Visualization Dashboards
We wanted one place that answers the questions a leadership team asks every morning: where do we stand, what's moving vs. what's stuck, what needs a decision, what did we spend. We settled the design on live pages, eight rounds of markup with the person who would use it (me), and signed it off on September 7th, 2026. The factory then built each page to that design and filled in the numbers once its own tests passed. We're still tweaking it and that will probably be true for the foreseeable future.
The Conductor's Office
Where I sort mail and keep track of people.
The office sorts my mail and texts and keeps track of the people behind them: what needs an answer, what is an event, what is spam. As of September 23rd, 2026 it has classified 103,950 emails, 5,480 of them in the last thirty days, and read 33,545 texts. It has raised 240 suggested events, seven approved onto the calendar and twenty-five turned down, and caught 6,349 spam messages. Each approval or refusal becomes a rule for the next pass, so the suggestions get more relevant with use. The next step is designed: approved events reaching the family's Skylight calendar.
SwabbieFit
A fitness app for a partner.
The partner had the requirements; we had the rules. On September 5th, 2026 we chose to build the first app by hand inside the factory's guardrails rather than wait for the machine to generate it, so these screens become the standard every generated screen is measured against. One scoring engine serves the phone and the browser, three themes switch at a tap, and it goes out through the same release steps as our own work.
On September 17th the app ran end to end on a simulated phone. Four build defects turned up; all four were fixed in the next weekly cycle, along with a demo mode and a live privacy page. Still a person's job: the store accounts and the step that puts the build on a physical phone. The next app starts with a shell for all three platforms, three themes and the release steps from the first app.
The Safeguards
The safeguards run on every build. The machine tests everything it can test; where it cannot tell, two independent systems compare answers. Where taste decides, a real, live human being decides what looks and feels right, and that decision is written down as a rule for the next build. Nothing reaches production except through three stages, each with its record kept; seven releases took that path between September 8th and September 14th, 2026. Every screen ships with three themes. Anything about a real person or company is proposed by the machine and confirmed by a person. Each cycle widens what the machine can test on its own.
What We Deliver
iPhone, Android and the Web
Your app is designed once and behaves like a native app on each of the three. Today that is the web and the iPhone simulator; the store versions come next.
A Record of Every Test and Every Release
You can see what was tested and who approved it. Every screen is tested and run before we call it done, and every release to production leaves a record of what was looked at and who said yes. Nothing goes out on a promise.
Your Judgment Stays in the Loop
When the machine cannot tell whether something is good, it stops and asks a person. What it should look like, what it should do and whether it should exist at all are never decided by a machine.
Your Clients and Relationships
Your clients and your relationships stay yours. We never train on your material unless you choose it, and then only on patterns you can see and take back. We never scrape, and we never contact anyone on your behalf. Partners keep their brand, their taste and their client; your notes go straight into the work and come back answered.
Built for a partner from his requirements: scores a fitness cycle from tape measurements, keeps every number on the device, and shows the same result in a browser and on an iPhone from one scoring module. Walked through end to end on an iPhone simulator on September 17th, 2026.
Fitness calculator · browserPractice history · browser
A Proposed App in Parklife Communications' Colors and Type
One visit to the public site of Parklife Communications, a marketing and branding strategy firm, was enough to propose an app in its colors and type, shown with its permission. The screens are a visit a client could book, at laptop and phone width. What was read, the colors, the type, the spacing and the corners, is one click away.
Laptop home: Come in. A first conversation about what you want to make next. Let's talk. Thursday at 10:00, Friday at 2:00, and Tuesday at 11:00.Phone home: the same screen, stacked, with Let's talk full width and the same three times.
I open the same Podium app we ship for customers: operations boards on production data each morning, personal mail and people in the Conductor's Office beneath. Every number below is read from the screen capture beside it.
Podium Overview · morning boardBusiness plan · milestones
On September 22nd, 2026 the overview board counts 128 changes accepted and 3 releases from September 15th to September 22nd, with 4 plan reviews waiting on Jack.
On September 23rd, 2026 at 10:35 AM CDT the plan page lists 5 milestones, none met yet, with the first due by November 1st, 2026.
Conductor's Office · mail · masked records
Click an email and its dossier opensInbox · people · masked records
Mail and tasks stay in the Conductor's Office with masked records on the public site.
People and organizations stay in the inbox directory with masked records on the public site.
Sample records, not real mail: this is the same screen we use on our own inbox, shown here with made-up senders.
Your Partner Page
Each partner has a page that shows what runs and what is next, and a box for notes. A note lands in the same queue our own work runs from, and the partner sees on the page what happened to it.
Every screen is built to a strict standard, tested and run before anyone calls it done. When the machine cannot decide whether something is good, it stops and asks a person instead of guessing.
One Effort, Three Platforms
One design and one set of rules become apps on iPhone, Android and the web that behave as natives on each, not one website wearing three costumes.
The first app, built by hand on these rules, runs on the web and an iPhone simulator. Automatically building its screens comes next.
Trio Themes You Can Switch Between
Every app ships with three complete visual languages, different in type, spacing, shape, depth, motion, layout and icons, and the person using it picks. You are looking at one now; the buttons at the top switch it. The library holds 36 themes.
Your Relationships Stay Yours
My commitments to a partner: No training on your material unless you choose it, and then only abstracted patterns you can see and revoke. No scraping, no contact made on anyone's behalf. Every person in our records is one a person confirmed; the machine proposes, never asserts.
Who We Work With
Design Studios and Small Agencies
You keep the brand, the taste, the curation and the client. We take the technical side: drawing out what the client needs by conversation, showing work as it is made, building, testing and shipping to three platforms, and making sure people with disabilities can use it. Taste is never decided by a machine; when it is unsure it asks you.
Partners with a Product and a Market
You bring the requirements and the people who will use it; we build it, keep it on the device where that matters, and change it in weekly cycles from your notes.
If we already work together, you have your own page. To talk about a new project, write to us.
Run our business through Podium for a full week and write up the results, planned for September 27th, 2026.
The fitness app on real phones once the developer account opens.
Next
The first app in the App Store and Play Store under C-Level Sales Guy LLC.
A studio's first real client screen built from its files, not around them.
Later
A production system for volunteer community theatres: the plan is written; building it comes later.
The Designosaurs™
Nine named roles carry the concerns of safe software innovation, security, privacy, ethics, efficiency, deployment, and whether we are building the right thing.
We work behind the scenes today; we envision two operating modes and have an idea on record for a parent-and-child teaching experience: see The Designosaurs.
Give us a public website and we capture what it is built from - colors, type, palette. That is enough to pitch a prospective customer for additional work in their own brand - an added feature, a website refresh, an app - using only publicly available information. See one built for Parklife Communications, a marketing and branding strategy firm, from its public pages, shown with its permission.
