Palantir.net
Overall Review Rating
4.2 (7 Ratings)
Overview
Palantir.net is a full-service web development company that creates engaging online experiences for clients who value sustainable, accessible, human-centered approaches to strategy, design, development, quality assurance, training, and support. Their collaborative process enables for transparency and trust between our team and their clients. They start by understanding our client’s business objectives, aspirations, audience behaviors and needs.
Services
- Digital Strategy
- Hyperledger
- Enterprise App Development
- Market Research
- Web Development
- Azure Services
- Cloud Governance
- Mobile App Development
- Android App Development
- Platform Development
- Cross Platform Development
- iOS App Development
Industries Served
Palantir.net Reviews
Have a look at these client reviews on previously delivered projects.
Gustavo Ferreira
VP of Technology - Amazônia Digital LtdaISO 27001 certification achieved on the first attempt. The preparation was that thorough.
What set this team apart in practice was their engineering judgment — specifically, their willingness to tell us when our requirements were wrong and explain what to do instead. Not every vendor does that. The consultative element elevated the final output well beyond what our original brief described. We ended up with something better than what we had asked for, which is not a sentence I expected to be writing in a review.
Project summary
International expansion required multi-currency, multi-language, and multi-warehouse capability our current platform could not support without a rewrite.
Abdullah Al-Shehri
Head of Innovation - Desert Tech VenturesInfrastructure-as-code that our team uses as a reference example internally
The platform has been live for six months and is handling three times the transaction volume we scoped for. That is not because we underestimated — it is because the architecture choices made during discovery were genuinely forward-thinking. Most vendors design for exactly what you tell them. This team designed for what you are likely to need. We are already scoping the next phase and there was no question about who we would use.
Project summary
A new care pathway required patient data to move between systems in a way our current architecture did not support. The integration complexity was beyond what we could handle in-house.
Tariq Al-Harbi
Director of Technology - Saudi Cloud HoldingsERP went live on the agreed date. Those of you who have been through ERP projects understand.
Three months post-launch our key metrics are all moving in the right direction — user adoption ahead of target, support volume down, time-on-task reduced for our core workflows. The product team has started planning features that were never viable on the previous platform. That is the real proof of the investment: it opened up possibilities rather than just replacing what was there before.
Project summary
Our agents were managing data across four disconnected systems. The time they spent on reconciliation was time not spent with clients. The ROI case for consolidation was obvious.
Amit Goldstein
VP of Product - Tel Aviv Ventures LtdClear-eyed assessment of where we were, followed by a credible plan forward
The knowledge transfer at the end of the project was notably good. Too many vendors see handover as a tick-box exercise. This team ran structured sessions, produced documentation our internal team actually references, and spent real time making sure we understood the architecture decisions well enough to maintain and extend the system independently. Six months later we are doing exactly that without needing to go back to them for every question.
Project summary
A failed engagement the previous year had made us more rigorous about vendor selection. We took the time to find a partner we actually trusted before we committed.
Flynn Buchanan
GM of Technology - Pacific Rim Commerce GroupSmooth launch, great reviews, no embarrassing bug reports from users in the first month
Honestly, I came into this engagement with some scepticism. We had a bad experience with a vendor twelve months earlier and I wanted to see evidence of competence, not just hear about it. The discovery documentation was the first signal. The sprint delivery consistency was the second. By go-live I had stopped being sceptical and started planning how to expand the engagement. The production system has been stable from day one and our internal team loves working with the codebase they left us.
Project summary
B2B customer churn was concentrated in accounts that rated our self-service portal poorly. A redesign was necessary before the next wave of contract renewals.