I turn complex work into calm, useful software.

Backend systems, automation, SaaS products, and operational tools—designed with care, built for real work, and made understandable for the people using them.

I turn complicated operations into calm, useful software.

Full-stack product developer Dhaka, Bangladesh GMT+6

Available for selected work 2026
Mehebub Mukut, full-stack product developer
Current focusDependable product systems
5-star ratedLevel 2 Fiverr seller
5-star Marketplace rating July 2026
Level 2 Seller status Fiverr
250+ Satisfied clients Across platforms
5+ Years building Products, APIs & automation

Current snapshot · July 2026

Selected products · 01

Five highlighted builds. Five detailed case notes.

These five are selected from 250+ delivered builds. Each case explains the problem, product direction, contribution, key decisions, and delivery boundary. An interactive sample appears only when it has been explicitly enabled for that project.

05selected products 05detailed case notes 100%privacy-aware proof
Product · Infrastructure Public product

Panelavo

A customer-first control layer that makes server and site operations safer, clearer, and easier to own.

Next.js TypeScript PHP Linux

Product · Infrastructure

Panelavo

A customer-first control layer that makes server and site operations safer, clearer, and easier to own.

Public product Next.js TypeScript PHP Linux
01 · The problem

Hosting control panels are powerful, but routine deployment, backup, Git, and service operations can still feel fragmented or dangerously technical.

02 · Product direction

A guided product layer over CloudPanel with explicit security boundaries, health checks, deployment workflows, and ownership-aware operations.

03 · My contribution

Product direction, workflow design, backend integration, deployment architecture, and production hardening.

04 · Core capabilities
  • Customer-oriented site workflows
  • Allow-listed privileged operations
  • Rootless per-site Docker boundaries
  • Safe updater and recovery paths
05 · Key decisions
  • Keep each hosted site isolated by ownership, runtime, and document-root boundaries.
  • Put privileged host operations behind a narrow allow-listed broker instead of exposing a general shell.
  • Treat backup, update, health, and recovery paths as product workflows rather than operator-only knowledge.
06 · What it delivers

Panelavo turns repeatable hosting work into guided flows while keeping high-risk operations deliberate, observable, and constrained to the site being managed.

Case notes disclose product reasoning without exposing private client systems or data.
SaaS · Messaging Product system

Action Sender

A consent-aware workspace for planning, reviewing, and operating business messaging without losing human control.

Node.js React Messaging Automation

SaaS · Messaging

Action Sender

A consent-aware workspace for planning, reviewing, and operating business messaging without losing human control.

Product system Node.js React Messaging Automation
01 · The problem

Campaign tools often optimise for volume while leaving teams to manage consent, account health, templates, timing, and conversation context separately.

02 · Product direction

A guided Connect → Message → Groups → Timing → Review flow, with clear safeguards and a single operational workspace.

03 · My contribution

Founder, product architect, backend developer, workflow designer, and deployment owner.

04 · Core capabilities
  • Guided campaign composer
  • Consent and policy safeguards
  • Template and account workflows
  • Human review before sending
05 · Key decisions
  • Separate drafting and review from provider delivery so an unfinished campaign cannot become an accidental send.
  • Surface account, template, recipient, and timing readiness inside one composer instead of scattering checks across tools.
  • Keep consent, safeguards, and a final human review visible at the point where the operator makes the send decision.
06 · What it delivers

Action Sender gives operators one coherent path from campaign intent to a reviewed delivery plan, with provider readiness and safety boundaries visible before anything can be sent.

Case notes disclose product reasoning without exposing private client systems or data.
Nonprofit · Donor directory Community product

Drop

A nonprofit blood-donor directory built to coordinate urgent requests while protecting donor privacy and consent.

React TypeScript Privacy Nonprofit

Nonprofit · Donor directory

Drop

A nonprofit blood-donor directory built to coordinate urgent requests while protecting donor privacy and consent.

Community product React TypeScript Privacy Nonprofit
01 · The problem

Urgent blood requests are often scattered across informal channels, while availability, eligibility, and consent are difficult to verify without exposing personal information.

02 · Product direction

An opt-in directory with blood-group and district discovery, verified availability, coarse locations, reviewed support organisations, and a protected contact relay.

03 · My contribution

Product strategy, privacy architecture, workflow design, full-stack implementation, and community operating model.

04 · Core capabilities
  • Opt-in donor availability
  • Protected contact relay
  • Reviewed support directory
  • Urgent request coordination
05 · Key decisions
  • Use explicit opt-in and renewable availability instead of treating an old donor record as permanent consent.
  • Match by blood group and coarse location without publishing a donor address or direct contact details.
  • Route contact through a protected request flow and make withdrawal possible without depending on an administrator.
06 · What it delivers

Drop helps a requester identify plausible, currently available support while keeping donor identity and contact details behind a consent-aware relay.

Case notes disclose product reasoning without exposing private client systems or data.
Commerce · Streetwear Client storefront

BXELEVEN

An urban streetwear storefront that turns a bold brand identity into a focused browse-to-checkout journey.

PHP JavaScript Commerce Responsive UX

Commerce · Streetwear

BXELEVEN

An urban streetwear storefront that turns a bold brand identity into a focused browse-to-checkout journey.

Client storefront PHP JavaScript Commerce Responsive UX
01 · The problem

A strong clothing identity can lose momentum when collection discovery, sizing, product detail, and checkout feel disconnected or generic.

02 · Product direction

A custom storefront with editorial collections, clear product choices, a persistent bag, and a direct account and order journey.

03 · My contribution

Storefront architecture, interaction design, custom PHP implementation, commerce workflows, and responsive delivery.

04 · Core capabilities
  • Editorial collection discovery
  • Focused product and size choices
  • Persistent cart journey
  • Responsive custom storefront
05 · Key decisions
  • Let the brand lead the composition while keeping product, size, price, and availability decisions immediately legible.
  • Preserve bag state across the browsing journey so editorial discovery does not interrupt purchase intent.
  • Build the storefront as a first-party responsive experience rather than forcing the identity into a generic theme.
06 · What it delivers

BXELEVEN carries one visual and interaction language from collection discovery through product choice and the shopping bag, giving the storefront a distinct identity without obscuring commerce basics.

Case notes disclose product reasoning without exposing private client systems or data.
Commerce · Deal discovery Product platform

HelloDeals

A German deal-discovery storefront that makes price context, freshness, and savings easier to judge.

PHP MySQL Automation Deal scoring

Commerce · Deal discovery

HelloDeals

A German deal-discovery storefront that makes price context, freshness, and savings easier to judge.

Product platform PHP MySQL Automation Deal scoring
01 · The problem

Deal feeds can overwhelm shoppers with noisy discounts, stale prices, and too little context to understand whether an offer is genuinely useful.

02 · Product direction

A curated storefront that combines deal scoring, price history, freshness, categories, and a clear retailer handoff.

03 · My contribution

Product architecture, storefront UX, data and automation integration, publisher workflows, and deployment hardening.

04 · Core capabilities
  • Price-history context
  • Freshness-aware deal cards
  • Curated category discovery
  • Controlled publishing workflows
05 · Key decisions
  • Show freshness and price context beside the headline discount so shoppers can judge an offer rather than trust a badge.
  • Keep automated ingestion separate from publication controls, allowing weak or stale offers to be held back.
  • Use hierarchical categories and clear retailer handoff points so discovery stays understandable as the catalogue grows.
06 · What it delivers

HelloDeals combines automated deal intake with editorial control, giving shoppers clearer evidence for an offer and giving publishers a safer path from feed data to a public deal.

Case notes disclose product reasoning without exposing private client systems or data.

Ways I can help · 02

One partner from system shape to shipped reality.

I work best where product decisions and engineering decisions need to stay close—especially when the software supports a real operational workflow.

01

Product & SaaS engineering

From a fuzzy operational problem to a focused product people can actually use.

  • Product architecture
  • Customer and staff workflows
  • Full-stack implementation
  • Launch and iteration
Useful outcome A product path the team can build, use, and evolve.
02

Automation & integrations

Reliable connections between websites, APIs, Google Workspace, messaging, and internal tools.

  • Browser automation
  • API and webhook systems
  • Google Apps Script
  • Data processing
Useful outcome Less repetitive work, with failures that stay visible.
03

Backend & infrastructure

The less visible work that keeps a product dependable, recoverable, and understandable.

  • Backend services
  • Databases and migrations
  • Linux and Docker deployment
  • Health and recovery paths
Useful outcome A recoverable foundation with explicit data and runtime boundaries.
04

Operational UX

Interfaces for real work: clear status, safe actions, useful defaults, and fewer avoidable decisions.

  • Internal tools
  • Role-aware dashboards
  • Guided multi-step flows
  • Responsive product polish
Useful outcome Fewer uncertain clicks and much clearer ownership.
Mehebub Mukut in a bright product studio
“Development is like a cartoon: some ideas come to life easily, while others demand patience, experimentation, and a lot of learning. But with enough curiosity and persistence, nothing is impossible.”

About · 03

Technical depth with a practical, human point of view.

I’m Mehebub Mukut, a full-stack product developer building software alongside a path in medicine—two disciplines that reward careful observation, clear decisions, and respect for the person at the other end.

My work tends to live between product, backend engineering, automation, and operations. I enjoy tracing the actual workflow, finding the part that creates friction, and turning it into a system the team can understand and trust.

01
Understand before abstracting

Start with people, constraints, data, and failure cases.

02
Make important state visible

Clear status and ownership prevent avoidable mistakes.

03
Prove the whole path

Production behaviour matters more than an isolated happy-path test.

Connected capabilities · 04

A product is a system. I work across the joins.

Strong interfaces need reliable data. Useful automation needs safe fallbacks. Good infrastructure should support the product instead of becoming the product.

Discuss your system
MProduct
systems
01

Product

Discovery · Workflow mapping · UI/UX · SaaS architecture

02

Frontend

React · Next.js · TypeScript · Responsive systems

03

Backend

Node.js · PHP · Python · REST & webhooks

04

Data

PostgreSQL · MySQL · SQLite · MongoDB

05

Automation

Playwright · Apps Script · Queues · Scheduled jobs

06

Operations

Docker · Linux · CloudPanel · Backups & health

Evidence · 05

Trust, without the noisy scoreboard.

A clear mix of public marketplace standing, owner-confirmed cross-platform reach, and inspectable work—without turning client trust into a wall of review counts.

Public marketplace profile Owner-confirmed reach Transparent case notes
fi
Fiverr

Marketplace standing

Public
5-star rated on Fiverr

A strong public rating paired with established seller status across automation, APIs, Google Workspace, and product work.

  • 5-starmarketplace rating
  • Level 2seller status
  • Publicsource profile
250+
Across platforms

Satisfied client reach

Owner-confirmed
250+ satisfied clients

Relationships built across marketplaces and direct project work, spanning practical automation, SaaS, and operational systems.

  • Automation and API projects
  • SaaS and operational systems
  • Marketplace and direct delivery
06
Selected systems

Transparent case notes

Portfolio
Every case shows the reasoning

The portfolio separates what can be verified from what must stay private.

  • Challenge, approach, and contribution disclosed
  • Sample data clearly labelled in every preview
  • No private client systems or invented outcomes

Selected client relationships

Happy clients across commerce, community, media, and operations.

A selection of organizations and products I have supported through development, automation, integration, or delivery work.

Owner-confirmed client relationships. Logos identify the respective organizations and remain the property of their owners.

How I work · 06

A calm path from ambiguity to proof.

Four lightweight stages. The outcome, ownership, data, failure paths, and evidence stay visible throughout.

Lightweight by design
OutcomeOwnershipDataFailureProof
  1. 01 Discover

    Find the real problem

    Map the people, constraints, data, edge cases, and outcome before choosing the solution.

  2. 02 Model

    Make the system visible

    Turn the workflow into a clear model, interface, delivery plan, and definition of done.

  3. 03 Build

    Build in useful slices

    Ship complete paths early, keep feedback close, and protect the architecture from accidental complexity.

  4. 04 Prove

    Prove it in reality

    Validate responsive behaviour, failure paths, persistence, deployment, and the actual production environment.

Useful answers · 07

Before you send the brief.

Enough context to decide whether this feels like a fit. We can handle confidential details later, in the right channel.

01What kind of work is the best fit?

Products and operational systems with a meaningful workflow: SaaS tools, internal platforms, integrations, data automation, customer funnels, and backend-heavy web applications.

02Can you work with an existing product?

Yes. I can trace an existing system, diagnose the real boundary causing a problem, improve a focused area, or help turn an unstable prototype into a maintainable release.

03Are the project previews live client products?

No. Every preview uses sample data in a purpose-built mock interface. It demonstrates product thinking and workflow without exposing private systems, customer data, or real project URLs.

04How do enquiries work?

The form securely records your message for a direct reply. Share the problem, timeline, and any important constraints; confidential details can wait until we have an appropriate channel.

Start a conversation · 08

Bring the messy part.

Tell me what is difficult today. We can turn the problem, the people, and the desired outcome into a useful first path.

01The problem 02The people 03The outcome
Current availabilitySelected product, automation, and operational software work
Telegram @MehebubMukut Fiverr View public profile

Protected by origin checks, rate limiting, and private server-side storage.