Mats Lundquist

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.

In a recap of the MWC trade show, Lundquist challenges the easy summary that the event was mostly about AI, cybersecurity and 5G. They point instead to SGP.32 and standardisation, a shift toward a tailored mix of connectivity technologies, and deeper industry collaboration as signs that the sector has matured.

The MWC recap says SGP.32 is expected to become commercially available in the fall; a later post announces the standard’s launch, turning the prediction into a product launch.

Read original

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.

The scale framing is simple: whether a company runs 50 devices or 50,000, the same remote-management argument applies, and the customer can be anywhere in the world.

The post explaining SGP.32 also announces its launch and pairs it with an existing roaming-selection tool, bringing education and a commercial offer together.

Read original · Original 2

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.

In the automotive post, Lundquist advises manufacturers to refocus on their core product and work with connectivity specialists: no company can handle every challenge alone while excelling at its main work. They openly flag the commercial bias in that recommendation rather than presenting it as neutral.

Read original · Original 2 · Original 3

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.

The post lists three problems in sequence: connectivity orchestration, including frequency bands, future-proofing, sourcing and cross-border compliance; eSIM adoption, where markets that restrict permanent roaming force flexible manufacturing; and cybersecurity, where the attack surface extends beyond the vehicle to its whole ecosystem, and over-the-air updates make security a question of market value.

Read original · Original 2

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.

The automotive post notes that some large markets do not permit permanent roaming. It says eSIM technology enables flexible manufacturing by letting cars connect to preferred operators globally while complying with local rules.

Read original · Original 2 · Original 3

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.

The post opens with a personal comparison, contrasting a first car bought for horsepower and freedom with cars today as extensions of digital life, then frames resilience as a possible European advantage. The main argument is in a linked article; ask for it to assess the full case.

Read original

This post is the clearest starting point: it answers the question in plain language before getting into company positioning.

Lundquist explains SGP.32 as an eSIM standard from the industry body GSMA that lets businesses manage connected devices remotely and at scale without physically swapping SIM cards.

• They picture a product with an eSIM built in at the factory, managed remotely for different markets later, with the option to switch IoT providers without changing the card.
• They make the scale concrete — whether a company runs 50 devices or 50,000, the argument is the same — and stress that the bigger benefit is flexibility over a long product life, rather than day-to-day convenience.
• The post then moves to their own position, describing an early industry launch of SGP.32 and pairing it with an existing roaming-selection tool so customers can choose between networks in most countries.
• A link at the end points to further material.

For brands planning a campaign

The strongest single piece to build around for a webinar or authored article aimed at an IoT connectivity provider.

• It shows Lundquist taking a technical standard, explaining the customer benefit and placing a specific commercial offer — SGP.32 plus roaming — on top.
• The structure is reusable: teach the standard, then show what a prepared provider looks like.

This post turns a broad topic into three named problems.

Lundquist frames the automotive industry as mature but recently transformed, tracing cars from hardware machines with simple remote functions to software-defined vehicles that need constant connectivity to operate and update.

• They list three challenges: connectivity orchestration, or the difficulty of managing connectivity across markets with different frequency bands and regulations; eSIM adoption, where markets that restrict permanent roaming make flexible manufacturing harder; and cybersecurity, where the attack surface extends beyond the vehicle to its whole ecosystem, and over-the-air updates make security a value question.
• The recommendation is consistent: manufacturers should focus on their core product and work with specialists.
• Lundquist openly flags their own commercial bias in arguing that the choice of connectivity provider matters.
• Three colleagues are tagged at the end.

For brands planning a campaign

Useful for a campaign aimed at automotive or mobility buyers.

• The three-part structure maps directly onto webinar segments or an article outline.
• The explicit admission of bias is a reminder to provide independent support elsewhere in campaign materials.

This recap offers the long view of someone who has worked in the space for nearly two decades.

Writing after an industry trade show, Lundquist skips the easy summary — AI, cybersecurity, 5G and robots — and argues that IoT has moved out of its development phase.

• They draw on their own timeline: seventeen years in the space, starting when players, roles and technologies were unsettled and many solutions were proprietary.
• Three observations follow: SGP.32 and the push for standardisation; a shift toward a tailored mix of connectivity technologies rather than one solution, adding flexibility but also complexity for customers; and partnerships and specialisation as ways to manage that growing complexity.
• They conclude that the real differentiator will be how businesses adopt these shifts, not the technology itself.

For brands planning a campaign

Best used as background or an opening frame for a thought-leadership piece about industry maturity: standardisation and partnering, not technology alone, decide outcomes. It offers fewer specific instructions than the SGP.32 or automotive posts, so use it as context rather than the centre of a campaign.

This short post signals a policy angle; ask for the longer article before developing it into a campaign.

Lundquist opens with a personal comparison — their first car was about horsepower and freedom, while cars today are extensions of digital life — then lists the pressures: fragmented regulations, rising cybersecurity risk and inconsistent rules across Europe. Their argument is that Europe could lead in connected cars, but only if it acts as one, with connectivity, security and regulation moving together.

For brands planning a campaign

The post offers a policy and European-market angle for an event or article aimed at regulators and industry bodies. Ask for the full article before building a campaign around its argument.

In a conference recap, they point to double-digit adoption, higher awareness and technologies built specifically for IoT, then identify SGP.32, tailored connectivity mixes and deeper partnerships as signs of a more mature industry.

Frames a conference recap around one argument about the industry's stage, supported by observations in bullet points.

For brands planning a campaign

Useful for a connectivity provider seeking thought leadership on market maturity, not just product features. The same arc can open a webinar or article before turning to SGP.32 and roaming specifics.

Examples: Source 1

They stress that factory-built eSIMs can be managed by market and switched between IoT providers, and link SGP.32 with roaming as a future-proofing combination.

Uses plain-language explanations, short question-and-answer framing and scale examples such as 50 or 50,000 devices.

The post also promotes Telenor IoT's roaming selection tool, combining a standardisation explanation with a provider offer.

For brands planning a campaign

Directly supports an authored article or webinar on SGP.32, roaming and automotive connectivity. A B2B provider can have Mats Lundquist explain the standard's operational benefit, while the brand supplies neutral market context or customer examples.

Examples: Source 1 · Source 2

They describe permanent roaming restrictions and cross-border transitions as practical constraints, and argue that customers increasingly need a tailored mix of connectivity technologies rather than one network or technology for every use case.

Connects technical standards to customer operations through automotive and general IoT examples.

For brands planning a campaign

A provider can evaluate Mats Lundquist for content that turns regulatory and roaming complexity into clear buyer guidance. Pair the standardisation explanation with the brand's network or compliance expertise.

Examples: Source 1 · Source 2 · Source 3

They list connectivity orchestration, eSIM adoption and cybersecurity as the main automotive challenges, and argue that manufacturers should focus on core products while partnering with connectivity specialists.

Uses a numbered challenge list, pairing each challenge with a practical consequence, such as cross-border transitions or cyberattack risk.

The post also announces a dedicated automotive team, mixing analysis with a company announcement.

For brands planning a campaign

Strong fit for a connected-vehicle thought-leadership brief. Mats Lundquist can anchor a session on why automotive is leading IoT adoption and where manufacturers need partner help, with cybersecurity and eSIM as follow-on modules.

Examples: Source 1 · Source 2

They say connectivity, security and regulation must go together, and that Europe can lead if it acts as one.

For brands planning a campaign

Useful for a policy-adjacent campaign or executive article aimed at European automotive and connectivity audiences. The brand can develop the regulatory-resilience angle with Mats Lundquist rather than ask for generic market optimism.

Examples: Source 1

Mats Lundquist argues that businesses should focus on core operations and use specialised partners, describing real-world partnership examples as a shortcut to faster innovation.

For brands planning a campaign

For a B2B IoT provider, this gives Mats Lundquist a natural co-innovation narrative for webinars or authored pieces. The brand can position its managed-connectivity role as the specialisation that lets customers stay focused.

Examples: Source 1 · Source 2

In the same post, they present the launch of the SGP.32 eSIM standard as something "we" are doing as one of the first in the industry, and argue that SGP.32 combined with Telenor IoT Roaming is a game changer for global IoT. Ask for their job title and start date if those details matter.

View example

They use LinkedIn posts to turn technical changes into practical engineering or business arguments.

Camacho stays closer to engineering practice: ISO/SAE 21434, static analysis, secure coding, embedded security testing and how teams verify software. Lundquist works one level up, on connectivity market structure, eSIM standards, roaming rules and why manufacturers should partner rather than build everything themselves.

Read original · Original 2

Kim concentrates on a single automaker's strategy and investment news, such as BMW's Neue Klasse reset and Munich robotics funding, with AI adoption as the through-line. Lundquist stays focused on connectivity: eSIM, roaming, cross-border rules and the IoT industry's move to standardisation.

Read original · Original 2

Sorani is a cybersecurity practitioner writing about offensive security, the origins of his own interest in it, and why remediation, not detection, is the hard part. Lundquist writes about connected devices and IoT connectivity, not security practice.

Read original · Original 2

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.

The connectivity provider would have to supply the session topic.

• Mats Lundquist's posts do not cover eSIM standards, SGP.32, roaming restrictions, connectivity orchestration or cross-border network management.
• They do offer a plain-language explanation of what SGP.32 changes: factory-built eSIMs, remote per-market management and switching providers without swapping the card.
• A session built around the sponsor’s topic would gain automotive security depth but lose that ready-made bridge to a connectivity product; the sponsor would have to write it.

Examples: Source 1 · Source 2

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.

The offer is analyst commentary on published corporate strategy and funding news, not practitioner explanation of connectivity technology.

• Neither post touches eSIM, SGP.32, roaming or in-vehicle connectivity operations, so the sponsor would supply all the technical substance; the alternative supplies the frame and market read.
• The posts are summaries and analysis at post length.
• Ask for evidence of long-form or live presentation experience before choosing a webinar format.

Examples: Source 1 · Source 2

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.

Lundquist's posts do not cover automotive, connectivity, eSIM or roaming, so the sponsor would have to supply the vehicle framing; the standards teaching they do in public is absent.

• This also targets a general security audience rather than people making vehicle connectivity decisions, putting the same budget in front of a different room.
• Choose it for a remediation-and-ROI conversation with security teams; choose Lundquist for connected-vehicle and eSIM decisions.

Examples: Source 1 · Source 2