7 case studies
Fintech
Wallets, investing dashboards, lending flows and fintech websites, with sign-up, identity checks and payment screens designed around the rules.
See fintech work →Product design and build, by industry
Every sector brings its own users, rules and data. These pages show the work my team has done in each one, the regulations I design around, and how a project runs, so you can judge the fit before we talk.
25 case studies on this site, designed by my team and built in React, Next.js, React Native and Flutter.

Each page has the case studies, problems, rules and questions for that sector.
One project each so far, so they sit here with their case study until there is a second.
04 differences
The method stays the same. These four things are what I relearn for every sector.
A trader, a nurse, a dispatcher and a first-time buyer read a screen differently. I start each project by finding out who uses it, where, and under what pressure.
Strong customer authentication in payments, privacy in health, permit numbers on property ads. Each industry page names the rules and links the regulator, so the design is checked against them early.
Balances that must reconcile, records that must not be lost, live locations that move. The data decides the empty, loading and error states, which I design before the busy screen.
In fintech it is a clear fee and a confirmation; in healthcare it is calm language and privacy; in SaaS it is a dashboard that matches the invoice. I design for that sector's version of trust.
A free 30 minute intro call, then a written scope and one fixed quote for the whole project, with no retainer and nothing billed by the hour.
We talk through the product, the users and the rules that apply. I send a written scope and one fixed quote.
Sprints in Figma with a review call each week and a written update in Slack every 48 hours.
The industry's rules and accessibility (WCAG 2.2) are checked against the flows before handoff, not after launch.
My team builds in TypeScript, React and Next.js, and React Native or Flutter, with the design system named the same in Figma and code.

Product design · Logistics
Ordering, tracking and on-time delivery in one mobile app, with the research and persona work behind it.
View case study
Product design · AI
Photograph a room, pick a style, get an AI redesign in seconds. The full iOS app, from user flow to final UI.
View case study
Website design · HR tech
A new website for core.hr, the HR tech company formerly CoreHR, designed together with its app visuals.
View case study
Website design · Product design · Real estate
An AI real estate platform for the UAE market: the website and the product screens.
View case study
Website design · Health
Website and app screens for a digital health platform that makes recovery feel human.
View case study
Product design · Healthcare
A mobile healthcare app, from user research and wireframes to the final UI.
View case studyThe same six services, shaped for each sector.
Working with Jubayer and the team has been a blast. Their creativity has honestly taken our platform to new heights. Incredibly professional and so proud to work with, we’re over the moon with their results, and we can’t wait to team up with them again.

I highly recommend Jubayer for any design project. He quickly grasps complex concepts, excels in standard design practices, and responds promptly.

No. These are the sectors with more than one project on this site, so each has its own page. I have also designed for HR tech, legal, marketing tech and agriculture, and the method carries over. In the intro call I tell you honestly how close your product is to work I have done.
Yes. I design the screens around the rules that apply, such as strong customer authentication, KYC, HIPAA or the FCA's Consumer Duty, and I name them on each industry page with links to the regulator. Your compliance and legal team make the final call; my part is making the rules usable.
Rarely, and that is fine. What carries over is the pattern: how a payment is confirmed, how a booking fails safely, how a dashboard shows exceptions. I show the closest work in the intro call and explain what would be different in yours.
It depends on the number of flows, roles, platforms and languages, and on how much of the industry's rules the screens must carry. After the intro call I send a written scope and one fixed quote for the whole project, with no retainer and no hourly billing.
Both. I design the product and stay with it into production: my team builds web apps and front ends in TypeScript, React and Next.js, and iOS and Android apps in React Native or Flutter. We use AI coding tools where they save time, and a person who knows the design reviews every change.
I work from Dhaka (UTC+6, Sunday to Thursday) with founders in Europe, the US, the Gulf and Asia. I hold evening calls from 7 to 10 pm Dhaka time for the Americas, and every week has a review call and written updates.