Apex Financial
A concept B2B wealth platform — designed and built in Webflow from first frame through publish.
A self-initiated concept for credible, modern B2B fintech — built to convert without generic patterns.
Apex Financial is a fictional brand — a portfolio case study built to test a full product narrative: positioning, interface discipline, Webflow architecture, and motion in one coherent build.
The brief was self-imposed: a homepage strong enough for an Awwwards portfolio review. Dark-first UI, restrained type, systematic components, motion that guides — not decorates.
Designed in Figma. Built in Webflow with Client-First and Variables. Animated with GSAP. The live site shows process and quality — not client outcomes.
Most B2B fintech homepages sound the same. The challenge was not finding references — it was building something credible enough to stand apart without inventing a client story.
Earn trust in sixty seconds — without looking like every other wealth platform template.
Category sameness
Dark gradients, interchangeable hero lines, stock UI patterns. The category trains visitors to skim past. This concept needed a distinct visual and verbal identity from the first frame.
Skeptical buyers
B2B buyers do not reward decoration — they reward clarity. Every section had to answer three questions: what is this, who is it for, and why believe it — without fake metrics or invented logos.
The brief was simple to state and hard to satisfy: feel premium, stay honest, build everything.
No client workshops to hide behind — just a clear frame for turning references into a repeatable build process.
Map the category, define the system, then earn every pixel through discipline.
Discover
Studied premium B2B fintech references and noted what felt credible versus template. Tagged patterns to avoid and qualities to borrow — editorial rhythm, honest framing, systematic discipline.
Define
Established typography, color, spacing, and component logic before page layouts. Named the system early so every section could inherit the same visual grammar.
Design & build
Built the CMS template, variables, and interactions in parallel — not as a polish pass at the end. Hero, overview, and body sections were designed as one narrative arc.
Refine
Iterated motion, hover states, and copy until the concept felt finished — not just populated. Every animation had to clarify hierarchy, not decorate it.
Design lens
Editorial hierarchy over decorative noise
Conversion-minded restraint, not landing-page hype
Honest concept framing — no fake client theatre
Build lens
Client-First structure with scalable class logic
CMS-driven template for repeatable case studies
GSAP motion with reduced-motion fallbacks
The process was the product — the site had
to prove systematic thinking, not just taste.
The interface had to feel finished before the copy was final — hierarchy, spacing, and contrast doing the persuasive work.
Dark-first UI that earns trustthrough restraint, not decoration.
Concept interface moments — built to demonstrate discipline, not shipped product screenshots.
Every meaningful choice carried a trade-off. These are the decisions that shaped the system — not the defaults the category would have handed us.
Restraint at the system level beats decoration at the component level.
Light editorial UI
Cream canvas, navy type, gold only where attention needs to land.
Dark gradients read as fintech wallpaper. Apex needed calm credibility — a surface that lets hierarchy and typography do the persuasion.
Typography as structure
Serif headlines, sans UI, strict type scale with no arbitrary sizes.
B2B buyers scan before they read. With placeholder copy throughout, the rhythm of headlines and labels had to carry meaning from day one.
Client-First architecture
Global classes, variable-driven spacing, CMS-ready page templates.
A concept case study still has to prove the build scales. The reusable template is part of the argument — not an afterthought.
What we chose
What we avoided
The best portfolio work doesn't pretend to be a case study with metrics.
It shows the thinking, the system, and the finish.
A concept project has no client results to report. What it can prove is process — and whether the work holds up as a portfolio argument.
Proof of discipline, not proof of performance.
End-to-end build
From brand surface to CMS template — every layer was designed, built, and published as one coherent argument.
Reusable system
The case study template is not a one-off page. It is a scalable CMS structure any future project can inherit.
Honest positioning
No inflated metrics, no fake testimonials. The work speaks through structure, typography, and finish — not invented ROI.
This project exists to show how I think, build, and finish — not to simulate a client win.
You've read one chapter. The portfolio doesn't stop here — one case study is live, more are in build, and the index stays open.
Keep exploring the work.
01 · Published
02+ · In build
Archive · Always open
When the next case publishes, it lands here first.
Until then — the full index holds every project.
If this case study read like the kind of process your next build needs — the conversation starts here.
Open to serious Webflow projects.Built on clear goals and shared direction
Based in Belgrade · Working remotely worldwide.