ValPay Labs: one home for every tool

Role and scope

Leadership: Project lead · Role: Technical Program Manager + product design · Infrastructure: Cloudflare + AWS · Identity: AWS Cognito · Access: Unified sign-in + product-scoped roles · Collaboration: Kenneth Fallon

Collaborator: Kenneth Fallon.

Context

ValPay’s internal and partner tooling had grown into a real product suite, but discovery, access, ownership, identity, and status still needed a single front door. ValPay Labs turns that collection into a clear platform story for employees, partners, and stakeholders.

One product layer, not disconnected microsites

I shaped Labs as the umbrella across Partner Portal, Admin Console, Deskly, and Success Hub. The suite makes the shared model visible: one identity, one design language, and tooling that plugs into common systems instead of starting from scratch each time.

Shared infrastructure, deliberately boring

Cloudflare provides the edge layer for fast delivery, DNS, TLS, caching, and front-door protection. AWS carries the core application services behind the suite. Common environment patterns, API boundaries, monitoring, deployment safeguards, and role-aware access give each product a production foundation without forcing every team to rebuild the plumbing.

One sign-in, permissions that still mean something

AWS Cognito provides the common authentication and session layer across the ValPay product ecosystem. A user signs in through one shared identity path; each product then applies its own role, portfolio, and operational scopes. That keeps the experience unified without flattening the difference between an employee, partner, administrator, or merchant-facing user.

Build once, extend across the suite

Shared authentication guards, token handling, design primitives, configuration, and deployment conventions let a new Labs product enter the ecosystem by adopting the foundation rather than inventing another account system. Product teams can spend more time on the workflow that makes the tool useful and less time recreating infrastructure.

Make the operating model part of the product

The site explains how Labs works—built from real friction, tested internally first, integrated once, and developed against an open roadmap. That framing helps people understand why the tools exist and gives stakeholders a clearer way to evaluate what should ship next.

Roadmap as interface

Live status, intended audience, and next steps sit alongside each product rather than disappearing into an internal document. Access requests and product updates use the same surface, reducing the distance between a user need and the team that can act on it.

Outcome

ValPay Labs gives the product suite a coherent home, with live products, working prototypes, and concepts clearly distinguished. Partner Portal is live in production; Deskly is a working prototype; Admin Console is a concept refresh.