Palantir is often presented as one of the companies defining the AI era. Its vocabulary supports that perception: ontologies, artificial intelligence, operational platforms and sovereign infrastructure.
Behind this vocabulary, I see a business model that feels very familiar. The company sells a strong vision to senior decision-makers, places highly capable people inside the customer, integrates fragmented systems and adapts its technology to the organization’s specific needs.
This is consulting combined with proprietary technology.
The model has been executed particularly well. It may also have productized more of the consulting work than traditional firms have managed to do. My issue is with the hype that presents this as a completely new and inherently scalable technology model.
This matters beyond one company. Many businesses now describe customized services as platforms. Consulting becomes deployment. Customization becomes configuration. A representation of the customer’s business becomes an ontology. Consultants become forward-deployed engineers.
The terminology is different, but the business question remains the same. Can the company reproduce the value it creates without rebuilding the relationship, implementation and delivery process around every customer?
A good business creates a fair trade of value between two parties. A successful business makes that trade repeatable and scalable.
Palantir clearly has a good business. I am less convinced that it has made the trade as repeatable as the market assumes.
Consulting presented as technology
Technology consultancies have used a similar proposition for decades.
Your data is fragmented. Your processes are inefficient. Your existing vendors do not understand your business. There is value trapped inside the organization, and we can help you recover it.
Consultancies rarely sell technical features alone. They sell access to expertise and the confidence that they can understand the client’s business. Accenture does not simply promise to install software. It promises to help the client improve the business through a combination of technology, industry knowledge and organizational change.
The proposition here is structurally similar.
Other technology providers want to extract the customer’s data, capture its economics and make it dependent on their platforms. This company claims to do something different. It enters the organization, understands how it operates and builds a system around that reality.
The important positioning choice is to present the technology as the product and the consulting as a deployment method.
This is probably the smartest part of the model.
The business does not look like a consultancy supported by proprietary software. It looks like a software company whose product is so advanced that it requires embedded engineers to realize its potential.
Many technical founders are attracted to this approach. They believe they have built a powerful and flexible system, but customers struggle to understand it. They add services so the customer can experience everything the system is capable of doing.
The initial assumption is usually that the services are temporary. The company will learn from early implementations, improve the platform and gradually reduce the need for custom work.
In practice, the services often remain central. Customers value the system, but they also value the people interpreting their needs, adapting the technology and turning organizational ambiguity into technical decisions.
The technology becomes better while each significant customer still requires a new process of discovery, persuasion and implementation.
The forward-deployed engineering question
Forward-deployed engineers identify requirements, integrate data, map operational relationships, configure workflows and adapt the system as the customer’s needs become clearer.
From the customer’s perspective, this can look a lot like high-end technical consulting.
The company’s answer is that these engineers work from a common platform. They are not producing an isolated analysis or a custom application that begins from zero. What they learn during one deployment can become a reusable capability in the platform.
I think there is real value in this approach. It may offer a better system for capturing and reusing consulting work.
The problem is that a common platform does not automatically make the customer’s path to value repeatable. The technical components can be standardized while every deployment still depends on unusual access, institutional knowledge, personal judgment and organizational commitment.
Both sides can therefore be right. The company sees a reusable platform. The customer experiences a group of talented people making that platform work in its particular environment.
The economic question is whether each new deployment requires a proportional increase in highly skilled delivery work. If it does, the business is scaling largely through people. If the implementation effort declines while customer value remains high, then it is successfully converting experience into software.
A keynote or product demonstration cannot settle this question. We need concrete customer outcomes, implementation costs and evidence that similar value can be produced repeatedly.
This was what I found missing in Alex Karp’s recent AIPCon presentation. He spoke at length about value creation without providing a clear example of the value created. There was no detailed case showing the operational problem, what the platform changed, the measurable result and the amount of custom work required to achieve it.
The vision was clear. The proof was not.
Claiming the AI category
The business also positioned itself as an AI company before the public understanding of AI became dominated by frontier-model providers.
Before ChatGPT, Claude and Gemini, the term could describe a broad range of predictive systems, analytics, decision tools and operational optimization. Palantir occupied that space early.
Frontier models changed the category. If a general-purpose model can perform analysis, write code and interact with business data, customers may begin to question why they need another expensive platform between the model and their operations.
The strategic response is to turn the frontier models into the problem.
The models are powerful, according to the argument, but they are expensive to use because of token charges. They lack precision, industry context and knowledge of the customer’s operations. They introduce safety risks. They may also expose the proprietary knowledge that creates the customer’s advantage, which Karp calls its “alpha.”
The application layer and ontology are offered as the answer. A customer can use frontier models, open-weight models or fine-tuned models while keeping its permissions, workflows, decisions and institutional knowledge under its own control.
This is a credible technical proposition. It is also a traditional way of responding to a competitive threat.
When a new technology threatens to commoditize your advantage, you emphasize what it cannot do and the risks it introduces. You then position your own platform as the layer required to make the new technology useful.
The company does not need to build the best general-purpose model. It needs to stop the model provider from owning the customer relationship and the operational context surrounding it.
This dynamic is relevant to many technology-enabled service companies. AI makes their experts more productive, but it also makes some of their expertise more accessible to customers and competitors. The companies respond by moving their value proposition toward orchestration, governance, proprietary context and strategic judgment.
Sometimes this produces a defensible software platform. Sometimes it gives consulting work a new vocabulary.
AI may allow a company to perform customized work with fewer people and earn better margins. That is a valuable improvement. It does not necessarily make the work repeatable.
A relationship-led model
This growth model differs from the best-known software playbooks.
It is not product-led growth in the style of Lovable, where an individual can discover the product, experience value quickly and spread adoption through the organization.
It is not an open-source model like the one that helped Databricks develop its ecosystem around Apache Spark.
It is not primarily a displacement model like Snowflake’s, where the company can identify an existing category of infrastructure and offer a clear technical replacement.
This model begins with trust.
The customer must believe that the provider’s people can understand the organization, that its platform can represent how the organization works and that both can be trusted close to important operational decisions.
The customer has to provide access, explain internal processes, expose organizational problems and commit to changing how work gets done. The system is most likely to succeed when the customer is fully committed.
Palantir reported 1,049 customers as of June 30, 2026. Considering the potential size of its contracts, this is not necessarily a low number. It does tell us what kind of growth model the company has chosen.
The business does not need millions of independent users. It needs a relatively small number of powerful institutions willing to build deep and expanding relationships.
The unit of growth is the relationship.
This also makes its ideal customer difficult to define. The ideal customer is not simply a manufacturer, government agency or financial institution of a particular size. It is an organization whose leadership believes its operations are important and unique enough to justify an intensive technological partnership.
That quality is hard to capture in a conventional ideal customer profile. It is usually discovered and developed through relationships.
This model can produce exceptional customer outcomes. It can also become difficult to challenge.
Customers that succeed are treated as evidence of the platform’s power. Customers that do not succeed can be viewed as insufficiently committed, insufficiently sophisticated or unwilling to transform.
The company can become less accountable for making its value proposition simple and repeatable because customer belief is considered part of the implementation.
The model is attractive while the community is committed. It becomes fragile if the community loses confidence.
The founder’s role in maintaining belief
Karp is important to this model, but I do not think the company should be analyzed mainly as a profile of its founder.
His role is to create and maintain the belief surrounding the system.
His patriotism, attacks on conventional software vendors and repeated references to neurodivergence give the business a strong identity. Customers are invited to see it as more serious, independent and mission-driven than the rest of the technology industry.
I am still not sure what Karp means by neurodivergence in this context. He appears to use it as a broad description of unconventional, abrasive and intensely productive people. It becomes a way to present temperament as differentiation. Aggression is framed as intellectual independence. Refusing a customer request becomes integrity. Difficulty fitting into conventional institutions becomes evidence of unusual ability.
Patriotism provides an even stronger form of alignment. The company does not treat defense work as an uncomfortable source of revenue. It identifies with the mission of the United States and its allies.
This helps build trust in environments where institutional relationships, security experience and political alignment matter as much as technical performance.
Karp’s charisma supports the claim that this is more than a vendor. It is a partner that understands what is at stake.
Founder charisma often plays a similar role in relationship-led enterprise companies. The founder acts as the interpreter of the technology and the guarantor of its potential. Strong conviction bridges the distance between what the system delivers today and what it promises to deliver in the future.
This can be a real commercial advantage. It is also difficult to separate from the product’s success.
When trust depends on the founder, senior relationships and a committed community, these are part of the distribution model. They cannot be dismissed as branding around an independently scalable software engine.
What the numbers tell us
The financial results make it too simplistic to dismiss the company as a consultancy.
In the second quarter of 2026, it reported 93 percent year-over-year revenue growth, an 85 percent GAAP gross margin and a 47 percent GAAP operating margin. Its cost of revenue grew much more slowly than revenue. Customer count increased from 849 to 1,049, and no customer represented more than 10 percent of revenue.
These are exceptional economics for a company with significant implementation requirements.
They show that the business has created substantial operating leverage. They also suggest that the platform captures and reuses at least part of the work performed during customer engagements.
What the numbers do not show is whether the next thousand customers can be acquired and implemented through the same process. They do not tell us how much growth depends on specialized personnel, senior access, founder charisma or favorable political conditions.
High margins measure the ability to capture value. They do not by themselves prove that the value creation process is repeatable.
Michael Burry’s comparison of the company’s deferred-revenue-to-revenue ratio with Accenture’s is relevant here. The reported ratio of about 32 percent does not prove that Palantir is a consulting company. Deferred revenue excludes contracted amounts that have not yet been invoiced, and the business reported approximately $4.8 billion in remaining performance obligations as of June 30, 2026.
Government contracts and termination provisions also make direct comparisons with conventional subscription software difficult.
The ratio is still an interesting signal because it directs attention toward the commercial model. The company may have software margins without having a fully software-like method of acquiring, implementing and expanding customers.
The useful question is not whether it is secretly a consultancy. The distinction is unlikely to be that clean.
The useful question is how much of the value can be delivered repeatedly by the platform, and how much continues to depend on the flexibility of its people and relationships.
A good business with a strong system of defense
The company has built a strong system around its model. It has proprietary software, accumulated deployment experience, embedded customer workflows, high switching costs, institutional relationships and a committed community.
It also has a narrative that turns changes in the competitive environment into arguments for why the platform is necessary.
Frontier models become evidence that customers need its control layer. AI-related security concerns reinforce its experience with sensitive systems. Political concerns about sovereignty strengthen its patriotic positioning. The complexity of implementation supports the need for forward-deployed engineers.
Each potential threat is incorporated into the company’s defense.
This may sustain a very successful business for years. But a strong defense does not answer the question of scalability.
A business based on deep relationships and flexible delivery can become enormous. Accenture demonstrates that. Its growth simply operates under different constraints from a product-led software platform. It requires continued access, trust, skilled people and a willingness to adapt around the customer.
That flexibility is one of this model’s greatest strengths. It may also be one of its limits.
The lesson extends to every company now presenting consulting as an AI platform.
Proprietary technology can improve the quality and consistency of delivery. AI can make teams much more productive. Relationships can create customer loyalty and pricing power. A charismatic founder can sustain belief while the platform develops.
These are all real advantages.
They do not automatically make the value exchange repeatable.
To establish that, a company has to show that similar customers can increasingly reach similar outcomes with less bespoke intervention, less founder involvement and less dependence on exceptional commitment.
Otherwise, it has not eliminated consulting. It has built a better and more profitable consulting model.
Good is not the same as scalable
The value exchange is real.
Customers provide access, commitment and substantial economic value. The company provides technology, embedded expertise and the possibility of meaningful operational improvement.
For the right customer, this can be an excellent trade.
The misguided hype begins when that successful exchange is treated as proof of a universally scalable technology model.
The company may not have invented a completely new category of software. Its more meaningful achievement may be the construction of a consulting-led business capable of producing software-like margins while presenting the consulting as incidental.
That model is powerful, but it is also demanding.
It works when customers believe, participate and commit. It works when relationships provide access to the right institutions. It works when the people delivering the system can translate customer complexity into reusable platform capabilities.
The risk is not that the business creates no value.
The risk is that too much of the value still depends on the flexibility, intimacy and conviction of consulting, while the hype assumes the repeatability of software.
A good business creates a fair trade of value between two parties.
A successful business makes that trade repeatable and scalable.
Palantir has demonstrated the first. The second remains the question, both for the company and for every business now describing its consulting model as an AI platform.
This article analyzes Palantir’s business model and public financial disclosures. It is not investment advice.
Sources: Palantir Q2 2026 Form 10-Q; Palantir Q2 2026 business update; Palantir revenue and remaining-performance-obligation disclosure; summary of Michael Burry’s argument.
98% AI generated article about AI consulting. We have achieved "no human in the loop" linkedin slop