# Mats Lundquist

Mats Lundquist writes about IoT connectivity, including eSIM standards, roaming and the challenges of connecting vehicles across markets.

- Profile: https://b2binfluencer.marketing/creators/mats-lundquist/
- LinkedIn: https://www.linkedin.com/in/mats-lundquist-b0770b31
- LinkedIn followers: 2,811
- Topics: cybersecurity
- Based on 10 dated posts, latest 2026-10-01

## Summary

Mats Lundquist is most useful for plain-language B2B thought leadership on IoT connectivity, eSIM standards, roaming and connected vehicles.

- Best for: A B2B IoT connectivity provider seeking a webinar or authored article on SGP.32, roaming and automotive strategy.
- Not for: Consumer electric vehicle brand wanting short-form lifestyle video on Instagram or TikTok.
- Check first: Confirm how collaboration fits with their Telenor IoT work and ask for audience data.

### Takeaways

- SGP.32 lets companies install eSIMs at the factory and manage connectivity remotely per market.
- Connected cars are software-defined vehicles with three hard problems: connectivity, eSIM adoption, cybersecurity.
- Roaming rules and regulation decide what is technically possible.

## Main ideas

- **The IoT industry has grown past its early, experimental phase**: Across these posts, the central claim is that IoT is no longer emerging. Mats Lundquist supports it with a long personal timeline, recalling an era of unclear roles, many players and proprietary technologies not designed for IoT. They contrast that with double-digit adoption, high awareness and technologies now built specifically for connected devices. The priority, they argue, is standardisation and new ways of working rather than novelty. How businesses adopt these shifts, not the technology itself, will decide outcomes.
- **SGP.32 matters because it keeps hardware flexible after it ships**: Lundquist explains SGP.32 as an eSIM standard from the industry body GSMA that lets businesses manage connected devices remotely at scale without physically swapping SIM cards. The case goes beyond day-to-day convenience: connected products have long life cycles, so building the eSIM in at the factory lets businesses manage it remotely for different markets later, including switching IoT providers without changing the card.
- **Growing complexity means companies should do less themselves and partner**: A recurring priority is that connected-device complexity has outgrown what a single company can master alongside its main business. Lundquist argues that businesses should focus on core operations and use specialised partners for areas outside their expertise. They describe partnership examples as a shortcut to faster innovation, not a fallback.
- **Connected cars are software-defined vehicles with three specific hard problems**: Cars are the most developed example in these posts. Lundquist traces their evolution from hardware-driven machines with simple remote functions to software-defined vehicles that need constant connectivity to operate and update. They argue that this shift creates specific problems manufacturers must plan for, not just general complexity.
- **Roaming rules and regulation decide what is technically possible**: Lundquist treats connectivity as more than a technical choice, repeatedly returning to market rules. Permanent roaming restrictions, inconsistent rules across Europe and cross-border transitions constrain how devices can be deployed. A tailored mix of connectivity technologies, rather than one network for every case, is the practical answer. That mix adds flexibility but also increases management complexity for the customer.
- **Europe can lead on connected cars, but only if it acts as one**: A separate commentary adds a policy angle. Lundquist argues that fragmented regulations, rising cybersecurity risk and inconsistent rules across Europe could slow the connected-car transition just when it needs to accelerate. Connectivity, security and regulation, they say, have to move together. Europe can lead if it coordinates.

## Work to read

- [SGP.32 and Roaming — The new Power Couple of global IoT](https://www.linkedin.com/posts/mats-lundquist-b0770b31_sgp32-and-roaming-the-new-power-couple-activity-7321083579587809281-CjEJ)
- [Automotive is leading the way – but there are challenges](https://www.linkedin.com/posts/mats-lundquist-b0770b31_automotive-is-leading-the-way-but-there-activity-7308785084344500225-2G9W)
- [IoT is growing up: My recap from MWC](https://www.linkedin.com/posts/mats-lundquist-b0770b31_iot-is-growing-up-my-recap-from-mwc-activity-7305518676055629824-CsEJ)
- [When I bought my first car, it was all about horsepower and freedom](https://www.linkedin.com/posts/mats-lundquist-b0770b31_when-i-bought-my-first-car-it-was-all-about-activity-7378397596316360704-ZJ5A)

## Brand relationships

- **Telenor IoT** (employment)

## Partnerships

Mats Lundquist's posts do not set out partnership or sponsorship formats: no rate card, media kit, stated deliverables or published inquiry process. Their content reads as company thought leadership rather than independent creator work: they announce Telenor IoT product and team launches (a dedicated automotive team, the SGP.32 eSIM standard, the Roaming Selection Tool), link to a Telenor IoT article and tag Telenor IoT colleagues. A brand should expect any collaboration to sit within those employer-side channels, not a personal creator offering. The posts do not mention past paid third-party brand integrations that could benchmark rates, scope or disclosure practice, or identify a route to buy placement in their feed. Before budgeting, confirm whether they accept independent partnerships and, if so, on whose behalf and through which commercial contact. Until then, treat them as a subject-matter voice closely tied to one connectivity provider.

## Alternatives

- Ricardo Camacho: A sponsored webinar and companion article on SGP.32, roaming and automotive connectivity strategy for a connectivity provider tilts toward Ricardo Camacho when the sponsor most wants to own the security argument inside software-defined vehicles, rather than the connectivity standard itself. Both posts cover millions of lines of code, hundreds of interconnected ECUs, over-the-air update mechanisms and telematics systems as attack surfaces; ISO/SAE 21434 as the framework for engineering security into product development; and a testing chain of static analysis, dynamic analysis and fuzz testing, and penetration testing, with AI-assisted verification alongside human oversight. For automotive security engineers, that sits closer to their daily work than a standards explainer. This is the stronger pick for a campaign on verifying security in a software-defined vehicle programme, with connectivity as context rather than topic.
- Hyunjeong Kim: This is the better choice when the campaign is about industry structure and manufacturer strategy rather than a standards-level explanation. The two posts cover that territory: a breakdown of BMW's Neue Klasse reset — regionalization of development and sourcing, AI used across engineering, procurement and decision-making, a shift from software-defined toward AI-defined vehicles, a changing supplier model, and roughly 8,000 positions planned to go by the end of 2027 — and a funding and market analysis of the Munich industrial-robotics company RobCo. That suits strategy, procurement and supply-chain decision-makers better than an engineer-facing standards session. A campaign on how OEM software and AI strategy reshapes supplier choices would land with them.
- Motti Sorani: This is the stronger alternative when the audience is security leadership and the question is commercial rather than engineering: why remediation at scale and measurable return matter, and how security tooling fits into developer workflows without slowing them down. One post argues that the industry over-prioritises detection and visibility when engineers need efficient ways to fix issues, comparing security to the telecom last-mile problem. The other is a first-person account, drawn from a conversation with a co-founder, of getting into offensive security by studying and then writing computer viruses. For an application-security or defensive-cyber audience, that founder voice and remediation-first argument carry more weight than a connectivity standards explainer.

---
AI-assisted summary of public posts. Audience demographics are not available. Engagement appears only where we checked recent posts. Method: https://b2binfluencer.marketing/methodology/