Overview
KREP supports distinct public packages, self-serve plans, and request-access paths for more sensitive offerings.
This guide explains how to keep public pricing, plan features, and onboarding rules aligned.
How to use it in KREP
- Create or update plans in SaaS admin with the right limits and module access.
- Map each splash-page CTA to the correct plan or request-access path.
- Document which features belong to each package and who qualifies for whitelabel review.
- Test the signup journey in incognito mode for every public package.
What to monitor
- Plan click-through to registration.
- Signup completion by package.
- Upgrade requests and package confusion.
Best practices
- Keep names simple and clearly separated.
- Do not over-promise features in lower-cost tiers.
- Test the whitelabel request path separately.
Related KREP modules
SaaS, Pricing, Authentication
Search topics covered
krep packages, saas signup flow, software pricing kenya