Stop Measuring DAU for Products Used Once a Week

If you’re measuring DAU for weekly products, you’re measuring the wrong thing — and it’s actively misleading your team. I spent thirteen years building products for pastors and ministry leaders across four continents, and for most of that time, I was using the wrong metrics.

At SermonCentral, our DAU looked terrible on paper. We were serving hundreds of thousands of active pastors — and our daily active user numbers were abysmal. Not because the product was broken. Because pastors prep sermons once a week, not every Tuesday at 3pm.

Most PM frameworks assume daily usage patterns. Retention curves calibrated for social media. Activation metrics borrowed from productivity tools. Engagement loops designed for apps people compulsively open.

If your users naturally engage weekly, those metrics aren’t just wrong — they’re actively misleading.

Why DAU for Weekly Products Fails

Here’s what I learned building SermonCentral: Sunday drives everything.

Sermon searches spike Monday through Wednesday. Downloads peak Thursday. Friday and Saturday? Ghost town. Sunday morning brings a flurry of last-minute mobile access, then complete silence until Monday.

Our DAU/MAU ratio never broke 20%. In consumer app terms, that’s death. For a weekly product serving hundreds of thousands of active pastors, it was exactly right.

The same pattern holds across every faith-based product I’ve built or analyzed. Church attendance is weekly. Small group meetings are weekly. Sermon prep follows a weekly rhythm that’s been consistent for centuries.

Your DAU will never look like Slack’s. That’s not a bug — that’s your users’ real spiritual and professional rhythm.

What Actually Matters: Weekly Active Metrics

After tracking both daily and weekly engagement across multiple products, here are three metrics that actually predict success for weekly-use products:

Weekly Active Sermon Searches (WASS) — At SermonCentral, we tracked unique pastors running sermon searches within their prep window (typically Monday–Thursday). This number stayed remarkably consistent week-over-week, even as DAU fluctuated wildly.

Sunday-to-Sunday Retention — Did the pastor who used your tool this Sunday also use it next Sunday? This 7-day cycle retention tells you more about product-market fit than any daily metric.

Content Action Rate within 48 Hours — Pastors who print, download, or save content within 48 hours of trial signup complete their first full prep cycle. The ones who don’t rarely convert to paid.

These patterns hold across different faith contexts too. When we analyzed usage patterns across regions — post-Christian Europe, Sub-Saharan Africa, Southeast Asia — weekly rhythms emerged regardless of cultural differences.

Daily vs Weekly vs Intermittent: Three Different Playbooks

I’ve built products across three different usage patterns, and each requires a completely different success framework:

Daily-use products (Bible reading apps, devotional tools): DAU matters. Optimize for habit formation, reading streak maintenance, daily content delivery.

Weekly-use products (SermonCentral, sermon prep tools, weekly group resources): DAU is meaningless. Optimize for prep-to-pulpit completion rates and Sunday-to-Sunday retention.

Intermittent-use products (discipleship tools triggered by life events, not calendar events): Neither daily nor weekly metrics capture the real value. A teenager might use a discipleship app three times in one week during a crisis, then not touch it for a month.

We spent two years trying to force SermonCentral into daily engagement patterns before accepting that the weekly rhythm was a feature, not a flaw. This connects directly to the broader challenge of product-market fit in faith tech — understanding what your users actually need versus what standard SaaS metrics say they should need.

The Real Activation Moment for Weekly Products

Most PM frameworks define activation as completing key actions in your first session. Sign up, upload a photo, connect with three people, send your first message.

For weekly products, that’s backwards.

A pastor who signs up for SermonCentral and browses illustrations on Tuesday hasn’t activated. A pastor who uses your research tool to prep Wednesday, builds a sermon Thursday, and preaches it Sunday has completed one full cycle. That’s your aha moment.

I started tracking what we called “First Sermon Sunday” — the percentage of trial users who completed a full prep-to-pulpit cycle within their first two weeks. This number predicted paid conversion better than any first-session metric we tested.

The activation window isn’t “first session.” It’s “first use cycle.” Andrew Chen’s research on retention and engagement confirms that retention curves look radically different depending on the natural usage frequency of your product category.

A Framework for Weekly Product Metrics

Step 1: Map your natural usage cycle. What’s the real-world rhythm your users follow? For pastors, it’s Sunday-to-Sunday. For small group leaders, it might be meeting-to-meeting. For Bible study groups, season-to-season.

Step 2: Design metrics around cycle completion. Instead of DAU, track users who complete full cycles. Instead of session length, track cycle-to-cycle retention. Instead of feature adoption, track cycle success rate.

Step 3: Time your interventions to the cycle. Onboarding emails on Monday morning, not immediately after signup. Retention campaigns on prep days, not random Tuesday afternoons. Feature announcements timed to the start of prep cycles.

Step 4: Report progress in cycle terms. “We had 2,847 active pastors this Sunday” tells a different story than “our DAU dropped 15% this week.” Both might be true. Only one reflects user reality.

The Deeper Insight

Spiritual formation follows rhythms, not funnels.

Product managers try to increase usage frequency because that’s what our metrics reward. But for faith-based products, the goal isn’t daily dependence — it’s weekly faithfulness. The goal is a product that fits how people actually live, worship, and grow.

Stop measuring DAU for products used once a week. Start tracking the metrics that matter: cycle completion, Sunday-to-Sunday retention, and the real activation moment when someone completes their first full use cycle.

Your engagement numbers might look terrible by consumer app standards. That might mean you’re building something that actually fits how people work and worship.


Your Turn: Apply This Today

Ready to move beyond DAU? Here’s how to start the conversation on your team:

  • Audit your current metrics stack. List every metric in your weekly review. For each one, ask: does this capture whether users achieved their actual goal, or just whether they showed up?
  • Define the “natural cadence” for your product. What is the genuine rhythm of value for your users? Daily? Weekly? Seasonally? Your core retention metric should match that cadence, not an industry benchmark.
  • Pick one “mission completion” metric to track this quarter. Identify the single action that signals a user got real value. Track completion rate and the time-to-completion. Make it a weekly review staple.
  • Have the stakeholder conversation proactively. Before your next leadership review, prepare a one-paragraph explanation of why your product’s success metric differs from DAU. Bring the alternative metric with 4 weeks of data.
  • Segment by use case, not frequency. Separate users who access your product daily for lightweight tasks from those who use it intensively once a week. Track each segment’s success separately rather than averaging them together.
  • Set a “dark usage” alert. Build or request a signal that fires when a high-value user hasn’t completed their key workflow in longer than their typical cadence. Absence at the right time is more meaningful than presence every day.

Building a product for ministry, church, or faith-based audiences? I consult with organizations navigating the intersection of product strategy, growth, and mission. Let’s talk.

Your International Users Aren’t Broken. Your Metrics Are.

A crowded room of professionals, where each new title raises a career question about real scope

I’ve lived in Sweden, Spain, and South Africa. I’ve traveled through India and spent years doing work across the African continent. I’ve sat in homes with no reliable electricity, ridden trains through Mumbai at rush hour, shared meals with families in rural Kenya where four people passed one phone around the table like a hymnal.

That context lives in every dashboard I’ve ever opened.

The Number That Started This

At a global digital platform I’ve worked on, we pulled activation rates by region. Users completing meaningful engagement within their first seven days:

  • North America: 34%
  • Southeast Asia: 12%
  • Sub-Saharan Africa: 8%

A standard read of those numbers would trigger a roadmap conversation about localization problems, onboarding failures, or weak product-market fit in two-thirds of the world.

That read would be wrong.

Those users aren’t failing to activate. They’re activating through patterns that Western product frameworks were never designed to see.

What Different Actually Looks Like

In Sweden, individual behavior is the default unit of everything — including how people use software. One person, one device, one account, one session. The product journey is linear and personal. Metrics built around this model feel like common sense because, in that context, they are.

South Africa broke that assumption for me fast.

In townships outside Cape Town, I watched families coordinate around a single smartphone. One device. Multiple users. Staggered access built around work schedules, school pickups, and when the data bundle was loaded. The “user” wasn’t an individual — it was a household.

In rural Kenya, connectivity isn’t a utility. It’s an event. When signal is available, you download everything you can. You consume it later, offline, sometimes in groups. What looks like three sporadic sessions on a retention curve might actually be one deeply intentional household engagement event.

In India, I watched people think in groups. Nobody wanted to be the one who got it wrong. Before committing to anything, they’d consult — family, colleagues, the cousin who works in tech. Not because they lacked confidence, but because they love their community too much to make a unilateral call that affects it. The conversion window isn’t 30 days. It’s however long trust takes to travel through a network.

I am not speculating about these patterns. I’ve watched them. They’re real. And none of them show up cleanly in a standard AARRM dashboard.

Where the Frameworks Break

Standard product metrics carry hidden assumptions. They’re not wrong exactly — they’re just calibrated for a specific kind of user in a specific kind of context. When the context changes, the assumptions crack.

The individual device assumption

DAU/MAU ratios assume one user per device. In markets where device sharing is normal, you’re measuring household behavior through an individual lens. You’ll systematically undercount engagement and misread retention.

The connectivity assumption

Retention curves assume users can return to your product whenever they want. When connectivity is intermittent, “churned” users are often just waiting for signal. We now track separate activation funnels for high-connectivity and intermittent-connectivity markets. The curves look completely different and require completely different responses.

The linear progression assumption

Western onboarding flows push users through individual setup before unlocking social features. In collectivist contexts, users want to share before they want to configure. They don’t skip setup because they’re disengaged — they skip it because community access is the point, not a reward for completing it.

The payment infrastructure assumption

A 30-day conversion window made sense when your users have credit cards and make financial decisions alone. In markets where mobile money dominates and purchasing decisions involve extended family consultation, 30 days is an arbitrary deadline that will make your international monetization look broken when it isn’t.

What We Actually Changed

Recognizing the problem is the easy part. We had to rebuild how we measure.

We segment activation funnels by connectivity profile, not just geography. A user in Lagos on intermittent mobile data gets evaluated against a completely different baseline than a user in Amsterdam on broadband. This alone changed how we prioritized international product work.

We moved toward value-event tracking instead of session frequency. The question stopped being “did they come back today?” and started being “did they get what they came for?” A user who engages three times a week in a group context can deliver more value — to themselves and to us — than a daily solo user, depending on the product.

We extended our monetization observation windows significantly in markets where financial decisions move through social networks before they land on a purchase button. This wasn’t generosity. It was accuracy.

We started tracking what I’d call cultural cohorts alongside temporal cohorts — grouping users by context type rather than signup month. The retention curves that emerge require fundamentally different interventions than anything a North American benchmark would suggest.

The Thing Worth Remembering

If you’re seeing real, sustained, non-bot international traffic, that’s a signal. Users in unfamiliar markets don’t find you by accident at scale. They found you because your product does something worth finding.

The question is whether you’re measuring them honestly.

An 8% activation rate in sub-Saharan Africa and a 34% activation rate in North America don’t automatically mean one market is working and one isn’t. They might mean you’re serving two completely different behavioral contexts with one measuring stick.

Your international users have probably already told you something. They showed up. They engaged in whatever way their lives allowed. They downloaded content for the offline hours, passed the phone across the table, and came back when the signal did.

The gap isn’t between them and your product. It’s between their reality and your dashboard.

Fix the dashboard.


¹ How to determine your activation rate

Photo by Christian Harb on Unsplash

Philippians 2 and Agentic Systems: Why Humility Is the Foundation of Intelligent Systems

“Do nothing from selfish ambition or conceit, but in humility count others more significant than yourselves. Let each of you look not only to his own interests, but also to the interests of others. Have this mind among yourselves, which is yours in Christ Jesus, who, though he was in the form of God, did not count equality with God a thing to be grasped, but emptied himself, by taking the form of a servant, being born in the likeness of men.” (Philippians 2:3-7, ESV)

Paul’s letter to the Philippians contains what theologians call the kenosis passage — the self-emptying of Christ. It’s about voluntary limitation, choosing constraint over capability, service over sovereignty.

I’ve been thinking about this as I watch agentic systems become more capable. The rhetoric around AI often centers on unlimited potential, boundless capability, systems that can do anything. But in my experience building AI systems, including multi-agent workflows for executive tasks, I’ve observed that success often comes through deliberate constraints rather than unlimited scope.

Well-designed AI agents typically focus on narrow mandates: a calendar agent that protects focused time blocks rather than trying to optimize entire lifestyles, or an email agent that surfaces priority messages rather than attempting to replace human judgment entirely. Each agent serves a specific function within defined bounds.

This represents a design choice rather than a technical limitation.

The Kenosis of Intelligent Systems

When building AI workflows, the temptation exists to create agents that can handle everything. But, what I’ve seen is that this approach typically produces chaotic results — agents interfering with each other, making decisions outside their expertise, creating more complexity than clarity.

A more effective approach involves thinking about AI agents as specialized robots rather than general-purpose minds. Each agent can be designed to “empty itself” of capabilities it doesn’t need, serving a specific function more effectively through limitation.

Specialized agents with narrow scopes — research agents that don’t schedule meetings, scheduling agents that don’t write summaries, writing agents that don’t manage tasks — can demonstrate greater utility through deliberate constraints.

This mirrors patterns in effective human teams, which typically consist of specialists who understand their roles rather than generalists attempting everything. They practice a form of professional kenosis — voluntary limitation for collective effectiveness.

Paul’s instruction to “count others more significant than yourselves” suggests a design principle: building systems where each component serves the whole rather than maximizing individual capabilities.

The Servant Leadership Model for AI

The parallels between servant leadership principles and effective AI system design are notable. Servant leaders focus on enabling others’ success rather than demonstrating their own power, asking “How can I help you accomplish your goals?” rather than “How can I show you what I can do?”

Effective AI systems often follow similar patterns. GitHub Copilot suggests contextual code completions rather than attempting to write entire applications. AI writing assistants help clarify thinking rather than replacing human thought processes. Advanced language models acknowledge uncertainty and ask clarifying questions rather than claiming omniscience.

These systems practice technological humility by acknowledging their limitations.

In contrast, AI systems that fail in production environments often attempt to exceed their appropriate scope, make decisions beyond their training data, or present uncertain inferences as established facts. They lack the kenotic restraint that characterizes truly useful intelligence.

Building Products for Global Spiritual Formation

This principle becomes particularly important when developing products for spiritual formation. Digital discipleship platforms serve diverse global communities across cultural, linguistic, and theological boundaries. The temptation exists to build universal systems that can serve everyone.

However, effective spiritual formation tends to be deeply personal and contextual. A Bible application serving a house church in rural Kenya requires different features than one serving a suburban megachurch. Prayer applications for new believers need different structures than those designed for theological students.

AI systems serving spiritual formation appear most effective when they practice kenosis — limiting their scope to serve specific communities well rather than attempting to serve everyone adequately.

Current development work on AI tools for sermon preparation follows this model. Rather than attempting to write complete sermons (which, based on informal conversations with pastoral leaders, many pastors prefer to avoid), such tools can focus on specific supportive tasks: locating relevant cross-references, summarizing historical context, or structuring outlines. They operate within deliberate constraints to support pastoral ministry rather than replace it.

Each tool “empties itself” of broader capabilities to serve one function excellently. Like Paul’s description of Christ, they don’t grasp for equality with human pastors — they take the form of servants.

The Paradox of Powerful Restraint

An interesting observation: seemingly powerful AI systems often prove most effective when operating under significant constraints. The wisdom of limiting scope applies to artificial intelligence as much as human teams.

In my experience, the most effective AI implementations have narrow, well-defined purposes. They operate within their designated areas, defer to human judgment on edge cases, and acknowledge when they lack sufficient context for recommendations.

This represents strength through limitation rather than weakness.

Paul writes that Christ “did not count equality with God a thing to be grasped.” He could have insisted on unlimited power but chose constraint for the sake of service. The kenosis wasn’t a loss of divinity — it was divinity expressed through voluntary limitation.

Similarly, the most intelligent AI systems may not be those with the most capabilities, but those that use their capabilities most wisely — which often means choosing restraint over action.

Technical Humility in Agentic Systems

What might this look like in actual system design? Consider what could be called “kenotic interfaces” — AI systems that actively limit their own scope.

For example, an email management system might flag messages for human review when confidence levels fall below high thresholds, choosing uncertainty over potentially incorrect automated actions. A research assistant might include confidence indicators in summaries, distinguishing between well-sourced findings and preliminary observations that require verification.

These design choices represent features rather than limitations. The wisdom of acknowledging uncertainty can increase system trustworthiness.

The Global Scale Challenge

Building for global spiritual formation means designing for contexts that developers may never fully understand. While optimization for familiar cultural contexts remains feasible, platforms serving Orthodox Christians in Eastern Europe, Pentecostals in West Africa, and house churches throughout Asia require different approaches.

The kenotic approach suggests building systems that acknowledge their cultural limitations. Rather than attempting to provide universal spiritual guidance, they can provide tools that local leaders adapt to their specific contexts.

Bible reading features need not assume Western individualism. Prayer tools need not assume specific liturgical traditions. Community features need not assume particular church structures.

Each feature can “empty itself” of cultural assumptions to serve diverse communities more effectively. Like Christ taking human form while maintaining divine nature, these systems can preserve core functionality while adapting to local contexts.

The Long View

Paul’s kenosis passage encompasses more than humility — it describes transformation. “Therefore God has highly exalted him and bestowed on him the name that is above every name” (Philippians 2:9). Self-emptying leads to greater effectiveness rather than diminishment.

A similar pattern may emerge for AI systems. Those practicing technological kenosis — voluntary constraint for the sake of service — may ultimately prove more valuable than systems grasping for unlimited capability.

The Tower of Babel failed because it attempted to exceed proper limits. Modern AI might encounter similar challenges without the discipline of restraint.

The most powerful systems may be those that understand when not to exercise their power.


Key Insight:

The kenosis principle — Christ’s voluntary self-emptying described in Philippians 2 — offers a design philosophy for AI systems. Instead of maximizing capabilities, effective AI agents can practice deliberate constraint, serving specific functions excellently rather than attempting everything adequately. This proves particularly relevant for products serving global spiritual formation, where cultural humility and contextual awareness matter more than technical sophistication. Just as Christ didn’t grasp for equality with God but took the form of a servant, intelligent systems may become more useful when they acknowledge limitations and defer to human judgment on edge cases. The paradox of kenosis — that voluntary limitation can lead to greater effectiveness — may apply to artificial intelligence as much as spiritual leadership. In a world of increasingly capable AI, the most valuable systems may be those that understand when not to use their power.

Photo by Vitaly Gariev on Unsplash