All projects

Carta

Capital Call Workflow

Turn high-stakes notices into an auditable workflow.

Role
Product Designer
Duration
2018 – 2020
Platform
Web · Enterprise SaaS
Team
1 PM, 4 Engineers, Investor Services partners
Users
Fund Administrators, Investor Services, GPs
Focus
Enterprise · FinTech · B2B

I led workflow architecture, structured forms, dynamic content, and review states.

Capital Call Workflow

Overview

The workflow connects structured fund data, investor-specific content, and send readiness in one place.

Fund notices were still assembled by hand outside the platform.

0→1
Notice workflow launched
3
Core steps in flow
LP-scale
Dynamic personalization

Problem

Critical Notices Were Assembled by Hand

Teams copied templates, reconciled values line by line, and rewrote the same language for every investor.

  1. Structured fund data lived outside the document
  2. Investor values were easy to mis-enter
  3. No shared definition of send-ready

Core decision

Constrain the Workflow. Personalize the Output.

Fund data became structured input. Investor-specific language came from dynamic fields. Review state decided when the notice could move forward.

Principles

  1. One path from data entry to dispatch
  2. Dynamic fields replace manual substitution
  3. Section status gates final send

Product system

Draft, Review, Send

Dense tables handle allocations. The editor handles reusable legal copy. The review screen shows exactly what remains before send.

Readiness and personalized content stay inside the same workflow.

Impact

From Manual Docs to Send-Ready Workflow

The notice became a product state, not a file passed between people.

3-step
Create → Review → Send
Section
Completion visibility
LP
Dynamic personalization
Single flow
Draft to dispatch

We finally had a clear path from distribution drafting to a send-ready notice without piecing documents together manually.

Investor Services Lead

Venture Fund Operations

Reflection

Key Learnings

  1. 01

    Documents Need Product-Grade State

    A draft becomes trustworthy when readiness is explicit.

  2. 02

    Structure the Flexibility

    Dynamic fields preserved personalization without sacrificing consistency.

  3. 03

    Density is a Feature

    Operations needed hierarchy and validation—not less information.