# ProSystem Full LLM Content Map Source: https://www.prosystem.com.bd Canonical sitemap: https://www.prosystem.com.bd/sitemap.xml Concise agent map: https://www.prosystem.com.bd/llms.txt This file is generated from the same curated content index used by the on-site ProSystem assistant. ## Documents ### [ProSystem Retail management, eCommerce and custom software](https://www.prosystem.com.bd/) - Type: page - ID: page:/ - Tags: home, company, overview A Bangladesh-based IT services company building retail management, eCommerce and custom software for 30+ businesses and 200,000+ users. ProSystem Limited is a Bangladesh-based IT services company. We build business management systems, eCommerce websites and custom software for growing retail, F&B, healthcare and services operations. Our flagship product is ProSystem BMS. Around it we run an eCommerce practice, a custom software practice, and a support and maintenance practice all staffed by the same engineers who built the core platform. ### [Products & Services](https://www.prosystem.com.bd/products) - Type: page - ID: page:/products - Tags: products, services, overview, BMS, eCommerce, custom IT, support Everything a growing Bangladeshi business needs to sell, operate and scale business management, eCommerce, custom IT and support, from one partner. Four practices, one team: ProSystem BMS for operations, custom eCommerce websites, custom IT (ERP, custom websites, custom applications, mobile & cloud solutions, integrations) engineered around your workflows, and an ongoing support engagement covering technical support, training, upgrades, migration, data stewardship and continuous enhancement. ### [BMS Business Management System](https://www.prosystem.com.bd/bms) - Type: product - ID: page:/bms - Tags: BMS, POS, retail, inventory, sales, accounting, ERP, multi-outlet Sales, inventory, customers, staff, reporting nine modules reading and writing to one source of truth. Designed, built and supported in Bangladesh. ProSystem BMS unifies sales, inventory, customers and reporting for multi-outlet operations. Sales on the floor, stock in the warehouse, customers in the database, staff on the roster every screen talks to the same source of truth, so the numbers at month-end agree with the numbers on the till. Permissions, location scope and configuration adapt per organisation, so the system stays calm as your team grows from a single outlet to a multi-site chain. Nine modules: Overview, Sales, Inventory, Customers, Human Resources, Finance, Reporting, Purchasing and Settings. Each reads and writes the same records, so a sale updates stock, a customer return updates loyalty, and a price change rolls across every outlet at once. Runs in the cloud with same-day go-live for a single outlet and a 99.5% uptime target (99.9% on Enterprise support). ### [How do I try a demo / get started?](https://www.prosystem.com.bd/bms#faq-1) - Type: faq - ID: faq:/bms#faq-1 - Tags: faq, demo, trial, sign up, register, registration, get started, try, BMS, POS, retail, inventory, sales, accounting, ERP, multi-outlet How do I try a demo / get started? Sign up directly at https://bms.prosystem.com.bd/registration create a free account, configure your organisation, add items and outlets, and start using the BMS right away. No sales call required to try it. ### [How long does a BMS launch take?](https://www.prosystem.com.bd/bms#faq-2) - Type: faq - ID: faq:/bms#faq-2 - Tags: faq, deployment, launch, BMS, POS, retail, inventory, sales, accounting, ERP, multi-outlet How long does a BMS launch take? A single outlet can be live the same day. You sign up, configure your organisation, add items and outlets, and start selling. The interface is intuitive enough that most teams don't need us on the call. ### [Can we keep our existing POS hardware?](https://www.prosystem.com.bd/bms#faq-3) - Type: faq - ID: faq:/bms#faq-3 - Tags: faq, hardware, POS, BMS, POS, retail, inventory, sales, accounting, ERP, multi-outlet Can we keep our existing POS hardware? Yes. ProSystem BMS works with any modern POS peripheral receipt printers, barcode scanners, cash drawers, card terminals. ### [Where is our data hosted?](https://www.prosystem.com.bd/bms#faq-4) - Type: faq - ID: faq:/bms#faq-4 - Tags: faq, hosting, data, BMS, POS, retail, inventory, sales, accounting, ERP, multi-outlet Where is our data hosted? In the cloud, on trusted data centres with strong availability and security guarantees. The data is yours you can export it, and you can leave with it. ### [How is BMS priced?](https://www.prosystem.com.bd/bms#faq-5) - Type: faq - ID: faq:/bms#faq-5 - Tags: faq, pricing, BMS, POS, retail, inventory, sales, accounting, ERP, multi-outlet How is BMS priced? Subscription-based. The plan scales with the features and support tier you need, and a Statement of Work sets out the exact figures for your setup. ### [What happens when we outgrow the standard plan?](https://www.prosystem.com.bd/bms#faq-6) - Type: faq - ID: faq:/bms#faq-6 - Tags: faq, scale, enterprise, BMS, POS, retail, inventory, sales, accounting, ERP, multi-outlet What happens when we outgrow the standard plan? Our Enterprise tier adds unlimited outlets, extended-hours critical response and a 99.9% uptime target. ### [Can I use BMS on my phone or tablet?](https://www.prosystem.com.bd/bms#faq-7) - Type: faq - ID: faq:/bms#faq-7 - Tags: faq, mobile, tablet, phone, access, browser, BMS, POS, retail, inventory, sales, accounting, ERP, multi-outlet Can I use BMS on my phone or tablet? Yes. BMS is a cloud-hosted web application that runs in any modern browser, on desktop, tablet or phone. For the POS till we recommend a tablet or touchscreen terminal; for reporting and admin tasks your phone is fine. ### [What does BMS integrate with?](https://www.prosystem.com.bd/bms#faq-8) - Type: faq - ID: faq:/bms#faq-8 - Tags: faq, integrations, payments, SMS, courier, SSO, API, BMS, POS, retail, inventory, sales, accounting, ERP, multi-outlet What does BMS integrate with? BMS integrates with the systems retail operations need most often: payment gateways and card terminals, SMS providers for receipts and OTPs, courier APIs for dispatch tracking, email providers for notifications, and identity providers for SSO. Custom integrations are scoped under a Statement of Work. ### [Can we control what each user can see and do?](https://www.prosystem.com.bd/bms#faq-9) - Type: faq - ID: faq:/bms#faq-9 - Tags: faq, permissions, roles, users, access control, multi-outlet, BMS, POS, retail, inventory, sales, accounting, ERP, multi-outlet Can we control what each user can see and do? Yes. BMS has role- and location-based permissions per organisation. Your admins define roles, assign users, and scope each role to specific outlets. Staff on the till only see what they need; regional managers see their sites; HQ sees everything. ### [Does BMS support multiple currencies or taxes?](https://www.prosystem.com.bd/bms#faq-10) - Type: faq - ID: faq:/bms#faq-10 - Tags: faq, currency, tax, VAT, international, BMS, POS, retail, inventory, sales, accounting, ERP, multi-outlet Does BMS support multiple currencies or taxes? Yes. Multi-currency pricing and country-specific tax rates (including Bangladesh VAT) are supported. Your accountants configure the rules once per organisation; the rest of the system inherits them. ### [What reports come out of BMS?](https://www.prosystem.com.bd/bms#faq-11) - Type: faq - ID: faq:/bms#faq-11 - Tags: faq, reports, analytics, dashboards, exports, BMS, POS, retail, inventory, sales, accounting, ERP, multi-outlet What reports come out of BMS? Daily sales, inventory movement, customer behaviour, staff performance and finance summaries all drilling through to the underlying transactions. Reports can be filtered by outlet, time window and user, and exported to CSV or PDF. ### [eCommerce websites built on your BMS data](https://www.prosystem.com.bd/ecommerce) - Type: product - ID: page:/ecommerce - Tags: eCommerce, website, Next.js, online store, omnichannel Custom Next.js websites connected to ProSystem BMS fast, accessible, conversion-tested, reading from the same data your operation runs on. We develop custom eCommerce websites that read from the same database your BMS reads from no CSV exports, no double-sold stock, no reconciliation spreadsheets at month-end. Built on Next.js with a careful performance budget (90 Lighthouse on desktop at launch). Orders, stock and customer records sync in real time with your BMS tenant. Typical time-to-launch is 24 weeks. We run the domain, DNS, SSL, deploys and uptime, so your team doesn't have to. ### [Does the website talk to BMS?](https://www.prosystem.com.bd/ecommerce#faq-1) - Type: faq - ID: faq:/ecommerce#faq-1 - Tags: faq, integration, BMS, eCommerce, website, Next.js, online store, omnichannel Does the website talk to BMS? Yes. Orders, stock and customer records sync in real time no double-entry, no double-sold stock. ### [Can we migrate from our existing platform?](https://www.prosystem.com.bd/ecommerce#faq-2) - Type: faq - ID: faq:/ecommerce#faq-2 - Tags: faq, migration, eCommerce, website, Next.js, online store, omnichannel Can we migrate from our existing platform? Yes. We've moved catalogs, customers and order history off every major hosted and self-hosted platform. We run the migration in parallel so you don't go dark. ### [How fast are the websites?](https://www.prosystem.com.bd/ecommerce#faq-3) - Type: faq - ID: faq:/ecommerce#faq-3 - Tags: faq, performance, Lighthouse, eCommerce, website, Next.js, online store, omnichannel How fast are the websites? Built on Next.js with a careful performance budget 90 Lighthouse on desktop at launch. Mobile is harder: 80+ is realistic for ecommerce once ads, analytics and imagery are in play. ### [Do you manage hosting and DNS?](https://www.prosystem.com.bd/ecommerce#faq-4) - Type: faq - ID: faq:/ecommerce#faq-4 - Tags: faq, hosting, DNS, eCommerce, website, Next.js, online store, omnichannel Do you manage hosting and DNS? Yes. We run the domain, DNS records, SSL certificates, deploys and uptime so your team never has to log into the registrar at midnight. ### [Can we A/B test?](https://www.prosystem.com.bd/ecommerce#faq-5) - Type: faq - ID: faq:/ecommerce#faq-5 - Tags: faq, experimentation, A/B testing, eCommerce, website, Next.js, online store, omnichannel Can we A/B test? Yes via your analytics stack. We'll wire experiments on the pages that matter most to you. ### [What payment methods and gateways are supported?](https://www.prosystem.com.bd/ecommerce#faq-6) - Type: faq - ID: faq:/ecommerce#faq-6 - Tags: faq, payments, bKash, Nagad, Stripe, cards, COD, eCommerce, website, Next.js, online store, omnichannel What payment methods and gateways are supported? We integrate with local and international payment gateways card (Visa, Mastercard), mobile financial services (bKash, Nagad, Rocket), bank transfer, cash on delivery, and international gateways like Stripe and PayPal for cross-border stores. The specific mix is decided during discovery based on your market. ### [Can we sell internationally?](https://www.prosystem.com.bd/ecommerce#faq-7) - Type: faq - ID: faq:/ecommerce#faq-7 - Tags: faq, international, multi-currency, shipping, translation, eCommerce, website, Next.js, online store, omnichannel Can we sell internationally? Yes. The website supports multi-currency pricing, country-based tax, localised shipping zones, and translated content. For cross-border shipping we integrate with the courier you prefer. ### [What about SEO?](https://www.prosystem.com.bd/ecommerce#faq-8) - Type: faq - ID: faq:/ecommerce#faq-8 - Tags: faq, SEO, sitemap, structured data, Open Graph, eCommerce, website, Next.js, online store, omnichannel What about SEO? Every website comes with a clean URL structure, JSON-LD product and breadcrumb schema, generated sitemap and robots.txt, meta/Open Graph tags per page, and fast Core Web Vitals all the SEO-critical basics wired up at launch. ### [Custom IT Development engineered around your workflows](https://www.prosystem.com.bd/custom-solutions) - Type: product - ID: page:/custom-solutions - Tags: custom IT, custom software, ERP, custom website, custom applications, mobile and cloud, integrations, discovery sprint, Statement of Work, managed hosting, legacy data migration, Next.js Custom IT engineered around the way your business actually runs ERP, custom website, custom applications, mobile & cloud and integrations, delivered by one accountable team. ProSystem designs, develops and maintains custom IT shaped to the way each business actually operates. Five solutions sit under this practice: ERP, custom websites, custom applications, mobile & cloud solutions, and integrations each tuned to the specific operation it supports. Engagements begin with a fixed-scope discovery sprint (typically 23 weeks) that frames the problem and produces a Statement of Work with a fixed scope and price for the first phase. Small, accountable teams deliver the engineers who design and develop the system stay with it through launch and beyond. DNS, SSL, deployments and uptime are maintained end to end. Progress against contracted outcomes is reviewed quarterly. Stack is TypeScript, React, Next.js and Node, extended to whatever the infrastructure calls for. Where existing systems are being retired, legacy data is migrated across as part of the delivery. ### [How do engagements start?](https://www.prosystem.com.bd/custom-solutions#faq-1) - Type: faq - ID: faq:/custom-solutions#faq-1 - Tags: faq, process, discovery, custom IT, custom software, ERP, custom website, custom applications, mobile and cloud, integrations, discovery sprint, Statement of Work, managed hosting, legacy data migration, Next.js How do engagements start? With a discovery sprint typically 23 weeks to frame the problem, de-risk the approach, and agree a Statement of Work with fixed scope and price for the first phase. ### [What stack do you use?](https://www.prosystem.com.bd/custom-solutions#faq-2) - Type: faq - ID: faq:/custom-solutions#faq-2 - Tags: faq, stack, tech, custom IT, custom software, ERP, custom website, custom applications, mobile and cloud, integrations, discovery sprint, Statement of Work, managed hosting, legacy data migration, Next.js What stack do you use? TypeScript, React, Next.js and Node, extended to whatever your infrastructure calls for. Our priority is code clarity over framework allegiance. ### [Do you work with our existing team?](https://www.prosystem.com.bd/custom-solutions#faq-3) - Type: faq - ID: faq:/custom-solutions#faq-3 - Tags: faq, collaboration, custom IT, custom software, ERP, custom website, custom applications, mobile and cloud, integrations, discovery sprint, Statement of Work, managed hosting, legacy data migration, Next.js Do you work with our existing team? Yes embedded, advisory or fully outsourced. Engagements are tailored to your team's capacity and ambition. ### [Do you manage hosting and DNS?](https://www.prosystem.com.bd/custom-solutions#faq-4) - Type: faq - ID: faq:/custom-solutions#faq-4 - Tags: faq, hosting, DNS, SSL, managed, custom IT, custom software, ERP, custom website, custom applications, mobile and cloud, integrations, discovery sprint, Statement of Work, managed hosting, legacy data migration, Next.js Do you manage hosting and DNS? Yes. We maintain the domain, DNS records, SSL certificates, deployments and uptime your team never has to manage the registrar directly. ### [What about maintenance after launch?](https://www.prosystem.com.bd/custom-solutions#faq-5) - Type: faq - ID: faq:/custom-solutions#faq-5 - Tags: faq, support, maintenance, custom IT, custom software, ERP, custom website, custom applications, mobile and cloud, integrations, discovery sprint, Statement of Work, managed hosting, legacy data migration, Next.js What about maintenance after launch? Covered by our Support plans from standard coverage to a dedicated engineering team. The same team that designs and develops the system continues to maintain it through every future update. ### [Do you migrate data from our existing systems?](https://www.prosystem.com.bd/custom-solutions#faq-6) - Type: faq - ID: faq:/custom-solutions#faq-6 - Tags: faq, migration, legacy data, go-live, custom IT, custom software, ERP, custom website, custom applications, mobile and cloud, integrations, discovery sprint, Statement of Work, managed hosting, legacy data migration, Next.js Do you migrate data from our existing systems? Yes, where existing systems are being retired. Legacy data is migrated across as part of the delivery, so the new platform goes live with the history it needs. ### [What does a typical engagement cost?](https://www.prosystem.com.bd/custom-solutions#faq-7) - Type: faq - ID: faq:/custom-solutions#faq-7 - Tags: faq, pricing, cost, budget, SOW, custom IT, custom software, ERP, custom website, custom applications, mobile and cloud, integrations, discovery sprint, Statement of Work, managed hosting, legacy data migration, Next.js What does a typical engagement cost? It depends on scope, but the discovery sprint is fixed-price (typically 23 weeks) and the Statement of Work for the first phase is also fixed. We share indicative ranges during the initial call so you can tell if it's the right ballpark before committing to discovery. ### [Support & Maintenance](https://www.prosystem.com.bd/support) - Type: product - ID: page:/support - Tags: support, maintenance, technical support, incident response, training, upgrades, migration, data stewardship, master data, continuous enhancement, uptime, response time Active operational support from ProSystem incident response, training, upgrades, migration, data stewardship and continuous enhancement, under a single agreement. ProSystem support is a continuous engagement not a tiered subscription. A named engineering team stays with your account across every request, from incident response through long-term enhancements. Six services sit under the engagement: technical support (incident response, troubleshooting), training (live sessions, remote by default or on-site when in-person works better), upgrades (platform releases tested against your configuration), migration (legacy cutover with parallel running and zero downtime), data stewardship (master data setup, bulk imports, catalogue curation, reconciliation, audits), and continuous enhancement (new reports, refined workflows, integration adjustments in rolling cycles). Response windows are written into your support agreement and measured against every incident. Critical incidents are prioritised and addressed the same business day. ### [How do I raise a ticket?](https://www.prosystem.com.bd/support#faq-1) - Type: faq - ID: faq:/support#faq-1 - Tags: faq, access, tickets, support, maintenance, technical support, incident response, training, upgrades, migration, data stewardship, master data, continuous enhancement, uptime, response time How do I raise a ticket? Email support@prosystem.com.bd, use the contact form, or pick up the phone. A named contact is attached to your account. ### [What's your response time?](https://www.prosystem.com.bd/support#faq-2) - Type: faq - ID: faq:/support#faq-2 - Tags: faq, response time, SLA, support, maintenance, technical support, incident response, training, upgrades, migration, data stewardship, master data, continuous enhancement, uptime, response time What's your response time? Response windows are written into your support agreement and measured against every incident. Critical incidents are prioritised and addressed the same business day. ### [Are new features included in support?](https://www.prosystem.com.bd/support#faq-3) - Type: faq - ID: faq:/support#faq-3 - Tags: faq, scope, enhancements, support, maintenance, technical support, incident response, training, upgrades, migration, data stewardship, master data, continuous enhancement, uptime, response time Are new features included in support? Platform releases are included. Custom changes a new integration, a new report, a workflow extension are scoped as Continuous Enhancement and delivered in rolling cycles. ### [Do you handle data work beyond incidents?](https://www.prosystem.com.bd/support#faq-4) - Type: faq - ID: faq:/support#faq-4 - Tags: faq, data, master data, reconciliation, catalogue, stewardship, support, maintenance, technical support, incident response, training, upgrades, migration, data stewardship, master data, continuous enhancement, uptime, response time Do you handle data work beyond incidents? Yes. Master data setup, bulk imports, catalogue curation, reconciliation and audits are part of the same engagement the foundational work that keeps reporting accurate as the business grows. ### [Do you migrate data off legacy systems?](https://www.prosystem.com.bd/support#faq-5) - Type: faq - ID: faq:/support#faq-5 - Tags: faq, migration, legacy, cutover, support, maintenance, technical support, incident response, training, upgrades, migration, data stewardship, master data, continuous enhancement, uptime, response time Do you migrate data off legacy systems? Yes. Parallel running, staged cutover and zero downtime through busy hours. Reconciliation report signed before the legacy system is archived. ### [Is there a minimum term?](https://www.prosystem.com.bd/support#faq-6) - Type: faq - ID: faq:/support#faq-6 - Tags: faq, contract, term, support, maintenance, technical support, incident response, training, upgrades, migration, data stewardship, master data, continuous enhancement, uptime, response time Is there a minimum term? Twelve months, renewing annually. Shorter arrangements are possible where the need is clear and the deployment is small. ### [What happens when we need something new?](https://www.prosystem.com.bd/support#faq-7) - Type: faq - ID: faq:/support#faq-7 - Tags: faq, enhancement, change request, feature, support, maintenance, technical support, incident response, training, upgrades, migration, data stewardship, master data, continuous enhancement, uptime, response time What happens when we need something new? Raise it as a Continuous Enhancement request. Small changes move in rolling cycles; larger projects are scoped through a Statement of Work, handled by the same team. ### [About ProSystem](https://www.prosystem.com.bd/about) - Type: page - ID: page:/about - Tags: about, company, mission, team, founded, 2020, Dhaka, Bangladesh, history Bangladesh-based IT services company building eCommerce, retail management and custom software for 30+ businesses and 200,000+ users. ProSystem Limited is a Bangladesh-based IT services company founded in 2020, headquartered in Dhaka. We build and run software for retail, F&B, healthcare, fashion, transport and security operations across Bangladesh and beyond. Four practices under one team: ProSystem BMS (business management), custom eCommerce websites, custom software engagements, and support & maintenance. The engineers who design and develop the system stay with it through launch and beyond. Leadership: Adnan Ahmed (CEO & Managing Director, co-founder) and Ahnaf Ahmed (CTO & Chairman). See /about/people for more. Scale: 30+ client businesses, 200,000+ end users, same-day go-live for single outlets, 99.5% uptime target (99.9% on Enterprise). Registrations: RJSC C-177767/2022 BASIS AS-22-07-010. ### [People](https://www.prosystem.com.bd/about/people) - Type: page - ID: page:/about/people - Tags: people, leadership, team, directors, founders, Adnan Ahmed, Ahnaf Ahmed, CEO, CTO, Chairman, Managing Director, Co-Founder The people behind ProSystem CEO Adnan Ahmed (business) and CTO Ahnaf Ahmed (engineering). ProSystem is led by two principals: Adnan Ahmed Chief Executive Officer & Managing Director. Co-founder. Business developer specialising in marketing optimisation and digital products. Experienced in delivering 30+ projects across ERP systems, eCommerce platforms and performance-driven strategies. Leads business development, client relationships and company direction. Ahnaf Ahmed Chief Technology Officer & Chairman. Software engineer focused on reliable, high-performance applications for corporate operations. Hands-on across the ProSystem BMS platform from POS, inventory and integrations to the eCommerce websites that extend them. Owns the platform, the code review bar and the uptime number. For business enquiries: hello@prosystem.com.bd. For engineering and support: support@prosystem.com.bd. ### [Companies we work with](https://www.prosystem.com.bd/companies) - Type: page - ID: page:/companies - Tags: clients, companies, portfolio The companies that run on ProSystem transport, healthcare, fashion, F&B, retail and security, across Bangladesh and abroad. ProSystem serves 30+ businesses across multiple industries. Each company links through to the case study covering the work we did with them. ### [Blog](https://www.prosystem.com.bd/blog) - Type: page - ID: page:/blog - Tags: blog, writing, engineering Notes on product, design and operations from the team at ProSystem Limited. The ProSystem blog covers product engineering, AI assistants, operations and the occasional long essay on software craft. ### [Case Studies](https://www.prosystem.com.bd/case-studies) - Type: page - ID: page:/case-studies - Tags: case studies, clients, stories Long-form write-ups of our work with ProSystem clients retail, eCommerce and custom software launches across Bangladesh and beyond. Case studies document the problem we were asked to solve, the approach we took, and the outcome with the metrics that moved. ### [Careers](https://www.prosystem.com.bd/careers) - Type: page - ID: page:/careers - Tags: careers, jobs, hiring What we work on at ProSystem Limited, how we work, and how to reach us if you'd like to contribute. Open roles in engineering, design and customer success Dhaka, Bangladesh. We hire engineers, designers and customer success people who care about the craft of developing software. Roles are mostly Dhaka-based with hybrid arrangements for senior staff. Apply by email at hr@prosystem.com.bd with a short note and a pointer to work you're proud of. ### [Contact](https://www.prosystem.com.bd/contact) - Type: page - ID: page:/contact - Tags: contact, phone, email, sales, support, careers, address, WhatsApp Talk to ProSystem Limited. Offices in Dhaka. Replies within one business day. Phone (sales and general enquiries): +880 1600 330 911. General / sales email: hello@prosystem.com.bd. Support email (existing clients): support@prosystem.com.bd. Careers email: hr@prosystem.com.bd. Offices in Dhaka, Bangladesh. Replies within one business day, typically sooner during business hours. Enterprise support clients also have a direct WhatsApp channel to the engineering team. To try the product directly without talking to sales, self-serve sign-up is available at https://bms.prosystem.com.bd/registration. ### [Documentation](https://www.prosystem.com.bd/documentation) - Type: page - ID: page:/documentation - Tags: docs, documentation, guides, API, reference Getting started, guides, API reference and changelog for ProSystem products. Four sections: Getting started (first outlet setup, user invites, payment providers), Guides (daily workflows), API reference (REST and webhooks), and the Changelog. ### [Partnerships](https://www.prosystem.com.bd/partnerships) - Type: page - ID: page:/partnerships - Tags: partners, partnerships, resellers Technology, reseller and consulting partners who build with ProSystem. Four partnership categories: Cloud & Infrastructure, Technology (payments, SMS, couriers, identity), Consulting (firms that implement ProSystem for their own clients), and Reseller (partners in markets we don't reach directly). ### [Press Kit](https://www.prosystem.com.bd/press-kit) - Type: page - ID: page:/press-kit - Tags: press, logos, brand, media kit Logos, wordmarks and a short company fact sheet for press and partners. Download ProSystem logos in SVG. Company facts: founded 2020, headquartered in Dhaka, RJSC C-177767/2022, BASIS AS-22-07-010. ### [Security](https://www.prosystem.com.bd/security) - Type: legal - ID: page:/security - Tags: security, compliance, data protection, encryption, SSO, 2FA How ProSystem protects client data: infrastructure, access control, monitoring and incident response. Infrastructure: cloud data centres, TLS 1.2+ in transit, AES-256 at rest. Access control: least-privilege staff access reviewed quarterly, mandatory SSO with hardware-backed 2FA for production, per-organisation user/role/permission management inside BMS. Monitoring and incident response run 24/7 with runbooks for priority incidents. ### [Privacy Policy](https://www.prosystem.com.bd/privacy) - Type: legal - ID: page:/privacy - Tags: privacy, GDPR, personal data, policy, Meta Pixel, Facebook Pixel, Conversions API, advertising, cookies, Cloudflare, Turnstile, bot detection, spam protection How ProSystem Limited collects, uses, and protects the personal data we handle. Covers the personal data ProSystem handles for clients, prospects and site visitors, how it is stored, and the rights you have over it. Advertising measurement and Meta tools: ProSystem uses Meta Pixel and Meta Conversions API to understand website interactions, measure campaign performance, attribute conversions and improve advertising. These tools may process page views, clicks, search and AI search interactions, contact and newsletter events, source URLs, IP address, browser and device information, _fbp and _fbc identifiers, and hashed contact identifiers where a visitor submits forms. Meta processes this information under its own Privacy Policy and Meta Business Tools Terms. Website protection and bot detection: ProSystem uses Cloudflare Turnstile on this website to verify whether a user is human rather than a bot, and to protect the site from spam, fraud and malicious abuse. Turnstile may collect technical information such as IP address, browser type and browser characteristics. Cloudflare processes this data under its own privacy policy and does not use it for targeted advertising or ad retargeting. See https://www.cloudflare.com/turnstile-privacy-policy/. ### [Terms of Service](https://www.prosystem.com.bd/terms) - Type: legal - ID: page:/terms - Tags: terms, legal, policy, privacy, cookies, Meta Pixel, Turnstile The terms governing use of ProSystem products and this website. The terms that govern the use of ProSystem products, services and this website. Website data and third-party tools are described in the Privacy Policy and Cookie Policy, including Meta Pixel, Meta Conversions API and Cloudflare Turnstile. ### [Cookie Policy](https://www.prosystem.com.bd/cookies) - Type: legal - ID: page:/cookies - Tags: cookies, policy, Meta Pixel, Facebook Pixel, Conversions API, advertising, _fbp, _fbc, Cloudflare, Turnstile, bot detection The cookies ProSystem sets and why. The cookies ProSystem sets on this website and in our products, and the categories they fall into. The site uses Meta Pixel and Meta Conversions API for advertising and conversion measurement. Meta Pixel may set or read identifiers such as _fbp and _fbc, and event data can include page views, clicks, searches, contact-form events, newsletter sign-ups, source URLs, IP address, browser and device information, and hashed contact identifiers where visitors submit forms. The site also uses Cloudflare Turnstile for website protection and bot detection. Turnstile may process technical information such as IP address, browser type and browser characteristics, and Cloudflare states this data is not used for targeted advertising or ad retargeting. ### [Putting an agent behind our own search bar](https://www.prosystem.com.bd/blog/ai-search-on-our-own-site) - Type: post - ID: post:ai-search-on-our-own-site - Tags: blog, AI, Engineering We rewrote search on prosystem.com.bd: a live typeahead under the box and an AI agent on submit. How it's built, what it can reach, and the three layers of abuse control before the model sees a request. By ProSystem Engineering 2026-04-24 6 min We rewrote the search on prosystem.com.bd a few weeks ago. The box looks the same, but underneath it's two things now: a live typeahead that resolves pages in under 50 ms, and an AI agent that answers open-ended questions with inline citations. This is a short write-up of how it's put together, what it costs, and what we'd choose differently if we did it again. Two tiers, not one Most visitors to a site's search bar aren't asking a question. They're navigating "bms", "pricing", "case studies" and they want the right page in the next keystroke. We didn't want every such query to round-trip through a model. So the search panel runs a client-side index as the user types. A `MiniSearch` instance holds every page, blog post, case study, client company, job listing and FAQ anchor on the site flattened into a few dozen searchable documents and renders grouped results under the box in real time. Typing "how long does a rollout take" surfaces the matching BMS FAQ; typing a client's name surfaces the case study; an empty query shows a curated "popular" list. The AI layer kicks in only when the user hits Enter. At that point the panel switches from a list of page matches into a streaming conversation, and the question goes to the server. The index, built once Every content source in the repo `posts.js`, `case-studies.js`, `companies.js`, `jobs.js`, plus the static landing pages exports its own content module. A small server-side layer imports them all at boot, flattens each FAQ into its own deep-linked document, and hands the result to a `MiniSearch` index with weighted fields (title 3, summary 2, tags 2, keywords 1.5). That same index is serialised into a slim JSON payload for the browser. The client build carries ids, titles, summaries, URLs and tags, but not full bodies. The server keeps the bodies and exposes them through a tool the agent can call when it needs to quote or reason across detail. One index, two views. One index, two views. An agent, not a mega-prompt The temptation with any AI-on-a-website feature is to stuff the whole corpus into the system prompt. We didn't. The system prompt is short a site map, a block of company facts (legal name, offices, hours, emails, registrations, leadership, socials) and a four-line tool-use policy. Everything else the agent needs, it fetches. Three tools hang off it. `search_site` runs `MiniSearch` over the server-side index and returns a ranked list. `get_document` returns the full body of one doc by id, so the model can quote or cross-reference. `web_search` is a thin fetch around Tavily, used only when the question is clearly off-site (industry trends, competitor info, current events) or when the first tool came back thin. The agent calls `search_site` first, escalates to `get_document` if the summaries aren't enough, and only reaches for `web_search` when the question genuinely isn't about us. Because the company-facts block lives in the system prompt, any identity or contact question "what's the CEO's name", "what are your office hours", "how do I email support" is answered without spending a tool call. Everything else does the full search dance. Three defenses before the model sees a thing A public AI endpoint is a free lunch someone will take. Before a request ever reaches the model, it passes three checks. First, a `Sec-Fetch-Site` / `Origin` / `Referer` same-origin test. If the browser claims this request isn't coming from our own page, it's rejected at the door. Second, an HMAC-signed session cookie minted on first page load, re-verified on every `/api/search` hit. A cookie forged on the client won't verify. Third, a per-IP sliding-window rate limit 30 requests per 10 minutes, with separate buckets for `/api/search` and `/api/message-assist` so the contact-form helper doesn't steal the search budget. None of these are impervious on their own. Together they raise the cost of abuse well above what this endpoint is worth. Streaming, citations, state machine The route handler streams the response with `streamText` and `toUIMessageStreamResponse`, and the client renders it through `streamdown` so the markdown arrives progressively. The model is told to cite inline with relative URLs `[BMS launch FAQ](/bms#faq-1)` and external sources with full origins, and to lead with the answer rather than narrate the search. The search panel itself is a small state machine. Empty input shows popular items. Non-empty input renders live typeahead with no API calls. Submitting swaps the list for the streaming conversation; a " View results" link swings back to the typeahead without losing scroll position. Follow-ups accumulate in the same thread for the session. What we'd do differently Two things, if we started over. First,... ### [Agentic RAG, in practice](https://www.prosystem.com.bd/blog/agentic-rag-in-practice) - Type: post - ID: post:agentic-rag-in-practice - Tags: blog, AI, Engineering Our inventory assistant looks like RAG from a distance. Up close it's a different pattern and the distinction decides what kind of data it can answer from. By ProSystem Engineering 2026-04-22 5 min From a distance the inventory assistant we wrote about looks like a RAG system a model grounding its answer in retrieved context. Up close it's a different pattern, and the distinction is worth a short post: it decides what kind of data the assistant can answer from and how fresh those answers are. What RAG actually is RAG retrieval-augmented generation is a specific pattern. You take a corpus of text (PDFs, documentation, support transcripts, release notes), split it into chunks, embed each chunk as a vector, and store those vectors in a database that can search by similarity. At query time, the user's question is embedded too, the top-k closest chunks are pulled out, and they're stuffed into the model's prompt as context. The model reads the chunks and writes an answer grounded in them. It's a beautiful pattern for unstructured knowledge. The catch: the answer is only as fresh as the last indexing run, only as precise as the embedding model's sense of similarity, and only as complete as the chunks that happen to land in the top-k. What we built instead Our inventory assistant doesn't embed anything. When a user asks "how many blue T-shirts in size small at the Dhanmondi outlet," the model doesn't retrieve chunks of text it calls a tool. The tool takes a typed input, runs a MongoDB aggregation against the tenant's live database, and returns a structured result. The model reads that result and answers. The industry term is tool-augmented generation, or function calling. The research community sometimes calls it agentic RAG to emphasize that the model decides which query to issue. The mechanism is different in kind, not degree. Four differences that matter Freshness. Vector RAG answers from whatever was last indexed yesterday, last week, whenever the pipeline last ran. A tool call hits the live database, so "how many units sold in the last hour" is a legitimate question. Precision. A pipeline with $match and $group returns a number. Similarity search returns a set of probably-relevant passages and the model has to reconcile them. For quantitative questions count, sum, average, top-N the tool path is unambiguous. Writes. Classical RAG is read-only by design: retrieval doesn't mutate state. Our tools can transfers, adjustments, receiving, price edits as long as the user approves each one. That's beyond what RAG is for. Cost profile. RAG pays for embeddings (once per chunk, re-run whenever the source updates) plus a similarity search per query. Tool calling pays for a schema preflight plus the query itself. Neither is strictly cheaper; they're optimized for different data. When the answer lives in rows, tool calling wins. When it lives in paragraphs, RAG wins. Where we would still reach for RAG Structured data lives in a database. Unstructured knowledge lives in prose manuals, runbooks, support transcripts, release notes. If we were building a "what did this feature used to do" assistant, or a "how do I configure a new outlet" assistant, a vector store over our documentation would be exactly right. The model would answer from the docs, with citations to the source chunks. The difference comes down to the shape of the data. Sometimes a single assistant wants both the support bot that quotes the manual and then checks the account and you end up with both patterns running under the same conversation. The right tool for the right data It's tempting to call everything that augments an LLM "RAG," because the high-level shape is the same retrieve context, then generate. But naming matters: it sets the expectation for what the system can do. A tool-calling agent that can move stock does not share safety considerations with a doc-search bot, and flattening the distinction costs engineers a mental model they need. We went with tools because inventory lives in rows. We'd choose differently for a corpus that lives in paragraphs and the next piece of the assistant, a help bot that answers from the BMS manual, probably will. ### [Making inventory feel like a conversation](https://www.prosystem.com.bd/blog/ai-inventory-assistant) - Type: post - ID: post:ai-inventory-assistant - Tags: blog, AI, BMS, Engineering An AI assistant we're building into BMS how a fast intent router, a typed tool library and a confirmation loop turn stock management from a form into a sentence. By ProSystem Engineering 2026-04-22 6 min Ask a warehouse manager how much of a product they have left across three outlets. They open four screens, filter twice, and read you a number. Our AI inventory assistant answers the same question in a sentence and, if the conversation is heading there, offers to transfer the stock it just found. Why a conversation, not a form Most inventory tools are a stack of forms. You know what you want, but you have to translate it first into which screen, then into which filter, then into which column. A chat interface short-circuits the translation: you ask, the system does the column work, and you see the answer in plain English. When the answer isn't enough on its own, the same thread carries into the next action without a context switch. The hard part isn't the chat bubble. It's making the model safe and specific enough that a sentence like "transfer ten blue T-shirts from the main warehouse to Dhanmondi" doesn't end in the wrong store with the wrong count. That is what the architecture below is for. Two passes instead of one Every user message goes through a small, fast router before the main model sees it. The router is a single-token call to a lightweight LLM with a strict system prompt: return one word "chat" or "inventory." Greetings, acknowledgements and small talk fall into the first bucket; anything touching stock, transfers, items or locations falls into the second. For "chat" we strip the tool library out of the next call the model answers conversationally without the overhead of a nineteen-tool context. For "inventory" we keep the tools attached and let the model plan. The net effect: warm small talk stays cheap, and the full pipeline kicks in only when it's earned. A tool library, not a prompt The assistant isn't a monolithic prompt with "rules." It's the main model plus nineteen named tools schema introspection, read-only queries over a dozen collections, stock transfers, adjustments, receiving, price and media edits, and a web-search escape hatch via Tavily. Each tool declares its input schema with Zod; each tool's description is written for the model, not for humans. The important split is inside the library. Reads execute immediately: the model calls them, gets a result, keeps planning. Writes don't they're declared without an execute function, which signals the AI SDK to surface a confirmation card in the UI. Nothing moves stock without a user's yes. Nothing moves stock without a user's yes. The approval loop, made idempotent When a user confirms a write, the approved tool call comes back in the next request and hits the server's tool executor. Before running the operation we check a ten-minute TTL cache keyed by the tool-call ID if the same approval is replayed (a network reconnect, a refresh mid-stream), we return the cached result instead of running the operation twice. That turns an AI-driven chat into something that behaves like a well-written POST endpoint. Tenant, permission, schema Before any tool runs, the request clears three gates: it's authenticated (per-request session validation), the user holds the VIEW_ITEMS permission, and any query tool first calls getSchemaContext for its target collection. The last one is explicit in the tool's own description the model is told, in prose, that it must read the schema before writing a pipeline. That removes a class of silent failures where the model invents a field that doesn't exist in this tenant's data. Database connections are scoped per tenant. The tool executor is built fresh for each request around a tenantId; there is no shared pool where the AI could accidentally read another company's records. Step-bounded, cache-friendly The main generation runs with a hard ceiling: at most seven planning steps before the stream must terminate. In practice a typical query resolves in two one to pull schema, one to run the aggregation but the bound keeps pathological loops out of production. Everything runs through Vercel's AI Gateway with caching set to auto. The system prompt and schema payloads hit the cache; user messages don't. On a warm cache, a question like "which items expire next month" costs a fraction of what a cold one does, and the user sees a faster response. What we're still working on The write-class tools are the most fun and the most dangerous. Simple transfers work well today; larger flows adjustments across a whole stocktake, bulk price updates need a better summary card before we put them in front of customers. We would rather develop one fewer capability than a capability that moves stock you didn't mean to move. Intent classification is also a moving target. The current router is a small heuristic on top of a small LLM; the heuristic catches "hi" and "thanks" locally, the LLM handles the rest. Over time we exp... ### [Why we build both ends in-house](https://www.prosystem.com.bd/blog/front-end-and-back-end-together) - Type: post - ID: post:front-end-and-back-end-together - Tags: blog, Product, Engineering The website and the stockroom aren't separate problems. A short note on why we develop them together. By ProSystem Engineering 2026-04-02 4 min Most of the agencies we replaced built pretty websites and left the back office to someone else. The result was predictable: the front said one thing, the back said another, and a reconciliation meeting closed the gap every Friday. Two halves of the same problem A website is a promise: we have this, it costs this, you can have it by Thursday. A back office is the system that has to keep that promise stock, fulfilment, payments, returns. Treating them as separate systems means the promise breaks on the seam. The front and the back aren't separate problems. We build both ends. The website reads from the same records the warehouse writes to. When a stock unit moves, the website knows. When an order clears payment, the till has it. There is no seam and no reconciliation meeting. It's also why we insist on hosting the whole stack ourselves. DNS, SSL, deploys, monitoring all of it under one roof, run by the people who wrote the code. The halves don't drift apart when one team owns both. ### [Running retail on one source of truth](https://www.prosystem.com.bd/blog/one-source-of-truth) - Type: post - ID: post:one-source-of-truth - Tags: blog, BMS, Operations Every multi-branch launch we've done starts with the same question: is there one record for this, or are there four? By ProSystem Customer Success 2026-03-04 5 min When a retailer comes to us with two outlets and spreadsheets, the fix is obvious. When they come to us with eight outlets, six tools and a month of disagreement about last quarter's numbers, the fix is the same it just takes more patience. Where drift starts Every outlet that has its own spreadsheet has its own version of the truth. Headquarters sees a reconciled view; the floor lives inside something else. Drift isn't a bug, it's the natural state of a multi-tool setup. What one record gets you When a sale at one outlet updates the same inventory record the warehouse reads, reconciliation stops being a task. Customer returns hit loyalty and ledger at once. A price change in shared data rolls across every outlet the next time a till opens. None of that is magic. It's a choice we make on day one stock lives in one place only and defend across every feature request after. How we phase it in For a multi-branch launch we pilot at one outlet for a short window, with the manager on-site, then ripple out in small waves. By the time the last outlet is live, we've caught the edge cases that would otherwise show up on the first busy weekend. ### [Five years, 30+ clients, one practice](https://www.prosystem.com.bd/blog/five-years-thirty-clients) - Type: post - ID: post:five-years-thirty-clients - Tags: blog, Company A short checkpoint on what we've tried to protect and the one thing we'd like to get better at. By ProSystem 2026-02-09 3 min Five years since we incorporated in Dhaka. Thirty-plus businesses and more than two hundred thousand users on ProSystem software. It's a reasonable checkpoint to ask the question founders don't ask often enough: is the company we're running still the company we'd want to join? What we've tried to protect Taste, quietness, and a small team. We've turned down bigger clients when the fit was wrong, and bigger rounds when the terms were. Neither was easy. Both were right. We still work with the first client we took on in 2020, and we intend to work with them for another five. What we'd like to get better at Writing things down. We're good at building the thing; we're less good at explaining why. This blog is part of the answer. If there's something you'd like us to write about, email hello@prosystem.com.bd we read everything. ### [KAVAZO KAVAZO eCommerce & operations, on a single system](https://www.prosystem.com.bd/case-studies/kavazo) - Type: case-study - ID: case-study:kavazo - Tags: case-study, F&B, KAVAZO, BMS, POS, eCommerce, F&B KAVAZO introduced their eCommerce powered by ProSystem BMS, joining the outlets, the hotline, the factory and every delivery partner under one platform. Industry: F&B Problem: KAVAZO sells through outlets, a customer care hotline, corporate accounts and delivery partners. The factory feeds the outlets, the outlets feed the customers, and HQ needs the whole operation in one view. Approach: We spent time on the floor with the team to map how the operation moves, then deployed ProSystem BMS to span every part of it from factory stock through to every sales channel. Outcome: Every sales channel runs from the same data, stock transfers carry a full audit trail, and the system holds up under concurrent writes across the outlets, the hotline and the factory so HQ gets real-time insight without anyone compiling it. Sales channels: Unified HQ insight: Real-time Outlets: 3 The KAVAZO team had grown an operation that no single tool was keeping up with a factory feeding three outlets, a hotline taking direct orders, corporate accounts and three delivery partners running their own curated menu. Keeping all of that consistent had been falling on people, by hand. On the floor with the team We spent time at the factory, behind the goods-in door and at the counter. The goal was to understand how product moves from the factory through distribution to the customer, and where information was crossing between people on paper, on the phone and in messages. The system we deployed mirrors that real flow. One menu, many faces The system carries the regular items, the bundled offerings, and a curated menu for delivery partners FoodPanda, Pathao and Foodi. A change to a master item propagates to every channel where it appears. Seamless ordering on KAVAZO's own website Alongside the delivery partners, the KAVAZO website takes orders straight from customers. The same menu and pricing structure run it, and online orders land in the same queue as the hotline and the counter, so the kitchen sees one list of work regardless of where the order came in. The site also handles custom orders customers attach references of what they want and the request reaches the team with everything attached, ready to discuss and quote. Corporate and direct orders Corporate orders run through a workflow built for them, with their own pricing and billing terms sitting on the order. The hotline writes into the same system as the counter, so phone orders and walk-ins move through the same flow. Stock transfers with a full audit log Every transfer between the factory and the outlets is recorded as a transaction with a full audit log what moved, when, who initiated it and who received it. Discrepancies surface in the log, where they can be traced back to the moment they happened. Built for concurrent operations on any device The interface runs in the browser, so the same staff can use it on a counter terminal at an outlet, a tablet at the factory or a phone on the hotline. Behind it, the system handles concurrent writes from staff across the three outlets, the customer care hotline and the factory at the same time, with operations designed to be idempotent so a retry on a flaky network never doubles a stock movement or a sale. Where it sits today HQ opens the system and sees the operation as it is sales by channel, stock by location, transfers in motion, partner numbers with the data ready as soon as the page loads. The BMS simplifies an extensive operation enough that the team running it can stay focused on the product. ### [SKINN ERP and website for SKINN, by Prof. M.N. Huda](https://www.prosystem.com.bd/case-studies/skinn) - Type: case-study - ID: case-study:skinn - Tags: case-study, Healthcare, SKINN, ERP, Clinic, Pharmacy, Healthcare ProSystem ERP runs SKINN's front desk and pharmacy on one application, kept as separate entities so each side stays focused on its own workflow. Industry: Healthcare Problem: SKINN's dermatology clinic and pharmacy share one roof front desk operations on one side, inventory and reporting on the other and both needed to work as one system. Approach: We deployed an ERP where the front desk and the pharmacy run as separate entities in one application a clean separation of concerns with automated SMS for procedures that need reminders. A website carries the practice's public face, with treatments and a booking form. Outcome: SKINN gained a unified operating system for its dermatology clinic and pharmacy. The ERP keeps front desk and pharmacy workflows distinct, while connecting bookings, reminders, inventory, and reporting into one reliable flow, making daily operations faster, clearer, and easier to manage. Front desk: Unified Pharmacy: Integrated Patient reminders: Automated A clinic that runs both consultations and a pharmacy under one roof carries two operations side by side the patient visit on the front desk, and a dispensing operation with its own stock, suppliers and reporting. The ERP underneath has to hold both without the team having to bridge them by hand. Front desk on one workspace Appointments, bookings, procedure billing and prescriptions all run from the same workspace. Reception books a slot, the doctor records the consultation and prescription, billing settles the invoice every step writing into the same patient record, so a returning patient is recognised the moment they walk in and their history is already on screen. Automatic SMS for patient, doctor and staff The system sends SMS reminders to the patient ahead of an appointment, to the doctor for relevant procedures, and to the PRO when their attendance is needed. The reminders are tied to the procedure type, so each role only hears about what's relevant to them, and the front desk stays focused on the patient in front of them. Pharmacy as a separate entity The pharmacy runs as its own entity inside the same ERP application kept separate from the front desk so each side stays focused on its own workflow. It carries the full pharmacy inventory, with stock, prices and movement recorded against each item, ready to draw on whenever those items sell. Reports that fall out of the work Sales, stock movement and patient flow all leave a record in the system as the team works. Month-end reports by item, by category, by doctor fall out of that data directly, so the team isn't compiling them from receipts and notebooks at the close of every month. The website patients arrive on Alongside the ERP, the SKINN website carries the practice online. A landing page lays out the important parts of the clinic in clear sections, a treatments list lets visitors browse the services on offer with filters for category and common causes, and a booking form lets a patient reserve a consultation with a doctor with the request reaching the front desk on the same system. Where it sits today The front desk and the pharmacy run side by side on one ERP, the website routes new patients through to the same workflow, and reporting that was compiled by hand falls out of the work that's already happening. ### [ARFIN BMS and eCommerce for ARFIN, since inception](https://www.prosystem.com.bd/case-studies/arfin) - Type: case-study - ID: case-study:arfin - Tags: case-study, Fashion, ARFIN, BMS, eCommerce, Fashion ARFIN's POS, eCommerce and operations all run on ProSystem BMS. Industry: Fashion Problem: ARFIN's craft brand was growing across multiple sales channels, and the operational stack underneath needed to grow with it. Approach: We designed and developed the system end-to-end alongside the ARFIN team, shaped around the way the brand actually runs its day-to-day. Outcome: ARFIN gained a complete business management system for selling, tracking, and operating across channels, from POS to eCommerce, with the structure needed to support continued brand growth. Sales channels: In sync Partner since: 2020 Brand voice: End-to-end ARFIN Handcrafted Footwear Co. is a leather-goods craft brand we've been building with since 2020 five years alongside a brand that's grown steadily across the partnership. Refined alongside the team The POS wasn't designed in isolation. We watched the team handle real customer interactions on the shop floor, took note of where friction surfaced, and made refinements steadily each round of observation reached the next. Five years on, the POS fits the way the team actually moves through their operations. How we developed We designed and developed the system end-to-end: ProSystem BMS, carrying the cloud POS for the atelier and everything that supports it, alongside an eCommerce site for online customers. Walk-in sales at the atelier, eCommerce orders and social media sales all flow through the same system, regardless of how the customer reaches ARFIN. Short SKUs the team thinks in Each piece carries a short SKU that the team uses to identify it on the floor, online or on a call. ARFIN's own SKU scheme is short and readable, and the system's search is built to match staff identify the piece in a second or two during discovery and at the counter. Five years later The platform has carried ARFIN through catalogue expansion and steady brand growth, holding firm underneath the day-to-day. The team's time has shifted to where it belongs on the craft. ### [RANGS MOTORS LTD. RANGS Motors' corporate website](https://www.prosystem.com.bd/case-studies/rangs-motors) - Type: case-study - ID: case-study:rangs-motors - Tags: case-study, Transport, RANGS MOTORS LTD., Website, Corporate, Transport RANGS Motors catalogue, corporate content, events, and offers are managed through one CMS, giving the marketing team full control over the website. Industry: Transport Problem: RANGS Motors needed a corporate site that could carry the breadth of their catalogue, present each vehicle in detail, and let the marketing team keep it current themselves. Approach: We collected the team's marketing materials and built the site around them vehicles, company, events and offers, all turning like the pages of a brochure. Outcome: Customers can browse the brand, compare vehicles, explore offers, and read detailed catalogue pages in one smooth experience. Behind the scenes, the marketing team can update vehicles, events, and campaigns directly through the CMS. Catalogue: Live Publishing: In-team Navigation: Streamlined RANGS Motors distributes some of the most recognised commercial-vehicle brands in the country. The brief was twofold: build a corporate site that does justice to the catalogue and the brand, and put publishing in the team's hands so the site keeps moving as the lineup evolves. Working from the team's own materials Before we wrote a line of code, we sat with the RANGS Motors marketing team and went through every brochure, spec sheet, partner-supplied asset and existing campaign piece they had. The site is built from those materials directly photography, copy, technical detail, brand notes so the page reads as something the team recognises. An intuitive vehicle listing The vehicle listing page is filterable by vehicle category and brand. A buyer looking for a specific class of vehicle, or a specific manufacturer, narrows the catalogue in two clicks; the rest of the page reflects the filter without a refresh. Vehicle pages that turn like a brochure Each vehicle has a detail page split into three tabs attributes (the unique things that distinguish this vehicle), specifications (the full technical breakdown), and reviews (what customers and the trade have said). Switching tabs feels like turning a page rather than loading a new one: the content slides in from the side, so the buyer's place in the vehicle's story is never lost between tabs. Beyond the catalogue The site carries the company's wider story alongside the vehicles. Sections cover the company itself history, leadership, after-sales footprint together with upcoming events, current promotional offers and campaign pages. Each is a content type the team can update; a new event or offer reaches the site the day it's announced. Navigation between these sections uses the same page-turn transitions, so moving across the site feels seamless rather than jumping between pages. Bangla and English, on every page The site is fully bilingual. Every page reads in either Bangla or English, with the visitor's choice held across the catalogue, the company sections and the editorial pieces. The translation layer is built directly on standard i18n functionality rather than a third-party plugin, so the team owns the copy in both languages from the same CMS and the language switch is instantaneous. Editable end-to-end Every page is editable without a developer copy, imagery, attributes, specs, reviews all from a CMS the team owns. Hosting, DNS, SSL and release pipelines run on ProSystem's stack; the team focuses on content, we keep the surface live. ### [ZEISS VISION CENTER POS and eCommerce for ZEISS Vision Center](https://www.prosystem.com.bd/case-studies/zeiss-vision-center) - Type: case-study - ID: case-study:zeiss-vision-center - Tags: case-study, Healthcare, ZEISS VISION CENTER, BMS, POS, eCommerce, Healthcare A multi-outlet POS and eCommerce website for OPSIS, running the ZEISS Vision Center network. One platform across every outlet, a deep catalogue customers can browse online, and a customer journey that's tracked from order to pick-up. Industry: Healthcare Problem: OPSIS run the ZEISS Vision Center network with a deep catalogue across multiple outlets every ZEISS lens and frame line, plus sunglasses from popular brands. They needed POS, online sales and the prescription record to work as one. Approach: We deployed ProSystem BMS across every outlet and developed the eCommerce by plugging it into the BMS, so the counter, the catalogue and the customer record all run from one platform. Outcome: ZEISS Vision Center gained a unified retail system across every outlet and online. Catalogue, stock, pricing, prescriptions, and customer orders all stay connected, giving OPSIS tighter operational control and giving customers a smoother path from product discovery to pick-up. Catalogue: Extensive Customer updates: Automated Outlets: 2 An optical chain runs on three things working together the customer's prescription, the inventory at the nearest outlet, and the order they're placing. OPSIS needed all three on the same platform across every ZEISS Vision Center. Multi-outlet POS Every outlet runs ProSystem BMS at the counter. Sales, returns, walk-in prescriptions and customer records all post into the same system, so a customer recognised at one outlet is recognised at every outlet, and outlet managers see stock across the whole network instead of just their own shelves. The full ZEISS range, plus the brands customers ask for The catalogue carries every ZEISS lens line and the frames that go with them, alongside sunglasses from the popular brands customers come in asking for. Each product is structured against the attributes that actually matter frame shape, material, lens type, coating, brand, gender, price band so the same data drives the POS lookup and the website filters. An eCommerce website built around the catalogue The website opens the inventory up to the customers who want to browse before they walk in. Filterable by brand and attribute, paginated cleanly, with product pages that lead with the photograph and the specs serious buyers check. Stock and pricing are pulled live from BMS, so what's online is what's actually available. Prescription module Optometrists record the vision test directly in BMS during the consultation. The prescription generates as a PDF on the ZEISS Vision Center letterhead and emails to the customer in one click, and the same record stays attached to the customer for future visits and reorders. SMS at every step of the order Eyewear orders move through stages confirmation, lab scheduling, ready for pick-up, completion. Each stage triggers an automated SMS to the customer, so they know where the order stands without calling the outlet. The notifications are wired into the BMS order workflow, so an outlet only has to advance the status and the message goes out. Where it sits today POS and eCommerce run as one platform across every ZEISS Vision Center. Customers find what they want online, walk in to a counter that already knows them, and stay in the loop until their eyewear is in their hands. ### [AMISHEE FINE JEWELS A presentation-led website for AMISHEE Fine Jewels](https://www.prosystem.com.bd/case-studies/amishee) - Type: case-study - ID: case-study:amishee - Tags: case-study, Fashion, AMISHEE FINE JEWELS, Website, Luxury, Fashion A website for AMISHEE designed like a lookbook collections lead, words follow. Enquiries arrive through a quiet contact flow. Industry: Fashion Problem: AMISHEE needed a website that felt as considered as the pieces themselves pace, restraint, and photography given room to breathe. Approach: We built the site around the photography and the atelier's language, with a discreet enquiry path and a content model the team can update themselves. Outcome: AMISHEEs website now works as a digital lookbook for the brand quiet, image-led, and deliberate. Visitors experience the collections before being guided into a discreet enquiry flow, creating a more considered path from discovery to contact. Voice: Atelier-led Enquiry path: Discreet Collections: Curated Luxury jewellery doesn't sell the way fast fashion does. The website's job is to set tone first and ask for an action second and to look as careful as the work it represents. How we approached it We worked from the photography outwards: layouts that frame the pieces, a content model that handles bespoke commissions, and an enquiry flow short enough to keep serious clients with us through to the end. Where it sits today The site is built to hold attention. Visitors linger over the photography, move through the collections at their own pace, and arrive at the enquiry already engaged with the brand. ### [RANGS PHARMACEUTICALS LTD. Corporate website for RANGS Pharmaceuticals](https://www.prosystem.com.bd/case-studies/rangs-pharmaceuticals) - Type: case-study - ID: case-study:rangs-pharmaceuticals - Tags: case-study, Healthcare, RANGS PHARMACEUTICALS LTD., Website, Corporate, Healthcare A broad corporate website for RANGS Pharmaceuticals, designed and developed end-to-end, covering every area of the organisation in a single, considered system. Industry: Healthcare Problem: RANGS Pharmaceuticals needed a corporate site that carried the full breadth of the organisation with the polish a regulated industry expects. Approach: We designed and developed end-to-end from the product photography through visual design to a CMS that gives every area of the organisation its own clear, editable section. Outcome: RANGS Pharmaceuticals now has a structured corporate website that reflects the scale and credibility of the organisation. Products, certifications, and company updates can be reviewed and published through the CMS, keeping the site current with less operational friction. Content: Structured Reviews: In-CMS Releases: One-click A pharmaceuticals corporate site has to do two things at once: communicate clearly to non-specialists and be precise enough for regulators and partners. The structure of the content matters more than the visual flourish. What we developed Therapeutic areas, products, certifications and careers as first-class content types. Editors work with structured fields, not free-form pages so a product entry is consistent everywhere it appears, and a certification update propagates without anyone tracking down stale references. Where it sits today The site stays current because updates fit into the team's existing workflow. Hosting, DNS and release pipelines are on ProSystem's stack. ### [OilCo Bangladesh OilCo Bangladesh, online and at scale](https://www.prosystem.com.bd/case-studies/oilco-bangladesh) - Type: case-study - ID: case-study:oilco-bangladesh - Tags: case-study, Transport, OilCo Bangladesh, BMS, eCommerce, Auto-parts A high-volume auto-parts eCommerce site with a structured catalogue, clear product pages and ProSystem BMS supporting the operation behind the scenes. Industry: Transport Problem: OilCo needed an online catalogue that could carry a wide auto-parts range while staying easy for buyers to search, compare and order from. Approach: We structured the catalogue around how customers look for parts, designed product pages for quick scanning, and connected the storefront with BMS. Outcome: A clear eCommerce experience for a large product range, with catalogue, stock and orders managed through one connected system. Performance: Optimized Stack: Scalable Traffic: High-volume OilCo Bangladesh needed an eCommerce experience that could carry a broad auto-parts catalogue without making customers work too hard to find the right item. The project focused on clear product discovery, fast browsing and a connected back office. A catalogue organised the way auto-parts customers actually shop Products are organised by vehicle type, brand, system and application, so buyers can narrow the range quickly instead of scrolling through the full catalogue. The structure is managed from BMS, keeping the website easier to maintain as the product range changes. Product pages with clear hierarchy Each listing leads with the information buyers need first, then supports it with specifications, variants and related context. The layout keeps dense product information readable without flattening everything into the same level of importance. Built for online orders The storefront is tuned for fast browsing and checkout, with ProSystem BMS supporting catalogue, stock, orders and customer records behind the scenes. Where it sits today OilCo now has a cleaner online buying experience for a large auto-parts catalogue, with the website and back office working from the same operational system. ### [SHIELD SECURITY SERVICES LTD. Corporate website for security company](https://www.prosystem.com.bd/case-studies/shield-security) - Type: case-study - ID: case-study:shield-security - Tags: case-study, Security, SHIELD SECURITY SERVICES LTD., Website, Corporate, Security A website for SHIELD Security Services that surfaces services, sectors served and accreditations clearly designed so buyers can do their diligence before the call. Industry: Security Problem: Security buyers do their diligence before they call. SHIELD needed a site that surfaced capabilities, sectors and accreditations without making prospects search for them. Approach: We organised the site around services, sectors and accreditations the things serious buyers actually evaluate with contact routes structured so the right enquiry reaches the right desk. Outcome: Prospects can now assess SHIELDs capabilities, sector experience, and accreditations before making contact, leading to better-qualified enquiries from the start. Services: Structured Accreditations: Surfaced Enquiries: Routed Security services are bought after diligence, not on impulse. The website's job is to answer the questions a serious buyer brings capabilities, sectors served, accreditations. Designing for first impressions We designed a contemporary visual language for the site clean layouts, considered typography, photography that frames the work seriously and gave each part of the company its own comprehensive page. The brand reads as the kind of organisation a serious buyer wants to work with on first sight. Clientele as a trust signal A dedicated clientele section showcases the organisations SHIELD already protects. Logos sit alongside short notes on the engagement, so a prospect can see the company is trusted by names they'd recognise the most direct trust signal in this category. Where it sits today The site does the heavy lifting before the call. Hosting and release run on our stack; the words and the work are SHIELD's. ### [ZAAR BMS and eCommerce for ZAAR, women's footwear brand](https://www.prosystem.com.bd/case-studies/zaar) - Type: case-study - ID: case-study:zaar - Tags: case-study, Fashion, ZAAR, BMS, POS, eCommerce, Fashion A POS for the outlets, an eCommerce site for online customers, and ProSystem BMS underneath. Online and in-store sell from one operation. Industry: Fashion Problem: ZAAR's footwear retail was growing into a multi-channel operation, and the system underneath needed to grow with it. Approach: We designed and developed the system end-to-end: ProSystem BMS, carrying the cloud POS for the outlets and everything that supports it, alongside an eCommerce site for online customers. Outcome: ZAAR gained a unified retail system for selling across outlets and online. ProSystem BMS keeps POS, eCommerce, inventory, and daily settlement connected, helping the team operate multiple channels. Channels: In sync Inventory: Unified Stock: Live ZAAR is a footwear retailer we've been building with since 2020 back then, a single outlet finding its feet. The brand has grown into a multi-outlet operation since, with the platform adapting alongside it as each new outlet came online. How we developed ProSystem BMS sits at the centre, with the cloud POS at the outlets and the eCommerce site online both reading and writing to it. The two surfaces see the same stock at the same second, so a sale on the floor is reflected online before the next visitor reaches the page. Where it sits today Online and in-store run from one operation. Stock-out cancellations stay rare, and the close-of-day comes out clean. The team's time has shifted to merchandising and customer care. ### [PASTRYARCHY POS and eCommerce for PASTRYARCHY's cloud bakery](https://www.prosystem.com.bd/case-studies/pastryarchy) - Type: case-study - ID: case-study:pastryarchy - Tags: case-study, F&B, PASTRYARCHY, BMS, eCommerce, F&B A connected eCommerce and POS system managed by the team from intake through preparation and pickup. Industry: F&B Problem: PASTRYARCHY needed a clearer way to manage incoming orders one that kept the kitchen aligned and made the pickup process smoother. Approach: We made ProSystem BMS the central order book, with the website writing orders into it directly and the kitchen and dispatch reading from the same record. Outcome: PASTRYARCHY gained a cleaner order-to-pickup workflow. Customer orders flow straight from the website into ProSystem BMS, giving the kitchen and dispatch team one reliable view of preparation status and fulfilment. Delivery: On-time Orders: Streamed in A cloud bakery wins or loses on the lag between an order arriving and the kitchen seeing it. Reduce that lag, and the rest of the operation gets easier. How we developed ProSystem BMS holds the central order book. The website writes orders into it directly, and the kitchen displays and dispatch read from the same record. An order travels intact from the customer's tap on place-order through to pickup. Where it sits today The kitchen sees orders the moment customers place them, and there's one queue internally regardless of where the order originated. Pickup times track the published estimates instead of the staff catching up to them. ### [MAINUL A scalable BMS and eCommerce for MAINUL](https://www.prosystem.com.bd/case-studies/mainul) - Type: case-study - ID: case-study:mainul - Tags: case-study, Fashion, MAINUL, BMS, POS, Fashion A portable POS that runs on any device, an eCommerce side that carries the brand online, and custom modules for menswear tailoring. Industry: Fashion Problem: MAINUL needed a POS the team could pick up without a learning curve, light enough to take to exhibitions across different venues. As the brand grew into bespoke menswear, the system needed to be scalable. Approach: We deployed a cloud POS that runs on any device along with a eCommerce website, then developed custom modules to support their bespoke workflow. Outcome: MAINUL gained a lightweight, scalable system for selling across stores, exhibitions, and bespoke menswear. The POS works from any device, while custom modules support the details of tailored orders without adding complexity to the teams day-to-day. POS: Portable Catalogue: Organised Bespoke orders: Modelled MAINUL is a fashion brand that has grown from retail into bespoke menswear tailoring. Across that journey, the system underneath had to be two things at once easy enough for any team member to pick up at the counter, and adaptable enough to grow as the brand's offering broadened. POS light enough for any device The POS runs in the browser on any device the team has at hand a counter terminal at the showroom, a tablet at an event. MAINUL takes that portability to exhibitions across different venues, running sales, capturing customers and managing the catalogue from whatever device they brought along. The catalogue side is shaped around ease of use, so a new staff member is productive without a long onboarding. Adapting as MAINUL grew into bespoke menswear As the brand moved into bespoke menswear tailoring, the system grew with it. We added a bespoke orders flow with its own workflow, and a measurements module that captures the customer's specs and ties them back to their record. New offerings reached the team as features without disrupting the day-to-day at the counter. Where it sits today The POS goes wherever the team needs it counter, exhibition floor, anywhere a sale happens. The catalogue is managed by the team day-to-day, and bespoke orders are captured with the measurements that drive them. A returning customer is recognised on their next visit, with their history already on screen. ### [TAHAR eCommerce and BMS for TAHAR, a fashion retail brand](https://www.prosystem.com.bd/case-studies/tahar) - Type: case-study - ID: case-study:tahar - Tags: case-study, Fashion, TAHAR, BMS, eCommerce, Fashion An eCommerce site for TAHAR that carries the brand online with refined design, conversion-focused shopping flows, and ProSystem BMS keeping website stock aligned with the retail store inventory. Industry: Fashion Problem: TAHAR needed an online channel that could present the brand with the same care as the physical retail experience, while giving customers a clear and reliable path to purchase. Approach: We shaped the site around brand presentation, fast browsing, clean product detail pages, and a checkout path that stays connected to ProSystem BMS inventory underneath. Outcome: TAHAR now has a polished eCommerce channel for brand-led shopping, with clean product discovery, focused checkout, and inventory that stays aligned between the website and retail floor through ProSystem BMS. Performance: Fast Design: Brand-led Channels: In sync TAHAR needed an eCommerce surface that could do two jobs at once: express the brand with polish and move customers confidently toward purchase. The site balances editorial presentation with the practical structure serious online retail needs. A brand-led shopping experience The visual system uses restrained typography, clean spacing, considered motion and product-led photography so the catalogue feels curated rather than generic. The brand registers before the customer reaches the cart, while the shopping path stays direct. Built for serious eCommerce Underneath the design, the build is tuned for conversion: fast page loads, frictionless checkout, and product detail pages that make selection clear. ProSystem BMS holds the inventory, so the stock a customer sees online is the stock available on the retail floor. Where it sits today The website gives TAHAR a polished digital storefront that can support campaigns, product discovery and checkout without separating online sales from store operations. Stock, catalogue and sales channels stay connected as part of the same day-to-day system. ### [ESSENCER An eCommerce site for ESSENCER's perfume range](https://www.prosystem.com.bd/case-studies/essencer) - Type: case-study - ID: case-study:essencer - Tags: case-study, Fashion, ESSENCER, BMS, eCommerce, Fashion An extensive perfume catalogue for ESSENCER across multiple brands every fragrance tagged with its scent notes, browseable by brand, by note or by mood for day or night. Industry: Fashion Problem: ESSENCER stocks perfumes across a wide range of brands, and shoppers reach the site by very different paths by brand, by scent note, by mood. Approach: We modelled the catalogue around how perfume is actually shopped for, with each fragrance tagged for its scent notes and filterable by brand and mood. Outcome: Shoppers find their perfume by brand, by note or by mood, and the team manages the listing from one place. Catalogue: Extensive Inventory: Multi-brand Navigation: Effortless Perfume is hard to sell online the shopper can't smell what they're considering, so the site has to do the work an in-store fragrance counter would normally do. Communicate enough about a fragrance for a customer to decide on it. What a perfume page tells the shopper Each product page carries the bottle photography, the brand context, the full list of top, heart and base notes, and the descriptors that help a customer place the fragrance in their head. The page reads the way a fragrance specialist would talk about it: house first, then character, then notes, then the bottle. A page for the shopper who knows the house Many ESSENCER customers shop by brand they've decided which house they want and they're after the full range. Each brand has its own destination on the site, holding every line ESSENCER stocks, with the photography and context the customer expects when arriving at a house's page. Inventory and the catalogue, on one platform ProSystem BMS holds both the catalogue and the stock, with the relationship between them. A new fragrance entered into BMS reaches the site the moment the team is ready to publish, and stock movements are reflected in the same second they happen. Where it sits today The site reads like a perfumery rather than a generic eCommerce every fragrance arriving with the context a customer needs to decide on it. ### [SNAPSHOT Wedding photography portfolio for SnapShot](https://www.prosystem.com.bd/case-studies/snapshot) - Type: case-study - ID: case-study:snapshot - Tags: case-study, Media, SNAPSHOT, Website, CMS, Media A portfolio site for SNAPSHOT where galleries are a first-class content type the team can drop in images, write the brief and publish a new project. Industry: Media Problem: The freshest work sells the next booking, and SNAPSHOT needed a portfolio they could keep current themselves. Approach: We designed a presentation-first portfolio with a CMS that fits the studio's workflow. Galleries are a structured content type drop in images, write a brief, publish. Outcome: The team publishes new weddings as they're ready, and bookings convert against the latest work. Galleries: Curated Design: Editorial Performance: Fast A wedding lives or dies on how it's told. A long timeline of similar photographs is a contact sheet; a paced sequence with the right cropping is a story. SnapShot's site is built around that distinction. Each project, told as an album Every wedding on the site is its own album a paced sequence of images and prose, ordered the way the team wants the day to read. The album, not the gallery, is the unit of work, and the CMS is shaped around that idea. Storytelling tools in the CMS Inside the CMS, the team shapes how each album reads. Layout varies per spread, pull quotes drop in where they need to, the masonry grid lays photographs out at their natural proportions, text blocks pause the rhythm where the story calls for it. The toolbox fits how a wedding is actually narrated, so the studio is shaping the work directly rather than bending a generic page builder around it. Editorial decisions stay with the studio Pacing, sequencing, the frames that make the final cut those decisions sit with the team. The CMS gives them the tools to shape the album; the site renders the result; and the studio's voice carries through because they're the ones holding the pen. Reservations collected in the CMS The booking form on the site routes new enquiries into the CMS for the team to read, sort and respond to. Each one sends an email notification so the team picks it up before they next sign in. ### [FLYBOT STUDIOS A content-rich portfolio for FLYBOT Studios](https://www.prosystem.com.bd/case-studies/flybot-studios) - Type: case-study - ID: case-study:flybot-studios - Tags: case-study, Media, FLYBOT STUDIOS, Website, CMS, Portfolio, Media A content-rich portfolio website that puts FLYBOT Studios' work centre-stage every project, film and shoot fully editable from the CMS, presented the way the team wants it seen. Industry: Media Problem: FLYBOT Studios needed a portfolio that showcased the breadth of their work without locking them into a fixed template and that the team could shape themselves as the work evolved. Approach: A content-rich portfolio site with rich media, structured project pages and a CMS that gives the team full control over how each piece is presented order, hierarchy, hero treatment, captions, the lot. Outcome: The portfolio reflects the studio's current work, told the way the team wants to tell it. New projects go live as soon as they're ready. Presentation: Team-led Hierarchy: Editable Layout: Customisable An agency's portfolio is its strongest pitch. The site has to carry the breadth of the work and stay current with whatever has just shipped and the team has to be able to shape it themselves, without going through a developer every time the pitch changes. A content-rich portfolio Each project is a full content entry, not a tile. Hero film or photography, supporting media, role, credits, copy, links all on a structured page that does justice to the work without flattening it. The portfolio reads as a body of work, not a grid of thumbnails. Presented the way the team wants The CMS doesn't just hold the content it controls the presentation. The team chooses the order projects appear in, which ones lead, how each is treated on the page, what's surfaced on the homepage, and how the captions read. Re-pitching the portfolio is a few minutes in the editor, not a redesign. Where it sits today The portfolio reflects the studio's current work fresh enough to pitch, structured enough to stay coherent, and entirely in the team's hands. ### [TURF NATION Booking and operations for a premier sports facility](https://www.prosystem.com.bd/case-studies/turf-nation) - Type: case-study - ID: case-study:turf-nation - Tags: case-study, Sports, TURF NATION, Custom Application, Website, Booking, Sports TURF NATION's bookings, payments and operations on a custom application that powers both the website and the back office. Live time slots, dynamic time-slot pricing, partial or full advance payments and automated game-day pass. Industry: Sports Problem: TURF NATION needed a reliable booking system live availability, dynamic pricing, payment options at the customer's choice, and a back office that the operations team could actually run the day on. Approach: A custom application powers both surfaces from the same live time-slot calendar. Pricing is configured by slot from the back office, customers pay full or partial advance, and confirmation emails carry a game-day boarding-style pass. Outcome: The team runs the entire facility bookings, payments, reporting from one system, and customers walk in with a game-day pass that has everything they need on it. Availability: Live Payments: Flexible Operations: Unified A sports facility runs on its booking calendar. If the website and the back office show different things, double-bookings happen and the customer notices first. We built TURF NATION a custom application where both surfaces work off the same time slots in real time. Live time slots, designed against double-booking Available time slots are computed live, not synced. The same calendar powers the customer-facing booking surface and the operations dashboard, so the moment a slot is taken on the website, on the phone, at the counter it disappears from every other view. Double-booking isn't prevented by a process rule; it's prevented by the data model. Dynamic pricing and promo codes Pricing isn't a flat hourly rate. The team configures rates per time slot from the back office peak hours, off-peak, weekday morning, Friday night and the website reflects whatever the team has set. Promo codes are created in the back office and redeemed by customers at checkout, useful for partnerships, opening offers and member-only deals. Rates, codes and seasonal promotions all change without a developer. Full or partial advance payment Customers can pay in full at the time of booking or pay a partial advance to confirm the slot, with the balance settled at the venue. Either way, the slot is held; either way, the payment is reconciled in the back office's billing module. A boarding-pass email customers actually use Booking confirmation isn't a generic receipt. It's an automated email with a game-day boarding-style pass venue, time slot, pitch, players, payment status, all on one card the customer can show on arrival. The team scans the pass at the gate; the customer doesn't have to remember anything. A back office built for running a facility The dashboard is where the operations team lives. A live overview shows today's bookings, available slots and payment statuses, against a sales-trend graph that goes back as far as the team wants. Bookings can be entered by hand from the back office for walk-ins or phone enquiries. Slots can be manually blocked and unblocked for maintenance or events. Every customer has a unique profile with their booking history, so a regular is recognised at the gate and at the dashboard. The billing and payments module tracks every transaction and generates the reports the team needs at the end of the day, the week, the month. Where it sits today TURF NATION's website and back office tell the same story, in real time. Bookings flow without friction; the team handles a busy weekend on the same dashboard they use on a quiet weekday; customers arrive with their pass already on their phone. ### [RELIANT MOTORS RELIANT Motors' Website and custom BMS](https://www.prosystem.com.bd/case-studies/reliant-motors) - Type: case-study - ID: case-study:reliant-motors - Tags: case-study, Transport, RELIANT MOTORS, Website, BMS, Custom modules, Transport We designed and developed a website where visitors browse the lot, download stock reports and pull a branded PDF brochure from any vehicle page and extended their BMS with custom modules for quotations and cash invoices that retire the typed document workflow. Industry: Transport Problem: Sales paperwork was hand-typed inconsistent branding, copy-paste errors, hours lost to formatting. And without a website, serious buyers had nowhere to browse the lot or take something away to consider. Approach: A quotation-led website with browse, stock-report download and per-vehicle branded PDF brochures generated on the fly from BMS. New BMS modules for quotations and cash invoices replace the typed documents. Outcome: Buyers can browse the lot, take away branded vehicle brochures, and access stock reports directly from the website. Behind the scenes, custom BMS modules turn quotations and cash invoices into a faster, cleaner sales workflow. Quotations: One-click Brochures: Take-away Stock report: On-tap An auto retailer runs as much on paperwork as it does on showroom floor traffic. Quotations, brochures, cash invoices, stock reports every conversation produces a document, and every document has to look like it came from the same brand. Before we got involved, every one of these was being typed by hand, which turned the sales team into typesetters: re-applying the logo, re-formatting the table, hunting for last quarter's spec sheet to copy fields out of, and inevitably letting a typo or an outdated price slip onto customer-facing paper. A quotation-led website that gives buyers something to take away The website is built around how RELIANT actually sells. Visitors land on a lot view that reflects available vehicles in real time, pulled from BMS as the lot moves. From any vehicle page, two actions matter: First, a brochure download. Each vehicle page generates a branded PDF on the fly RELIANT Motors masthead, hero photography, curated specs, a clean layout that reads like the brand behind it. Every piece of that content (specs, copy, images, the order they appear in) is edited by the team from BMS without touching code; if a vehicle's photography is updated this morning, the brochure that downloads this afternoon carries the new images. Buyers leave the site with something they can sit with, share with a partner, or take to their accountant. Second, a stock report. Serious buyers and trade partners often want the whole lot at a glance rather than a piece-by-piece browse. A single click pulls the current stock list as a PDF, generated against live BMS data so what's on the report is what's on the lot. Custom BMS modules for quotations and cash invoices On the BMS side, we built two new modules Quotations and Cash Invoices designed around the team's actual sales process. Each starts as a structured form: vehicle, customer, price components, terms, validity. The branding is set once at the template level, so every quote and invoice that leaves the showroom looks like it came from the same place. The generated PDF is ready to send the moment the form is saved; numbering is automatic and sequential; a copy of every document is retained in BMS for future reference. What used to be a 20-minute typing exercise per quotation open last week's, change the names, change the numbers, hope nothing was missed is now a few fields and a save. The team stopped retyping the same boilerplate. The customer started receiving paperwork that's consistent across every interaction. One tag system, doing double duty Vehicle specs in BMS are organised through a tagging system fuel type, transmission, drivetrain, body style, engine displacement, year, condition, the long tail of features a serious buyer asks about. Tag a vehicle once and that data flows everywhere it's needed: spec lines populate automatically inside a Quotation without the salesperson re-typing them, and the same tags drive the categorisation and filtration on the website's lot page so visitors can narrow the catalogue by exactly the dimensions buyers actually shop on. The win is that a single tagging exercise feeds the whole system. Add a new vehicle in BMS, mark it up once, and it shows up on the website with the right filters, generates a brochure with the right specs, and produces a quotation with the same details without anyone re-entering the data anywhere. Internal records and the public website stop drifting because they're built from the same source. Where it sits today RELIANT's customer-facing paperwork now reads the way the brand does coherent, consistent, branded because the team isn't formatting it by hand any more. The website is the lot, the brochure is in the buyer's downloads before they leave the page, and the quotation lands in their inbox by the time the sales call ends. The typed document workflow that swallowed a chunk of every sales day is gone. What's next We're currently building an auction-sheet verification feature so prospective buye... ### [WAASEY eCommerce development for Waasey, premium menswear](https://www.prosystem.com.bd/case-studies/waasey) - Type: case-study - ID: case-study:waasey - Tags: case-study, Fashion, WAASEY, Website, eCommerce, Design, Fashion We designed and developed an eCommerce site from the ground up landing with a scaled brand mark that holds the page until the visitor scrolls, presenting collections piece by piece, and handling multi-currency checkout. Industry: Fashion Problem: The brand needed an eCommerce surface to match: a place to browse the collections, a path to buy, and support for the international buyers reaching out from outside the country. Approach: We designed and developed the brand's first eCommerce site: collection-wise showcases, regular and custom size options for products, and multi-currency checkout. Outcome: Customers find the right fit through the size finder, choose regular or custom sizing, and complete checkout in their own currency. Navigation: Effortless Collections: Curated Currency: Multi Premium menswear has to make its case quickly. WAASEY needed an eCommerce site that opened well and gave the craftsmanship space to do the rest. An entrance that holds the visitor still The first thing a visitor sees is the WAASEY logo at full scale, filling the screen. It blends into the landing as the page settles, holding at that scale and inviting the visitor to scroll for more to discover. Collection-wise showcase Pieces aren't dropped into a flat product grid. Each collection has its own moment on the page an introduction, a hero piece, then the supporting items so the visitor reads the collection's story before they reach the buy buttons. Browsing feels closer to walking through a curated room than scrolling a catalogue. A size finder built around the buyer Sizing is the most common reason a serious menswear customer hesitates online. We built in a size finder that walks the buyer through a few measurements and recommends the closest standard fit fast enough that it doesn't feel like a form, considered enough that the recommendation is trustworthy. Regular sizing alongside custom Every piece is offered in regular sizes and as a custom commission. The custom path captures the buyer's preferences and request details directly through the site, so a request that used to require a phone call now lands in the team's queue ready for them to begin. Multi-currency checkout for international buyers Checkout supports multiple currencies, with prices shown in the buyer's own currency through the journey rather than at the last step. International buyers complete the purchase the same way local buyers do without the moment of friction that comes from seeing an unfamiliar currency at confirmation. Where it sits today WAASEY's site reads the way the work feels: careful, deliberate, made by hand. Visitors stay; orders arrive with the brand already understood; international customers buy alongside domestic ones; and the team's queue is full of well-formed custom requests instead of half-formed phone calls. ### [CARAT WORLD Jewellery told as carefully as it's made](https://www.prosystem.com.bd/case-studies/carat-world) - Type: case-study - ID: case-study:carat-world - Tags: case-study, Fashion, CARAT WORLD, Website, Luxury, Branding, Fashion We designed and developed a soothing, brand-forward site that begins with an animated cursive-logo introduction with sparkles, then settles into the landing page for more to discover. Industry: Fashion Problem: Fine jewellery sells on a feeling that takes time to settle in. CARAT WORLD needed a web presence that carried the brand's identity from the moment a visitor landed, and presented each piece with the dignity it earns at the bench. Approach: A soothing, brand-forward design with a cursive-typography logo animation as the opening traced in with soft sparkles for a slow, lasting first impression. Underneath it, a clean grid lets the photography do the work, piece by piece. Outcome: The website defines the ateliers presence from the first screen. Through considered structure, imagery, and product flow, it turns the collection into a clear path toward enquiry. Navigation: Effortless Design: Soothing Layout: Clean grid Jewellery isn't sold on the cart button. It's sold on the time a client spends imagining the piece on themselves, on someone they love, at an occasion that hasn't happened yet. The website's job is to set the mood for that imagining, then give the pieces the room to do their work. An introduction in cursive The first thing a visitor sees is the CARAT WORLD logo arriving in cursive each letter traced in slowly, soft sparkles trailing behind the pen, until the wordmark settles fully on screen. It's a small piece of motion held for a long beat, deliberately. By the time it ends, the brand has registered: this is an atelier, the work is considered, and the rest of the site is going to read at that pace. A soothing visual language Underneath the entrance, the design is quiet on purpose a calm palette, generous white space, a serif that carries the right amount of weight without leaning ornamental. Nothing competes with the pieces. The page lets the visitor breathe between sections, which is where most fine-jewellery decisions actually happen. A clean grid that frames each piece Pieces are presented in a clean, well-spaced grid every photograph framed with consistent margins, scaled to its own merit, captioned in a hand that feels written rather than catalogued. A click opens the full piece into a deeper view; the grid stays as the calm spine the visitor returns to. Where it sits today Clients arrive into the brand before they arrive at a piece. They linger before they ask. Enquiries land with context the client already knows the atelier's voice, and often, the piece they want to see in person. ### [KORAL KLAUSET A catalogue worth browsing for KORAL KLAUSET](https://www.prosystem.com.bd/case-studies/koral-klauset) - Type: case-study - ID: case-study:koral-klauset - Tags: case-study, Fashion, KORAL KLAUSET, Website, eCommerce, Design, Editorial, Fashion A content-rich, editorially-paced catalogue that represents the brand. We designed and developed the site around the photography, the styling, the words and the way each collection earns the visitor's attention. Industry: Fashion Problem: Boutique fashion is a brand-first category. The brand has to register before the cart button does, which means giving the visitor a reason to scroll instead of pushing them toward checkout on the first frame. Approach: We led the design end-to-end layout pacing, typography, voice and how the team's photography is composed and developed what we'd visualised, on a content model the team can refresh themselves. Outcome: A polished experience that strengthens the boutiques online brand presence and gives the team a flexible platform for publishing future collections. Layout: Editorial Voice: Brand-led Catalogue: Curated Boutique fashion is a brand-first category. The customer arrives looking for a piece that fits the silhouette, the styling, the tone of the brand. The site has to make space for that feeling alongside the catalogue itself, and design with something to say at every step. Designing for the brand, not the funnel Each frame earns its place. Each collection is introduced before it's listed; each piece gets the room to be seen. The visitor scrolls because there's something worth seeing in the next frame, and the pacing rewards that attention letting the brand register before the cart does. Content the team can keep alive Feature stories, lookbooks, styled collections and seasonal edits all sit on a content model designed for a small team's pace. Adding a new arrival or publishing a new edit is the kind of thing the team does themselves, in minutes not the kind of thing that waits on us. Where it sits today The site reads as carefully as the boutique itself. Customers come back to browse before they buy and when they do buy, they arrive at the cart already convinced. The brand is felt before the cart is opened. ### [YAZMEEN LUXE Enabling YAZMEEN LUXE's POS](https://www.prosystem.com.bd/case-studies/yazmeen-luxe) - Type: case-study - ID: case-study:yazmeen-luxe - Tags: case-study, Fashion, YAZMEEN LUXE, BMS, POS, Retail, Fashion We powered YAZMEEN LUXE's retail operations with ProSystem BMS in-house barcode generation, a cloud POS that runs on any device, and a clothing inventory developed with room to extend into an online channel. Industry: Fashion Problem: YAZMEEN LUXE needed retail operations that match a premium boutique's pace quick checkouts, reliable barcode scanning, accurate inventory without locking the team to a dedicated POS terminal. Approach: ProSystem BMS as the operations backbone in-house barcode generation, a low-friction cloud POS that runs on any device, and an inventory structured for an eCommerce channel later. Outcome: Checkouts are fast and reliable. The POS works wherever the team is working. Inventory is accurate, with eCommerce ready when the boutique adds it. POS: Cloud Barcodes: In-house Inventory: Structured A premium boutique earns its loyalty in the few minutes between picking the piece and walking out with it. Slow checkouts, mis-scanned barcodes, an out-of-stock surprise at the counter each one chips at the experience the rest of the boutique is trying to build. We powered YAZMEEN LUXE's retail floor on ProSystem BMS so those minutes feel as considered as the rest of the visit. Barcodes generated in-house Every item gets a barcode produced from BMS print on demand, owned in-house. New arrivals are tagged the moment they're added to inventory, so the floor is always working with labels that already exist in the system. A cloud POS that runs anywhere The POS is a clean, low-friction interface designed for speed. Checkout is a few steps, with reliable barcode scanning at the centre scan, confirm, payment, receipt. Because it's cloud, the team can choose their device: a MacBook on the counter, a desktop in the back office, a browser on a tablet all are valid POS terminals, on whatever hardware the team already owns. Inventory ready to extend Clothing inventory is modelled cleanly from the start, so the team always knows what's available without hunting through the SKU label. The data structure is built with room to extend when the boutique is ready to add an online channel, the eCommerce surface plugs into the same inventory without a redesign. ### [KRYSTAL LIFE Selling guilt-free, the way KRYSTAL LIFE means it](https://www.prosystem.com.bd/case-studies/krystallife) - Type: case-study - ID: case-study:krystallife - Tags: case-study, F&B, KRYSTAL LIFE, Website, eCommerce, Design, Wellness KRYSTAL LIFE makes healthy, guilt-free drinks and consumables for health-conscious customers. We designed and developed an eCommerce site with an organic visual language and product pages that put the benefits first. Industry: F&B Problem: KRYSTAL LIFE's products are genuinely different from what sits next to them on the shelf cleaner ingredients, no guilt, more thought in every formulation. The website needed to make that difference clear before a customer reached for the cart. Approach: A fun, organic visual language playful where it should be, soft type, considered photography, palette drawn from the products themselves. Product pages lead with the benefit, then the specs, then the buy button. Outcome: The new website helps customers understand what makes each product better cleaner ingredients, clearer benefits, and a more considered way to shop. Design: Organic Product pages: Benefit-first Motion: Fluid Healthy, guilt-free products are bought with the head as much as the gut. The customer wants to know what's actually in the product, why it's better, and whether the brand has thought about it as carefully as they have. The website has to answer all three before it asks for the sale. A fun, organic visual language We led the design across type, palette, photography and voice. The result is fun and organic, with a playful streak warm without being sentimental, clear without being clinical, and a long way from the usual wellness-aisle look. Making the most of the product photography The team supplied the products as cut-out PNGs, which gave us room to compose freely on the page. We arranged them in product listings that feel curated rather than gridded each piece set against generous white space, tilted just enough to look in motion, scaled to give each variant its own moment in the catalogue. On select sections, hovering over a product brings the raw ingredients out from behind it herbs, fruit, seeds, whatever's in that specific formulation fanning into view in a small, deliberate animation. The interaction connects what the customer sees on the shelf to what they're really buying, without a single line of marketing copy. Product pages that lead with the benefit Each product page leads with what the product actually does for the customer why it's guilt-free, how it's formulated, what makes it different from the thing on the shelf next to it. The specs and ingredients come next; the buy action sits where the conviction is built. Where it sits today Customers arrive at the cart already convinced. The team has a digital surface that reflects the care that goes into the products themselves a place they're proud to send first-time visitors and repeat buyers alike. ### [BMICC, Canada Between the prayers, a community centre online](https://www.prosystem.com.bd/case-studies/bmicc-canada) - Type: case-study - ID: case-study:bmicc-canada - Tags: case-study, Social Welfare, BMICC, Canada, Website, CMS, Community, Non-profit BMICC serves the Muslim community of Calgary a place to pray, meet, learn and raise funds for noble causes. We designed and developed a new website that brings the centre's day-to-day into one surface: live prayer times, services, events, classes and donations. Industry: Social Welfare Problem: BMICC's old WordPress site had an outdated design and a back office that made even small edits a chore and the centre's daily life was being tracked across phone calls and WhatsApp groups instead. Approach: We retired the old WordPress and designed and developed a new site from the ground up. Live prayer times sit on the homepage, services and events run from a CMS the team owns, and giving is integrated for supporters at home and abroad. Outcome: Members come to the site for prayer times and stay for everything else. Events fill faster, donors contribute easily and the centre runs its public communications from one place. Prayer times: Live Communications: Unified Donations: Integrated A community centre is many things at once: a place of worship, a school, a meeting room, a fundraising base. The website's job is to hold all of that together without making any one part feel like an afterthought. Replacing the old WordPress BMICC's existing site was a years-old WordPress build that had aged on every front design, content management, performance. Even small edits required walking around quirks the team had inherited rather than chosen. We retired it cleanly and designed and developed a replacement from the ground up. Live prayer times The homepage carries live prayer times calculated for Calgary, updating through the day. It's the single most-checked piece of information on the site, and it's the reason members open it more than once a day. Once they're there, the rest of the centre's life is one click away. Services and events the team can run themselves Prayers, classes, family services, social events and special programmes sit on a CMS designed for the team's rhythm. Forms are short, structure is predictable, publishing is instant so a new event goes live the day it's decided, not the next sprint. Donations that fit the supporter Giving is integrated into the same surface, with Stripe and PayPal running side by side so donors at home in Calgary and supporters overseas use the same form. Goal-based campaigns sit alongside the standard donation form each campaign has a target, a running total visible to the next donor, and the same payment path so a campaign gift takes the same few clicks as any other. Where it sits today BMICC's members have one place to be in touch with the centre. The team's hours go to programmes and pastoral work, not to copy-paste between platforms. ### [NRG LIFE INC. eCommerce & BMS development for perishable goods](https://www.prosystem.com.bd/case-studies/nrg-life-inc) - Type: case-study - ID: case-study:nrg-life-inc - Tags: case-study, Agri-tech, NRG LIFE INC., Website, Design, Agri-tech NRG LIFE works at the edge of agri-tech and fresh food bringing better-grown, better-handled produce to consumers. We designed and developed a website that puts the work, the philosophy and the product range in front of the customer with the clarity the brand deserves. Industry: Agri-tech Problem: NRG LIFE had a serious offering and a serious story behind it, but no online presence that conveyed either. New visitors had no way to understand what the brand actually solves. Approach: We designed and developed the site ourselves type, palette, photography and voice and presented something the team was proud to call theirs. The structure leads with the work, then the product range, then the routes for customers to act. Outcome: The site turns NRG LIFEs technical, product-led story into a simple customer journey: what they do, why it matters, what they offer, and how to get in touch. Design: Brand-led Navigation: Effortless Performance: Fast Agri-tech that takes itself seriously is a hard thing to communicate on the web. The work is technical at its core and human in its outcome and the website has to carry both without flattening either. We designed it We took the design lead end-to-end typography, palette, photography style, the voice the site uses when it explains what NRG LIFE does. What we presented was a fully-formed visual language rather than a set of options to discuss. The team responded to it with ownership proud to call it theirs the moment they saw it. Structuring the story The site leads with the problem NRG LIFE works on better-grown, better-handled fresh food then explains the approach, surfaces the product range, and gives customers clear routes to act. Each section earns the next; nothing is filler. Where it sits today The website carries the brand the way the team intended. Visitors arrive with curiosity and leave understanding the work and the team has a digital surface they're proud to point partners and customers to. ### [BUET 88 CLUB BUET graduate club website & members' directory](https://www.prosystem.com.bd/case-studies/buet-88-club) - Type: case-study - ID: case-study:buet-88-club - Tags: case-study, Social Welfare, BUET 88 CLUB, Website, CMS, Community A cohort that graduated from BUET in 1988 has stayed close ever since. We designed and developed a members' site that gives the alumni a place to find each other and stay connected as a class across cities and decades. Industry: Social Welfare Problem: The members directory ran on a Google Form and a spreadsheet the committee combed through by hand. Communications, events and shared memories were scattered across whatever channel the moment demanded. Approach: A members directory keyed to a clear committee hierarchy and a shared gallery for reunions and milestones all as first-class content types on a CMS the committee can run themselves. Outcome: Members find each other through the directory and see each other through the gallery. The committee owns the content end-to-end. Directory: Live Gallery: Curated Hierarchy: Structured Alumni clubs are a long-running coordination problem. The site has to be easier to update than the email thread that would otherwise replace it and rich enough that members open it for reasons beyond the next reunion. Two ends: public and member The website is built in two layers. A public-facing surface introduces the club and its work to anyone who lands on it; the deeper detail full directory, gallery, internal communications sits behind a sign-in for verified members only. The two ends share the same design language, so a member crossing into the private section feels continuity rather than a context switch. A comprehensive sign-up with admin approval Joining the members' side is a deliberate process, not an open form. Prospective members fill in a comprehensive sign-up identity, batch details, contact channels which lands in an admin queue rather than going live. An administrator reviews each request against the cohort roster; only once the request is approved does the system send a one-time invitation link to the verified email, which the member uses to sign in. The friction is the point: it keeps the membership area genuinely member-only. Members directory Every member has an entry name, batch role, contact channel of their choice, current city and the directory itself is searchable and filterable. Finding a classmate becomes a few keystrokes rather than a chain of WhatsApp messages. A clear member hierarchy The committee structure (executive committee, sub-committees, advisory roles) is modelled into the site so the chain of responsibility is visible. Members know who to reach for what; new committee members inherit a structure rather than a folder. A private gallery for members only Reunions, milestones, casual meet-ups the gallery collects them all on one surface, sitting behind the same secure auth layer that protects the directory. The committee uploads on the team's schedule; members browse on theirs, knowing the photographs aren't drifting onto the public web. Decades of cohort memory live in one place rather than scattered across personal phones. Where it sits today The site stays current because the workflow fits the committee. Members find each other, see each other, and stay in touch with the cohort across cities and decades all on a surface only they can see into. ### [FARE Enabling online donation through website development](https://www.prosystem.com.bd/case-studies/fare) - Type: case-study - ID: case-study:fare - Tags: case-study, Social Welfare, FARE, Website, CMS, Donations, Non-profit The Foundation for Autism Research and Education works on autism research, awareness and education across Bangladesh. We designed and developed a website that represents the foundation and its programmes clearly with fundraising built into the same surface in a way that fits how local donors pay. Industry: Social Welfare Problem: FARE needed a web presence that did three things at once: communicate the foundation's mission and the people behind it, surface ongoing programmes and events so the work is legible to anyone visiting, and turn that interest into fundraising through a path that fits how donors here actually pay. Approach: We designed and developed the site around the foundation's voice mission, team, programmes, events with fundraising built into the same surface and a live donation counter the next supporter can see. Outcome: FARE's mission, programmes and events are legible to anyone who lands on the site. Donors give through a flow that feels native, not foreign. The team sees confirmations in real time and updates programmes alongside the fundraising page without a developer. Payments: Integrated Donation counter: Live Programmes: Editorial The Foundation for Autism Research and Education does work that has to be understood before it can be supported research, awareness, education programmes, public events. The website's job is to make that work legible first, then make supporting it easy enough that intent doesn't pass before it converts. A design built to be read We worked on the site as a piece of editorial as much as a fundraising surface. Clean typography sets the pace generous line-heights, careful hierarchy, headings that earn their weight and the layouts make room for substance: programme write-ups, research notes, event recaps, profiles of the people doing the work. The reader can spend time on the foundation before they're asked to support it, which is the order in which support is actually earned. Built around how donors here pay We integrated SSLCommerz, a Bangladesh-based gateway that handles the full local payment landscape cards, mobile financial services and bank options on a single rail. For a cause that's gathering support inside the country, that breadth without a stack of integrations mattered. Momentum a supporter can see Donations on FARE's page are tallied in real time and surfaced as a live counter the next visitor can see. The point isn't a vanity figure it's social proof. A donor weighing a small contribution behaves differently when they can see other supporters are doing the same thing right now. What else we built Programs, events and donor updates sit on a CMS the team owns short forms, predictable structure, instant publish so the campaigns running alongside the donation page never go stale. Where it sits today Donors give through a flow that fits the way they pay. Confirmations land in real time. The team's hours go to programs and supporter relationships. ### [RANGS MOTORS LTD.](https://www.prosystem.com.bd/case-studies/rangs-motors) - Type: company - ID: company:rangs-motors - Tags: company, Transport Corporate Website for major commercial vehicle distributor Industry: Transport ### [ZEISS VISION CENTER](https://www.prosystem.com.bd/case-studies/zeiss-vision-center) - Type: company - ID: company:zeiss-vision-center - Tags: company, Healthcare BMS & eCommerce Website for OPSIS outlets Industry: Healthcare ### [AMISHEE FINE JEWELS](https://www.prosystem.com.bd/case-studies/amishee) - Type: company - ID: company:amishee - Tags: company, Fashion Website development for luxury jewelry atelier Industry: Fashion ### [RANGS PHARMACEUTICALS LTD.](https://www.prosystem.com.bd/case-studies/rangs-pharmaceuticals) - Type: company - ID: company:rangs-pharmaceuticals - Tags: company, Healthcare Corporate Website for Bangladeshi pharmaceuticals company Industry: Healthcare ### [OilCo Bangladesh](https://www.prosystem.com.bd/case-studies/oilco-bangladesh) - Type: company - ID: company:oilco-bangladesh - Tags: company, Transport eCommerce Website & BMS for auto parts retailer Industry: Transport ### [KAVAZO](https://www.prosystem.com.bd/case-studies/kavazo) - Type: company - ID: company:kavazo - Tags: company, F&B Custom BMS & eCommerce Website for KAVAZO outlets Industry: F&B ### [SHIELD SECURITY SERVICES LTD.](https://www.prosystem.com.bd/case-studies/shield-security) - Type: company - ID: company:shield-security - Tags: company, Security Corporate Website for security company Industry: Security ### [SKINN By Prof. M N Huda](https://www.prosystem.com.bd/case-studies/skinn) - Type: company - ID: company:skinn-centre - Tags: company, Healthcare ERP, BMS and Website development for dermatology clinic Industry: Healthcare ### [ARFIN](https://www.prosystem.com.bd/case-studies/arfin) - Type: company - ID: company:arfin - Tags: company, Fashion eCommerce Website & BMS for men's leather goods retailer Industry: Fashion ### [ZAAR](https://www.prosystem.com.bd/case-studies/zaar) - Type: company - ID: company:zaar - Tags: company, Fashion BMS & eCommerce Website for women's footwear retailer Industry: Fashion ### [PASTRYARCHY](https://www.prosystem.com.bd/case-studies/pastryarchy) - Type: company - ID: company:pastryarchy - Tags: company, F&B BMS & eCommerce Website for cloud bakery Industry: F&B ### [MAINUL](https://www.prosystem.com.bd/case-studies/mainul) - Type: company - ID: company:mainul - Tags: company, Fashion BMS and eCommerce Website for fashion tailor Industry: Fashion ### [TAHAR](https://www.prosystem.com.bd/case-studies/tahar) - Type: company - ID: company:tahar - Tags: company, Fashion BMS and eCommerce Website for fashion retailer Industry: Fashion ### [ESSENCER](https://www.prosystem.com.bd/case-studies/essencer) - Type: company - ID: company:essencer - Tags: company, Fashion BMS and eCommerce Website for perfume retailer Industry: Fashion ### [SNAPSHOT](https://www.prosystem.com.bd/case-studies/snapshot) - Type: company - ID: company:snapshot - Tags: company, Media Portfolio Website and CMS for wedding photography Industry: Media ### [FLYBOT STUDIOS](https://www.prosystem.com.bd/case-studies/flybot-studios) - Type: company - ID: company:flybot-studios - Tags: company, Media Portfolio Website and CMS for media agency Industry: Media ### [TURF NATION](https://www.prosystem.com.bd/case-studies/turf-nation) - Type: company - ID: company:turf-nation - Tags: company, Sports Custom BMS and Website for premier sports facility Industry: Sports ### [RELIANT MOTORS](https://www.prosystem.com.bd/case-studies/reliant-motors) - Type: company - ID: company:reliant-motors - Tags: company, Transport Website and BMS for auto retailer Industry: Transport ### [WAASEY](https://www.prosystem.com.bd/case-studies/waasey) - Type: company - ID: company:waasey - Tags: company, Fashion BMS and eCommerce Website for fashion tailor Industry: Fashion ### [CARAT WORLD](https://www.prosystem.com.bd/case-studies/carat-world) - Type: company - ID: company:carat-world - Tags: company, Fashion Website development for luxury jewelry atelier Industry: Fashion ### [KORAL KLAUSET](https://www.prosystem.com.bd/case-studies/koral-klauset) - Type: company - ID: company:koral-klauset - Tags: company, Fashion BMS and eCommerce Website for fashion boutique Industry: Fashion ### [YAZMEEN LUXE](https://www.prosystem.com.bd/case-studies/yazmeen-luxe) - Type: company - ID: company:yazmeen-luxe - Tags: company, Fashion BMS for premium boutique Industry: Fashion ### [KRYSTAL LIFE](https://www.prosystem.com.bd/case-studies/krystallife) - Type: company - ID: company:krystallife - Tags: company, F&B BMS and eCommerce Website for health & wellness brand Industry: F&B ### [BMICC, Canada](https://www.prosystem.com.bd/case-studies/bmicc-canada) - Type: company - ID: company:bmicc-canada - Tags: company, Social Welfare Website and CMS for non-profit organization Industry: Social Welfare ### [NRG LIFE INC.](https://www.prosystem.com.bd/case-studies/nrg-life-inc) - Type: company - ID: company:nrg-life-inc - Tags: company, Agri-tech BMS and eCommerce Website for perishable goods Industry: Agri-tech ### [BUET 88 CLUB](https://www.prosystem.com.bd/case-studies/buet-88-club) - Type: company - ID: company:buet-88-club - Tags: company, Social Welfare Website and CMS for graduate club members Industry: Social Welfare ### [FARE](https://www.prosystem.com.bd/case-studies/fare) - Type: company - ID: company:fare - Tags: company, Social Welfare Website and CMS for non-profit organization Industry: Social Welfare ### [Senior Product Engineer Engineering](https://www.prosystem.com.bd/careers/senior-product-engineer) - Type: job - ID: job:senior-product-engineer - Tags: careers, job, Engineering, Full-time Develop customer-facing features across ProSystem BMS. Typescript, React, Node. Strong taste, short feedback loops. Team: Engineering Dhaka On-site Full-time You'll own customer-facing features end to end from product shaping with our clients, through implementation, to the post-release read of how real users are using it. We write TypeScript in React and Node. We release every week. Our test discipline is pragmatic; our review discipline is serious. Requirements: - 5+ years developing product in a customer-facing codebase. - Fluent in TypeScript, React and a Node-based backend. - Product instinct you can argue for the feature that should launch and the one that shouldn't. - Care about craft: interactions, performance, clarity of code. Apply: hr@prosystem.com.bd ### [Design Engineer Design](https://www.prosystem.com.bd/careers/design-engineer) - Type: job - ID: job:design-engineer - Tags: careers, job, Design, Full-time Live at the seam between Figma and React. Motion, interaction, type. Opinions about typography welcome. Team: Design Dhaka On-site Full-time You'll sit between design and engineering, translating intent into interfaces that feel as good as they look. Expect to spend the day in React, CSS and Figma, and the evening arguing about kerning. Requirements: - 3+ years designing and developing interfaces. - Fluent in React and modern CSS; comfortable in a codebase. - A portfolio that shows taste type, motion, restraint. Apply: hr@prosystem.com.bd ### [Customer Success Lead Success](https://www.prosystem.com.bd/careers/customer-success-lead) - Type: job - ID: job:customer-success-lead - Tags: careers, job, Success, Full-time Own the launch, training and adoption of ProSystem BMS at our enterprise clients. Operations brain. Steady hand. Team: Success Dhaka On-site / Hybrid Full-time You'll be the human face of ProSystem inside our clients' organisations the person who gets the launch right and the renewal signed. You understand operations, you teach well, and you're not afraid of a spreadsheet or a tough conversation. Requirements: - 4+ years in B2B customer success or enterprise launch. - Comfortable owning onboarding plans, training sessions and escalation calls. - Operations literacy you can read a P&L and a stock ledger. Apply: hr@prosystem.com.bd