# Tatiana Finkelsteyn

Tatiana Finkelsteyn writes about enterprise telecom and zLinq’s Telecom Lifecycle Orchestration approach, which brings technology, contracts, and billing into one view so IT leaders can make better-informed decisions.

- Profile: https://b2binfluencer.marketing/creators/tatiana-finkelsteyn/
- LinkedIn: https://www.linkedin.com/in/tatianafinkelsteyn
- Topics: leadership, email-marketing
- Based on 15 dated posts, latest 2026-10-09

## Summary

Tatiana Finkelsteyn is most useful for making enterprise telecom lifecycle and hidden contract risks concrete.

- Best for: A telecom expense management company planning a co-marketing webinar on telecom lifecycle orchestration.
- Not for: A direct-to-consumer brand running short-form Instagram Reels or TikTok sponsorship for 18 to 34 year olds.
- Check first: Confirm audience data, media kit, rate card, deliverables, exclusivity, disclosure, lead time and approvals.

### Takeaways

- Telco information is split across teams, so nobody sees the whole picture.
- Conference game exposed a $150,000 difference between one manager's estimate and actual monthly telecom spend.
- A bank faced a $250,000 contract penalty after a technically sound migration.

## Main ideas

- **Telco information is split across teams, so nobody sees the whole picture**: This is the argument underneath almost everything else they write. Engineering knows what is installed; accounts payable knows what is billed; procurement knows what has been contracted; provider portals hold another layer; and a spreadsheet somewhere tries to hold it all together. Everyone is doing their job, but no one continuously looks across all three functions. That turns ordinary questions into hard ones: what do we actually have, what are we paying for, which services are changing, and who owns the problem when something breaks? Finkelsteyn calls the result the Triangle of Inefficiency and treats visibility as the first step, not the finish line. The goal is to identify savings, adapt contracts as needs change, and flag problems before they become fire drills.
- **Choose the remedy that fits the problem, not the business model you happen to sell**: Finkelsteyn has watched enterprises tackle telecom through the same handful of models for nearly 20 years. They describe five by what each does well and where each stops. An aggregator simplifies billing to one invoice but adds provider migrations and a layer between the customer and the carrier. A consultant brings strategy but not implementation. An agent is valuable in procurement, one phase of the lifecycle. A TEM platform normalizes invoices, but software alone does not resolve billing disputes, manage carrier relationships, or run projects. An IT partner or MSP brings engineering depth but usually grew from a single-vendor alignment that shapes technology selection. The tension is deliberate: none of these models is wrong; each exists because it solves something. The argument is that none is holistic, so the right answer for a given customer may be fixing what exists, renegotiating a contract, or migrating.
- **Technology decisions carry hidden contract liabilities**: A technically sound change can still trigger a financial penalty because commitments attached to the technology live in contracts, invoices, spreadsheets, and provider records rather than next to the architecture diagram. Finkelsteyn's priority is pre-decision diligence: before making a change, an IT leader should be able to answer “what commitments does this touch?” — and do it in an afternoon, not after weeks of digging. The post notes that customers with good records across all of it are unusual.
- **One operating model across three layers: contracting, engineering, invoicing**: This is the specific product argument. Telecom Lifecycle Orchestration, abbreviated TLO, is described as one tool and one team working across three layers at once rather than another point solution. Contracting covers procurement, contracts, ROI tracking, and business alignment. Engineering covers performance, uptime, vendor landscape, and technology fit. Invoicing covers invoice verification, general ledger coding, and billing dispute resolution. The claim is that these are connected problems: assembling a complete telecom inventory requires someone who can link technical, contract, and financial data. The alternative is asking engineers to become telecom accountants.
- **Teach with games and peer conversation, not slideware**: Much of Finkelsteyn's telecom writing centers on live formats and analogies rather than product features. They aim to get IT leaders comparing notes about what is actually happening inside their organizations instead of talking theory, and to step away from day-to-day work long enough to learn from peers.

## Work to read

- [The conference game that measures telecom blindness](https://www.linkedin.com/posts/tatianafinkelsteyn_one-of-my-favorite-games-at-conferences-is-activity-7496204434465689600-1MlN)
- ["What you can see can't hurt you" — the four visibility questions](https://www.linkedin.com/posts/tatianafinkelsteyn_what-you-can-see-cant-hurt-you-but-when-activity-7500190736034750464-pgBR)
- [Twenty years of telecom business models, and the doctor's-office analogy](https://www.linkedin.com/posts/tatianafinkelsteyn_for-nearly-20-years-ive-watched-enterprises-activity-7495487233160839168-ORVu)
- [The $250,000 penalty behind a reasonable technology decision](https://www.linkedin.com/posts/tatianafinkelsteyn_request-a-demo-zlinq-activity-7506737553002377216-t6Ie)
- [The "Triangle of Inefficiency" and what lifecycle orchestration covers](https://www.linkedin.com/posts/tatianafinkelsteyn_who-has-the-complete-picture-of-your-telecom-activity-7499103563118358528-Wn7m)
- [Keynoting a CIO summit on being the "CEO of IT"](https://www.linkedin.com/posts/tatianafinkelsteyn_last-friday-i-had-the-opportunity-to-keynote-activity-7498394848622723083-7a8S)

## Brand relationships

- **zLinq** (owned_business)
- **AIM Utah CIO Summit** (mention)

## Partnerships

Tatiana Finkelsteyn's posts do not publish a sponsorship menu, media kit, rate card or partnership policy. The commercial activity they describe runs through zLinq, the enterprise telecom business: connectivity, unified communications and contact center work, and a service called Telecom Lifecycle Orchestration that combines contracting, engineering and invoicing. Several posts invite readers to contact them by direct message or follow a zLinq demo link; these are sales and audience-contact routes, not official partnership or media inquiry channels. The only third-party brand engagement visible in the posts is a keynote at the AIM Utah CIO Summit, where they spoke about CIOs as "CEOs of IT" and credited Ken Knapton and AIM Utah for organising the event. The posts disclose no fee, sponsorship, deliverables or commercial terms for the appearance. For a brand considering a co-marketing webinar, ask directly about deliverables, exclusivity, disclosure wording, production lead time, approval steps and pricing; none are published in the posts.

## Alternatives

- Alex Gonzalez: Choose Alex Gonzalez when the campaign's center of gravity moves from telecom spend visibility to AI voice in customer communications — for example, an MSP or telecom-provider partner whose webinar is about deploying AI call handling and measuring what calls actually accomplish. The two posts argue that a slightly robotic agent that completes tasks reliably beats a human-sounding one that fails, and that providers should report appointments booked, leads captured and requests resolved rather than calls answered. That supplies a concrete debate frame and an MSP/telecom-provider audience angle that Tatiana Finkelsteyn's enterprise-IT framing does not cover.
- Michael Taylor: Choose Michael Taylor when the campaign focuses on contract compliance — checking what was invoiced against the terms actually signed, and recovering the difference. One post lays out the core practices of strong contract compliance: a centralized, version-controlled repository; obligation tracking built into the process from signature; standard clause libraries; continuous performance monitoring against terms; a defensible audit trail; and a named owner per contract. The other walks through the PRGX approach: a neutral third party connects contract to invoice to payment, runs thematic reviews on one question at a time, and uses AI-assisted contract reading. The retailer case — 900+ supplier agreements, more than half of suppliers paid earlier than required, terms running 30+ days shorter than peer benchmarks, $22M in working capital unlocked and $2.8M+ in interest savings — offers the kind of specific numbers a co-marketing webinar on invoice verification needs.
- Jordan Zamir: Choose Jordan Zamir when the partner's product sits closer to billing and revenue recognition for software businesses than to telecom expense. One post dismantles the assumption that upgrading from QuickBooks to NetSuite, Campfire or Rillet solves ASC 606. It argues that ERPs are built around the general ledger and invoices and rarely hold the original deal context, so finance staff end up retyping contract data — for example, a $15,000 annual deal recognized at $1,250 a month, with bundled software and implementation split by standalone selling price. The other is a working webinar announcement: a live build in Claude with four connected data sources (a Google Sheet, an Excel file, a CRM and Turnstile) producing an automated morning briefing, with the starter prompt, a save-and-automate framework and template materials promised to registrants. For a vendor seeking a demonstrated webinar production model rather than a telecom narrative, this is closer.

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