Project Help · Company Profile 2026

Everything a client asks before they sign

15 pages: what we build, where it has shipped, how an engagement runs, and what you own at the end. Read it here or take the PDF — both come off this page, so they cannot disagree with each other.

Book a call

Company Profile 2026

We build the software.
You own every commit.

Custom Software Development Company in Dhaka, working with product teams worldwide.

28+Projects delivered

25Technology experts

Who we are

A small studio that ships, not a body shop that bills.

Founded 2021 in Dhaka, Bangladesh.

2021Building software since

28+Projects delivered

25Technology experts

95%Client satisfaction score

We are a product studio, not an agency with a sales floor. The engineers who scope your build are the engineers who write it, which is the whole reason a fixed price and a fixed date can survive contact with the work.

Everything in this document is drawn from the same records the website publishes — the same projects, the same stack, the same numbers. If one changes, both change.

Capabilities

Seven things we build, and what we build them with.

Every service below is one we have shipped and still support.

SaaS PlatformsMulti-tenant architecture

eCommerceB2C & B2B storefronts

DevOps & CloudCI/CD pipelines

AI/ML & DataPredictive analytics

ConsultingArchitecture assessments

Mobile AppsNative iOS & Android

CybersecurityVulnerability assessments

Technology we use

Sectors

Where the work has actually shipped.

Delivered projects by sector, across the whole portfolio.

0907050403

E-Commerce & RetailStorefronts & marketplacesSaaS & B2B PlatformsMulti-tenant productsHealth TechClinic & patient systemsFintech & PaymentsLedgers & reconciliationLogistics & Supply ChainFleet & warehouse tooling

Different sectors, one pattern: a catalogue or a caseload, a set of rules nobody has written down, and an operations team finding out too late. That is the problem we are usually hired to fix.

Engineering

One stack, all the way down.

The screen, the logic behind it, the data under that, and the platform it runs on.

01Design & InterfaceEverything your users touch — drawn first, then built, for whatever they are holding.

UI/UX design
Design system
Web application
iOS & Android

02Services & AIThe rules, the workflows and the models behind the screen.

Documented API
Microservices
Auth & roles
Models & AI agents

03Data & CommerceWhere the truth is kept, how it moves, who may see it, and how money changes hands.

Schema & migrations
Event pipeline
Reporting views
Checkout & payments

04Platform & AutomationHow it ships on a Tuesday, stays up at three in the morning, and runs when nobody is watching.

CI/CD pipeline
Monitoring & alerts
Automated workflows
Runbook & handover

Engagement

How an engagement runs.

Four steps, and you can stop us at the end of any of them.

Step 01Discovery callWe ask about your users, your deadline and your budget before we talk about technology at all.

Step 02Scope & architectureA written scope, wireframes, and a fixed price and timeline to sign off on — no surprises later.

Step 03Build in sprintsShort, fixed cycles. Every two weeks you see working software and can redirect us — not a slide deck.

Step 04Test, launch & supportQA on staging, a rehearsed go-live with a rollback plan, then 6–12 months of fixes and patches on us.

Handover

What you are left holding.

Handed over as the build runs, not assembled in the last week of it.

01The repositoryEvery commit, in your organisation, from the first day of the build rather than the last.

02A documented APIEndpoints, payloads and auth written down, so the next team does not have to read the controller to learn what it returns.

03Schema & migrationsThe data model and the ordered migrations that produce it, runnable against an empty database.

04A deployment pipelineCI/CD that builds, tests and ships — with the rollback path rehearsed before go-live, not after it.

05Monitoring & alertsDashboards and thresholds already wired, so the system tells you it is unwell before a customer does.

06A runbookHow to deploy it, how to restore it, and who to call. Written for someone who has never seen the codebase.

Selected work 01

Signature Bangla — Grocery & Pharmacy Delivery

eCommerce · Delivery Platform

One storefront selling groceries, pharmacy items and household essentials, with location-aware catalogs and an operations dashboard carrying live rider tracking and bulk CSV catalog uploads.

Technology used

Next.jsNode.jsPostgreSQLSocket.IOAWS

8xCatalog ManagementBulk CSV upload replaced item-by-item entry, cutting the time to publish a full catalog update from a working day to under an hour.

What made it hard

Three Catalogs, One Storefront. Groceries, pharmacy items and household goods each needed different stock rules, but customers expected a single basket.
No Live Operations View. Staff could not see where riders were or which orders were stalling until a customer called to complain.
Catalog Management By Hand. Every price and stock change was entered item by item, across multiple locations.

LiveOrder Visibility

3Categories Unified

99.9%Uptime Since Launch

Selected work 02

Fashion eCommerce Storefront

eCommerce · Web App

A direct-to-customer storefront replacing a marketplace listing: size and colour variants, a three-step checkout, and an admin panel for products, orders and promotions the client runs without us.

Technology used

Next.jsNode.jsPostgreSQLStripeCloudflare

0%Commission Per SaleSales moved onto the client's own domain and payment account, so marketplace commission stopped applying to every order.

What made it hard

No Customer Relationship. Orders arrived without a customer record, so repeat buying could not be encouraged or even measured.
Variants Modelled As Separate Products. Every size and colour was its own listing, which made stock counts and merchandising unmanageable.
Nothing Could Be Changed Without Help. Prices, banners and promotions all needed someone technical, so campaigns moved at the speed of a support ticket.

Same dayCampaign Turnaround

3Checkout Steps

1 sourceCatalog Accuracy

Selected work 03

Clinic Management System

Health Tech · SaaS

A digital front desk for a multi-doctor clinic: appointments booked against real availability, digital patient records, and a shared prescription history that replaced paper books and double-booked slots.

Technology used

Next.jsNode.jsPostgreSQLRedisAWS

0Double BookingsSlots are generated from each doctor's working pattern, so an unavailable time cannot be selected at the front desk at all.

What made it hard

Double-Booked Slots. Availability was remembered rather than recorded, so two patients regularly arrived for the same time with the same doctor.
History Not At Hand. A returning patient's previous prescriptions were in a folder somewhere, so doctors re-prescribed blind more often than anyone wanted.
No Numbers To Manage With. Patient volume, no-show rates and doctor utilisation were invisible, so staffing was guesswork.

SecondsRecord Retrieval

6Doctors Scheduled

DailyReporting

Selected work 04

Restaurant POS System

Point of Sale · Hospitality

Fast counter order entry, automatic kitchen ticket routing over websockets, and a reporting dashboard giving same-day visibility into sales, covers and top-performing menu items.

Technology used

ReactNode.jsPostgreSQLSocket.IOElectron

InstantOrder RoutingConfirmed tickets reach the correct kitchen station over websockets, replacing a verbal handoff across the service window.

What made it hard

Orders Lost In Transit. A verbal handoff between counter and kitchen fails exactly when service is busiest and mistakes cost the most.
No Same-Day Numbers. Sales by item, by hour and by staff member were reconstructed from receipts days later, if at all.
Menu Drift Between Tills. Price and availability changes had to be made twice and were regularly made once.

Same daySales Reporting

3Kitchen Stations

1Menu Source

Selected work 05

Expense Tracker Mobile App

Mobile App · Fintech

Sub-five-second expense entry, category tagging, recurring bills and monthly budget charts, delivered to iOS and Android from a single React Native codebase.

Technology used

React NativeTypeScriptNode.jsPostgreSQLSQLite

< 5sTime To LogAmount, category, save — on one screen with sensible defaults, which is the number the whole app was designed against.

What made it hard

Entry Too Slow To Sustain. Multi-field forms lose users in the second week, and an incomplete ledger is worth almost nothing.
Useless Without Signal. An expense happens at a till, sometimes underground — an app that needs connectivity misses exactly those moments.
Numbers Without Meaning. A list of transactions is not insight; users need to see whether this month is going the way the last one did.

1Codebases

AlwaysOffline Entry

AutomaticRecurring Bills

Clients

Who we build for.

Named with their permission. The rest of the portfolio is under agreement.

Three names we are allowed to print, out of 28+ delivered projects. The work on the pages before this one is published in full on the website, with the same figures it carries here.

The case

Five reasons teams stay.

Each one is a term of the engagement, not a sentiment about it.

01Senior engineers on your buildThe people who scope the work are the people who write it. Nothing is priced by one team and handed to another to figure out.

02A fixed scope before a line is writtenWritten scope, wireframes, price and timeline, signed off before the build starts — so the conversation at the end is about the software, not the invoice.

03Working software every two weeksYou see the product running on a fixed cycle and can change direction while changing direction is still cheap.

04You own it from the first commitThe repository is yours throughout. No licence to renegotiate, no escrow, no leverage held over the handover.

05Support that outlasts the launchSix to twelve months of fixes and patches after go-live are part of the build, not a separate contract.

Next step

Tell us what
breaks first.

A thirty-minute call, and no deck from us. You describe the problem, we tell you what it would take — whether or not that is us.

Websitewww.projecthelpbd.com

Emailhello@projecthelpbd.com

Phone+880 1975-005362

Studio3rd Floor, House 76/A, Road 11, Banani, Dhaka 1213, Bangladesh

Everything a client asks before they sign

We build the software.You own every commit.

A small studio that ships, not a body shop that bills.

Seven things we build, and what we build them with.

Where the work has actually shipped.

One stack, all the way down.

How an engagement runs.

What you are left holding.

Signature Bangla — Grocery & Pharmacy Delivery

Fashion eCommerce Storefront

Clinic Management System

Restaurant POS System

Expense Tracker Mobile App

Who we build for.

Five reasons teams stay.

Tell us whatbreaks first.

We build the software.
You own every commit.

Tell us what
breaks first.