This page is here to help lifecycle, product, and engineering stay aligned on what gets hard-coded vs. what gets built in Appcues—and to make that decision consistently, quickly, and collaboratively.
Use this for fast gut-checks. If you're still unsure, scroll for the full framework.
Start here:
❓ Is this experience permanent, tightly tied to core functionality, or reliant on backend data?
→ Yes? Hardcoded is probably the right fit.
→ No? Keep going ↓
❓ Do we need to test, target specific users, or update this regularly?
→ Yes? Appcues is likely the better home.
→ No? Keep going ↓
❓ Who owns the outcome?
→ Lifecycle/Marketing? Lean Appcues
→ Product/Engineering? Lean hardcoded
❓ Is it one-size-fits-all or will different audiences need different versions?
→ Different audiences? Use Appcues
→ Everyone sees the same thing? Could go either way—use the full checklist below