back homeFlagship FDE case
Rely: company operations made visible.
The flagship FDE case: a real business process with customers, admins, documents, provider states, and production constraints.
Ambiguous operations to product
Rely
Company operations made visible for non-US founders and internal teams.
open case- Role
- Mapped founder and operator workflows, then shipped customer/admin surfaces over provider-heavy operations.
- Outcome
- A complicated company process became visible, stateful, and easier to operate.
- Evidence
- Public Rely site, sanitized product surfaces, production-backed workflows.
- Context
- LLC formation mixes filings, documents, banking steps, provider states, deadlines, and support.
- Built
- Customer onboarding, dashboard states, document surfaces, admin queues, and provider flows.
- Stack
- React, TypeScript, Kotlin/Spring Boot, PostgreSQL, Auth0, Stripe, R2, third-party APIs.
- Proof
- Public site and sanitized product work; no customer data shown.
case notes
The product had to show the work.
Rely is not only a marketing site. It has to make a complicated company process understandable to founders and usable for operators.
Guided formationDashboard statusDocumentsAdmin toolsProvider APIs
what I focused on
- Turn formation progress into clear customer states.
- Give admins enough context to act without digging through systems.
- Keep document, filing, provider, and support flows readable.
- Expose progress without exposing private customer data.
fde signal
- Ambiguous business process.
- Multiple external systems.
- Customer-facing surface plus internal operations.
- Production constraints instead of a clean demo.