Role
Sole product designer
Products
Web app
Timeline
5 weeks (2026)
Status
Live
Tools
Figma
Before: documents are read-only.

Before: flat surfaces, little depth.

Forms nobody could configure. Documents were uploaded by the admin and then frozen. Without fields, there was nowhere for the investor, advisor or fund manager to act inside them, and nothing the admin could change when requirements changed.
A flat interface. The client felt TSG Invest was too flat, with contrast problems, and wanted to move to the TerminaONE identity.
An admin builds the form
1.Template Studio - Document Management
2.The three-panel editor and the publish popup.

3.The same document moves through four roles
1.Investor chooses an account, sets units and signs the required fields inside the document.

2.Advisor reviews the signed documents and approves or rejects, with a reason when rejecting.

3.Investor sees the decision and pays.

4.Fund manager confirms payment and countersigns.

Three panels instead of hidden tools
The editor held a PDF, settings, role assignment and guidance on one screen. Hiding tools in menus would have calmed it, but admins could miss something. I grouped everything by job instead: field settings on the left, the document in the centre, roles on the right, with a four-step guide in the empty state.
Full freedom that still feels safe
Admins can create any field, so I took Google Forms as a reference for making that easy. Every field type has its own icon, and every field is tagged to the role that fills it. Fields auto-save.
Account types chosen at publish
This was my idea. Account types are what apply once a template is published, so the choice sits inside the publish confirmation, and “Save & Publish” stays disabled until mandatory values are filled. Admins confirm the template and its audience in one step.
Purple, dark and glass for depth
We presented three options and the client chose mine. Purple felt futuristic and readable, with a hint of AI and fintech. I added glassmorphism, dark surfaces and a clearer hierarchy, and the client, developers and BA all responded well.
1.The three-panel editor and the publish popup.




Explore first, ask later:
Friendlier, but can’t tell serious users from casual ones.
Ask before entry:
A stronger filter, but more friction.




Light theme
What it was: The usual healthcare look, which I recommended
Why it changed: The client chose dark mode
Final: Dark with glassmorphism
What it is: A midnight blue and cyan palette, with glassmorphism and rounded corners
Why it works: It stands apart from standard white therapy apps




Design the failure first.
Patients didn’t worry about the smooth path. They wanted to know what happens to their money when a session breaks. Now I start there.
Ask about regulation in week one.
Country rules arrived late and forced me to change finished flows. Next time I’ll ask which rules apply before I draw anything.
Bring builders in early.
Developers and the BA settled Stripe’s rules with me, and a developer confirmed my photo-card worry. I leave to the client what is theirs to decide, and take the rest to the builders.
Disagree once, then make it work.
I lost the dark mode and the three-step gate arguments, and the 48-hour lockout was set by the client. I made each one feel calm, short and caring.
One designer means watching consistency.
Designing three apps alone showed me the whole chain, but small mismatches can slip in.











