Marketing AgentMarketing Agent
← All posts

We asked for permission before we'd shown a single screen of value

Contemporary stationary black rectangular monitor showing time on display with wires placed on brown background at convenient workplace in room

Photo by Skylar Kang on Pexels

During a recent product audit, we observed ChurchWork's mobile app requesting push-notification permission from new members during signup, before they had seen a single screen of real content or experienced any value. This sequence is suboptimal because users are far more likely to grant permission after they understand why they would want notifications, rather than before.

The Problem With Premature Permission Asks

The principle here, popularized by Nir Eyal in Hooked, is that permission asks should occur after a person has experienced enough value to genuinely want to opt-in, not before. When a user first opens an app or lands on a new service, they are in an exploratory phase. Their guard is often up, and they are assessing whether the product is even useful to them. An out-of-context permission prompt at this stage often elicits a reflexive decline.

This reflexive "no" is not just a momentary setback. It's often difficult to reverse later. Once a user has denied an app permission, changing that setting usually requires navigating through system menus, a process many users won't bother with, even if they later recognize the value. ChurchWork's early prompt was generic: "ChurchWork would like to send you notifications." This gave no context about what kind of notifications, or why they would be useful. Without understanding the benefit, why would anyone grant an abstract permission?

Consider the user's mindset: they've just downloaded an app, gone through a quick signup, and before they even see the dashboard, a modal pops up asking for system-level access. It feels intrusive and confusing. They haven't had a chance to connect with their groups, see upcoming events, or understand how the app might support their community involvement. At this point, "no" is the path of least resistance.

The Audit's Prescribed Fix: Contextualized Permission

The audit recommended a specific change: move the push notification request to fire after a member's first genuinely useful action within the app. For ChurchWork, this meant after a member had joined their first group and viewed its upcoming meeting schedule. At this point, the user has experienced direct value: they've connected with their community and found relevant information.

Critically, the permission prompt was also reframed. Instead of a generic system prompt, it became: "Get notified when your group meets?" This framing connects the permission directly to a specific, understood benefit. Users now see a clear advantage: opting in means they won't miss important events for the group they just engaged with. The request also appears immediately after they've taken an action that makes the benefit obvious, reinforcing the "why." This creates a much higher likelihood of a "yes."

This change aligns with the idea that permissions should be earned. By showing value first, you create a sense of trust and utility that makes the permission a natural next step, rather than an arbitrary hurdle. Why AI-written marketing content still needs a human approval gate touches on a similar principle: decisions should be made with sufficient context and human oversight.

A Broader Teaching Point: Order Matters

This specific instance with ChurchWork highlights a broader, critical lesson in product design and marketing: the order in which operations happen matters as much as whether they happen at all. Many teams focus intensely on what features to build or what messages to send, but give less thought to the when.

Permission requests, whether for notifications, location data, or access to your camera roll, are one of the most common places teams get this order backwards. They treat permissions as a checkbox to be ticked at the earliest possible moment, rather than a privilege to be requested at the most opportune one. This isn't limited to app permissions; it applies to any ask you make of your user, from signing up for a newsletter to sharing personal data.

By asking for permission when the user is most primed to understand its value, you respect their attention and increase the likelihood of conversion. This applies to your marketing efforts too. Presenting a compelling offer after a user has engaged with valuable content, for example, is more effective than a cold, uncontextualized pitch. Thinking through the sequence of user interactions is a powerful way to improve engagement and retention, creating a smoother, more intuitive experience overall.

Marketing Agent

Your autonomous marketing operator: it gets a product market-ready, defines who it is for, audits what will make it stick, creates the blog, content and videos, and publishes to connected channels so builders can focus on building.

Try Marketing Agent

Comments

No comments yet.