How we built 2USE
2USE came to us with a business that no off-the-shelf platform could run. We designed and built the whole thing — three portals, one engine — and we're still building it two years on..
The brief we were handed
Build the system nobody sells off the shelf.
2USE wanted to buy, grade, refurbish and resell used devices at scale — and to do it with proof, not promises. Our first job was to work out what that actually required, because no existing platform does it.
What 2USE wanted
One system every device passes through
Prices from rules, applied identically everywhere
Grades, battery health and scratch percentages
IMEI verified, warrantied, fully traceable
Every item in that right-hand column was an engineering problem we had to solve: a rules engine instead of a price list, IMEI checks wired into intake, condition captured as data rather than adjectives. We took it from first analysis through Figma, into code, and into production — then stayed on to keep building.
The architecture we chose
One engine, three connected portals
The decision that shaped everything: rather than bolting features onto a shop, we built three interfaces on a single shared engine — so a rule written once behaves identically everywhere.
Customer-facing marketplace
We built the catalogue, checkout, buyback and trade-in flows bilingual English and Arabic with full RTL, and structured for organic search from day one.
The
supply engine
We designed an in-store assessment tool for partner companies, driven entirely by 2USE's central rules — and made it white-label so partners can run it under their own brand.
Where the
business is run
We put every commercial lever in the admin — catalogue, campaigns, content, and the buyback question sets and pricing that drive the other two portals.
The flow we designed
Five steps, one closed circle
Analysis
Understanding the buying, grading and refurbishment operation before designing anything.
Design in Figma
Three portals designed as one coherent system, not three separate products.
Build & launch
Next.js storefront, Laravel engine, React admin and retailer interfaces — into production.
Ongoing development
Two years and counting. New features ship as the business grows.
The customer doesn't walk out with cash.
They walk out with a voucher.
We treated the retailer portal as a supply engine, not a discount login. Because we kept every condition question and price under central control, onboarding a new partner became a configuration task rather than a negotiation which is what lets the network scale.
How we worked
Analysis to production, then onwards
2USE didn't hand us a spec to implement. We started at the beginning and stayed past launch.
Analysis
Understanding the buying, grading and refurbishment operation before designing anything.
Design in Figma
Three portals designed as one coherent system, not three separate products.
Build & launch
Next.js storefront, Laravel engine, React admin and retailer interfaces — into production.
Ongoing development
Two years and counting. New features ship as the business grows.
The partnership
We didn't deliver and disappear
2USE now runs its entire operation on the platform we built — customers, retail partners and admin, across two languages and multiple sales channels. More than two years in, we're still on it: shipping new features, extending the system, and adapting it as the business grows. That's how we work with every client.
" Working with Programi Tech has been an incredible experience. Their innovative solutions and commitment to success have truly helped our business grow. We've seen consistent achievements, and we look forward to many more."