MVP development for startups, from the developer who also designs your product

Most MVP development services leave founders translating between a designer and a coder; I do both, so your React app ships looking like its Figma file. I'm Maniruzzaman Jubayer, and I work with founders across Europe, the US, the Gulf and Asia in hours that overlap theirs.

Free 30 min intro call · One fixed quote · No retainer

Founders in SaaS, fintech and AI build with me

Raised by my clients
$30M+
Monthly visits on client platforms
10M+
Client satisfaction in project reviews
90%
Companies helped
50+
Years building web and mobile apps
6+
Behance features
20+

Trusted by teams at

  • boon
  • Asendia AI
  • sitecove
  • mergepoint.ai
  • Parfait Art Logistics
  • oneclick

Designed and built by Maniruzzaman Jubayer, design engineer.

Why startup web apps drift away from their design

These are the four problems founders describe on almost every first call with me.

Design and code live in different heads

When one studio designs and another builds, spacing, empty states and error messages get guessed.

I design and build from one Figma file and one Slack channel, so nothing is lost inside a handover document that nobody reads twice.

The quick MVP now fights every feature

Fast first builds often skip shared components, so each new feature copies old code and every copy breaks in its own way.

I start with a small component library in code that mirrors the design system, and assemble every screen from it.

AI features that users do not trust

A model reply that appears after a long silence feels broken, and an answer without a source feels made up.

I stream responses, show where answers come from, and build the loading, failure and undo states around the model.

Speed that nobody owns

Every release adds a library and a little weight, until pages lag on a mid-range phone. Google counts a page as good when its main content appears within 2.5 seconds, so I measure that on real devices and treat a slow page as a bug.

Products I designed, the kind I build in code

A healthcare SaaS, a delivery app and a fintech SaaS website, all designed by me. Each shows the level of interface detail I carry into React.

VitalHealth: A healthcare SaaS for finding and booking doctors

Product design · Healthcare

VitalHealth

A healthcare platform with more than 50 screens, from the design process to the final dashboard.

Read the case study →
Shipora: A delivery app built around live tracking

Product design · Logistics

Shipora

Ordering, tracking and on-time delivery in one mobile app, with the research and persona work behind it.

Read the case study →
Fintech SaaS website: A product website for a fintech SaaS

Website design · Fintech

Fintech SaaS website

A dark, product-led website for a fintech SaaS, designed for Webflow.

Read the case study →

Does your live app look nothing like the Figma file? Let's close the gap.

Book an intro call

SaaS web application development: what I deliver

Production code from the person who drew the screens, written so your own engineers can keep going after I leave.

App Router pages, server components where they help, and every state from the design: loading, empty, error and success, on desktop and phone.

Tokens for colour, type and spacing, plus documented components, so your next developer builds a feature without reinventing the button, the table or the form.

Sign-in, data fetching, caching, forms and validation connected to your API or database, whether that is Supabase, Postgres or a service your team already runs.

Streaming replies, visible sources, stop and retry controls and honest limits around your model, using the patterns in my guide to shipping AI features people trust.

Core Web Vitals measured on real phones, semantic HTML, keyboard access, metadata and structured data, so the app works for people and for search engines.

Readable TypeScript, tests on the risky paths, a written README and a recorded walkthrough, with the repository and cloud accounts in your name from day one.

How a build with me runs

Four steps from first conversation to a shipped product, with the price agreed before any work starts.

  1. 01

    Free 30 minute intro call

    Tell me what the product does, who uses it and what already exists. I will say plainly whether I am the right fit and what I would build first.

  2. 02

    Written scope and one fixed quote

    Every screen, integration and state goes on paper with the stack and the timeline, priced as one project. You approve a single number, and there is no retainer.

  3. 03

    Design and build sprints

    Weekly sprints in your repository. Design and code move on the same feature in the same week, and every pull request comes with a preview link you can click.

  4. 04

    Launch and handover

    Speed and accessibility checks, a calm release, then a README, tests and a recorded session that brings the engineers you hire next up to speed.

Working with me

Time zone
UTC+6, working remotely with founders abroad
Shared hours
the afternoon with Europe, most of the day with the Gulf and Asia, and evening calls for the US
Stack
TypeScript, React and Next.js, hosted on Vercel, Cloudflare or your own cloud
Ways to talk
Slack, video calls on Google Meet and comments on your pull requests

Industries I build web apps for

Each sector asks something different of a front end. The images come from real work I did in that field.

  • SaaS and B2B tools: a screen from a product I designed

    SaaS and B2B tools

    Dense tables, filters, roles and permissions, and reporting views that hold up under real data. Business buyers judge a product by how quickly they finish the dull task they repeat every day.

    My b2b saas work →
  • Fintech and wealth: a screen from a product I designed

    Fintech and wealth

    Charts that update smoothly, numbers that never round wrongly, firm confirmation steps and clear audit trails. In a finance product, trust is earned one screen at a time, and lost the same way.

    My fintech work →
  • Healthcare: a screen from a product I designed

    Healthcare

    Scheduling, records and patient flows that busy staff use between appointments, with careful permissions and accessible forms. Here clarity matters far more than decoration, and every extra click costs time.

    My healthcare work →
  • Logistics and mobility: a screen from a product I designed

    Logistics and mobility

    Live maps, status timelines and dispatcher views that update in real time, plus phone screens for drivers who work outdoors with one free hand and a weak signal.

    My logistics work →
  • AI products: a screen from a product I designed

    AI products

    Streaming results, visible progress, sources, and controls to stop, retry or undo. The interface around the model decides whether people believe what it produced and come back tomorrow.

    My ai products work →
  • Real estate and proptech: a screen from a product I designed

    Real estate and proptech

    Listings with maps and filters, agent dashboards and enquiry flows, where image-heavy pages still have to load quickly on a phone held in a viewing.

    My real estate work →

How I work with founders abroad

Remote does not have to mean distant. This is how I stay close to your team.

My day
Your day

7hours of your working day overlap mine

  • You talk to me, the maker

    No account managers. I design and build your product, answer you directly in one shared Slack channel, and lead the weekly call myself.

  • Hours that overlap yours

    I share the afternoon with Europe and most of the day with the Gulf and Asia. For the US, I keep evening calls, 7 to 10 pm my time, which is your morning.

  • Everything written and tracked

    Figma for design, your repository for code, a written Slack summary every 48 hours, and working software on screen at each weekly review, never slides.

  • I know your market

    Right-to-left Arabic layouts, national sign-in systems such as Smart-ID, local payment methods and privacy rules go into the scope, not into a fix after launch.

Hire a Next.js developer in-house, use a freelancer or work with me

Each choice suits a different stage. Here is where each one is strong, and where it is not.

Compare with
With me5 of 7
In-house hire2 of 7
What you getWith meIn-house hireFreelancer
Design and code from one accountable personYesNoSometimes
No hiring process before work beginsYesNoYes
Several senior skills on one projectYesSometimesNo
Work continues through holidays and sick daysYesNoNo
Price fixed before the first sprintYesNoSometimes
Knowledge stays inside your company for yearsSometimesYesNo
Physically in your officeNoYesSometimes

Founders I work with

Four kinds of founder bring their build to me. Most arrive with a design, a deadline or both.

Pre-seed and seed startups

You need a first version that looks credible to users and investors, and you cannot spend months hiring. I design and build the MVP, then hand it cleanly to your first engineer.

Scale-ups with a crowded roadmap

Your engineers own the core product. I take a defined piece, such as an admin tool, a customer portal or a new onboarding, and build it to your conventions and review rules.

Founders outgrowing a no-code build

Your Framer, Webflow or Bubble product has hit its limits. I help you decide what should move to Next.js, using this comparison, then rebuild it without losing what works.

Teams launching in a new market

Entering the Gulf, Europe or Southeast Asia brings new languages, sign-in systems and rules. I plan right-to-left layouts, local identity and payment methods into the build from the first sprint.

Where I work with development clients

I work remotely, with real overlap in your working day.

  • Dubai

    Web development in Dubai with React and Next.js: Arabic and English, UAE PASS, Aani and hosting inside the UAE, from one developer.

    How I work with Dubai teams →
  • Riyadh

    Web app development in Riyadh, in React and Next.js: built right to left, with Nafath, mada and PDPL-aware hosting.

    How I work with Riyadh teams →
  • Tallinn

    Web apps in Next.js for Estonian founders, with Smart-ID sign-in and three languages built in.

    How I work with Tallinn teams →
  • Amsterdam

    Accessible React and Next.js front ends for Dutch teams, ready for the EAA and Wero.

    How I work with Amsterdam teams →

The best front ends start from a clear design. Most of my build clients start with one of these.

In their words: founders on working with me

“The final product exemplified Muhammed’s profound comprehension of UI design principles, presenting a visually captivating experience that was both seamless and intuitive for users.”
Youssef RzikiClient, oil and gas trade
“I highly recommend Jubayer for any design project. He quickly grasps complex concepts, excels in standard design practices, and responds promptly.”
Abhishek NaleProduct lead, Strell

Guides on building with React and Next.js

Practical reads on stacks, AI interfaces and handoff, written from my own projects.

Free tools for this

Small jobs from this kind of work, done in your browser. Free, no sign-up, and nothing you add leaves your device.

SVG to JSX

Optimise an SVG with SVGO and turn it into a React or React Native component, a data URI or CSS.

Open the tool: SVG to JSX →

Design tokens to Tailwind

Convert DTCG, Figma and Tokens Studio JSON into a Tailwind v4 @theme, CSS variables, SCSS and TypeScript.

Open the tool: Design tokens to Tailwind →

LLM token counter

Exact token counts with OpenAI's published encodings, a context window budget, a token map and a chunker, in the browser.

Open the tool: LLM token counter →

MVP development for startups: your questions answered

Short, complete answers to the doubts founders raise before trusting a remote developer with their codebase.

Ask me on a free call
  • It depends on what the app must do. Screens and user roles, integrations, AI features, languages and how complete your design is drive the cost. Once we have spoken on the free intro call, a written scope and a single fixed price for all of it follow, so the number you approve is the number you pay.
  • Choose Next.js when the product has sign-in, real data, custom logic or performance targets that a builder cannot reach. For a marketing site, Framer or Webflow is often the faster and cheaper choice, and I will say so. The decision depends on who edits content, how much logic you need and who maintains it after launch.
  • Yes. I read the code first, agree naming, structure and review rules with your engineers, and then work in small pull requests that your team approves. If something in the codebase slows every feature down, I raise it in writing with a suggested fix, rather than quietly rewriting it.
  • The front end is my core, and I wire it properly to whatever sits behind it: sign-in, payments, data fetching, caching, forms and webhooks. For a product that needs a large custom back end, I work beside your back-end engineers, or agree the API with them before I build the screens that use it.
  • Yes. I review your Figma files first and list the missing states, such as empty, loading, error and permission screens. I fill those gaps with you before development reaches them, which is far cheaper than discovering them in a pull request a week before launch.
  • By designing everything around the model, not only the prompt. Answers stream as they arrive, sources are visible, people can stop, retry or undo, and failures say what happened in plain words. The model may be the same one your competitor uses; the interface is what makes people trust it.
  • Neither a large company nor a lone freelancer. You work with me directly in one shared Slack channel, so questions reach the person writing your code. I work remotely, sharing most of the working day with the Gulf and Asia, the afternoon with Europe, and evening calls with the US.
  • You do, from the first day. The repository, hosting, domain and third-party accounts are created in your company's name, and I work in them as an invited member. At the end you remove my access, and nothing about the product depends on me any more.
  • Book the free 30 minute intro call. Bring the product, what already exists and the date that matters. If I am the right fit, a written scope follows with one fixed price and no retainer, and together we pick where the first sprint starts.
  • Product design and the build in one project: the user flows and screens in Figma, a small design system, and the web app in React and Next.js with the sign-in, payments and admin it needs, analytics, and a launch on your own accounts. You click through a prototype first, then see working code every week. A project starts with a free 30 minute intro call, then a written scope and one fixed quote.
Sources and references (2)
  1. web.dev (Google), Web Vitals: good LCP within 2.5 seconds, INP 200 ms or less, CLS 0.1 or less, at the 75th percentile, 2 October 2026: web.dev
  2. IANA time zone database via Node.js Intl, Asia/Dhaka UTC+6 and America/New_York UTC-4 in summer (7 to 10 pm Dhaka is 9 am to 12 noon in New York), 2 October 2026: iana.org

Your design deserves the same care in code

A free 30 minute call. You leave with a clear next step, whether we work together or not.

Book a free intro call