The Challenge
A social commerce platform sells through people, not catalogs. Shoppers follow sellers, watch them, ask questions and buy in the same session, so the product changes every week as the client tests what keeps an audience engaged. The client serves the Philippine market and works with teams in both the Philippines and Singapore. They needed engineering capacity that could absorb that pace without a hiring cycle for every new feature, and without the work splitting into two groups that never meet.
What Nexora Built
Nexora provides a dedicated team of 32 developers that works inside the client’s sprint rhythm. The team carries the platform’s day-to-day development, from new commerce features to bug fixing, and also took on a second product built on the same foundations.
- Sprint-based delivery of the social commerce platform, currently in sprints 27 to 30
- Search indexing so shoppers find products and sellers quickly
- AI features built into the platform
- Multi-region support for the two markets the client operates in
- A social podcast platform for a separate client in France, built as a sub-product
How a Team of 32 Stays Coordinated
A team this size fails on coordination before it fails on code. Work is cut into cards, and roughly 1,800 of them move through the board each month across 32 assignees. Both the Philippine and the Singapore groups hold their own daily stand-up, so every developer has a short, regular point of contact in their own time zone. Worklogs sync to a time-tracking tool, which gives the client a record of where effort went by sprint. A Nexora technical lead owns the plan for each sprint and the handoff between the two groups.
Search Indexing
Search is where a social commerce platform feels fast or broken. Product and seller data lives in the main database and a hosted search index mirrors it, so every change has to reach both places. Index data issues and redirect behavior are among the bugs the team handles in its sprints, and they are the reason the index gets the same care as any other part of the product.
AI Features
AI is part of the platform’s roadmap rather than a separate project. The same sprint team that ships the storefront ships the AI work, which keeps those features tied to real commerce flows and the real data behind them. Details of individual features stay with the client.
A Podcast Platform From the Same Foundations
The team’s experience with social platforms led to a second product: a social podcast platform for a client in France. It reuses the patterns the team already knew, such as feeds, following and sharing, and applies them to audio instead of products. It also shows that a team built for one platform can carry a new product without starting from zero.
Results
The platform is in active development and the team has delivered sprint after sprint in a steady cycle, now past its twenty-seventh sprint. For a client in this market the useful outcome is predictability: a known team size, a regular cadence and a board where progress can be read at any time. Usage and sales figures belong to the client and are not published here.
Tech Stack
The core platform runs on PHP, with a hosted search service for indexing and AI features added alongside it. The deployment spans more than one region, which shapes how data, search and redirects are configured. The stack is conventional on purpose: with 32 developers contributing, a familiar technology lowers the cost of each new person joining the team.