Skip to content
Selected work

Full-stack engineer (team delivery) · 2025

Client delivery · anonymized under NDA

US Business-Formation & Operations Platform

A B2B SaaS for international founders expanding to the U.S., spanning guided company formation, payment state, document delivery, internal review workflows, and provider-gated post-formation setup surfaces.

US business-formation and operations platform - system architecture
US business-formation and operations platform - system architectureOpen largerimage opens in a new tab

01 Scope

The product context behind the work.

Problem

The product needed to turn a fragmented, high-trust process into one guided operating system: founder intake, company structure, ownership details, payment state, legal document delivery, admin review, mail/address handling, communications, and banking setup gates all had to stay tied to the right organization.

My role

  • Worked across the guided formation application: structure, company name, business description, founders, ownership, equity terms, roles, 83(b), review, and payment
  • Supported the founder dashboard, start/manage surfaces, document vault, and provider-gated setup surfaces for virtual address, mailroom, business phone, and bank setup
  • Connected product state through organization-scoped auth, Postgres/Prisma records, Supabase document storage, payment intents/webhooks, and provider-gated integrations
  • Supported internal admin workflows for organization review, formation task advancement, document upload/categorization, and status updates

02 Approach

How the work was shaped.

This was delivered for a client under NDA, so it is shown here without identifying details - the focus is on the architecture and the work performed, not the client identity.

The product is a B2B SaaS for international founders expanding to the U.S. The founder side covers organization setup, a guided formation application, payment state, and a document vault. The post-formation side keeps provider-gated setup surfaces tied to the same organization record, including virtual address, mailroom, business phone, and banking setup gates.

The core challenge was keeping a complex process coherent. A founder can move through company structure, name, business description, founders, ownership, equity terms, roles, 83(b), review, and payment. At the same time, the internal team needs to review the organization, advance formation tasks, upload and categorize documents, and keep the founder-facing status current.

Underneath, the system connects a Next.js dashboard, organization-scoped auth, Prisma/Postgres state, Supabase document storage, payment-intent and webhook state, admin workflows, and provider-gated integrations for mail, address, communications, and banking-related setup.

Because this is sensitive client work, the public case study uses architecture diagrams instead of screenshots. That keeps the proof useful for technical buyers while protecting founder data, legal documents, banking details, mail/phone information, and client identity.

Gallery

Architecture and flow.

How a founder moves from formation request to post-formation setup
The platform connects founder intake, payment status, internal review, document delivery, and provider-gated setup surfaces into one organization-scoped workflow.Open largerimage opens in a new tab

03 Outcome

What the work made clearer.

Qualitative outcomes

Formation journey

Organization setup -> guided intake -> payment state -> admin review -> document vault

Post-formation setup

Virtual address, mailroom, business phone, and banking setup gates surfaced through org-scoped provider configuration

Architecture

Next.js dashboard, Clerk org context, Prisma/Postgres, Supabase storage, payment webhooks, admin console, and provider-gated integrations

Stack

Next.jsTypeScriptReactSupabase / PostgresPrismaClerkTailwind CSS

Reflections

  • For business-formation products, trust is mostly sequencing and state clarity: founders need to know what is next, while the internal team needs the same record to drive filings, documents, and status updates.
  • The strongest public proof for this project is architecture, not screenshots - diagrams show the product complexity without exposing legal, banking, mail, phone, or client identity data.

Next step

Have a similar project?

If this looks close to the product work you need, use the contact path and I will help scope the next step clearly.

Book a call