A chat built for parcels
Lamjed Gaidi
Senior full-stack engineer · Tunis
I am Lamjed Gaidi, a senior full-stack engineer based in Tunis.
Who I am
Senior full-stack engineer in Tunis: five years of production web and mobile products, applied AI with human review.
Read my story →- I am Lamjed Gaidi, a senior full-stack engineer based in Tunis.
- Five years taking products from the business problem to production.
- React and Next.js, Node.js and NestJS, React Native, FastAPI, PostgreSQL, Docker and GitHub Actions.
- Logistics, PropTech, TravelTech, HRTech, EdTech, health and fitness.
- I am open to long-term roles, permanent or regular freelance.
Who should read every email?
Repetitive triage eats hours that people need for real decisions.
Repetitive email triage eats hours that people need for real decisions.
Argus, the project I am proudest of
A tool-calling LLM agent at IntiGo that triages emails on production data, with a human approving every action.
See how Argus works →- Repetitive email triage eats hours that people need for real decisions.
- Argus reads the email, checks the facts in production data through tools and MCP, drafts a decision, and a human approves it.
- The leads and reports dashboard Argus works with.
- Email triage V1 is in use at IntiGo. Further modules are planned.
- Less routine work, same accountability: the agent proposes, a person decides.
Five people, one parcel
Customer, driver, merchant, agency, system.
Every parcel involves up to five parties: customer, driver, merchant, agency and the system.
A chat built for parcels
The parcel chat backbone I am extracting into a SaaS: one thread per parcel, five roles, one event fanned out to every channel.
Read the architecture →- Every parcel involves up to five parties: customer, driver, merchant, agency and the system.
- One commit emits one event, and a dispatcher sends it to the WebSocket inbox, push notifications and signed webhooks, each with its own retries.
- In production at IntiGo: more than 256,000 conversations and 114,000 messages, snapshot of 21 October 2026.
- The admin analytics of the chat on 21 October 2026.
- The core is extracted; the tenant and identity layer is in progress.
Code is not done until users have it
Code is not done until it reaches users, safely and repeatably.
From code to production
Release pipelines to the App Store and Play Store, merchant plugins, and backups with alerts at IntiGo.
See the IntiGo work →- Code is not done until it reaches users, safely and repeatably.
- GitHub Actions builds, signs and uploads the React Native apps to the App Store and the Play Store.
- Four iOS apps went through App Review: three ready for distribution, one in review. Intigo Mobile is live on Google Play.
- Shopify app, WooCommerce plugin and a PrestaShop module for versions 1.7, 8 and 9 push orders into IntiGo.
- Automated database backups to six targets, with Slack and email alerts, running within my first two weeks.
- My first production change shipped in week one.
"I have products. I want parcels on the road."
What IntiGo sellers needed.
Sellers already sent their parcels with IntiGo. They needed the shop in front of their parcels.
From an idea to a product
How a seller need became the IntiGo e-commerce module: storefront builder, catalog, COD confirmation and Meta tracking, now in a staging pilot.
Open the case study →- Sellers already sent their parcels with IntiGo. They needed the shop in front of their parcels.
- I turn the need into user stories, a data model and API contracts, build the seller back office, then pilot it on staging.
- A theme-based storefront builder with publish revisions.
- A cash-on-delivery confirmation queue with risk scoring.
- Django, PostgreSQL, Celery, a theme engine, Meta Pixel and Conversions API, idempotent jobs, right-to-left support.
- The module runs as a staging pilot; it is not launched yet.
The rest is on the site
Detailed projects, career path and contact.