Invela pt.1

Designing trust infrastructure for regulated data ecosystems
Role: Creative Director / Head of Product Experience Scope: 0 → 1 product design, experience architecture, platform workflows Timeline: 1.5 years in Stealth · 6 months live Environment: Regulated open-finance ecosystem

Invela builds shared trust infrastructure for regulated data ecosystems where access, compliance, and third-party risk intersect. Over six months, I served as the founding design and experience lead, taking the platform from concept to production — establishing the architecture and workflows that supported customer validation and a $XXM funding round.

Invela Platform Interface

Trust First

Designing for regulated financial data ecosystems — particularly under evolving frameworks like Section 1033 of the Dodd-Frank Act — means optimizing for trust, traceability, auditability, and regulatory defensibility, not speed or surface-level polish. The work required translating statutory requirements, CFPB rulemaking guidance, data access rights, liability frameworks, and third-party risk obligations into operational workflows that operators, compliance teams, executives, auditors, and investors could all clearly understand — and stand behind.

01

Regulatory Experience Architecture

I defined the core system architecture and guided two senior UX designers and a front-end refinement team through execution. My role focused on translating regulatory and governance requirements into structural design principles, ensuring every visual and interaction decision aligned with compliance and operational defensibility.

02

Unified fragmented risk into a single experience layer

Risk data lived across documents, vendors, contracts, spreadsheets, and disconnected tools. I designed a unified experience model that brought visibility to the full data-access lifecycle — from onboarding through continuous monitoring. This shifted the product from point-solution thinking to system-level risk visibility.

03

Designed for ecosystems, not single organizations

Invela required trust between independent organizations with asymmetric risk. I focused on experience patterns that supported shared accountability, standardized workflows, and defensible decision-making across participants. This enabled the system to scale across ecosystems rather than optimizing for a single organization.

Product Dashboard Main View
01 / Dashboard Overview — Unified Risk View
Product Dashboard Main View
01.2 / Parse Ai Tool Modal
Compliance Workflows
02 / Compliance Workflows — Audit Trail
Data Access Control
03 / Data Access Control — Granular Permissions
Data Access Control
04 / Data Access Control — Granular Permissions

Building under constraint.

The platform was developed within active regulatory uncertainty, investor oversight, and multi-party workflow complexity. I led experience architecture from discovery through production — translating policy and governance requirements into executable product logic.

Key constraints
  • Regulatory ambiguity
  • Investor scrutiny
  • Multi-party workflows
  • Compressed timeline
  • Limited historical data
Key metrics

These outcomes reflect execution under regulatory, operational, and investor constraints — not vanity growth.

0 → 1 in 6 months

Took the platform from initial concept to a production-ready system in under six months, establishing core product architecture, experience patterns, and workflows suitable for regulated environments.

$XXm raised

The product and experience foundation supported investor validation and contributed to a successful $XXM funding milestone, demonstrating market confidence in the platform’s approach to open-finance risk and trust infrastructure.

Final thoughts

Work represents a snapshot in time. Details are shared at a high level due to confidentiality.

Disclosure & Consent Builder pt.2

Operationalizing consent in open-finance ecosystems
Role: Creative Director / Head of Product Experience Scope: Consent workflow design, experience architecture, platform tooling Timeline: 1.5 years in Stealth · 6 months live Audience: Financial institutions, platform operators, compliance teams

In open-finance systems, consent is not a screen — it is a governed, stateful process. Institutions must author disclosures, define duration, manage version history, and ensure the consumer experience precisely reflects what compliance approved. This work transformed consent from brittle, hard-coded implementations into a configurable, auditable workflow that institutions could operate safely at scale.

Disclosure Builder interface

Where policy becomes product logic

Every disclosure, duration setting, and approval state carries downstream risk implications. This work focused on embedding governance directly into the configuration layer so operational flexibility never compromised regulatory control.

01

Consent as stateful infrastructure

I reframed consent as a multi-stage system (initiation → disclosure → authentication → authorization → confirmation), making regulatory checkpoints explicit within the product architecture. This created flexibility for policy evolution without requiring structural redesign.

02

Configuration with structural guardrails

Institutions require flexibility — but compliance cannot drift. The builder enables disclosure authoring, duration controls, and CTA configuration within enforced validation rules, required fields, and defensible defaults.

03

Admin intent → consumer fidelity

Configuration is meaningless if rendering diverges. I paired the builder with a live mobile preview, surfaced version history and approval states, and made ownership and timestamps visible — ensuring the rendered experience matched approved language, end-to-end.

01 / Builder Overview — Workflow + Validation
Modal / tool state Approval and status Consumer preview Consent configuration

End-to-end system design

The Disclosure & Consent Builder spans administrative configuration, compliance validation, and the rendered consumer experience. I designed the workflow architecture, interaction model, and guardrail logic to ensure institutional flexibility without compromising regulatory defensibility.

Key constraints
  • Regulatory ambiguity
  • Investor scrutiny
  • Multi-party workflows
  • Compressed timeline
  • Limited historical data
Key metrics

These outcomes reflect long-horizon execution under regulatory, operational, and investor constraints — prioritizing durability and trust over speed or vanity growth.

Stealth → Public Platform

Established the core consent architecture, interaction patterns, and configuration tooling required for a production-ready, regulator-aligned platform.

$XM raised

The structural integrity of the consent and governance systems supported investor validation and contributed to a successful capital raise.

Final thoughts

This work represents an early production phase of the platform. Specific implementation details are summarized at a high level due to confidentiality.