S Level 1
Stability
Fix crashes. Ship reliability. Earn trust before you ask for attention.
SEE Framework
Three levels. One scorecard. Real results.
Built by Court Bluford after 40+ apps and a decade of App Store battles — SEE is how teams know what to fix first and what to measure next.
SEE Framework · mini quest
Swipe through the three levels
Scroll vertically on the page — then explore Stability → Engagement → Expansion sideways. Each phase unlocks the next.
E Level 2
Engagement
Behavioral economics + emotional design — habits people choose, not tricks that trap them.
E Level 3
Expansion
App Store wins, reviews, and growth loops that compound after launch.
← Drag or swipe the cards · Works with keyboard focus too
Sequence beats speed
SEE is ordered on purpose. Stability earns trust. Engagement earns return visits. Expansion earns discovery. Funding level three while level one is on fire is the most expensive mistake we see in govtech and lottery mobile.
Stability first
Crashes, offline failures, slow first open, or review rejection loops
Fund: Crash monitoring, offline mode, session-zero UX, rejection playbook
Pause: ASO campaigns, influencer spend, and feature sprints that skip the foundation
Engagement second
Stable enough to open — but users bounce, do not return, or do not trust the vibe
Fund: Copy, emotional design, feedback loops, responsible-play visibility, perception work
Pause: Vanity redesigns and expansion spend while retention is flat
Expansion third
Users can complete core tasks and come back on purpose
Fund: ASO, store creative, deep links, review strategy, growth loops
Pause: Nothing — unless Stability or Engagement scores say otherwise
Seven obstacles we see in every gov app post-mortem
From the SEE book — patterns that block lottery and govtech teams from reliable apps and sustainable growth.
Building features before fixing Stability
Teams ship roadmaps while session zero crashes. Features do not matter if citizens hit error messages on first open.
The leaky bucket problem
Marketing pours users into an app with holes — bugs, lag, broken login. Expansion spend amplifies distrust instead of growth.
Transactional, not relational
Gov apps ask "how do we complete the task?" Winning apps ask "how do we make citizens feel valued enough to return?"
Ignoring feedback as "just one review"
Store reviews and session replays are free consulting. Teams that listen fastest improve fastest.
Building for averages, not outliers
Heavy users show what to double down on. Struggling users show what blocks adoption. The middle follows the edges.
Marketing a broken app
ASO and ads on a bad first session waste budget and damage reputation. Fix Stability before you scale spend.
SEE as a project, not a system
Six-month pushes fade when teams stop measuring. SEE is a scorecard rhythm — quarterly at minimum.
Benchmarks worth measuring
Outcome-based partnerships start when winning is defined — not when hours are billed.
| Pillar | Metric | Target | Note |
|---|---|---|---|
| stability | Crash-free sessions | 98%+ (under 2% crash rate) | Citizens forgive slow more often than broken. |
| stability | First-open success | Core task completable without confusion | Measure session zero like a stranger, not a stakeholder. |
| engagement | 30-day retention | 40%+ for lottery/gov apps with daily use cases | Industry average is ~6% — public apps must beat that with trust. |
| engagement | Store sentiment | Reviews mention trust, clarity, or reliability | Not just star count — read the adjectives citizens use. |
| expansion | Store listing conversion | 20%+ view-to-download on branded searches | Listing and first tap are the same product. |
| expansion | App Store rating | 4.0+ sustained after Stability work | ASO without narrative clarity is expensive guesswork. |
What the scorecard produces
- → Scores for Stability, Engagement, and Expansion (0–100 each)
- → Your focus layer right now — based on sequence, not vanity metrics
- → Top gaps from your weakest answers
- → What to pause funding on until the foundation holds
- → A 90-day roadmap shape you can defend to leadership and auditors
Full scorecard workbook ($34.99) and operational playbook ($79). Complete kit $99.
Sample scorecard items
stability
Our crash rate is below 2% of sessions and we monitor it weekly.
engagement
Users can complete core tasks without confusion on first try.
expansion
Our store listing explains the app in plain language a citizen would use.
Rate 1–5 in the full workbook. Mini assessment uses twelve high-signal questions online.
Shop
Workbook + Playbook — run SEE in the room
The book is free. These are the tools teams buy for QBRs, vendor renewals, jackpot gates, and quarterly scorecard workshops.
SEE Scorecard Workbook
$34.99
65 questions · lottery-specific Stability · operator/vendor alignment
View workbook →SEE Playbook
$79
10 templates · vendor SOW clauses · jackpot & marketing gates
Get the playbook →SEE Complete Kit
$99
Workbook + Playbook · one workshop purchase
View complete kit →Read the free book · digital downloads delivered by email after purchase
- 40+
- Apps built & scaled
- 400K+
- Peak monthly users
- 4.7★
- Ratings raised to
- 10+ yrs
- App Store battle-tested
Outcome-based partnership
Outcomes over hours
In the AI era, output is cheap — results are not. We align fees to milestones you can measure: stability, retention, approvals, ratings.
Shared scorecard
Before we start, we agree what “winning” looks like — crash-free sessions, review velocity, download targets, or civic trust metrics.
No surprise scope
Audits are fixed. Engagements phase in. You always know what unlocks next in the SEE journey.
FAQ
What is the SEE Framework?
SEE stands for Stability, Engagement, and Expansion — a three-phase system to audit, fix, and grow mobile apps, especially in public sector and regulated markets.
How does the free assessment work?
Twelve questions across the three pillars. You get scores, a focus layer based on SEE sequence rules, prioritized actions, and what to pause funding on. Save results with your email to reference later.
How does Lissiland price engagements?
We price on agreed outcomes and milestones — crash rates, retention, App Store approval, ratings — not open-ended hourly billing.
Who is SEE for?
Civic tech, lottery, govtech, and startups whose apps must pass review on iOS and Android, retain users, and earn public trust.
Do you change code or only advise?
Both. We consult and guide with SEE scorecards, and we build native iOS and Android when you want a partner in the codebase.
Free strategy call (30 minutes)
Problem → solution → proof → action. Here’s what happens on the call:
- You describe what’s broken — in your words, not ours
- We map it to Stability, Engagement, or Expansion
- You get a SEE scorecard snapshot + honest fit check (build, guide, or both)
- No obligation; outcome-based engagements only if it makes sense
Good fit if…
- ✓ App in market but “not working” on iOS, Android, or both
- ✓ Facing App Store or Play rejection loops
- ✓ Need product leadership, native build, or AI/MCP architecture
Probably not yet if…
- — You only need a quote for pure dev hours with no product ownership (we’re not a body shop)
- — You want a full redesign with no appetite for measurement
Common questions
We already have developers.
Good — we don’t replace them by default. We own sequence, perception, App Store, SEE, and what to measure. We build iOS and Android when you want us in the codebase.
Do you only do iOS?
No. We develop and advise on native iOS and Android. Store strategy covers Apple and Google.
Can’t AI build the app for us?
AI can generate screens and MCP tools. It can’t guarantee approval, retention, or civic trust. We help you use AI and agents responsibly — and we price on results, not typing speed.
Can you improve UX without code changes?
Often, yes — we start with perception, copy, and behavioral design. When crashes, backend gaps, or policy risk block trust, we’ll tell you straight: stabilize first, then adjust how the app feels.
We only need ASO.
ASO without stability and trust is lipstick. We’ll tell you if Expansion alone is enough — or if you’re solving the wrong layer.
Know your SEE layer in three minutes
Take the free assessment — get the playbook to run it — or book a call to validate the roadmap.