How do you market apps to car manufacturers?

Selling an app to a car manufacturer is not like selling software to a retailer or a hospitality brand. The sales cycle is longer, the stakeholder map is more complex, and the buying criteria are rarely the ones you think they are. App companies that approach original equipment manufacturers (OEMs) the same way they approach any other B2B prospect tend to lose not because their product is weak, but because they misread what the organisation is actually evaluating.

The companies that win OEM deals understand the procurement process before they write a single line of pitch material.

The automotive sector is moving fast. By 2030, nearly 95% of new vehicles will be connected, up from 50% in 2020 (TMA Solutions), and the software that runs inside and alongside those vehicles is becoming a genuine commercial battleground. App developers who understand how to position themselves inside that shift will find real opportunities. The ones who treat OEM procurement like a standard enterprise sale will spend years in pilot purgatory.

We have worked directly in the automotive space, including a pitch we ran for BMW focused on a fleet and rental vehicle management product. That experience shaped a lot of how we think about what manufacturers are actually looking for, and what app companies consistently get wrong when they try to earn a seat at the table.

How automotive procurement actually works

OEM procurement is a process that typically runs across multiple departments, each with different priorities and different definitions of success. Engineering teams care about integration. Legal and compliance teams care about liability and data governance. Brand teams care about in-cabin experience and how a third-party product reflects on the manufacturer's reputation. Finance teams care about total cost and commercial model. Every one of those groups has to say yes, or at least not say no loudly enough to kill the deal.

The timelines involved reflect that complexity. From first contact to a signed agreement, OEM procurement cycles regularly run to 18 months or longer. A product that enters the process without understanding this tends to push for decisions at the wrong moments, misread silence as progress, and exhaust the patience of internal advocates who were actually on their side.

What this means practically is that your go-to-market strategy needs to be built around sustaining relationships over time, not closing quickly. The pitch materials, the proof of concept, the brand presentation, the integration documentation, all of it is doing work across a much longer window than most app companies plan for.

Why features are not the buying criteria

The instinct when pitching to a large organisation is to lead with capability. Here is what the product does, here is the feature list, here is how it compares to alternatives. That approach works in some markets. In automotive OEM sales, it tends to produce polite interest followed by nothing.

Manufacturers are buying confidence that the relationship will hold up over a vehicle lifecycle that spans five to seven years from design lock to end of production. A feature that sounds useful in a pitch means very little if the organisation cannot be certain the vendor will still be operating, still updating, and still able to support the integration halfway through that window.

This is worth sitting with if you are preparing a pitch. A feature comparison table is easy to produce and easy to ignore. What is harder to produce, and much harder to ignore, is a clear answer to the question of what happens to this product and this relationship in year three or year five. OEM buyers are trained to think in vehicle lifecycles. An app company that thinks only in release cycles signals, without meaning to, that it does not understand what it is being asked to take on.

Build your pitch materials around lifecycle questions, not feature lists. Show what your support model looks like in year three, and name the people responsible for it.

The role of trust in long sales cycles

Trust is the primary filter in automotive procurement. A buying team that does not trust a vendor will not move the relationship forward regardless of how good the product is, because the downside of a failed integration inside a vehicle platform is far more serious than the downside of missing a useful feature.

We encountered a version of this dynamic on a toll management project, where part of our work involved educating the client about what it would actually take to establish formal data-sharing relationships with established toll operators. A brand-new, unproven product simply does not have the leverage to negotiate API access with incumbents. The smarter approach, and the one the client accepted, was to launch using a preloaded credit model first and pursue API integrations later, once the platform had established credibility. The staged approach was not a retreat; it was the route that made the eventual integrations possible.

The same logic applies when approaching OEMs. Trust is built through demonstrated competence in adjacent contexts before you ask for the high-stakes relationship. Salesforce's State of the Connected Customer report found that 54% of users say it is harder than ever for companies to earn their trust, and that finding holds in B2B contexts as much as in consumer ones.

Trust is built before the high-stakes relationship begins, through demonstrated competence in smaller, adjacent contexts.

An OEM that has seen your product work reliably in a lower-risk context will approach the deeper integration conversation very differently than one that is being asked to take everything on faith.

Integration fit: what manufacturers are really evaluating

Beyond trust, the technical evaluation that carries the most weight in OEM procurement is integration fit. This means whether your product can slot cleanly into an existing platform architecture, whether it creates security or liability exposure, and whether it requires the manufacturer to change things they are not willing to change.

90% of B2B buyers agree that a vendor's ability to integrate with their existing tech significantly influences their decision to shortlist that vendor (Inbox Insight). In automotive, where the existing tech stack includes proprietary operating systems, hardware constraints, and regulatory requirements across multiple markets, that figure feels conservative.

The integration question is also where app companies most often underestimate the complexity they are walking into. We saw this pattern on the BMW fleet vehicle work we did, where the interface challenge was not primarily about design or features but about what the system could actually ask of a user given the context they were in. A post-accident user cannot be expected to navigate a complex form, regardless of how well designed it is. The integration has to account for emotional and cognitive state, not just technical compatibility.

Before your first OEM meeting, map your product against their known platform architecture. If you cannot name the constraints you would be working within, the technical evaluation team will find out in the first fifteen minutes.

Staging your market entry to build credibility

The toll management project taught us something that applies directly to any app company trying to enter the automotive supply chain. You do not earn the right to the complex, high-value integration by pitching it first. You earn it by demonstrating that a simpler version of the relationship works.

For that client, the staged approach meant launching with a preloaded credit model, building a track record, and then returning to the API conversation with incumbents from a position of proven commercial viability rather than theoretical promise. The manufacturers and operators they needed to work with were far more receptive once there was something real to evaluate.

For an app company approaching OEMs, staging might look like securing a fleet management contract before pursuing in-cabin integration, or demonstrating the product inside an aftermarket context before asking to be considered for a factory-fit programme. The sequence matters because each step changes what you are able to claim in the next conversation.

A working prototype also does more work in these conversations than most app companies expect. We saw this with a trading card platform client who struggled to generate traction from pitch decks alone, but made real progress once he had a demonstrable product he could show and walk people through. In automotive procurement, where scepticism about new entrants is high, something a technical evaluator can actually interact with changes the temperature of the room.

How your brand experience signals readiness

OEM buyers are evaluating your company, and the quality of your brand experience is one of the clearest signals available to them about how seriously you take the relationship you are asking them to enter.

A rough pitch deck, inconsistent language across documents, or a website that does not reflect the standard of the product all register, consciously or not, as signals that the company is not yet operating at the level the manufacturer requires. This is about what those aesthetics communicate about internal standards and organisational maturity.

We think about brand experience the same way across all the sectors we work in, from wellness and supplements to fitness and activewear. The question is always whether every touchpoint is consistent with the character the product is trying to project. In an OEM context, where your brand is being evaluated by people whose own brand is built on precision and engineering rigour, the standard is particularly unforgiving.

Review every document, slide, and email template you send to an OEM as though a senior brand director at that manufacturer will see it. If it would not pass that test, it is not ready to send.

This extends to the quality of documentation you provide around APIs, integration requirements, and support processes. A well-structured technical document signals that you have done this before, or are at least operating as though you have. A poorly structured one signals the opposite, and that impression is very hard to walk back.

Navigating gatekeepers and internal champions

In any large organisation, the person you first meet is rarely the person who makes the decision. In automotive OEM procurement, there are typically several layers between the innovation team or the connected services group that initially engages with you and the executive committee or the programme board that approves the contract.

Understanding this map is part of the job. Your goal in the early stages is to find the person inside the organisation who has both genuine enthusiasm for what you are building and enough organisational standing to move the conversation upward. Without an internal champion, the relationship tends to stall at whatever level it entered.

Finding that champion requires listening carefully in early meetings for signals about internal politics, about which teams have budget authority, and about where the energy around connected services actually sits. The person who takes your call enthusiastically is not always the one with the influence to push the programme forward.

Once you have identified a potential champion, your job is to make their internal case as easy as possible to make. That means giving them materials they can share upward, clear answers to the objections they will face, and a narrative that connects your product to something the organisation already cares about publicly, whether that is safety, sustainability, or driver experience.

What a compelling proof of concept looks like in automotive

A proof of concept in the automotive context needs to do something specific. It needs to demonstrate that your product works reliably within the constraints of the environment where it will actually be used, not in ideal conditions but in the conditions the vehicle and the driver will actually encounter.

The BMW fleet vehicle work we ran for a pitch is a good illustration of what this means in practice. The challenge was an app that asked accident victims to photograph damage and fill in claim forms. Users were not completing these tasks properly, and the team initially could not work out why. The answer was straightforward once you considered the context: a person who has just had an accident is not in a state to navigate a complex interface, recall what information is needed, or type detailed descriptions of what happened.

The redesign we proposed addressed this by separating what the system needed immediately from what it could gather later. First, the app checks whether the user needs emergency services and is in a safe location. Then it presents an exploded diagram of the vehicle, drawn from the kind of image you see on rental car agreements, where the user taps the areas where damage occurred to indicate where photos are needed. Instead of typed claim forms, it uses voice recording for witness statements, which can be transcribed later when the person is calm. The proof of concept demonstrated that the product worked and that it understood the actual human context it was working within.

That is the standard a compelling automotive proof of concept needs to meet.

Common mistakes app companies make when pitching OEMs

Most of the mistakes we see follow a recognisable pattern. They come from applying consumer app logic or standard enterprise sales logic to a procurement process that operates by different rules.

1. Leading with features rather than lifecycle fit, and leaving the manufacturer to work out how the product serves a five-year programme.
2. Underestimating the integration complexity, and signalling in early technical conversations that the product was built without deep knowledge of the platform it is being asked to join.
3. Pitching to the wrong level, making contact with innovation teams that have enthusiasm but no budget authority, and never building a relationship with the people who hold the programme budget.
4. Asking for too much too early, proposing a factory-fit integration before demonstrating anything in a lower-risk adjacent context.
5. Letting brand presentation slip, sending materials that do not reflect the standard of a company ready to support a manufacturer's product for seven years.
6. Misreading silence as progress, treating the absence of a no as evidence of a yes, when in OEM procurement, silence often means the internal champion has hit an obstacle they have not yet found a way around.

The thread connecting most of these is a failure to think from inside the manufacturer's position. What does a programme director at an OEM need to be true before they can take this to a board? That question, asked honestly and early, tends to reorganise the pitch in the right direction.

Conclusion

Selling an app to a car manufacturer rewards a particular kind of patience and a particular kind of preparation. The companies that find their way into OEM programmes tend to have one thing in common: they understood the buying organisation's real concerns before they started selling, and they built their market entry around demonstrating credibility at each stage rather than pushing for the largest possible deal as fast as possible.

The connected vehicle market is large and growing. The global automotive software market is projected to reach over $462 billion by 2030 (McKinsey), and the competition for that opportunity is intensifying. App companies that understand how OEM procurement actually works, and who invest in their brand, their integration documentation, and their staged market entry accordingly, are the ones who will convert that opportunity into real commercial relationships.

The work we did on the BMW fleet vehicle pitch, and the lessons from the toll management project around staged credibility building, have shaped how we approach this kind of challenge. The right product presented the wrong way loses. The right approach, applied consistently over a long sales cycle, gives a good product the chance it deserves.

If you are building for the automotive market and want to think through how to approach OEM conversations with more confidence, let's talk about your go-to-market strategy.

Frequently Asked Questions