Services
Freelance & contract
UI/UX design services for SaaS and AI products.
Most of the products I work on got complicated faster than their interfaces did. A dashboard grew into six dashboards. A CRM picked up modules nobody planned for. An AI feature shipped before anyone decided how users would correct it.
That's the work: taking a system that already exists, understanding what it's actually doing, and designing an interface that matches. Here's how I usually package it.
SaaS product design
End-to-end design for platforms with real complexity underneath. I map the data model before I open a design file, because information architecture decides more than layout does.
- Deliverables
- User flows, wireframes, high-fidelity UI, interactive Figma prototypes, and a spec developers can build from without guessing.
- Best for
- Seed to Series B SaaS teams shipping a v2, or founders replacing an interface engineers built under deadline.
CRM, ERP and internal tool UX
Internal tools get used for six hours a day by people who did not choose them. Every extra click compounds. I design for repetition: keyboard paths, bulk actions with preview-then-confirm, states that tell you what changed and where.
- Best for
- Teams whose support tickets are mostly “how do I…” rather than bug reports.
Dashboard and data interface design
A dashboard should answer the question the user opened it to ask, in about five seconds. That means ranking information before styling it, and being willing to remove charts that look impressive and inform nobody.
- Best for
- Analytics products, admin panels, and reporting views that have accumulated widgets over time.
AI product and AI-CRM interface design
Designing for probabilistic output is a different job. Users need to see where a suggestion came from, how confident the system is, and how to override it without feeling like they broke something. I design the correction path as carefully as the happy path.
- Best for
- Teams adding AI features to an existing product, or AI-first products where trust is the adoption bottleneck.
Design systems and component libraries
Tokens, components, naming conventions and documentation. The components are the easy part. The naming decides whether anyone can find them a year later.
- Best for
- Teams with two or more designers, or a single designer handing off to engineering at volume.
Landing pages and conversion-focused web design
Marketing sites for technical products, designed in Figma and shipped in Framer or Webflow. Clear story, one job per section, a call to action that earns its place. I have designed 20+ Shopify landing pages and storefronts alongside the product work.
Engagement
How we'd work together
Design audit
A fixed-scope review of an existing product with a prioritised list of what to fix and why. Low-risk first project.
Project sprint
A scoped piece of work with a fixed deliverable, usually two to four weeks. Good for a single feature, one flow redesigned, or a marketing site.
Monthly retainer
An agreed number of days per month for teams shipping continuously.
Tools I work in
- 01Figma
- 02Framer
- 03Webflow
- 04Miro
- 05Adobe CC
- 06Blender
- 07ClickUp
- 08Claude Code
Files are handed over organised, named and ready for developers rather than reverse-engineered afterwards.
FAQ
Questions people ask first
01What does a SaaS product designer actually do?
A SaaS product designer decides how a software product works before deciding how it looks. On my projects that means mapping the data model, designing the flows a user moves through, building the high-fidelity interface in Figma, and handing engineering a spec they can build from. On complex products, most of the value lands in the first two.
02How much does SaaS UI/UX design cost?
It depends on scope, but the useful frame is time rather than screens. A design audit runs a few days. A scoped project sprint, one feature or one flow fully designed, usually runs two to four weeks. Ongoing product work is better handled as a monthly retainer with an agreed number of days. Tell me the problem and the deadline and I'll give you a number.
03Do you work with teams outside Bangladesh?
Yes. I'm based in Dhaka (GMT+6), which overlaps with European mornings and Australian afternoons, and I've worked with teams in the US and Canada. Most collaboration runs async through Figma, ClickUp and Slack, with calls scheduled in the overlap.
04What's different about designing an AI-powered product?
The output is probabilistic, so the interface has to do three jobs a normal interface doesn't: show where a suggestion came from, signal how confident the system is, and make overriding it feel safe rather than destructive. I design the correction path with the same care as the primary path, because that's where trust is won or lost.
05Can you work with our existing design system?
Yes, and usually that's the better outcome. I'll audit what exists, work inside its conventions, and flag the specific places where the system is fighting the product rather than proposing a rebuild by default.
06Do you do development as well as design?
I build marketing sites in Framer and Webflow, and I write enough HTML and CSS to hand off designs that account for how they'll actually be implemented. For application development I work alongside your engineering team rather than replacing them.
07How do you hand off designs to developers?
Organised Figma files with named layers, documented components, defined tokens for spacing, type and colour, and interactive prototypes covering the states that matter: loading, empty, error, and the edge cases that get discovered in QA otherwise. The goal is a developer never having to guess or ask.
08How long does a typical project take?
A design audit takes under a week. A single flow or feature takes two to four weeks. A full product v2 takes two to four months depending on how many modules are in scope. I'd rather scope a smaller first piece accurately than a large one optimistically.
09Are you available for full-time roles?
Yes. I'm open to product designer roles on SaaS or AI products, remote or Dhaka-based, where design gets involved before requirements are frozen. I also take freelance and contract work.
10What information do you need to quote a project?
What the product does, who uses it, what's breaking, and when you need it by. A link, a screenshot or a Loom is enough. No formal brief required. A budget range saves us both a round.
Contact
Not sure which one you need?
Tell me what you're building and where it's stuck. A link, a screenshot or a rough brief is enough to start from. Email reaches me fastest.