About Dev-id LA
Dev-id LA is a software development company that turns ideas into working products. Their core services include Mobile App Development. Its team includes 10 - 49 specialists working across design, development, and delivery. Typical hourly rates run around $100 - $149 / hr/hr. Dev-id LA holds a 5.0-star rating across 1 client reviews. Their home base is Marseille, France. This gives a quick snapshot of what to expect when working with Dev-id LA.
Where We Specialize
Industry Expertise
Typical Project Size
Dev-id LA Reviews
Write a ReviewAn app our customers return to daily — the engagement numbers speak for themselves
Omar Al-Farsi / Chief Technology Officer - Falcon Digital VenturesJun 05, 2026
Project summary: Our engineering capacity was committed to maintaining existing systems and could not absorb a net-new build of this complexity. An external partner with the right skills was the only viable option.
We had worked with three agencies before this engagement. The comparison is not flattering to the others. What distinguished this team was a systematic approach to understanding the problem before proposing a solution — something that sounds obvious and is practiced far less often than it should be. The delivery phase ran to schedule, the codebase is clean enough that our internal engineers made positive comments during handover review, and we have not logged a critical incident in five months of live operation. We intend to use them for our next phase of work.
Deep domain knowledge that reduced the discovery overhead significantly, proactive risk identification before issues became incidents, delivery cadence that our stakeholders found reassuring
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
Architecture review that saved us from a vendor decision we would have regretted for years
Nora Al-Otaibi / VP of Engineering - Salam Digital SolutionsJun 04, 2026
Project summary: Serialisation requirements under new traceability legislation had a compliance deadline. Our supply chain system required targeted development to meet it — generalist knowledge was not sufficient.
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
Their insistence on a detailed functional specification before development began felt like friction at the time. In retrospect, it was the reason the development phase ran without the ambiguity that has derailed similar projects for us previously
Questions & Answers
Distributed ledger that finally solved a trust problem we had spent three years arguing about
Tobias Lindemann / Leiter Digitalisierung - Lindemann Industrie GmbHMay 28, 2026
Project summary: Unplanned downtime had become our single largest cost driver and our data showed that predictive maintenance could address the majority of it — if we had the right infrastructure to act on it.
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
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
Multi-region setup that has delivered 99.97 percent uptime since go-live
Siobhan Gallagher / Chief Technology Officer - Northumbria FinTech LtdMay 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.
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.
Delivery timeline that proved achievable rather than optimistic, estimation accuracy that reflected real analysis rather than competitive bidding, scope discipline that prevented the feature creep we had experienced before
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
Performance marketing that produced positive ROAS in the first full campaign cycle
Sebastian Lapointe / CTO - Boreal Systems IncApr 01, 2026
Project summary: The transition to EV had created demand for dealer network management capabilities our existing system was not designed to support. A targeted rebuild was the agreed path forward.
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.
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
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
CI/CD pipeline that transformed how our engineering team thinks about release risk
Matthieu Renard / Directeur Technique - Lumière Technologies SASMar 13, 2026
Project summary: Digital-first buyer behaviour had made our property search experience a genuine competitive liability. We needed it to match the quality of the portfolio it was representing.
The technical quality of the final deliverable is the easiest thing to point to. The automated test coverage is thorough, the deployment pipeline is reliable, the documentation is genuinely useful rather than ceremonially produced. But the metric I keep returning to is the number of post-launch conversations we have not had to have. No incident calls at two in the morning. No emergency patches. No retrospective discussions about what went wrong. The absence of those events is the evidence I would show to someone considering this vendor.
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
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
Machine learning in production that the board could see working within eight weeks
Dominic Fairfax / Head of Digital Transformation - Arcadian Consulting LtdMar 10, 2026
Project summary: Our campaign management workflow had grown to involve twelve different tools and significant manual reconciliation. The inefficiency was affecting both speed and accuracy.
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
Blockchain expertise that came with clear explanations, not just technical jargon
Hyun-Su Lim / Director of Platform - Hanam Tech SolutionsFeb 08, 2026
Project summary: Digital service standards required all citizen-facing applications to meet accessibility and performance benchmarks that our inherited systems failed. Remediation was not viable — we needed a replacement.
We gave this team an aggressive timeline, a technically complex scope, and a client-side project team that was stretched thin and not always available at the speed the engagement required. They absorbed all of that gracefully. Where they needed input they were precise about what they needed and when. Where they could proceed independently they did. The result was a delivery that landed on time despite the constraints on our side, which I regard as evidence of genuine professional maturity.
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
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