PixelWidget
Back to work
Built internal system

Oldsols Admin OS

Initiator, product design, systems, QA

The internal operating system I started building once OldSols had grown past scattered tools and manual workflows.

Oldsols Admin OS welcome screen with OS mark and iridescent prism

At a glance

Status

Built internal system

Scope

Admin + operations + content

Privacy

No exposed member data

Build model

AI-assisted implementation

The story

OldSols had grown past the point where scattered tools and manual workflows made sense. So I started building the operating system I wanted behind it: admin workflows, analytics, content and member tooling, and the community operations that used to live in too many places.

My role

Workflow architecture, product design, QA ownership, AI-assisted build

I initiated, designed, and built this using AI-assisted development workflows.

How I built it

I mapped how the work actually happened, designed admin surfaces for the highest-friction tasks, built with AI-assisted development workflows, and owned QA across every path.

How it moved

Phase 01

Workflow mapping

Documented how admins, content, and member operations actually worked day-to-day.

Phase 02

System design

Designed unified admin surfaces for the highest-friction operational tasks.

Phase 03

AI-assisted build

Implemented workflows using AI-assisted development, with me as operator and QA owner.

Phase 04

QA & hardening

Tested every admin path, validated data boundaries, and tightened the admin workflows.

The work

Oldsols Admin OS welcome screen
Welcome screen — OS·X entry point for the admin operating system
Oldsols Admin OS coin creation workflow
Coin creation — community economy tooling inside the admin OS
Oldsols Admin OS adoption workflow
Adoption flows — onboarding and member lifecycle operations

Result

A functioning internal OS for admin workflows, analytics, content, member tooling, and community operations. A public demo would need sanitized data, so it stays internal.