Creator Marketing Platform

Creator marketing platform — public site, customer dashboard and admin console

We delivered the full technical platform for a regional creator marketing service: a multi-tenant SaaS that connects end customers with an aggregated catalog of engagement services across thirteen social platforms. Our scope covered the entire engineering surface — Java Spring Boot backend, Next.js 16 customer dashboard, dedicated admin console, payment infrastructure, automated refund handling and a provider-sync layer that ingests, normalizes and prices a continuously shifting upstream catalog of more than 1,200 individual services. The platform is operated by an external client targeting the CIS market. Operational compliance with each social platform's terms of service, advertising regulations and payment processor policies remains the operator's responsibility; our role was to deliver the technical infrastructure they specified — audit-ready and built for sustained operator use.

For comparable platform engagements, see our Backend development and Startup & MVP development services.

Decision Context

The brief mixed a fast-moving consumer-facing surface with operator-grade backend control. Both sides had to land at the same time, on the same data model, and survive frequent provider catalog changes without breaking customer orders in flight.

Treating this as either a thin storefront or a back-office tool would have produced the wrong system. We modeled it as a single platform with three distinct surfaces — public marketing site, authenticated customer dashboard and admin operations console — sharing one canonical service registry and one pricing engine.

Key risks at the decision stage:

A volatile upstream catalog (1,200+ services, weekly churn) breaking customer-facing prices and limits.
Payment integration with regional processors plus automated refunds without manual reconciliation overhead.
Multi-role surface — customer, support agent, superadmin — needing strict role-based access without slowing operators down.
Operator obligations toward platform terms of service and consumer-protection law sitting outside our scope but visible from the technical platform — the system had to make those constraints expressible and auditable.

We designed the platform around a single canonical service registry, a pricing engine that lets the operator override provider markups at any level, and an audit log on every state-changing action — so the operator can demonstrate to processors, providers and authorities exactly what was charged, refilled, refunded and to whom.

Platform Scope & Capabilities

The system covers the complete order lifecycle from public discovery through payment, fulfillment, refund and reporting. Three coordinated surfaces share one backend.

Key capabilities:

Public marketing site with platform-specific landing pages and a 9-category × 13-platform service catalog (~50 final pricing pages, server-rendered, sitemap-indexed).
Customer dashboard with a 3-step order flow, balance top-up, transaction history, refill requests and an auto-boost rule editor for recurring publications.
Admin operations console with global markup, per-service pricing overrides, provider sync, order intervention (cancel, compensate, refund), user management and full audit trails.
Provider-aggregating catalog layer that ingests upstream listings, normalizes platform/service/plan, applies pricing rules and exposes the catalog to the customer site through a single read API.
Automated payment and refund pipeline aligned with regional processors, with idempotent compensation flows and human-review gates for non-trivial cases.

The platform lets the operator scale the catalog without engineering involvement: new providers, new services and new pricing rules are configured through the admin console, and the customer-facing site rebuilds the relevant pages on the next request.

Creator marketing platform — public site, customer dashboard and admin console - Image 1

1 / 57

Architecture

Backend — Java 21 with Spring Boot 3, PostgreSQL, Redis and a job queue for asynchronous provider sync, refund processing and order polling. A strictly typed REST API with role-based access enforced at the controller layer; per-endpoint audit interceptors capture every state-changing call. Frontend — Next.js 16 (App Router, Turbopack) and React 19 with TypeScript across both the marketing site and the dashboard. Server-rendered marketing pages for SEO; a client-side dashboard with server actions and React Query for live data. The admin console is a separate route segment behind an authentication guard. Catalog & pricing — a single canonical registry maps every upstream provider service to a (platform, service kind, plan) tuple. The pricing engine accepts global markup, per-service overrides, fixed-price packages and refill multipliers; quotes are computed server-side and signed before being shown in checkout, so client-side tampering cannot mismatch the actual charge.

Operator-Facing Compliance Surface

The platform itself does not assume any specific regulatory regime — that decision belongs to the operator. What we delivered are the technical primitives the operator needs to comply with whichever rules apply in their target market:

A full audit log of every charge, refund, top-up and admin override, queryable by user, by order and by time window.
Idempotent payment and refund operations keyed by external payment IDs to prevent double charges or double refunds.
Per-service terms-of-service flags and operator-configurable disclaimers surfaced in checkout when a provider requires them.
An account deletion request flow with a defined retention window for data the operator is legally required to keep.
Role-based access control with a defined superadmin / admin / support hierarchy and a separate audit feed for sensitive actions.

The operator decides which obligations apply to their market. The platform makes those decisions visible, configurable and reviewable rather than scattered across hardcoded business logic.

Engineering Highlights

The provider-sync layer ingests an upstream catalog that drifts weekly — services renamed, deprecated, repriced or split into new variants. We built a deterministic matcher that maps each upstream entry to (platform, service kind, plan) using a tunable rule set, so 90%+ of catalog changes flow through without manual intervention; only edge cases land in the admin review queue. The pricing engine separates the upstream price (provider cost) from the customer price (operator markup) and lets the operator override at any level — global, per-platform, per-service or per-bundle. Quotes are signed and short-lived, so the price the customer sees in checkout matches the charge to the cent. The admin console is built for sustained operator use: a searchable catalog (1,240 entries), keyboard-friendly modals for pricing and balance adjustments, optimistic UI for low-stakes actions and an explicit confirm dialog for anything that moves money or status.

Project Context

This was a single-vendor delivery: from initial scope through architecture, full implementation, infrastructure setup and operator handover. The screenshots in this case study were captured from a staging environment populated with English mock data; the production deployment is operated under a separate brand by the client and serves a regional CIS audience. We present this case as an engineering portfolio piece — to illustrate how we structure multi-surface SaaS platforms, separate operator concerns from product surface, and design backend primitives that let operators absorb upstream churn without breaking the customer-facing experience.

What We Delivered

Java Spring Boot backend (REST API, PostgreSQL, Redis, job queue, audit middleware).
Next.js 16 marketing site with platform-specific landing pages, services catalog and SEO-tuned service detail pages.
Next.js 16 customer dashboard: 3-step order flow, balance, transactions, support, auto-boost rules.
Admin operations console: catalog with provider sync and pricing rules, users, orders, payments, refunds, system settings.
Provider-aggregating catalog ingestion with deterministic matcher and admin review queue.
Pricing engine with global, platform, service and bundle-level overrides; signed quotes for checkout integrity.
Payment integration aligned with regional processors and idempotent automated refunds.
Role-based access control with audit trail for sensitive actions.
Bilingual content surface (operator's primary language plus an English mirror used for portfolio screenshots).

Result

The operator went live with a single-vendor-built platform covering public discovery, authenticated ordering and full operational tooling — and can now extend the catalog, adjust pricing and absorb provider changes without engineering involvement. For us, the case is a reference for how we approach multi-surface SaaS where the operator's day-to-day matters as much as the customer-facing UX: one canonical model, three coordinated surfaces, every state change reviewable. All third-party platform names referenced in the screenshots are the property of their respective owners. The platform itself is operated by an external client; we delivered the engineering only. Screenshots were captured from a staging environment populated with English mock data.