Creator tools across campaigns, commerce, and learning
At Serlzo, I built features across the creator dashboard and member-facing application, spanning communications, CRM, commerce, communities, courses, billing, and team access.
These areas share users and data, but each has distinct rules and interactions. I translated those requirements into frontend features and made the loading, validation, and error states clear as users moved through each flow.
01
Campaigns and email tools
Built and refined email, SMS, and WhatsApp campaign flows, including audience filters, merge tags, message previews, sending options, and test-send controls. Implemented a visual email-template builder with reusable content blocks and style controls.
02
CRM and automations
Implemented contact and lead-management features, including CSV import dry-run analysis and preview, contact-list filtering, lead scores, and webhook setup. Added a review step so users can inspect imported data before continuing.
03
Products and commerce setup
Built multi-step digital-product setup with resumable drafts, pricing controls, deliverable uploads, buyer previews, and course details. Implemented storefront setup and checkout-configuration interfaces.
04
Communities, courses, and memberships
Built community administration, course-management, analytics, affiliate-reporting, and payout features in the dashboard; implemented learner navigation in the member-facing application.
05
Billing and team access
Connected subscription and billing views to platform APIs, surfaced plan usage and account states, and implemented a workspace roles-and-permissions interface for configuring team access.
The engineering work behind the screens
Integrated frontend features with platform APIs through shared models, services, and hooks.
Debugged cache refreshes, retries, loading and error states, and payment-return behavior.
Adapted dialogs, tables, editors, and course navigation for compact screens.
My role focused on frontend implementation and platform API integration, including the states needed for loading, errors, retries, and changes in server data.
See how I take independent projects beyond the interface.