Skip to content

Work — 06 projects

Selected Work

Products, platforms, ERP systems and modernization work: the context, our role, the engineering decisions and the results.

  1. 01 — Mobile engineering

    Social Media App

    Urgent feature work inside an existing Flutter codebase.

    Modifications to a social media app already built in Flutter, with GetX for state management and Firebase behind it, for a client on Upwork between December 2024 and February 2025.

    Client
    Upwork client, social media app
    Challenge
    The client needed changes made urgently to an app that already existed, so the work had to fit its GetX and Firebase architecture rather than start over.
    Role
    Flutter engineering on the existing app
    Results
    Completed in February 2025 and rated 5.0 by the client.
    Stack
    Flutter · GetX · Firebase
    Read the case study: Social Media App

    Client review5.0 out of 5Jan 2025

    “Abhishek is an outstanding mobile developer and an absolute asset to any project. His technical expertise, attention to detail, and ability to deliver clean, efficient code truly set him apart. He communicates clearly, understands project requirements quickly, and consistently meets deadlines. Beyond his technical skills, Abhishek brings a proactive attitude and is always ready to offer valuable suggestions to improve the overall product. I highly recommend Abhishek for any mobile development project—he’s reliable, talented, and a pleasure to work with!”

    Upwork contract review
  2. 02 — Business systems

    ERP Purchase Control

    Purchases verified by weight at the gate, not by paperwork.

    An ERPNext implementation of the purchase cycle built around the weighbridge at the gate. Every inbound vehicle is recorded on entry, weighed loaded and empty, and reconciled against its purchase order before stock is received or the vehicle is allowed out.

    Client
    Client of an ERPNext consultancy
    Challenge
    Material was going missing at the gate. Deliveries were accepted on the strength of paperwork, so nothing tied what physically arrived to what had been ordered and paid for.
    Role
    Technical lead, within an ERPNext consultancy: purchase cycle from gate entry and weighment to receipt and gate exit
    Engineering
    The purchase flow was rebuilt in ERPNext around the weighbridge. A gate entry links each vehicle to its purchase order; the first and second weighments give the net weight; the purchase receipt is made from that net weight, and mismatches are held for review before stock is accepted. A vehicle leaves only against a gate exit record, so every load is accounted for in and out.
    Results
    Theft through the gate was prevented: stock now enters the books at the weight that actually arrived, matched to its purchase order.
    Stack
    ERPNext · Frappe · Buying & Stock · Weighbridge
    Read the case study: ERP Purchase Control
  3. 03 — Product engineering

    Offline & Online POS

    Billing that never stops: online, on a weak signal, or with no internet at all.

    A Flutter point-of-sale app for fast counter billing: items, cart, taxes and payment in a few taps. It works the same with or without internet, so a slow or dropped connection never holds up a sale.

    Challenge
    The client needed to run the POS even without internet. Their counters couldn't stop selling whenever the network was slow or down, but a POS that waits on the server for every bill turns low bandwidth into a queue at the counter, and no connection into lost sales.
    Role
    Built the app end to end: Flutter development and the offline sync
    Engineering
    The app was built to work offline first. Every bill is completed and saved on the device without waiting for the network. When a connection is available, sales sync to the server in the background, so the cashier works the same way whether the connection is strong, weak or gone.
    Results
    The counter keeps billing on a weak connection or with no internet at all, so a network outage no longer means a queue or a lost sale. Sales made offline sync to the server once the connection returns.
    Stack
    Flutter · Dart · Offline-first sync
    Read the case study: Offline & Online POS
  4. 04 — Business systems

    Manufacturing ERP

    CRM, purchasing, production, stock and HR in one connected system.

    An ERPNext implementation that runs a manufacturing business end to end. A deal won in CRM becomes a sales order; the sales order drives the production plan and its work orders; material shortfalls are raised to purchasing; stock, quality, HR and payroll sit in the same system, so every department works from one set of numbers.

    Client
    Manufacturing client of an ERPNext consultancy
    Role
    Technical lead, within an ERPNext consultancy: implementation across CRM, Buying, Manufacturing, Stock and HRMS
    Stack
    ERPNext · CRM · Manufacturing · Buying · HRMS
    Project overview: Manufacturing ERP

    Case study in preparation

Have a complex problem worth solving?

Tell us what you're trying to build, fix or change, and what's at stake. We'll read it properly and reply with questions or a time to talk.