https://www.thenational.scot/news/26055524.palantir-hired-30...
Build: you need expertise in contracts, knowing what you need and also software development.
It's obviously easier to buy than build, especially for civil service roles where they can't attract the best developers due to political/ideological constraints.
But if you have a government department that builds software, they can also spec it. And everyones interests are aligned.
Further you open the door to bell labs/DARPA type speculative work.
Seems to me, the type of work environment where you have that freedom, are able to open source work would be attractive to a lot of people.
Spending 10x more on IBM or Palantir can't get them fired, but trying to build something in-house their organization don't have competence for can get them fired.
And this is even if you don't take lobbying or corruption into account.
Almost all governments have a legally defined public procurement framework. If this is overridden, it's pretty much always by elected politicians, not by regular government employees.
> Almost all governments have a legally defined public procurement framework.
> If this is overridden, it's pretty much always by elected politicians, not by regular government employees.
Also it's not like 4 years ago either UK or EU governments would expect they will soon want to get rid of all US companies in their public sector.
But its kind a obvious why some system for refugees was outsourced for consultancy.
https://en.wikipedia.org/wiki/Government_Accountability_Offi...
I'll give you an example. At a previous employer, We used Google Analytics. We paid for Google Analytics. I feel positive that as a mid size company, We shouldn't have paid for Google Analytics. The free product with 50 events in GA4 should be plenty for us. But why do we use Google Analytics in the first place? Because everyone uses Google Analytics.
I agree that sometimes Salesforce might be a good idea. However, it should be a part of an overall strategy, not just because everyone does it. This kind of deliberate tooling strategy is difficult though because the way Google Analytics or Salesforce works from what I understand is make marketing folks feel they are specialized in Google Analytics or Salesforce so they feel like they have to keep using it or their skill will become useless.
It is like resume driven development but for the whole business.
It's like this for most software, but as a salaryman it's better for you if you use the common software. If you have an interview you can now say "I know how to use the thing that most people use" instead of "Actually we had an inhouse system so if you hire me I need to be onboarded for 3 months".
I got hired to my 2nd job in large part because I knew how to use Broadridge Paladyne (back then it was pretty good if you got over the pretty bad UI/UX, by today's standards it's not great).
„Everyone does that“ is definitely part of decision-making process almost everywhere, but I personally have not seen companies where it’s just a cargo cult rather than a reasonable strategic choice. The obvious benefits are that it’s easier to find implementation partners, the costs are predictable and your users may already know the system, so you won’t have unnecessary friction in your ops.
1. Palantir isn't selling consulting as much as Palantir is selling the confidence you get from buying a name brand. It's the same as paying for McKinsey to provide justification to do what you already want to do.
2. Palantir actually has some good core tech. An in house team can probably do a better job just because the incentives are better aligned, but they'll be starting from behind and have to catch up.
3. LLMs aren't at a level to replace a team of FDEs. Maybe in a couple of years. The role requires too much understanding of the human systems, and too much initiative to keep the ball rolling/acknowledge and deal with real problems.