Most operational software is the same shape: intake, records, workflow rules, approvals, history. These templates capture that shape once so a client build starts on week one with auth, roles, audit and seed data already working.
The catalog
- Research Operations OS — request intake, schema-driven metadata, deterministic validation, execution tracking, QC review, approvals, deliverable release. Tuned for bioinformatics service teams.
- Intake + Triage + Follow-Up OS — configurable intake forms, qualification, routing rules, SLA flags, reminders and outcomes. Agencies, clinics, consulting.
- Teaching Operations OS — courses, rosters, lesson plans, assignments, per-student tracking, support notes and communications.
- Field Service Operations OS — office and field surfaces, a FastAPI operational API, dispatch and job detail, trade packs, and a copilot scaffold that stays inside job context. Plumbing, HVAC, electrical.
The rule they share
LLM features can draft, summarize and suggest. They do not silently mutate authoritative workflow state. Every template ships org-scoped permissions, server-side guardrails and an event history for meaningful changes.
First derived product: Teachers Assistant, built from the teaching template with onboarding, roster import, transparent risk flags and a grading pipeline.