Matt Murphy
Status: In development

Encore

I’m building one system for community-college continuing-education teams: catalog, registration and payment, class operations, attendance, completion and certificates.

My role
Product owner and builder
Built with
AI coding agents that I direct
For
Continuing-education and workforce-training teams at community colleges
Status
In development
Policy centerVersioned, witheffective datesPolicy snapshotfrozen per enrollmentCatalogEach college’sown brandingRegister& payPriced atregistrationClassoperationsSessions, rostersand closeoutAttendanceTaken in theinstructor portalCompletionCertificates youcan verifyReportingEnrollment,attendance,revenuePayment goes straightto the college

The problem

Continuing-education learners are working adults who pay when they register and take short classes, often taught by industry instructors. Systems built for credit students model this poorly, so staff fill the gaps by hand.

Who it’s for

Continuing-education and workforce-training teams at community colleges: directors, registrars, operations and finance staff, instructors and learners.

What I did

I designed the product and its business rules and direct the AI coding agents building it.

Decisions that shaped it

  1. A platform, not a marketplace

    Each college keeps its own branded catalog. There’s no cross-college storefront and no take-rate.

  2. Policy frozen at enrollment

    Refund, attendance, eligibility and pricing rules are versioned, and the rule in force is frozen onto each enrollment, so later changes never rewrite history.

  3. Price at registration

    Prices are calculated when someone registers, from policy, timing and eligibility, rather than stored on the class.

  4. Operational depth over feature sprawl

    Deepen the screens staff already use instead of adding shallow new ones.

What’s built

  • Institution-branded catalog with search, cart and time-limited seat holds
  • Registration and card payment, with refund workflows and a refund ledger (verified in test mode)
  • A versioned policy center with effective dates and audit reasons
  • A staff workspace that keeps a class’s sessions, instructor, rosters and closeout in one place
  • An instructor portal for rosters, attendance and grades
  • Completion rules, certificates and a public verification page
  • Enrollment, attendance and revenue reports

Constraints

  • Each college’s data stays separate, enforced at the application and database layers.
  • Learner data boundaries are designed with FERPA in mind: no education-record data in logs, analytics or email subject lines.
  • Money moves directly to each college. The platform never sits in the flow of funds.

Stuck with software that makes your staff do the integration?