About Alexapps
Alexapps has been in business since 2008, delivering technology projects for clients. Their core services include Custom Software Development and Web Development. Alexapps employs 2 - 9 people. Projects are generally billed around $25 - $49 / hr/hr. The team is based in Alexandria, Egypt. Overall, Alexapps is one of the options worth shortlisting for a technology project.
Where We Specialize
Industry Expertise
Typical Project Size
Alexapps Reviews
Write a ReviewDesign work that measurably improved every conversion metric on our platform
Sebastian Lapointe / CTO - Boreal Systems IncJan 18, 2026
Project summary: Multi-touch attribution across our media mix had become the most-requested capability from every client in our portfolio. We could not deliver it without rebuilding our data layer.
I came into this engagement as a sceptic. We had been through a failed implementation with a previous vendor and I had high standards for what evidence of competence looked like before I would trust a partner with our core systems. This team earned that trust progressively — through the quality of the discovery documentation, the rigour of the technical proposals, the consistency of the sprint deliveries, and ultimately the stability of the production system. I no longer lead with scepticism when recommending them.
Architectural decisions designed for longevity rather than just the current brief, thorough automated test coverage, post-launch stability that validated every technical choice made during discovery
The quality of documentation they produce means our team needed to set aside dedicated review time to do it justice — a minor scheduling point rather than a genuine criticism
Questions & Answers
Gameplay feel that matched the design intent precisely — a harder achievement than most realise
Clémentine Aubert / Head of Digital Products - Arc-en-Ciel Digital SASJan 16, 2026
Project summary: Customer expectations had reset and our conversion funnel data showed precisely where we were losing them. We needed a commerce platform capable of delivering the experience our competitors already had.
Our stakeholder group included board members, clinical leads, compliance officers, and end users — each with different technical literacy and different success criteria. This team navigated that stakeholder landscape as well as any vendor I have seen. They adjusted their communication register depending on the audience without losing the substance. They managed expectations honestly throughout. And they delivered a system that each group can point to as meeting their requirements. That breadth is genuinely uncommon.
Production system that has performed as specified since go-live without remediation work, documentation thorough enough to support internal maintenance, knowledge transfer that left our team genuinely capable
Time zone coordination required some deliberate overlap management from both sides in the first couple of sprints, after which we had an efficient async rhythm that worked for the whole project
Questions & Answers
A DevOps engagement that delivered cultural change as well as technical change
Liselotte Bakker / Head of Platform Engineering - Harbour Digital BVJan 14, 2026
Project summary: Lean manufacturing initiatives required real-time OEE data at the line level. Our existing systems could not provide it without significant manual aggregation.
The project brief was ambitious and we had received proposals ranging from two to five times our eventual budget from other vendors. This team came back with a proposal that was commercially realistic and technically credible — and then delivered against it. That alignment between proposal and outcome is not something I take for granted. I have been on the other side of it enough times to know it requires both honesty in the sales process and discipline in delivery. We experienced both.
Commercially transparent throughout — no hidden assumptions, no bill shock at the end, change requests that were fair and clearly explained rather than used as a margin-recovery mechanism
We underestimated the input required from our subject matter experts during the requirements phase. The team flagged this early but our resource planning did not fully reflect it — our responsibility, not theirs
Questions & Answers
Test automation that our developers adopted as a genuine aid rather than a compliance exercise
Matthieu Renard / Directeur Technique - Lumière Technologies SASJan 09, 2026
Project summary: Matter management had become a significant overhead for our fee earners. Every hour spent on administration was an hour not spent on billable advisory work — the business case was straightforward.
The thing that retrospectively seems most significant is how little drama there was. Complex technology projects tend to accumulate incidents, escalations, and tense conversations. This one did not. Problems were surfaced before they became incidents. Scope changes were handled with process rather than conflict. Risks were managed rather than avoided. That level of maturity is rare in my experience and it made the delivery feel almost effortless from our side, which I know it was not from theirs.
Clear and consistent communication adapted appropriately for both technical and non-technical stakeholders, shared tooling that gave our team real-time visibility, reliable sprint delivery throughout
Their discovery process is more rigorous than we were accustomed to and required more preparation from our side than we had initially allocated — but the quality of what followed justified every hour of it
Questions & Answers
Single source of truth delivered — if you know how rare that is, you understand why we are impressed
Fatima Al-Suwaidi / Head of Digital Strategy - Gulf FinTech HoldingsJan 04, 2026
Project summary: Cross-agency data sharing had been blocked by incompatible systems for four years. A secure integration platform was the prerequisite for every transformation initiative in our roadmap.
What made the most difference in practice was the quality of the engineering judgment on this team. Not the ability to execute a specification — that is a baseline expectation. The ability to recognise when a specification was suboptimal, explain why, propose an alternative, and support the client in making a decision about it. That consultative dimension elevated the output beyond what the brief described and resulted in a product that is more fit for purpose than the one we had originally specified.
Commercially transparent throughout — no hidden assumptions, no bill shock at the end, change requests that were fair and clearly explained rather than used as a margin-recovery mechanism
We underestimated the input required from our subject matter experts during the requirements phase. The team flagged this early but our resource planning did not fully reflect it — our responsibility, not theirs
Questions & Answers
Gameplay feel that matched the design intent precisely — a harder achievement than most realise
Lars Pfeiffer / VP of Technology - NordTech Logistik GmbHJan 02, 2026
Project summary: Our audience data was fragmented across eight tools with no single identity layer. Personalisation had become impossible without first solving the data foundation.
Our stakeholder group included board members, clinical leads, compliance officers, and end users — each with different technical literacy and different success criteria. This team navigated that stakeholder landscape as well as any vendor I have seen. They adjusted their communication register depending on the audience without losing the substance. They managed expectations honestly throughout. And they delivered a system that each group can point to as meeting their requirements. That breadth is genuinely uncommon.
Architectural decisions designed for longevity rather than just the current brief, thorough automated test coverage, post-launch stability that validated every technical choice made during discovery
The engagement was priced at the quality level rather than the budget level. We evaluated the alternatives and concluded that the delta was a reasonable premium for the reduction in delivery risk