A fintech platform for Pakistan's creator and freelancer economy. Projects, invoicing, milestone payments, early payouts, and a wallet built around how creators actually get paid.
The core of how creators manage work. Each project tracks deliverables, deadlines, and payment terms in one place. Milestone-based payments let creators and brands agree on payment gates upfront — money releases when work is approved, not when someone remembers to pay.
The flow was redesigned twice based on testing. The version that shipped was significantly simpler than where we started — fewer steps, less terminology, more action.
Invoices that generate themselves from project data and follow up automatically when payment is overdue. No more manually tracking who's paid, who hasn't, and whether you sent that reminder.
Beta users told us they were spending 3–4 hours a week on payment admin. The automated follow-up system removes most of that completely — the creator sets the terms, the platform handles the chasing.
Creators shouldn't have to wait 30–60 days for a brand to process payment. Early payout lets creators draw against approved invoices immediately — for a transparent fee, shown upfront, before they commit.
The fee display was a direct result of user testing. The original flow showed the fee only at confirmation. Testers felt misled. We moved it to the very first screen — the feature became significantly more trusted once users understood the cost before making a decision.
Every incoming payment, due date, and payout scheduled on a timeline so creators can see their cash position weeks in advance. Discovered as a need during beta sessions — creators were managing this in a spreadsheet.
A proper CRM for creator-brand relationships. Track payment history, project records, and communication with every brand — no more piecing it together from DMs.
Built because testers kept asking "how do I make this official?" — a two-party e-signing flow tied directly to project terms, replacing informal WhatsApp confirmations.
A creator wallet that holds balances, tracks transaction history, and supports direct payout to local accounts. Infrastructure that works for Pakistan's payment rails.
Using Lovable early wasn't about cutting corners — it was about making the questions concrete. A working prototype forces you to decide things a Figma file lets you avoid: what happens when this field is empty? What does the confirmation state look like? What's the error copy? Getting those decisions made earlier — even imperfectly — is almost always better than deferring them to engineering.
When users clicked through the Lovable prototype, they didn't give feedback on the design — they gave feedback on the experience. They got confused, they got impatient, they asked questions the design hadn't answered. That's the feedback that actually shapes a better product. A presentation deck gets "this looks great." A working prototype gets "wait, what happens to my invoice if the brand hasn't approved the milestone yet?"
The digital agreement feature wasn't in the original spec. The early payout fee display wasn't designed that way first. The financial calendar wasn't a planned feature. All three came from listening to people use the prototype. The initial design gave us a surface to test — but the actual product was the result of iteration on real reactions from real users.
"Everything is very intention-based. Most people don't understand the value in intentional design, but they are the most impactful ones. Through the process I have learnt a lot because everything was so methodically led."