Florin Tatulea writes about go-to-market (GTM) strategy, account-based marketing (ABM), and the account data teams need to make sales and marketing work more accurately. Tatulea's posts explain how to map buying committees, keep account records current, and connect account lists, buyers, conversion signals, and account context.
Most useful for practical ABM and account data frameworks for sales and marketing teams.
Best for
A revenue operations data platform wanting sponsored thought leadership and a co-branded playbook.
Not for
A sales coaching vendor wanting short video clips and SDR reach proof.
Key takeaways
An ABM play has four layers: target accounts, buyers, conversion signals, account context.
Fragmented CRM records can show Google and Waymo as separate accounts.
A renewal plan maps the buying committee, then identifies missing stakeholders.
Check first: Ask for audience demographics and any documented sponsorship formats, deliverables, or pricing.
Main ideas
AI agents inherit the quality of the account data underneath them · An ABM play rests on four layers—and fails when they stay apart · Stale CRM hierarchies and job changes leave AI acting on fragments
Florin Tatulea writes about go-to-market (GTM) strategy and account-based marketing (ABM), helping sales and marketing teams build a more accurate, connected picture of target accounts and buyers. Their posts explain how fragmented or outdated account data can undermine human decisions and AI workflows, and offer practical ways to improve account planning and renewal preparation.
Tatulea turns data problems into clear frameworks and steps.
In a four-layer ABM framework, the layers are target accounts, buyers, conversion signals, and account context; the point is to connect them before orchestrating a campaign.
A post about CRM account records shows the cost of fragmented information, with examples such as Google and Waymo appearing as separate accounts.
In a renewal-planning walkthrough, they start with a near-term renewal and recommend mapping the buying committee, then identifying missing stakeholders.
These examples are useful to readers building ABM programs, improving revenue operations, or evaluating AI for sales.
Florin Tatulea's posts make one argument: go-to-market AI doesn't fail because teams lack tools; it fails because the account data underneath is stale, split across systems, and never resolved into a current view.
Read more
The priorities follow: build the account list, buyers, conversion signals, and account context, and keep them in one place; fix account hierarchies and job changes before automating on top; and teach the work through a repeatable scenario, such as a renewal or an ABM build, rather than theory.
Tatulea states the tension directly: AI amplifies bad data, yet the examples they demonstrate still use AI.
Verification comes first; orchestration comes second.
AI agents inherit the quality of the account data underneath them
The same claim appears in all three posts, each in a different setting.
Read more
Tatulea argues that GTM teams don't need more AI tools; agents working from fragmented account records aren't working from reality.
In the ABM post, the mechanism is precise: an agent chains steps, so a wrong field at step one becomes the assumption every later step builds on, faster and at greater volume than a person can catch.
The CRM post makes the same point about systems holding puzzle pieces without a current view of the whole.
In the renewal post, it appears in contact titles that reflect what someone last typed into the CRM.
Tatulea quotes Henry Schuck: “reasoning without verified data is fluent guesswork.”
The posts recommend agent tooling while warning about its risks.
Tatulea's argument is that AI is risky when data is unresolved and useful once it's verified; the order matters.
The ABM post spells out the failure: a wrong field at step one in an agent's chain becomes the assumption every later step inherits, at a speed and volume no human can catch.
An ABM play rests on four layers—and fails when they stay apart
Tatulea says every ABM play “we've run scaling to $1.2bn+” depends on four layers: a named list of target accounts, the named buyers at each one, signals proven to predict conversion, and the context already held about each account.
Read more
The problem isn't that teams miss a layer; it's that each lives somewhere different—in the CRM, marketing automation platform, intent tool, call recordings, or someone's spreadsheet.
Revenue operations and GTM engineers stitch them together, the data goes stale, a new tool arrives, and the stitching starts again.
Tatulea's remedy follows an explicit order: build the four layers, bring them into one place, then orchestrate.
Four layers live in four different systems, forcing RevOps and GTM engineers to rebuild the same joins whenever a tool changes.
Stale CRM hierarchies and job changes leave AI acting on fragments
Tatulea opens by asking readers to check their own CRM, then predicts three specific failures: Google and Waymo held as separate accounts with no link to Alphabet; a SpaceX acquisition of Cursor that never changes the account hierarchy; and Travis Kalanick still listed at Uber in a marketing system, though they now run CloudKitchens.
Read more
The problem isn't general messiness.
Each system holds part of the picture, but none provides a current view of the whole account, leaving AI to work from fragments.
Tatulea proposes a Context Graph for GTM, a layer connecting entities, history, and activity so teams and agents can work from the full account.
The post places the idea alongside categories with comparable tools: Harvey and Legora in legal, Sourcegraph in engineering, and Glean in enterprise search.
Travis Kalanick listed at Uber in the marketing system, though they now run CloudKitchens—a case readers can check in their own data.
Teach through a scenario: map the buying committee, then rank the gaps
The renewal post shows Tatulea's method through one account.
Read more
It sets up a thought experiment for reps: you inherit an account renewing in three months, with only thin CRM notes and two call recordings.
The steps are ordered.
First, map the buying committee: separate those who are engaged from names listed in the CRM and people who have never been contacted.
Then identify missing stakeholders and rank them by seniority and likelihood of moving the deal, with reasoning attached to each recommendation.
One detail puts the data-quality argument into practice: contact titles come from a live data connection inside the assistant, not the CRM record.
The post ends with a video walkthrough and a link to the prompts and skills used.
An inherited account renewing in three months, with two call recordings, anchors a step-by-step guide to mapping the buying committee and ranking gaps.
This is the clearest summary of Florin Tatulea's method: build the account list, buyers, conversion signals, and account context in one place before orchestrating.
Read more
Read it to understand the framework behind their other posts.
Tatulea writes that every ABM play “we've run scaling to $1.2bn+” rests on four layers: a named list of target accounts, the named buyers at each account, signals proven to predict conversion, and context about what is already known about each account.
The common failure, they say, is keeping the four layers in separate systems—CRM, marketing automation, intent tools, call recordings, or someone's spreadsheet.
Rev Ops and GTM engineers repeatedly stitch them together, and the data goes stale.
They argue this matters more with AI because an agent chains steps: a wrong field at step one becomes the assumption every later step builds on, at a speed and volume no human can catch.
They quote Henry Schuck: “reasoning without verified data is fluent guesswork.”
The recommended order: build the four layers, bring them into one place, then orchestrate.
For brands planning a campaign
A revenue operations platform could commission a follow-up where Tatulea expands one layer—such as proven conversion signals or account context—into a practical playbook. The strongest sponsored angle: accurate, current account data is an AI-adoption prerequisite, not a reporting chore.
Read this to see the account-data problem Tatulea treats as foundational: systems hold fragments, and AI agents act on those fragments.
Read more
They explain the “context graph” they propose as the missing layer beneath GTM AI.
Tatulea asks readers to check their CRM and predicts specific failures: Google and Waymo held as separate accounts with no link to Alphabet; SpaceX acquiring Cursor without the account hierarchy changing; Travis Kalanick listed at Uber even though he now runs CloudKitchens.
The point is not just that CRM data is messy.
They argue that every system holds a piece of the puzzle, none holds a current view of the whole account, and AI operating on those fragments is “operating on fragments of it” rather than reality.
They frame the fix as a “Context Graph for GTM” that connects entities, history, and activity so teams and agents work from the full picture.
The post places the idea alongside category examples: Harvey and Legora for legal, Sourcegraph for engineering, Glean for enterprise search, and now ZoomInfo for GTM.
For brands planning a campaign
A revenue operations platform could use this post to open a sponsored explainer on account resolution: Tatulea gives concrete CRM failure examples before introducing a category. The collaboration is strongest if it shows how hierarchy changes are detected and maintained, not just why they matter.
Start here to see the framework applied to one account.
Read more
A rep inherits a renewal with incomplete CRM notes and two call recordings, then maps the buying committee and finds gaps.
Tatulea sets up a thought experiment for renewal reps: you inherit an account renewing in three months, with only “some half baked CRM notes and 2 call recordings.”
They outline a starting workflow with Claude and ZoomInfo.
First, map the buying committee to see who is actually engaged, who is only a CRM name, and who has never been contacted.
Second, identify missing stakeholders, ranked by seniority and likelihood of moving the deal, with reasoning behind each recommendation.
They say the contact titles come through ZoomInfo's MCP integration inside Claude, so they reflect what is accurate today rather than what someone last entered in the CRM.
The post points to a video walkthrough and a link for the skills used.
For brands planning a campaign
This is a natural sponsored-use-case format if the sponsor can support a real walkthrough with visible prompts and data checks. The post references video and skill assets but does not include them, so ask whether the sponsor can provide or recreate those working assets.
Recurring argument: agents inherit the quality of the data underneath them3
Format and teaching approach3
Product-linked posts about GTM data infrastructure3
Why CRM account records go stale—and what it costs1
The four layers of an ABM play1
Anatomy of a renewal: mapping the buying committee1
Why CRM account records go stale—and what it costs
Tatulea opens with a check any reader can run: the CRM holds Google and Waymo as separate accounts with no link to Alphabet; a hypothetical SpaceX acquisition of Cursor never changes the account hierarchy; and Travis Kalanick's move to CloudKitchens is not reflected in marketing systems.
Read more
The failure modes are mismatches: the right person and wrong account, the right account and wrong person, or the right person and account but the wrong message.
The proposed fix is a layer that resolves entities, history and activity into one current view of an account, giving AI agents the full picture instead of isolated records.
The post calls this a context graph for GTM and places it alongside tools such as Harvey, Legora, Sourcegraph and Glean.
Opens with a verifiable exercise, follows with three failure modes, then reaches a product-shaped conclusion.
For brands planning a campaign
Useful for a data, enrichment or sales-intelligence vendor seeking to frame a problem before mentioning its product: the hierarchy and job-change examples give readers specifics to test against their own systems.
ABM plays that scale rest on four layers: a named list of target accounts, the buyers at each one, signals that predict conversion, and the context already held about each account.
Read more
The recurring problem is that each layer lives somewhere different—CRM, marketing automation, intent tools, call recordings or a spreadsheet—so revenue operations and GTM engineers repeatedly stitch them together while the data goes stale.
The post argues that this creates a particular risk for AI: agents chain steps, so a wrong field at step one becomes an assumption inherited by every later step, at a speed and volume no human can catch.
The order matters: build the layers, bring them into one place, then orchestrate.
For brands planning a campaign
A ready-made structure for a sponsored playbook, webinar or diagnostic. A vendor could provide the consolidation layer across the four layers or co-author a four-layer assessment as an entry resource.
Anatomy of a renewal: mapping the buying committee
The scenario: an inherited account is up for renewal in three months, with thin CRM notes and two call recordings.
Read more
The walkthrough starts by mapping the buying committee: who is engaged, who is only a name in the CRM, and who has never been contacted.
It then identifies gaps by ranking missing stakeholders by seniority and likelihood of moving the deal, with reasoning attached to each recommendation.
The post notes that contact titles come from a live data connection inside the assistant, not from whatever someone last typed into the CRM, and points readers to a video walkthrough and a link to the prompts and skills used.
Scenario-driven: a concrete handover situation, ordered steps, then a link to longer working material.
For brands planning a campaign
A strong template for practitioner-led content aimed at sales and revenue operations teams. A contact-data or sales-engagement vendor could host the walkthrough, using the renewal scenario as its worked example.
Recurring argument: agents inherit the quality of the data underneath them
The same claim runs through all three posts: AI in go-to-market fails not because of a shortage of tools, but because the account picture remains unresolved.
Read more
One post argues for giving the agent a better understanding of the world it operates in.
Another quotes Henry Schuck's line that reasoning without verified data is fluent guesswork.
A third says the connection inside the assistant returns titles that are accurate today rather than stale records.
The practical conclusion is consistent: verify the data before adding automation.
For brands planning a campaign
The clearest position to build thought leadership around: it recurs across the material rather than appearing just once. A brand could commission a piece testing the claim against its own data-quality approach.
The posts are long-form LinkedIn text, built around a hook, short one-line paragraphs, arrow or dash lists, and a closing pointer to deeper material: a linked write-up, video walkthrough, or link to prompts and skills.
Read more
They teach by running a scenario or a check readers can repeat, then naming the steps in order. Numbers, named companies and named people carry the argument instead of general claims.
Worked scenarios and numbered steps; each post ends by giving readers something to use next.
For brands planning a campaign
Works well in sponsored formats with a repeatable structure: a hook post leading to a gated playbook, walkthrough video or downloadable prompt set. The creator supplies the scenario rather than the vendor supplying the theory.
Product-linked posts about GTM data infrastructure
Two posts present a GTM data vendor's capabilities—a context-graph launch and an assistant integration that reports current contact titles—while a third attributes a line on data quality to Henry Schuck.
Read more
In each case, the product appears as the answer to a problem the post has already made concrete, not as the opening subject.
For brands planning a campaign
Shows how a vendor mention lands: after the problem is established and tied to a named capability. Brands should expect readers to weigh the claim against the problem framing that precedes it.
The posts point to one commercial connection: ZoomInfo.
Read more
Two first-person posts discuss its products: one announces a new product, and the other walks through a renewal workflow built on ZoomInfo data inside Claude.
Neither states Tatulea’s role at or contractual relationship with ZoomInfo.
Ask whether the connection is employment, sponsorship or another arrangement.
ZoomInfo
Disclosed partnership
A first-person post announces a new ZoomInfo product, a “Context Graph for GTM,” and closes by positioning ZoomInfo alongside tools like Harvey, Glean and Sourcegraph for other functions.
Read more
A second post walks through a renewal-planning workflow using ZoomInfo’s MCP integration inside Claude to pull current contact titles instead of relying on CRM entries.
Both posts promote and explain ZoomInfo products, but neither states Tatulea’s connection to the company.
Ask what their role or relationship with ZoomInfo is.
The account-hierarchy post sets up the problem and asks you to check your own CRM, making it a useful self-test.
The four-layer ABM post explains what a working account model needs and why the layers rarely sit in one place.
The renewal walkthrough is the practical guide: an inherited account, thin CRM notes, two call recordings, and a numbered method for mapping the buying committee and ranking missing stakeholders, with a link to the video and the prompts used.
Follow the linked playbook, walkthrough and prompt set for the supporting material.
For the same argument from a different angle, Henry Schuck and Shivvani Seyth cover data readiness before agentic AI, while David H.
Johnson shows what the workflows look like when someone builds them.
Both make the case that go-to-market AI is limited by unresolved account data.
Read more
Schuck's posts cite Cisco appearing as several separate records, a promo that reached existing customers because subsidiaries like Uber Freight were never rolled up, and the line that reasoning without verified data is fluent guesswork. Tatulea's account-hierarchy post makes the same argument with Google and Waymo held apart and Travis Kalanick still listed at Uber.
Schuck writes at category level, naming the vendor battleground and closing with a reference dataset as the answer. Tatulea stays closer to the practitioner, framing the problem as something readers can check in their own CRM and following it with ordered steps rather than a market position.
Both argue that the data model, not the tooling, determines what anyone gets out of agentic AI.
Read more
Seyth's posts call for one named owner of account and contact data, locked stage history and original source, a single definition of an account, and an ICP rebuilt from closed-won, closed-lost and churn cohorts rather than assumptions. Tatulea takes the same readiness-before-automation position.
Seyth writes in an analyst register, citing McKinsey and Gartner and evaluating a specific tool against your own pipeline history. Tatulea teaches through a scenario and named steps, with few outside citations beyond a quoted line.
Johnson builds the layered, orchestrated agent pattern Tatulea describes in principle.
Read more
His posts argue that eliminating before selecting beats one large prompt.
His account-intel agent uses parallel enrichment paths, consistent JSON contracts between steps, guardrails to prevent bad inputs from poisoning downstream summaries, and an aggregation layer a person can use.
Tatulea makes the related point that a wrong field at step one becomes an assumption every later step inherits.
Johnson writes for people constructing agents, covering workflow tooling and interface details. Tatulea explains the data prerequisites for sales and revenue operations readers and shows the payoff in a renewal play, not a build.
LinkedIn is the only channel with measured audience data: 75,990 followers as of October 8, 2026.
Read more
That supports a LinkedIn placement decision for a RevOps campaign, but doesn’t establish the audience’s employer, job function, seniority, geography, age, or gender.
The three recent posts—account-data hygiene, ABM layer stacking, and a renewal walkthrough—are aimed at practitioners.
If seniority or function mix matters to a campaign, ask for survey results or documented demographic data.
LinkedIn followers
75990
LinkedIn profile follower count, same account export as the selected posts · 2026-10-08
No partnership or sponsorship format is documented in Florin Tatulea's posts.
Read more
The three posts tie their writing to ZoomInfo product work: the launch of a GTM context graph, a renewal-planning walkthrough built on ZoomInfo's integration inside Claude, and an ABM playbook that quotes ZoomInfo's chief executive.
That is product and co-marketing context, not a published offer to brands.
The posts provide no placement types, deliverables, pricing, lead times, disclosure practices, sponsorship examples, or official partnership intake route.
Before planning a paid collaboration, ask for a sponsor policy, media kit, rate card, or details of a disclosed branded collaboration.
Campaign A: a revenue operations platform selling account data infrastructure wants to reach practitioners who own GTM data and ABM programmes with a sponsored thought-leadership piece and a co-branded practical playbook.
Read more
Tatulea fits closely.
Across the three posts, the argument is consistent: AI in go-to-market fails because account information is unresolved, not because tools are scarce.
One post says teams and agents should work from the full picture instead of isolated records; another quotes the line that reasoning without verified data is fluent guesswork; a third says an assistant returns titles that are accurate today rather than what someone last typed into the CRM.
That is the case a revenue operations data platform sells.
The four-layer ABM post offers a ready-made playbook structure: target accounts, named buyers, conversion signals and account context, plus the risk of leaving them in separate systems.
The sponsor's product can be positioned as the place those layers meet, rather than made the opening subject.
The renewal post supplies a practitioner template: a handover scenario, ordered steps, missing stakeholders ranked with reasoning, and a handoff to prompts.
Their format suits the commission: long-form LinkedIn text, numbered steps, named companies and people, and a closing pointer to a deeper asset—the shape of a sponsored hook post plus gated resource.
The audience section reports 75,990 LinkedIn followers as of 8 October 2026.
For a campaign promising a particular buyer mix, ask for audience data by function, seniority and geography.
Their posts describe a specific GTM data vendor's context-graph launch and assistant integration, so a competing platform should resolve whether that existing tie-in is a conflict.
No partnership format, rate card or intake route is published; agree terms before planning the campaign.
When to choose a specialist
Campaign B: a sales coaching and enablement vendor wants a short-video-led demand campaign aimed at frontline sales managers and reps, with vertical clips, a downloadable script bank and a monthly slot reporting audience demographics to prove reach among SDRs.
Read more
The posts point to a poor fit.
Tatulea's audience section gives one measured number: 75,990 LinkedIn followers on 8 October 2026.
To substantiate a claim of reaching SDRs specifically, ask for a breakdown by function, seniority, geography and age.
The three posts are long-form LinkedIn text; none mentions short-form or vertical video.
The two deeper assets they point to—a video walkthrough and the prompt and skill pack—are not linked, so ask for examples of clip production and video performance before commissioning.
The partnerships section lists no formats, deliverables, pricing, lead times or intake route, so a monthly slot would need to be scoped from scratch.
The subject matter is also a mismatch: the posts build their case through account-resolution details—hierarchy drift, buying-committee gaps and current contact titles—leaving little of their strongest material for a generic sales-motivation or coaching campaign.
A revised campaign could fit better: replace the demographic promise with a practitioner-facing renewal scenario, and swap the clips for a long-form post plus a worked template, both of which appear in the posts.
A worked campaign example
Campaign angle for the RevOps campaign: "The account audit"—a sponsored thought-leadership piece plus a working asset, sequenced like Tatulea's posts.
Post one, the hook: open with the check they already use—the reader looks at their CRM and finds Google and Waymo as separate accounts with no link to Alphabet, and a job change that never propagated.
Then set out the three-part failure list: right person and wrong account; right account and wrong person; both right and wrong message.
Add the consequence for AI: an agent chains steps, so a wrong field at step one becomes the assumption every later step builds on.
Introduce the sponsor's data-resolution capability at the end, as the answer to a problem the post has made concrete, as in their existing context-graph post.
Close with a link to the working asset.
The working asset: a four-layer account assessment for readers to complete—target accounts, named buyers at each, signals proven to predict conversion, and the context already held about each account—using the ABM post's structure and including a completed example and a blank version.
The renewal scenario supplies the worked example: a rep inherits an account renewing in three months with thin CRM notes and two call recordings, maps the buying committee, and ranks missing stakeholders by seniority and likelihood of moving the deal.
Produce this material for the campaign: the prompts and video mentioned in the post are not available to reuse.
An optional short walkthrough video would require access to the sponsor's platform so contact titles reflect current data rather than last-entered CRM values.
Why it should work: it uses the hook-then-steps-then-handoff structure of their posts, introduces the sponsor after the problem, and gives readers a resource they can use beyond the piece—a blank assessment plus a worked example.
Before proceeding, agree the sponsorship format, deliverables, price and lead time; none is published.
The sponsor should also decide whether Tatulea's existing GTM data vendor relationship is a conflict.
Choose Henry Schuck when a revenue operations campaign needs a category-level, vendor-side voice rather than a practitioner walkthrough.
Read more
The posts argue that most AI workflows in go-to-market produce garbage because account data is unresolved, and name four requirements: entity resolution, hierarchy resolution, stitched first- and third-party data for each account, and metadata an agent can read.
They also frame GTM context as the next vendor battleground and call CRM a mess, with Google and Waymo sitting as separate accounts and job changes never propagating.
That makes Schuck a strong fit for sponsored thought leadership that defines the problem agenda for a revenue operations data platform, especially if the sponsor wants a senior-sounding argument for why isolated records cannot support agents.
The posts offer concrete examples to anchor the opening: a company sending a discount to existing customers because subsidiaries were not rolled up, and an agent writing account plans about the wrong company after a name is transcribed badly.
The sponsor’s product can follow.
The tradeoff is positioning and conflict.
Schuck’s posts place them inside ZoomInfo’s context-graph effort, including the line that GTM now has ZoomInfo.
A competing revenue operations data platform should decide whether that association is a blocker before commissioning the same account-resolution argument.
The posts make executive and category arguments, not step-by-step assets: they name the data problems but include no blank workbook, buying-committee exercise, or renewal walkthrough.
A sponsored playbook would need to be built separately, so the sponsor would be buying agenda-setting and credibility, not a demonstrated practitioner template.
Choose Shivvani Seyth when the campaign needs an operations-and-analysis voice that turns research and governance into practical RevOps rules.
Read more
The posts unpack the McKinsey agentic-AI chapter behind the chart, draw on Gartner’s agent-sprawl warning, and translate the problem into concrete data-ownership steps: one named owner for account and contact data, locked stage history and original source, one definition of an account across CRM, billing and board reporting, and structured meeting outcomes.
Another post tests a free ICP builder on a real site, then explains why a generated ICP becomes less useful once pipeline history exists: renewal rates, high-effort deals, and closed-lost accounts carry signals a website scan cannot see.
For a revenue operations data platform, Seyth is a better fit than a generic creator list when the sponsored asset is a data-quality checklist, an ICP validation exercise, or a co-branded piece on using outcome data to correct generated assumptions.
The posts also offer a practical playbook structure: take a popular chart or tool, open the layer most readers skip, then deliver a short list of rules a revenue team can apply.
The tradeoff is that Seyth’s posts focus more on data governance and ICP validation than on named-account ABM execution.
They include no four-layer ABM stack, buying-committee map, or renewal walkthrough, so the sponsor would need to supply or develop the account-resolution examples for a practitioner playbook.
Seyth also reviews third-party tools and cites outside research; a sponsored collaboration would need clear boundaries around existing tool mentions and avoid implying endorsement beyond the commissioned piece.
The posts do not document audience composition or commercial terms, so ask for those before validating reach and format assumptions.
Johnson when the campaign needs a builder’s technical playbook rather than a market-level argument.
The posts describe a layered reasoning system with six single-job stages — fact check, parse, map constraints, pick action class, compose output, strip AI smell — and a modular account-intel agent in Make that runs parallel enrichment paths, normalizes each one, and rolls them into a structured GTM object.
Johnson names principles a revenue operations platform can use in a co-branded asset: consistent JSON contracts between steps, guardrails to keep bad inputs from poisoning downstream summaries, routing logic that keeps domains independent, and a final aggregation layer a human can use.
They also report using the system to audit deal activity and generate demo prep with claims tagged by confidence level.
That’s concrete enough for a technical practitioner audience and gives the sponsor a way to present account-data work as an engineering pattern rather than a slogan.
The tradeoff is audience and scope.
Johnson’s posts focus on system design and build logs, not broad thought leadership on account hierarchy or buying committees; they lack the four-layer ABM frame and a rep-level renewal scenario.
A sponsored campaign would get a strong architecture walkthrough but would need to add the commercial account-data argument and buyer-facing examples.
One post also ends with an Apollo careers call to action, so a competing RevOps platform should check for employer or vendor conflict before commissioning.
Ask for audience size, sponsorship format, and an intake route before proceeding; the posts do not document them.
Three LinkedIn posts by Florin Tatulea show three CRM failures a reader can check in their own data — Google and Waymo held as separate accounts, an acquisition that never changes the account hierarchy, and Travis Kalanick still listed at Uber — and propose a context graph that connects entities, history and activity so teams and agents work from a current view of an account.
A second post sets out the four layers behind the ABM plays Tatulea describes running to $1.2bn+, and the problem of each layer living in a different system.
The third walks through a renewal, starting from an inherited account with thin CRM notes and two call recordings, and orders the work as mapping the buying committee, then ranking missing stakeholders by seniority and likelihood of moving the deal.
The similar-creators section compares posts by three similar creators; those posts do not support claims about Tatulea.
One audience figure is used — a LinkedIn follower count of 75,990 on 8 October 2026.
The posts do not show publication dates, so none are given.
The posts point to assets including a video walkthrough, a prompt and skill pack, and a deeper playbook, but do not describe them; they are referenced as available elsewhere.
The posts here do not mention an employer, client relationship, book, show, sponsorship format, rate card or inquiry route, and the follower count carries no breakdown by function, seniority or geography.
These gaps affect campaign planning, but do not establish what Tatulea does or does not do.
