About Lightbase
Lightbase has been in business since 2017, delivering technology projects for clients. Lightbase focuses on Web Development and Mobile App Development. The company operates with a team of 10 - 49 professionals. Typical hourly rates run around $100 - $149 / hr/hr. The team is based in Utrecht, Netherlands. This gives a quick snapshot of what to expect when working with Lightbase.
Where We Specialize
Industry Expertise
Typical Project Size
Lightbase Reviews
Write a ReviewDelivered on scope, on time, and with code quality that passed our strictest review
Sebastian Lapointe / CTO - Boreal Systems IncMar 19, 2026
Project summary: B2B customer churn was concentrated among accounts that had complained about portal usability. We needed a complete redesign of the self-service experience before the next contract renewal cycle.
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.
Deep domain knowledge that reduced the discovery overhead significantly, proactive risk identification before issues became incidents, delivery cadence that our stakeholders found reassuring
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
Custom modules that fit our operational processes rather than forcing us to change them
Eoghan Fitzgerald / VP of Engineering - Shannon Tech Solutions LtdMar 13, 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 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.
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
End-to-end quality programme that halved our post-release incident rate inside three months
Zara Hussain / Head of Technology - Ravi Digital AgencyMar 08, 2026
Project summary: B2B customer churn was concentrated among accounts that had complained about portal usability. We needed a complete redesign of the self-service experience before the next contract renewal cycle.
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.
Collaborative culture that made the team feel like a genuine extension of our organisation, strong asynchronous communication across time zones, zero-drama handling of the inevitable mid-project changes
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
A partnership that began with a single project and earned a place on our preferred vendor list
Reuben Loh / CTO - Marina Bay Ventures Pte LtdMar 04, 2026
Project summary: Rapid growth had created a skills gap on the platform engineering side of our business. We needed an experienced partner to close that gap while our internal team scaled, without compromising quality or timeline.
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.
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
CRM integration that connected our marketing automation to our revenue motion seamlessly
Adriana Voss / Director of Platform Engineering - Cascadia Digital VenturesJan 29, 2026
Project summary: Our trading platform had been extended incrementally for seven years. Latency was degrading, technical debt was compounding, and a clean rebuild was no longer optional.
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.
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
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
E-commerce build that united our digital and in-store inventory for the first time
Rupert Ashford / Director of eCommerce - Hargrove Retail PLCJan 07, 2026
Project summary: Several years of incremental development had left us with a platform that was technically functional but strategically limiting. A structured rebuild was the agreed path forward.
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.
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