Mehebub Mukut Product developer Start a project

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.

Explore selected work Tell me what you are building

One builder, whole-system thinking.
Product, interface, backend, automation, and launch.

Available for selected work 2026
Mehebub Mukut, full-stack product developer
Current focusDependable product systems
5.079 public reviews
5.0 Fiverr rating 79 public reviews
91 Completed Fiverr orders Seller dashboard snapshot
16.5K Package downloads 12-month npm snapshot
5+ Years building Web, APIs & automation

Verified snapshot · July 2026

Selected systems · 01

Work shaped around the problem, not the template.

A mix of products and privacy-safe case studies. Every preview is a purpose-built mockup using sample data—not a live client system.

06selected systems 03problem spaces 100%sample-data previews

Showing all 6 systems

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
Designed around
  • Customer-oriented site workflows
  • Allow-listed privileged operations
  • Rootless per-site Docker boundaries
Open interactive preview

Product · Infrastructure

Panelavo

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

01 · The challenge

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

02 · The approach

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

03 · My role

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

04 · Designed around
  • Customer-oriented site workflows
  • Allow-listed privileged operations
  • Rootless per-site Docker boundaries
  • Safe updater and recovery paths
Explore the sample preview Mock interface · sample data · no client systems exposed
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
Designed around
  • Guided campaign composer
  • Consent and policy safeguards
Open interactive preview

SaaS · Messaging

Action Sender

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

01 · The challenge

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

02 · The approach

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

03 · My role

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

04 · Designed around
  • Guided campaign composer
  • Consent and policy safeguards
  • Template and account workflows
  • Human review before sending
Explore the sample preview Mock interface · sample data · no client systems exposed
Client system · Operations Anonymised case study

Vehicle Ops

A role-aware vehicle workflow connecting intake, inspection, bodywork, preparation, costs, and handover.

Next.js PostgreSQL Workflows RBAC
Designed around
  • Mandatory inspection gates
  • Conditional bodywork job cards
Open interactive preview

Client system · Operations

Vehicle Ops

A role-aware vehicle workflow connecting intake, inspection, bodywork, preparation, costs, and handover.

01 · The challenge

A vehicle can cross several departments before sale, making responsibility, mandatory checks, status, and cost difficult to see in one place.

02 · The approach

One visible operational journey per vehicle, with conditional job cards, health checks, alerts, ownership, and department-level costing.

03 · My role

Requirements analysis, workflow architecture, data modelling, product UX, and full-stack implementation.

04 · Designed around
  • Mandatory inspection gates
  • Conditional bodywork job cards
  • Expiry and readiness alerts
  • Departmental cost visibility
Explore the sample preview Mock interface · sample data · no client systems exposed
Fintech · Personal operations Private product

Poisha

A money workspace designed around people, obligations, reserves, transfers, and the real story behind a balance.

PHP SQLite Finance UX Mobile-first
Designed around
  • Person-to-person money flows
  • Account reservations and reserves
Open interactive preview

Fintech · Personal operations

Poisha

A money workspace designed around people, obligations, reserves, transfers, and the real story behind a balance.

01 · The challenge

Traditional ledgers show transactions but often hide commitments, person-to-person context, fees, credit exposure, and reserved money.

02 · The approach

A mobile-first model that treats accounts, people, liabilities, and reservations as connected parts of the same financial picture.

03 · My role

Product design, service architecture, financial workflow logic, data modelling, and responsive implementation.

04 · Designed around
  • Person-to-person money flows
  • Account reservations and reserves
  • Liability coverage visibility
  • Mobile-first daily workflows
Explore the sample preview Mock interface · sample data · no client systems exposed
Lead funnel · CRM Anonymised case study

Property Offer Platform

A postcode-first property journey that carries a homeowner from first intent through valuation and follow-up.

Next.js APIs CRM Conversion UX
Designed around
  • Postcode-first conversion path
  • Valuation API integration
Open interactive preview

Lead funnel · CRM

Property Offer Platform

A postcode-first property journey that carries a homeowner from first intent through valuation and follow-up.

01 · The challenge

Long, generic forms create friction before a seller understands the process, while disconnected lead systems slow down valuation and follow-up.

02 · The approach

A focused postcode-first funnel connected to a valuation API and operational CRM, with every lead state visible to the team.

03 · My role

Journey design, API integration, CRM implementation, responsive UX, and production validation.

04 · Designed around
  • Postcode-first conversion path
  • Valuation API integration
  • Structured lead progression
  • Responsive customer and CRM views
Explore the sample preview Mock interface · sample data · no client systems exposed
Automation · Integrations Delivered systems

Automation Studio

Resilient browser, Google Workspace, webhook, and data workflows built for changing real-world environments.

Playwright Node.js Apps Script APIs
Designed around
  • Browser and API orchestration
  • Google Apps Script workflows
Open interactive preview

Automation · Integrations

Automation Studio

Resilient browser, Google Workspace, webhook, and data workflows built for changing real-world environments.

01 · The challenge

Automation breaks when it assumes perfect pages, stable selectors, instant responses, or clean data—conditions that rarely survive production.

02 · The approach

Defensive workflows with observable steps, controlled retries, validation, scheduling, and human-readable failure paths.

03 · My role

Discovery, automation architecture, implementation, Linux deployment, monitoring, and maintenance.

04 · Designed around
  • Browser and API orchestration
  • Google Apps Script workflows
  • Defensive retries and validation
  • Scheduled Linux execution
Explore the sample preview Mock interface · sample data · no client systems exposed

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
“The best software makes a complicated job feel surprisingly obvious.”

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.

GitHub Fiverr LinkedIn

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

Evidence over inflated numbers.

Current aggregate signals from public profiles, open-source use, and verified delivery history. No anonymous testimonials, hidden client names, or invented scale.

Public profiles Seller history Open-source usage Case transparency
fi
Fiverr

Verified delivery history

Public
5.0 ★★★★★

Consistent client feedback across automation, APIs, Google Workspace, and product work.

5 star78

4 star1

  • 79public reviews
  • 91completed orders
  • Level 2seller status
npm
baileys_helper

Open-source adoption

Public
16,504 12-month downloads

Verified package use across the twelve months ending 24 July 2026.

  • 12GitHub stars
  • 16repository forks
  • Opensource code
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

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

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