Telecommunications
Enterprise services
Connectivity products sold to businesses.
Four products, one pattern: the person who signs is technical, already knows the vocabulary, and asks an engine to settle a design question before any supplier is contacted. Connectivity and managed WAN are researched properly and are where enquiries come from. Roaming is negotiated bilaterally and VAS is sold partner to partner. We pitch each for what it is.
Where the answer is being lost
You are asked to quote a design that was settled in somebody else's answer.
A network manager with a new plant in Hosur types 'What is the difference between MPLS and SD-WAN for multi-site connectivity' and reads one paragraph. A week later the CIO above her asks 'Should we manage SD-WAN in house or outsource it'. By the time either speaks to an account manager, the topology is chosen, the managed split is decided and three vendors are already named. If none of them is you, the branch sites go live on links sized for the company you were when the last contract was signed.
How we win this
The programme for enterprise services
Write the decision page
The two questions that decide an enterprise deal are MPLS against SD-WAN and in-house against outsourced. Most operators answer both with a product brochure. We write the comparison properly: what each costs to run, where each breaks, when the cheaper option is correct. A network manager can act on that, and acting on it means calling you.
The provisioning date and the credit note
Every enterprise deal narrows to two awkward questions: when can you actually light this address, and what has your SLA credit paid out on the occasions you missed. Both answers already sit inside your provisioning and service-credit systems, and no operator puts either in public. We publish both as data-assets: dated, with the sample they were drawn from stated. That gives an engine a claim it can repeat and a procurement officer something they can verify. An adjective about reliability is neither.
Consent before the add-on
Value added services carry a reputation problem the whole industry earned. So the content there is explanatory and nothing else: how consent is captured, how a subscriber turns something off, what the regulator requires of both partners. That reads as competence to a product head choosing a VAS partner, and it does not start an argument with subscribers.
Roaming is not a funnel
Wholesale roaming is settled directly between two commercial teams, across a table, on terms neither side publishes. No page changes that, and we will not bill you as if it did. What content does there is narrower: the entity an engine describes when a new market entrant or a regulator's consultation asks who you are, and proof of how you are described.
The mix that carries it
Content
Answer and comparison pages
Cost, process, eligibility and comparison pages built for direct extraction, not for a reader who scrolls.
Content
GEO blogs and authority content
The definitive written answer to the questions your buyers put to an engine, structured so it can be lifted and attributed.
Foundation
Entity and schema engineering
Structured data and entity definition so engines know exactly what you are, where you operate, and what you are credible in.
Authority
Original data and benchmarks
Proprietary numbers, surveys and benchmarks — the most-cited asset class there is, because nobody else has them.
Content
Video and YouTube
Video run as a primary AI source, for the dense, entity-rich transcripts models read and quote.
Distribution
Practitioner and executive content where B2B buyers and the models watching them both look.
Measurement
AI Presence tracking
Standing measurement of inclusion, share of answer and competitor movement as models update.
The constraint we work inside
Two ceilings. Wholesale and enterprise pricing sits under contract confidentiality, so we publish the mechanism and the ranges you are free to state, never a rate card. And consent rules from the regulator govern how value added services are described and activated, so that copy stays explanatory rather than promotional.
Specialisations
4 total
The pitch is different for each one, because the buyer, the trigger and the rules on what may be published are different for each one. Open the one that is yours.
A roaming and interconnect head at a partner operator, preparing for a renegotiation after a season of one-way traffic, checks how the market prices what you are about to quote.
The question deciding this today
“How is wholesale roaming priced between operators”
- Who they sell to
- Subscribers using other operators' networks abroad
- Who signs
- Roaming and interconnect head
- What starts it
- Traffic imbalance, new agreement, regulatory change, travel season
- Cost of staying invisible
- Revenue leaking through agreements nobody re-examined
Ask an engine 'How is wholesale roaming priced between operators' and you get an explanation assembled from GSMA documentation, a clearing house primer and a consultancy explainer. No operator's own wholesale team is in that answer. It matters less for winning the deal, which is done face to face, than for what the person across the table arrives believing about IOT rates, discount tiers and settlement. Someone else set that expectation, and you negotiate against it.
What we would run
- 01Entity and schema engineering
An entity definition for your wholesale arm: the operating name, the networks and markets you actually carry traffic on, the agreements you are open to, tied to the group entity so an engine stops merging you with your retail brand.
When an engine names carriers for a market, it works from what it can resolve. A wholesale unit with no defined entity gets described as the consumer brand.
- 02GEO blogs and authority content
A written explanation of how wholesale roaming is actually priced: inter-operator tariffs, volume commitments, balanced-traffic discounts, how settlement runs through a clearing house, what a regulatory change to surcharges does to an existing agreement. Under a named person in your wholesale team.
Nobody signs from a blog here. But the counterpart, the consultant advising a new entrant and the analyst writing about the market all read the clearest explanation, and it is currently not yours.
- 03LinkedIn
Posts from your roaming and interconnect lead, written around the calendar the business actually runs on: pre-conference positions on steering and settlement, a plain reading of a regulatory change, what a traffic imbalance does to a renewal.
The market is small enough that the counterparties already know each other's names. LinkedIn is where they check what you now think, before a meeting is booked, and engines read it.
- 04AI Presence tracking
A standing check on how the major engines describe your wholesale entity: which markets they say you cover, which partners they associate you with, whether they still cite a divested unit or an old brand, with the corrections filed as they appear.
The risk in a bilateral market is not absence, it is being described wrongly to someone deciding whether you are worth a meeting. Monitoring is how you find out.
What we would not recommend
- Answer and comparison pages. Nobody compares roaming partners on a cost or eligibility page. The terms are confidential and the shortlist is two operators who already have a contract history.
- Reviews and testimonials. No operator publishes a testimonial about settlement terms with another operator. There is nothing genuine to structure, and asking would be read as odd.
- Instagram. Roaming charges are a consumer grievance. A brand feed on the subject collects bill complaints and reaches nobody in wholesale.
What a lead looks like
The realistic one is not a purchase request. It is a wholesale lead at a new entrant or an MVNO's adviser who read your pricing explanation, wants to know whether you would carry their traffic in two markets, and opens with terms rather than with what an IOT rate is. Occasionally a journalist or a regulator's consultation. Both are worth the meeting.
What we measure
- Correct wholesale entity in engine answers
- Cited on roaming pricing mechanics
- Named when a market is listed
- Old brands and divested units removed
What changes
Enquiries arrive later in their thinking and earlier in yours. A network manager opening a third site writes with a topology already sketched from your comparison page and asks what the last mile looks like at that address. A CIO asks for the co-managed split, not for an SD-WAN explanation. A product head at an operator asks how your consent flow works before asking about revenue share. Fewer first conversations spent teaching.
Start here
See who gets named in enterprise services today
We put your buyers' real questions to the live models and come back with the businesses they name, the sources behind those answers, and the gap between that list and yours.