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.
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.
Key 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.
Check first: Confirm audience data, media kit, rate card, deliverables, exclusivity, disclosure, lead time and approvals.
Main ideas
Telco information is split across teams, so nobody sees the whole picture · Choose the remedy that fits the problem, not the business model you happen to sell · Technology decisions carry hidden contract liabilities
Tatiana Finkelsteyn writes about enterprise telecom and zLinq’s Telecom Lifecycle Orchestration approach.
Their posts show how technology, contracts, and invoices can tell different parts of the same story—and how the gaps can lead to wasted spend or costly decisions.
Practical examples include a conference game that exposed a $150,000 difference between one manager’s estimate and the organization’s actual monthly telecom spend, and a bank’s $250,000 contract penalty after a technically sound migration.
One post also shows Finkelsteyn speaking to CIOs about leadership beyond telecom operations.
Finkelsteyn makes a fragmented enterprise problem concrete, tracing its consequences across teams.
Rather than treating telecom as only a billing or engineering issue, they connect what is installed, contracted, and paid for.
Memorable numbers, recognizable workplace situations, and direct questions—such as “What commitments does this touch?”—show why that connection matters before an organization changes providers or technology.
A useful exception to the mainly telecom-focused material is their CIO summit recap, which emphasizes peer learning and leadership rather than a product or operational problem.
Finkelsteyn's posts return to one diagnosis and one prescription.
Read more
The diagnosis: enterprise telecom spend, contracts, and engineering records are held by different teams, so even basic questions — what do we have, what are we paying for, who owns a problem — go unanswered.
The prescription is Telecom Lifecycle Orchestration: one team working across contracting, engineering, and invoicing rather than another dashboard.
A second thread is how to choose a remedy: aggregators, consultants, agents, TEM platforms, and MSPs each solve a real problem but have built-in limits.
The recommendation, Finkelsteyn argues, should follow the customer's need rather than the model's incentives.
A third thread is that technical decisions quietly carry contractual liabilities recorded elsewhere, and IT leaders should be able to answer “what commitments does this touch?” in an afternoon.
Telco information is split across teams, so nobody sees the whole picture
This is the argument underneath almost everything else they write.
Read more
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.
An infrastructure manager new to the role at a large engineering company confidently estimated the organization's telecom spend at about $20,000 a month.
When the records were pulled together, the real figure was closer to $170,000.
Tatiana Finkelsteyn's point is not that the manager was careless, but that the information was never in one place.
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.
Read more
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.
Finkelsteyn compares enterprise telecom to a doctor's office: you do not walk in assuming surgery is the answer, because some patients need physical therapy, some need medication, and some genuinely need surgery. The recommendation should follow the customer's situation, not the limits or incentives of a particular model.
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.
Read more
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.
A large bank moved its contact center to a new provider, which required moving its SIP trunks to Bandwidth.com.
The architecture was reasonable and would have passed a technical review.
Because contract information was not connected to the engineering decision, the bank incurred a $250,000 AT&T contract termination penalty that the CIO then had to explain to finance.
Finkelsteyn presents this as a customer story; buyers should ask for supporting documentation.
One operating model across three layers: contracting, engineering, invoicing
This is the specific product argument.
Read more
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.
In the visibility post, Finkelsteyn frames the three layers as the answer to one question — who has the complete picture of your telecom environment? They describe the work as taking gap-finding and opportunity-spotting off the customer's team, rather than handing them a dashboard.
Teach with games and peer conversation, not slideware
Much of Finkelsteyn's telecom writing centers on live formats and analogies rather than product features.
Read more
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.
A favorite conference exercise is “Guess Your Telecom Spend”: Finkelsteyn asks a few questions about an organization's connectivity, unified communications, and contact center environment, guesses the monthly spend, and pays $100 when wrong.
At the most recent conference, the guess was right about half the time.
The misses exposed organizations that had already optimized, were under-provisioned, were being overbilled, or simply did not know their own spend.
The CIO summit post follows the same instinct: roughly 40 CIOs and VPs of IT gave up a Friday afternoon for the session, and Finkelsteyn singles out the experience-sharing that followed.
They credit Ken Knapton, a CIO and AIM Utah board member, with organizing the event, and share the stage with Jennifer Anderson, who spoke about compassion and humanness in the age of AI.
These were guests' contributions, attributed by Finkelsteyn, not their own positions.
Start here for the clearest statement of the problem Tatiana Finkelsteyn writes about: most organizations cannot say what they spend on telecom, and the gap between belief and reality is large.
Read more
Tatiana Finkelsteyn describes a conference game called "Guess Your Telecom Spend," in which they ask a few questions about an organization's connectivity, unified communications, and contact center environment, then guess the monthly spend and hand over $100 if wrong.
At the most recent conference, they were right about half the time.
The misses had four causes: organizations that had already optimized and spent less than expected, organizations that were under-provisioned, organizations being significantly overbilled, and organizations that simply did not know their own spend.
The standout example is an infrastructure manager new to the role at a large engineering company who confidently put their telecom spend at about $20,000 a month; when the full picture was assembled, it was closer to $170,000.
Finkelsteyn attributes this to a split of responsibility — engineering manages the technology, accounts payable processes invoices, leadership owns the budget — with nobody continuously looking across all three.
For brands planning a campaign
The game is a ready-made live format.
A webinar or conference session could run the same guess-the-spend exercise with an audience, then use the reveal to introduce lifecycle orchestration as the fix.
It gives a co-marketing partner a participatory hook instead of a slide presentation.
This is the shortest entry point for a newcomer: it names the four basic questions enterprise telecom teams struggle to answer and explains why the struggle is structural.
Read more
Tatiana Finkelsteyn argues that seeing the full telecom picture is harder than it sounds because the information is split across groups.
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 together.
Everyone has a piece; nobody necessarily has the whole.
With that split, even basic questions become hard: what do we actually have, what are we paying for, which services are changing, and who owns the problem when something goes wrong.
The post frames visualization as the first step of Telecom Lifecycle Orchestration, bringing the engineering, contracting, and payment layers together so savings can be identified, contracts can adapt to business change, and problems get flagged before they become fire drills.
For brands planning a campaign
The four questions work as a diagnostic checklist for a landing page, webinar registration prompt, or discovery call. They let a telecom expense management partner qualify interest without pitching, because the reader answers the questions themselves.
This post explains why the company positions itself as a "fractional telecom department" rather than an aggregator, consultant, agent, or platform — a distinction a brand partner needs to understand before proposing anything.
Read more
After nearly 20 years of watching enterprises attack the telecom problem through different business models, Tatiana Finkelsteyn lays out five of them and what each leaves out.
An aggregator puts everything on 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 during procurement, but procurement is one phase of the lifecycle and the agent's focus follows what it sold.
A TEM platform normalizes invoices, but software alone does not resolve billing issues, manage carrier relationships, or execute projects.
An IT partner or MSP brings engineering depth, but most grew out of a single-vendor relationship, so technology selection follows that alignment.
The post compares the situation to healthcare: you do not walk into a doctor's office assuming surgery, because some patients need physical therapy, some need medication, and some do need surgery.
The recommendation should follow the customer's needs rather than the incentives of a particular business model.
For brands planning a campaign
The five-model breakdown gives a partner a comparison table it does not have to build. It also supports a joint webinar angle on "when a TEM platform is not enough," aimed at buyers already using a point solution.
A concrete failure story is the fastest way to show how the missing connection between technical and contractual information costs real money.
Read more
A large bank incurred a $250,000 contract termination penalty from AT&T after moving its contact center to another provider, which required moving its SIP trunks.
Technically, the move made sense and would have passed a technical review.
The problem was that the information needed to understand the financial impact lived in different places: engineering data in spreadsheets, payment information on invoices, contract terms in separate contracts, and basic service details in provider records or with account managers.
Tatiana Finkelsteyn notes that it is unusual to find a customer with good records across all of it, which is how a reasonable migration creates a liability the CIO has to explain to finance.
The suggested question for IT leaders before any change is "What commitments does this touch?" — and answering it should take an afternoon, not weeks of digging.
For brands planning a campaign
Penalty and liability stories like this one convert well in co-marketing because the cost is specific and the failure is recognizable. A webinar could pair the story with a checklist of contract and commitment questions to ask before a migration.
A reader who wants the vocabulary Tatiana Finkelsteyn keeps returning to should see it stated in full.
The post asks who holds the complete picture of a telecom environment.
Engineers focus on technology but may not see costs or contracts; IT leadership selects technology and negotiates pricing but may not have time to benchmark, audit, or verify what is billed; accounts payable pays invoices but may not know whether the organization is paying for the right things at the right price.
Tatiana Finkelsteyn calls this the Triangle of Inefficiency and argues the answer is not another point solution but one tool and one team working across three layers at once: contracting (procurement, contracts, ROI tracking, business alignment), engineering (performance, uptime, vendor landscape, technology fit), and invoicing (invoice verification, general ledger coding, billing dispute resolution).
Assembling a complete telecom inventory takes someone who can connect technical, contract, and financial data.
For brands planning a campaign
The three-layer structure is a natural agenda for a joint session: one segment per layer, each with a partner-side expert. It also gives the partner a way to show where its own product sits rather than claiming the whole model.
Most of the other posts are about the telecom problem.
Read more
This one shows Tatiana Finkelsteyn in front of an IT leadership audience — the setting a co-marketing partner would be buying.
Tatiana Finkelsteyn keynoted the Association for Information Management (AIM) Utah CIO Summit on what it means for CIOs today to be the "CEOs of IT" — leading themselves, their team, and the organization.
The post notes that roughly 40 CIOs and VPs of IT gave up a Friday at 1:00 PM for the session, credits Ken Knapton with organizing the event, including an after-hours gathering for families, and mentions sharing the stage with Jennifer Anderson, who spoke about compassion and humanness in the age of AI.
The closing reflection is about stepping away from day-to-day work to learn from peers.
For brands planning a campaign
This is evidence of an existing speaking track with IT leadership audiences, and it suggests formats beyond product-led content: leadership and team topics that can carry a sponsor without making the session a pitch. The title "CEOs of IT" is a usable session name.
Telecom Lifecycle Orchestration as an operating model4
Enterprise telecom visibility and the Triangle of Inefficiency3
Diagnostic teaching formats: conference games and healthcare analogies2
Contract risk hidden inside technology decisions1
Vendor model critique and the fractional telecom department1
CIO leadership and peer learning beyond telecom products1
Enterprise telecom visibility and the Triangle of Inefficiency
Finkelsteyn argues that enterprise telecom information is split across engineering, accounts payable, procurement, provider portals, and spreadsheets, leaving no single group with the whole picture.
Read more
In one post, an infrastructure manager estimated monthly telecom spend at about $20,000; after the records were pulled together, the real number was closer to $170,000. Finkelsteyn calls this the Triangle of Inefficiency: costs, contracts, and engineering decisions live in different places, weakening spend management and provider accountability.
A first-person conference anecdote, a surprising before-and-after number, and a simple triangle diagram in prose make an abstract visibility problem concrete.
The argument targets enterprise IT roles, not a specific vendor product; the product connection comes after the diagnosis.
For brands planning a campaign
A webinar can open with a diagnostic question: Can the audience say what they have, what they pay for, and who owns the problem? The post offers a concrete cost-visibility story and a clear framework for a co-marketing session on telecom audits and baseline data.
Telecom Lifecycle Orchestration as an operating model
Finkelsteyn describes Telecom Lifecycle Orchestration, or TLO, as one team and one tool working across contracting, engineering, and invoicing.
Read more
Contracting covers procurement, contracts, ROI tracking, and business alignment; engineering covers performance, uptime, vendor landscape, and technology fit; invoicing covers invoice verification, GL coding, and billing dispute resolution. The goal is not another dashboard or point solution, but a way to make telecom information visible, actionable, and in sync.
Defines a proprietary operating model by listing its three layers and contrasting it with fragmented tools, spreadsheets, and point solutions.
For brands planning a campaign
This is the strongest co-marketing spine for a webinar: it offers a three-part agenda that a telecom expense management company can demonstrate against—contracts, engineering, and invoices. The section can also support a follow-up asset explaining what each layer includes.
Finkelsteyn recounts how a large bank incurred a $250,000 AT&T contract termination penalty after moving its contact center to a provider that required moving SIP trunks to Bandwidth.com.
Read more
The technical rationale was sound, but the financial commitments were scattered across contracts, invoices, spreadsheets, and provider records. The takeaway for IT leaders before making a change: What commitments does this touch?
A named penalty amount, a plausible technical decision, and a short checklist question turn a complex contract-risk problem into a story with a practical takeaway.
Finkelsteyn reports the bank, provider, and specific penalty as part of a customer example. Ask for documentation of the event before presenting it as independently verified.
For brands planning a campaign
A webinar or written piece can use this case to discuss migration risk, contract exposure, and the link between architecture decisions and financial liability. It offers a specific, high-stakes example that a telecom expense management audience will recognize.
Vendor model critique and the fractional telecom department
Finkelsteyn compares five common ways enterprises address telecom: aggregators, consultants, agents, TEM platforms, and IT partners or MSPs.
Read more
Each solves a real problem but has limits: aggregators add a layer and provider migrations; consultants may not implement; agents focus on procurement; TEM software does not manage carrier relationships or projects; and MSPs often grew from a single-vendor partnership. Finkelsteyn positions zLinq as a fractional telecom department that works across engineering, contracting, and invoicing without forcing one model onto every problem.
Builds a balanced critique by naming each model’s value and structural limitation before offering a sixth option.
The post says there is nothing wrong with the other business models and that each exists to solve a real problem; the contrast is about holistic coverage, not fault.
For brands planning a campaign
This suits a comparison-style webinar or article that helps buyers understand how a lifecycle orchestration approach differs from an aggregator, consultant, agent, TEM tool, or MSP. It gives the partner a clear competitive frame without suggesting that other models are simply wrong.
Diagnostic teaching formats: conference games and healthcare analogies
Finkelsteyn uses interactive, analogy-driven formats to teach telecom management.
Read more
One favorite conference game, Guess Your Telecom Spend, asks a few questions about connectivity, unified communications, and contact center environments, then guesses monthly spend and pays $100 if wrong.
The misses reveal organizations that optimized early, under-provisioned, were overbilled, or did not know their spend.
Finkelsteyn also compares enterprise telecom to healthcare: the best doctors first understand the patient, and the right telecom answer might be fixing what exists, renegotiating a contract, or migrating.
Turns sales education into a game, then generalizes the approach through a familiar healthcare analogy and simple questions.
The guessing game is a conference activity, not a formal audit method; treat it as an engagement device rather than a measurement tool.
For brands planning a campaign
These formats translate directly into webinar interactivity: a live spend-guessing segment, a short diagnostic, or a triage framework for matching telecom remedies to buyer needs. They also show how to teach a technical topic without leading with product features.
CIO leadership and peer learning beyond telecom products
Finkelsteyn keynoted the Association for Information Management Utah CIO Summit on what it means for CIOs to be the CEOs of IT, covering leading yourself, your team, and your organization.
Read more
The post highlights roughly 40 CIOs and VPs of IT spending a Friday afternoon learning from peers, and they praise the experience-sharing that followed the formal session.
A personal speaking appearance, audience detail, and reflective takeaway signal credibility with senior IT leaders.
The post shows leadership speaking range but does not mention zLinq, TLO, or telecom cost management; ask for telecom-specific examples before treating it as evidence of expertise in those areas.
For brands planning a campaign
This shows a speaking lane beyond vendor-specific telecom content. A co-marketing webinar could pair telecom lifecycle orchestration with CIO leadership themes or use a peer-learning format instead of a product demonstration.
Tatiana Finkelsteyn's posts are written from inside zLinq, the telecom company whose Telecom Lifecycle Orchestration service they describe and promote.
Read more
In their own words the work shaped how "we built zLinq," and they write about what "our team" takes off IT leaders' plates, so the business relationship is stated by Tatiana rather than inferred.
The only other organization named as a relationship in the posts is AIM Utah, whose CIO Summit they keynoted.
Within these six posts no sponsorship, affiliate, or paid-partnership relationship is disclosed; companies such as AT&T and Bandwidth.com appear only as carriers inside client stories.
zLinq
Owned business
Tatiana writes as part of zLinq.
Read more
They say observing the enterprise "Telecom Problem" over nearly 20 years "shaped how we built zLinq," and describe a solution that "feels less like a vendor and more like a fractional telecom department."
The other posts keep selling the same company: they explain the "Triangle of Inefficiency" between engineering, contracting, and invoicing, link to zlinq.com, and describe Telecom Lifecycle Orchestration as what "we built," with "our team" identifying gaps for IT leaders.
The posts read as a co-founder or company-side voice rather than an outside commentator.
Tatiana keynoted the Association for Information Management (AIM) Utah CIO Summit, speaking about CIOs as the "CEOs of IT" and leading themselves, their teams, and their organizations.
Read more
The post says roughly 40 CIOs and VPs of IT attended and thanks AIM Utah board member Ken Knapton for organizing it. The post does not say whether the keynote was paid; ask about compensation if that matters.
Follow one question across Tatiana Finkelsteyn’s posts: who has the complete picture of enterprise telecom?
Read more
Start with the conference spend-guessing post on cost visibility, then read the posts naming the Triangle of Inefficiency and listing the four basic questions.
The twenty-year comparison of telecom business models argues that aggregators, consultants, agents, TEM platforms, and MSPs each solve one part of the problem.
Posts on Telecom Lifecycle Orchestration explain the proposed alternative across contracting, engineering, and invoicing; the bank contract-penalty story shows why the gap matters.
For adjacent reading, see the similar creators below on Voice AI reliability, contract compliance, and revenue recognition.
Both write for telecom and managed-service audiences, emphasizing operational reliability over demo appeal.
Read more
Alex Gonzalez argues that Voice AI should be judged by completed tasks, correct transfers, and consistent production behavior; Tatiana Finkelsteyn argues that telecom decisions should be judged by visibility across engineering, contracts, and invoices.
Alex Gonzalez focuses on voice AI for MSPs, call outcomes, and the communications experience. Tatiana Finkelsteyn covers enterprise telecom lifecycle orchestration across contracts, engineering, and invoicing.
Both connect contracts to invoices and obligations, and link gaps in visibility to avoidable financial and compliance problems.
Read more
Michael Taylor lays out practices for contract repositories, obligation tracking, and audit trails; Tatiana Finkelsteyn applies the same visibility logic to enterprise telecom contracts, engineering decisions, and billing.
Michael Taylor focuses on contract compliance and invoice auditing for finance and healthcare supplier agreements, including AI-assisted contract review. Tatiana Finkelsteyn covers telecom lifecycle orchestration across engineering, contracting, and invoicing.
Both argue that contract data should be a usable source of truth connected to billing and financial workflows.
Read more
Jordan Zamir critiques ERP revenue-recognition gaps and manual retyping of contract data; Tatiana Finkelsteyn critiques telecom visibility gaps and the need to dig manually through invoices, spreadsheets, contracts, and provider records.
Jordan Zamir focuses on revenue recognition, ASC 606, and finance automation for growing companies. Tatiana Finkelsteyn covers enterprise telecom contracts, invoices, and engineering decisions.
Tatiana Finkelsteyn’s posts address enterprise telecom costs, contracts, billing, and the consequences of decisions made without a joined-up view, making them relevant to a co-marketing webinar for telecom expense management buyers.
Read more
Before committing, request current LinkedIn audience data and documentation of professional roles, such as audience survey results. YouTube demographic data would not verify employer, occupation, or seniority.
Tatiana Finkelsteyn's posts do not publish a sponsorship menu, media kit, rate card or partnership policy.
Read more
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.
A telecom expense management company planning a co-marketing webinar on telecom lifecycle orchestration is a strong fit for Tatiana Finkelsteyn.
Read more
The posts focus on this exact problem: telecom information split across engineering, procurement, accounts payable and provider portals; the three layers of Telecom Lifecycle Orchestration (contracting, engineering, invoicing); and the cost of decisions made without a joined-up view.
They also offer ready-made session formats.
The “Guess Your Telecom Spend” conference game can become a live audience poll, and the 20,000 versus 170,000 monthly spend example gives the reveal its punch.
The $250,000 contract termination penalty story offers a high-stakes hook for a segment on migration and contract risk.
Their speaking track is another signal: a keynote to a CIO summit on “CEOs of IT” shows experience with senior IT leaders—the audience a telecom expense management vendor would want in the room—and provides a usable joint webinar title.
Before committing, ask for current LinkedIn audience data, a media kit or rate card, and details on deliverables, exclusivity, disclosure wording, production lead time and approval steps.
The posts describe direct messages and a zLinq demo link as contact routes, but not a partnership inquiry process.
When to choose a specialist
For a direct-to-consumer brand, such as a nutrition or apparel company, running a short-form Instagram Reels or TikTok sponsorship aimed at 18 to 34 year olds, the posts point to a poor fit.
Read more
They consist of LinkedIn text content for enterprise IT, telecom, procurement and finance professionals, with no consumer-facing work or video and visual formats.
The only third-party appearance described is a keynote at an AIM Utah CIO summit, with no disclosed commercial terms and an audience of CIOs and VPs of IT rather than consumers.
That combination makes a short-form consumer campaign costly to test: the format is unproven, audience fit is unsupported by data, and the posts offer no indication that Finkelsteyn’s explanatory, text-led style transfers to fast consumer video.
An HR tech vendor targeting HR leaders would be a better second campaign than a consumer one: the CIO summit and leadership keynote offer some audience overlap.
Before committing to a consumer campaign, ask for current audience data and examples of short-form sponsored work.
A worked campaign example
Worked campaign angle for the telecom lifecycle orchestration webinar: a joint webinar on telecom lifecycle orchestration.
Working title: “Guess Your Telecom Spend: four questions your organization probably cannot answer.” Format: a 45 to 60 minute joint session.
Opening, about 10 minutes: run a live version of Finkelsteyn’s conference game.
Collect three environment questions (connectivity, unified communications, contact center) in a pre-event survey, guess the registrants’ monthly spend on camera, and reveal the spread of real answers.
The large engineering company that estimated $20,000 and turned out to be closer to $170,000 carries the segment.
Middle, about 20 minutes: use the Triangle of Inefficiency as the spine, with one segment each on contracting, engineering and invoicing, matching their three-layer definition of Telecom Lifecycle Orchestration.
The partner should show where its own TEM product sits inside the invoicing layer rather than claim the whole model.
Then compare the five business models (aggregator, consultant, agent, TEM platform, MSP) and what each leaves out.
This gives the partner a comparison table and a natural place to explain its position honestly.
Case segment, about 10 minutes: use the $250,000 AT&T termination penalty story to introduce the question “What commitments does this touch?” and a short pre-migration checklist. Pair the story with a downloadable checklist so the session produces an asset, not just a recording.
Close, about 10 minutes: use the four visibility questions from “What you can see can't hurt you” as a self-assessment for the audience to complete before leaving, then direct attendees to the partner’s audit offer.
Angle and assets: position the webinar as the diagnostic step before any remediation purchase. The two joint assets are the four-question self-assessment and the migration commitment checklist.
Before agreeing, ask for current audience data (employer, seniority, geography) for the LinkedIn following; confirm whether a paid co-marketing format exists and agree on deliverables, exclusivity, disclosure wording, lead time, approval steps and pricing; and confirm that the title, agenda and the 20,000 versus 170,000 and $250,000 examples can be used in joint promotion.
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.
Read more
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.
The tradeoff: none of the material addresses the telecom lifecycle itself, or spend, contracts and invoices.
It does not cover the Triangle of Inefficiency, the five telecom business models, or contract risk such as the $250,000 termination penalty.
A telecom expense management partner would have to carry that part of the session alone.
The posts are written for MSPs and telecom providers deciding what to deploy for their customers, not enterprise IT leaders deciding what to do about their own telecom estate, so the buyer role in the room shifts.
Choose Michael Taylor when the campaign focuses on contract compliance — checking what was invoiced against the terms actually signed, and recovering the difference.
Read more
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.
The tradeoff: the recurring problem is supplier agreements in finance and healthcare supply chain, not telecom.
The named capability is a contract-insight service, and the audience is CFOs and hospital supply chain leads rather than CIOs and IT leaders.
Ask whether the session can include telecom-specific examples; otherwise, a telecom expense management partner would need to bring its own telecom context, and the contract-compliance frame would not provide those examples.
Choose Jordan Zamir when the partner's product sits closer to billing and revenue recognition for software businesses than to telecom expense.
Read more
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.
The tradeoff: the subject is revenue recognition and finance operations at growing software companies, not telecom lifecycle orchestration.
The two posts do not cover telecom contracts, carrier relationships, invoice verification against telecom terms, or the CIO and IT-leader audience a campaign aimed at telecom buyers targets.
Ask whether the creator can bring telecom-specific examples and CIO or IT leaders into the session; otherwise, a telecom expense management vendor would be recasting the topic rather than joining one this creator already owns.
This page draws on six LinkedIn posts published by Tatiana Finkelsteyn on the account listed for them, read as full text rather than as titles or excerpts, and on two posts each by three adjacent creators used for the comparison list.
The account was observed on 8 October 2026; the individual posts have no publication dates, so they represent a bounded sample rather than a lifetime archive.
Tatiana Finkelsteyn's posts are the source for statements about their work, business relationship with zLinq, and speaking appearances.
Questions that remain open include whether a book, show, or earlier body of work is part of their public identity; whether any sponsorship, paid-speaking, or paid-partnership arrangement exists; the composition of their audience; and any transcript of the CIO summit keynote, which is described in one post but is not available here.
Claims that depend on those gaps are marked as such on the page rather than filled in.
