About Despark
Since 2007, Despark has operated as a technology services provider. The company's main offerings are Mobile App Development. Despark employs 10 - 49 people. Typical hourly rates run around $100 - $149 / hr/hr, with an average project cost near $55,000. Clients have rated Despark 4.7 out of 5 in 13 reviews. Despark operates out of Sofia, Bulgaria. This profile is a starting point — reach out to Despark directly to discuss project specifics.
Where We Specialize
Industry Expertise
Typical Project Size
Despark Reviews
Write a ReviewPenetration testing delivered with clear findings and actionable remediation steps
Minjun Oh / Director of Engineering - Sejong Digital CorpJan 14, 2026
Project summary: Claims fraud detection had been rule-based for years and we were losing ground to more sophisticated patterns — we needed a machine learning model built on our own historical data.
The engagement started with a discovery workshop that immediately signalled this team was different. They pushed back on two of our assumptions in the first session with evidence and a better alternative. That kind of intellectual honesty is rare and it set the tone for the whole project. Deliverables were consistently ahead of schedule, code reviews were taken seriously, and the final product is something we are proud to show enterprise clients during due diligence calls.
Technical depth across the full stack, honest and timely communication, delivered exactly what was scoped without surprise additions to the invoice
Time zone difference required some adjustment to our internal communication habits but the team managed the overlap window efficiently and it never affected momentum
Questions & Answers
Security posture transformed from a known liability to a competitive differentiator
Gustavo Ferreira / VP of Technology - Amazônia Digital LtdaJan 11, 2026
Project summary: An international expansion required multi-currency, multi-language, and multi-warehouse capabilities that our existing platform could not support without a fundamental re-architecture.
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.
Senior-level engineering presence throughout the entire project, not just during the pitch, honest and commercially fair handling of scope changes, codebase that our internal team praised on review
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
Questions & Answers
Sensor network and analytics layer built by engineers who understood both halves equally
Marcus Holloway / SVP of Engineering - Vertex Cloud DynamicsJan 02, 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.
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.
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
Prototype-to-handoff process that our developers actually appreciated
Jordan Mills / Director of Operations - Cascade ManufacturingJan 16, 2025
Project summary: Guest experience scores had plateaued and our data showed that friction in the pre-arrival and in-stay digital journey was the primary cause — we needed a purpose-built guest app.
Project governance was one of the things that impressed me most. We had a dedicated project manager who ran tight fortnightly sprints with clear acceptance criteria, a shared backlog that gave us full visibility at all times, and a change request process that was fair and transparent. Nothing slipped through the cracks, no bill shock at the end, and the final delivery matched the original scope document almost perfectly. In my experience that kind of discipline is genuinely uncommon.
Engineering quality that our internal team can maintain without calling the vendor, thorough documentation, proactive risk identification throughout the project
The initial project brief document they required was more detailed than we were used to providing, but in hindsight that rigour was part of why the project ran so smoothly