Systems showcase

Systems we've built. Real operations, plainly described.

A grounded look at the systems we've built. Names withheld out of respect for the organizations. The work, the manual processes they replace, and the kind of operational change they make are described as honestly as we can.

Cooperative

Cooperative election system

Context

Cooperatives running annual elections of officers, with hundreds of members to verify and ballots to count by hand on the day of the assembly.

Before

Member lists printed and ticked off with a pen
Paper ballots counted by hand at the end of the day
Verification disputes are hard to resolve once the room clears
Final tallies announced late, sometimes the next day

What we built

Member verification using existing cooperative records
Voting interface for in-person casting
Real-time tally with audit-ready logs of each cast
Printable result sheets for the board and the audit committee

What this changes

Less manual counting and re-counting
Members spend less time waiting in line to verify
Officers can show real-time tallies instead of computing in front of the room
A clear record exists if a vote is questioned later

College / School

Class scheduling system

Context

Schools and colleges arranging class schedules each term across rooms, faculty, sections, and subjects — usually inside spreadsheets that grow harder to manage every semester.

Before

Schedules built in spreadsheets, term after term
Conflicts found by repeated visual checking
Faculty preferences and room availability tracked separately
Late changes ripple through several other schedules

What we built

A single view of faculty, rooms, sections, and subjects
Conflict detection when the same room or teacher is double-booked
Schedule edits with the changes carried through
Export to printable schedules for posting and distribution

What this changes

Reduced manual schedule checking
Adjustments are easier for school staff to make
Less back-and-forth when faculty preferences change
Conflicts surface before the term begins, not during the first week

Cooperative

Cooperative operations workflows

Context

Cooperative offices running daily transactions, member requests, and internal records across notebooks, spreadsheets, and chat threads — with different staff keeping different copies of the same information.

Before

Different staff keep different copies of the same information
Member requests are tracked verbally or on paper slips
Daily and monthly figures are reconciled by hand
Officers can't easily check the status of an ongoing request

What we built

Shared records for member transactions and requests
Daily and monthly summary views for officers
Logs of who did what and when
Workflows that follow how the office actually runs

What this changes

Staff work from the same view of what is happening
Less time spent reconciling records that were never aligned
Transactions and requests are less likely to be lost
Officers spend more time on members, less on paperwork

Local Government

Disbursement voucher tracking

Context

Local government offices processing disbursement vouchers that move between several offices for review and approval — usually tracked through paper logs at each desk.

Before

Vouchers tracked in paper logs at each office
Status checks require walking the document down or calling
It is hard to see where a voucher is stuck
Reports on processing time are difficult to assemble

What we built

Voucher records with reference numbers
Status updates as the voucher moves between offices
A view of pending and completed vouchers per office
Basic reports on volume and processing

What this changes

Staff can see voucher status without leaving their desk
Bottlenecks become visible
Less time spent answering "where is my voucher" questions
Office heads have honest numbers when they need them

Civic event

Pageant tabulation system

Context

Pageants and scored events where judges submit scores during a live program, and results need to be computed quickly without arithmetic mistakes.

Before

Judges fill paper score sheets
Tabulators compute results by hand or in a spreadsheet during the show
Mistakes are caught only after the announcement
The audience waits while the math gets done

What we built

Score entry per judge, per criterion
Automatic tabulation following the rules of the contest
Real-time view for the technical committee
Printable result sheets for the board of judges

What this changes

Tabulation finishes as the event ends
Less risk of arithmetic mistakes during a live program
Judges focus on judging, tabulators focus on the rules
Results can be reviewed before they are announced

Local Business

Transportation booking platform

Context

Transport operators handling trip bookings, schedules, and customer details across phone calls, chat, and a paper calendar — with bookings often slipping through the cracks on busy days.

Before

Bookings written in a notebook or chat thread
Double-bookings happen during busy days
Customers cannot see availability without messaging first
Schedules change in chat groups, not in one place

What we built

Booking interface with real-time availability
Customer records with trip history
Trip schedule view for operators and staff
Confirmation messages to customers

What this changes

Customers and staff see the same schedule
Double-bookings become rare instead of common
Booking is possible outside office hours
Follow-up does not depend on remembering the chat

We try not to inflate what we've done. If a system you see here matches your situation, we're happy to walk you through how it actually works, what it does well, and where it still has rough edges.

See your operation in any of these? Let's talk.

We'll listen first, and only build something if it genuinely helps. If what you need is close to a system we've already built, we'll say so plainly.

Talk to us about your operations