Resolutions for Filio
End-to-end shareholder resolution workflow for VC fund GPs — from drafting and template selection to LP signature collection, reconciled in one place.
GPs handling shareholder resolutions face a slow, manual process.
VC fund managers draft resolution documents in Word, email them individually to LPs, chase signatures across inboxes, and reconcile responses by hand. For funds with 50–200 LPs per resolution, this can take weeks — and it's a process that only gets run a handful of times a year, so no one ever gets faster at it.
Filio needed a purpose-built resolution workflow that GP teams could use without legal or ops overhead: one place to create, send, track, and close out a resolution.
Legal-weight documents that still feel fast to produce.
The core tension was dual. The product needed to feel serious enough for legally binding documents — no sloppy edges, no ambiguity about what LPs would receive — while remaining fast enough that a busy GP would actually choose it over firing off another email.
Most fund admin software over-engineers the problem with approval chains, rigid templates, and role-based permissions nobody asked for. The real need was simpler: a focused wizard with minimal inputs, maximum output quality, and a live preview so GPs can see exactly what an LP will open before they hit send.
A GP shouldn't have to imagine what a resolution looks like. They should see it being drafted as they type.
— Design principleA split-screen wizard anchored by a live A4 preview.
I designed a two-step creation flow: controls on the left, a real-time document rendering on the right. Every field change — title, recipients, resolution body — instantly reflects in the preview pane, eliminating the usual uncertainty of "will this look right when it arrives?"
Template selection was surfaced as the primary early decision. Six pre-built resolution types — Standard, Budget, Exit, Amendment, Dividend, and Custom — cover the most common GP needs. This removed blank-slate paralysis without taking flexibility away from teams that need it.
Restraint as a signal of seriousness.
The design system uses a deliberately narrow palette — pure white surfaces, a single #EBEBEB hairline, Geist for the UI chrome, Georgia for the document preview. The material difference between "app" and "legal document" is immediate: the left half is a tool, the right half is the paper that LPs will actually sign.
On the recipient step, each LP is rendered as a chip showing their share percentage, so GPs can eyeball who's included and whether the maths adds up before sending. This addresses a specific anxiety in the existing email workflow — "did I forget anyone? are the percentages right?" — by making the answer visible at a glance.
The signature collection stage mirrors the creation view: the document stays anchored on the right, while the left column tracks who's opened, who's signed, and who still needs a nudge. GPs send reminders inline without composing new emails.
From weeks of email threads to a single workflow.
Resolutions shipped as a functional HTML prototype detailed enough to demo the full creation-to-sign workflow end-to-end, with the live preview and recipient logic fully interactive. The prototype was used in customer conversations to validate the wizard approach and was adopted directly as the reference for engineering implementation.
The live-preview pattern and document rendering system were carried forward into the production build. The bigger outcome was organisational: the prototype gave the Filio team something concrete to agree on, which compressed the usual cycle of spec debates into a single-afternoon review.