Tempus

Brand Positioning Memo
S4 Deliverable · AI-Accelerated Entrepreneurship Practicum · Spring 2026
Chase Petersen · Vanderbilt Owen MBA
Positioning Statement
For Catholic diocesan leadership who need to optimize sacramental access across dozens of parishes,
Tempus is the only AI-powered resource allocation platform that forecasts confession demand
using the liturgical calendar and automatically generates optimal priest staffing schedules —
replacing word-of-mouth coordination with data-driven stewardship.
The Problem

Sacramental Access Is a Staffing Problem

During Holy Week 2026, a practicing Catholic in Nashville attempted confession three times across three days and was turned away every time. The cause: one priest staffing a confessional during the highest-demand week of the liturgical year. This isn't a faith problem — it's an operations problem.


Catholic dioceses manage 50-80+ parishes with limited priests. Confession scheduling is done by individual pastors using gut feel, tradition, and word of mouth. There is no demand forecasting. No cross-parish coordination. No visibility at the diocesan level. The result: predictable surges (Advent, Lent, Holy Week, First Fridays) overwhelm single-priest confessional setups, and the faithful are turned away from a sacrament.

Brand Vocabulary — The "-ity" Framework
Temporality
Time is sacred. Tempus treats the liturgical calendar as a demand signal — not background decoration. Every feast, fast, and holy day carries a quantifiable impact on confession volume. The system knows when demand will surge before the parish does.
Visibility
Diocesan leadership currently has zero aggregate view of confession capacity across parishes. Tempus gives the Vicar General a single pane of glass: which parishes are understaffed, which priests are overloaded, where the gaps are — in real time.
Availability
The core output. Tempus optimizes for one thing: ensuring a priest is available when a penitent arrives. Every scheduling decision is measured against this metric. Availability is the product.
Authority
Tempus respects the canonical authority structure of the Catholic Church. The AI recommends — the pastor and Vicar General decide. Human-in-the-loop isn't a feature; it's a theological requirement.
Scalability
Start with one parish. Scale to a diocese. Then to a province. The data model is parish-atomic — each church is a self-contained node that can be aggregated upward without restructuring.
Simplicity
Parish secretaries and 70-year-old pastors need to use this. No training. No onboarding decks. Clean inputs, clear outputs. If it's harder than a paper schedule, it fails.
Dignity
Being turned away from confession is a failure of pastoral care. Tempus exists so that no one drives to three parishes in three days and leaves without receiving a sacrament. The product serves the dignity of the penitent.
Fidelity
Faithful to the liturgical calendar. Faithful to Canon Law. Faithful to the operational reality of parish life. Tempus doesn't abstract away the Church — it serves the Church as it actually operates.
Competitive Landscape
Competitor What It Does What It Misses
Word of Mouth / Pastor Gut Feel Pastor sets confession times based on tradition and personal judgment. Adjustments happen reactively, if at all. No demand forecasting. No cross-parish coordination. No diocesan visibility. Completely breaks during surge periods.
Parish Secretary (Manual) Secretary manages priest calendar in spreadsheets, paper, or basic calendar apps. Coordinates via phone/email. Single point of failure. No liturgical demand modeling. Cannot optimize across multiple priests or parishes. Data dies with the secretary.
ParishSOFT Enterprise church management: financials, sacramental records, census, giving. Used by many Catholic dioceses. Records sacraments after they happen — doesn't optimize access to them. No scheduling intelligence. No demand forecasting. No AI. Designed for back-office administration, not operational allocation.
Breeze ChMS Lightweight church management: member database, giving, check-in, basic event scheduling. Popular with Protestant churches. Not built for Catholic parish structure (no canonical roles, no liturgical calendar integration). Generic event scheduling — no sacrament-specific logic. No multi-parish aggregation. No demand intelligence.

The Structural Gap

Every existing solution treats scheduling as a static calendar problem. Tempus treats it as a dynamic resource allocation problem — the same class of optimization used in fleet dispatch, hospital staffing, and air traffic control. The liturgical calendar is the demand curve. Priests are the constrained resource. Confession availability is the service level. No one else is running this math.

Competitive Radar Charts

Tempus vs. Word of Mouth

Tempus vs. ParishSOFT

Tempus vs. Breeze ChMS

Defensible Moat
Go-to-Market

Phase 1 — St. Ann Catholic Church, Nashville

Single-parish proof of concept. Collect priest roster, Mass/Confession schedules, and availability data for St. Ann. Build the liturgical demand forecast. Demonstrate to Fr. Michael Fye (Pastor, Vicar General) that Tempus can predict Holy Week confession bottlenecks and recommend optimal staffing.


Phase 2 — Diocese of Nashville

Scale to all ~60 parishes. Aggregate view for diocesan leadership. Cross-parish priest sharing recommendations during surge periods. Present to the Vicar General as a diocesan management tool.


Phase 3 — Multi-Diocese Expansion

Expand to adjacent dioceses in Tennessee, then nationally. Each diocese added enriches the liturgical demand model. Target: diocesan Chancery offices as the buyer.