Design and Development of Finlancr App Landing page by Zakria AsimDesign and Development of Finlancr App Landing page by Zakria Asim
Built with Framer

Design and Development of Finlancr App Landing page

Zakria Asim

Zakria Asim

Why does every freelancer finance app assume you live and earn in one currency?

Finlancr is a personal finance app I designed and built myself, for Pakistani freelancers who earn in USD and spend in PKR. This is not a concept project, it is the real live app, and this landing page is its actual marketing site.

First flow - Hero

Context:
this is the first ten seconds, a freelancer landing here needs to instantly get what makes this different from every other budgeting app.
What I did:
I opened with "Built for freelancers to manage money" as the headline, paired with three quick tags right above the app screenshot, USD + PKR tracking, real-time tracking, private cloud sync. I kept the CTA choice simple, Download the app as the primary action, See Benefits as the secondary one for people who need convincing first.
Why this matters:
a freelancer scanning a landing page decides in seconds whether this app is for them. Leading with the dual-currency angle instead of generic budgeting language tells them immediately this was not built for a salaried employee, it was built for exactly their situation.

Second flow - Problem

Context:
before selling the solution, I needed the visitor to feel understood.
What I did:
I kept this to one line, "Clients, payments, currencies and everyday expenses are constantly moving." No bullet list, no long paragraph, just enough to name the chaos freelancers already live in.
Why this matters:
freelancers already know their problem, they do not need it explained at length. The job of this section was not to educate, it was to nod and say I get it, so they keep scrolling with trust instead of skepticism.

Third flow - Solution and Features

Context:
this is where I had to prove the app actually solves what I just named, without turning it into a spec sheet. What I did:
I split it into five features, each with its own screenshot, Dual-Currency Tracking, Smart Fund Allocation, Private by Design, All Your Money in One Place, and Know Your Financial Story. Each one gets a short, benefit-first line instead of a technical description. Smart Fund Allocation, for example, is framed around not distorting income or expense stats when moving money between wallets, not around how the transfer mechanism actually works. Why this matters:
a freelancer does not care how the currency locking works internally, they care that moving money between Payoneer, SadaPay, and a bank account will not quietly mess up their monthly numbers. Writing every feature from the outcome side keeps the section scannable instead of turning into documentation.

Fourth flow - How It Works

Context:
after features, people still ask, okay but is this actually simple to start using. What I did:
I broke onboarding into exactly three steps, Add new account, Log it your way, See your financial story. Step two specifically calls out logging income in USD and expenses in PKR without forcing a single currency choice. Why this matters:
three steps is close to the psychological ceiling before something starts to feel like a chore. Calling out that they can log in whichever currency is natural to them directly answers the anxiety this exact user has been carrying through the whole page, will I have to do currency math myself.

Fifth flow - Testimonials

Context:
by this point the visitor believes the idea, now they need to believe real people use it. What I did:
I used four testimonials, each tied to a specific freelance role, an Upwork freelancer, a product designer, a full-stack developer, a creative director, so different visitor types can see themselves in at least one. Each quote names a specific pain, USD to PKR math, juggling three apps and a spreadsheet, not trusting bank logins, planning tax reserves, instead of generic praise. Why this matters:
vague five-star quotes get skipped, specific ones get read. Matching the testimonial roles to the range of people who would actually land on this page means almost every visitor finds one that mirrors their own situation.

Sixth flow - FAQ

Context:
the last hesitation before download is almost always trust and effort, not interest. What I did:
I kept the FAQ to five questions, all aimed at removing friction, is my data private, do I need to connect my bank account, what happens if the exchange rate changes later, do I need to sign up, where is my data stored. Why this matters:
these are not feature questions, they are risk questions. A freelancer worried about bank passwords or sign-up walls will bounce before ever opening the app, so this section exists purely to remove the last excuse not to download.

Final flow - Closing CTA

Context:
the page needed to end on the same emotional note it opened with. What I did:
I closed with "Stop converting currencies in your head" instead of a generic get started line, paired with a two-minute promise right before the final download button. Why this matters:
it echoes the exact mental tax the whole page has been talking about, so the last thing a visitor reads is the same relief they were promised at the top, not a disconnected sales line.
Designed and built in Framer.
Like this project

Posted Sep 12, 2026

Designed and built a sleek beautiful and well thought landing page dsign in framer.