Acts — Product & UX Audit Framework

Prepared by Bryan · for Steve / Acts Ventures

A clickable prototype proves the *idea*. This audit answers the next question: is this the right experience, and what's the smallest set of changes that makes Acts feel like a product people return to? I review the current flows, find where the journey breaks, and hand back a prioritized redesign plan with hours — so the build estimate is grounded, not guessed.

The core thesis

The prototype's gap isn't a missing homepage — it's a missing loop. Today: *sign up → do one act → the experience ends.* A product that retains users answers three questions at that ending moment:

Reason to come back · Reminder that pulls them back · Reward that pays them off when they do.

I design the loop first; the home screen, community, and onboarding are surfaces that *serve* it. That's the difference between "make the screens prettier" and "make Acts a product."

What I audit (5 lenses)

| # | Lens | The question I answer | |---|------|----------------------| | 1 | Onboarding | Does a first-timer understand what Acts is and feel oriented in <60 seconds? | | 2 | The core act | Requesting / responding to an act — is the path obvious, fast, and emotionally rewarding? | | 3 | The dead-end | What happens the moment an act completes? (This is where the product currently ends — and where it should *begin*.) | | 4 | Home base | Is there a persistent place that orients, surfaces activity, and gives a reason to return? | | 5 | Community & retention | What does "community" mean here — connection, witness, or encouragement — and which loop fits Acts? |

What you get back (the deliverable)

1. Flow map of the prototype as it exists today, with the break points marked.
2. The Acts loop — a recommended retention model (reason / reminder / reward) tailored to a faith-based product.
3. Prioritized redesign list — each screen or flow ranked *must-have → nice-to-have*, with rough hours, so design and engineering investment line up with your fundraising timeline.
4. MVP cut line — what's essential for an investor-ready, *working* version vs. what can wait.

Questions I'll need from you

• After someone completes an act, what one feeling or behavior do you want next?
• Does community mean people *connecting*, or *witnessing* good being done? (Very different products.)
• Who is the first real user — the giver, the receiver, or a church/group?
• What's the smallest thing investors need to see working, not just clickable?

Scope & estimate

The ~20-hour frame is reasonable for redesigning the key flows. I confirm the number after the audit — when I can size each item instead of guessing. The audit itself is the fast, low-risk first step: a written teardown you can act on immediately, whether or not we go further.