Daniel Steinberg writes about enterprise SaaS sales, focusing on why complex deals stall and how differing priorities across teams shape buying decisions and adoption.
Most useful for explaining why complex enterprise SaaS deals stall and how teams misalign.
Best for
A B2B SaaS sales-enablement brand wanting content on enterprise deal cycles.
Not for
Benchmark research, charts, ROI numbers, video demos, or product-led templates and checklists.
Key takeaways
Teams can agree to buy a tool without agreeing on the problem.
A deal can look active while making no progress.
Procurement may be where a deal is stuck, not what is stopping it.
Check first: Ask for format, deliverables, terms, audience composition, seniority breakdown, and post-performance data.
Main ideas
Teams can agree to buy a tool without agreeing on the problem · A deal can look active while making no progress · Procurement may be where a deal is stuck, not what is stopping it
Daniel Steinberg writes about enterprise SaaS buying and why complex deals and rollouts stall.
In four LinkedIn posts, they examine the gap between what a company intends and how different teams interpret it: a deal can keep moving without resolving internal disagreements, and a purchase can look agreed while teams define the problem and success differently.
Their work helps readers understand what “still aligning internally” or “stuck in procurement” may conceal.
Steinberg makes abstract organizational friction concrete by tracing its effects across people, teams, and time.
In one post, the same operational memo means lost autonomy to sales, a budget shift to finance, and more red tape to product; months later, adoption has stalled and workarounds have spread.
In another, an enterprise deal stays active as new stakeholders and edge cases keep appearing, without anyone clearly saying no.
They also offer a useful counterpoint: procurement may be where a deal is parked, not the cause of the delay.
These examples make their central lens practical: look for differences in incentives and definitions of the problem before treating a stalled deal or rollout as a simple process failure.
Daniel Steinberg’s posts connect stalled enterprise deals and failed rollouts to a shared problem: people may appear aligned while interpreting the situation differently.
Read more
They look past visible obstacles such as procurement and ask what teams actually understand, want, or are trying to solve.
Teams can agree to buy a tool without agreeing on the problem
Steinberg argues that a shared purchase does not prove a buying group is aligned.
Read more
If each department starts with a different problem, each will judge the result by a different measure of success.
In a post about choosing a contract-lifecycle platform, IT sees tool sprawl, legal sees contract risk, sales sees slow approvals, finance sees revenue leakage, and procurement sees a lack of visibility. Six months after the purchase, legal calls the rollout successful while IT reports poor adoption and sales calls it a waste of time.
Steinberg shows how continued meetings and sincere updates can disguise a deal stuck in a holding pattern.
Read more
As replies slow and new edge cases keep appearing, the seller may still have no clear decision or reason for the delay.
The post recounts an enterprise legaltech deal that had been in progress for over a year.
The champion first reported strong momentum; later updates became “still aligning internally,” while questions about legacy agreements, sales intake, and international approvals kept surfacing.
Steinberg ends by asking why people keep engaging if the deal is dead—and why nobody says no.
Procurement may be where a deal is stuck, not what is stopping it
Steinberg treats “stuck in procurement” as a description of a deal’s location, not necessarily its cause.
Read more
They suggest looking for the internal issue behind the delay instead of assuming procurement itself is the blocker.
After hearing several enterprise SaaS and legaltech sales leaders name procurement or legal as their biggest hurdle, Steinberg connects the stall to more stakeholders, “still aligning internally,” and multiplying edge cases, then asks what is actually slowing the deal down.
People act on how they interpret a change, not just how leaders describe it
Steinberg argues that a rollout’s intended message can be lost when different teams read it through their own concerns.
Read more
Those interpretations shape adoption, workarounds, and trust.
In the “Operational Alignment Initiative” scenario, sales hears a new logging requirement as a threat to autonomy, finance reads centralized procurement as a budget shift, and product sees more approvals.
A week after launch, adoption is stalling; six months later, the system needs rework.
Answers the question "why do rollouts stall when the plan is sound?" and is the clearest entry point into how Daniel Steinberg thinks about internal misreading.
Read more
Daniel Steinberg traces a single internal memo through a working day.
Leadership intends one idea: this initiative will help us operate better.
By 9:03 AM, sales reads a logging requirement as lost autonomy and a slower close rate; by 9:17 AM, finance reads the same line as a budget shift from CapEx to OpEx; by 9:31 AM, product reads it as more approvals and slower delivery.
The post follows the consequences over months: adoption stalls, workarounds multiply, legacy tools stay open, consultants are brought in, and trust thins for the next launch.
The closing line, "Implementation follows interpretation," makes the argument in four words.
The mechanism is simple: people read the same text against different incentives.
For brands planning a campaign
A sales-enablement brief on adoption or change management can use this as a diagnostic frame: before messaging a rollout, map what each function will hear. It supports content on internal communication for deal-cycle tools rather than product features.
Answers "what does a stalled enterprise deal actually look like from the inside?" and gives a newcomer the lived detail behind the phrase "still aligning internally."
Read more
Daniel Steinberg recounts a conversation with an enterprise account executive at a legaltech company who worked a deal for over a year: roadshow travel, stakeholder meetings across legal, IT, finance, procurement, and security, security reviews, internal champions, and patient navigation of procurement.
The champion kept reporting strong momentum until emails slowed from weekly to biweekly, then to "still aligning internally," as edge cases arrived one after another: legacy agreements, sales bypassing intake, and international approvals.
The deal still looks alive; everyone is sincere and still meeting, and nobody ever says no.
The piece ends with the question that makes it useful: if the deal is dead, why is everyone still engaging?
For brands planning a campaign
Directly supports a campaign angle on diagnosing stalled enterprise deals. It gives a sales-enablement audience a recognisable pattern to test against their own pipeline, with a natural hook for content about buying-committee dynamics and honest qualification.
Answers "is procurement really the blocker?" and shows how Daniel Steinberg turns a recurring complaint into a sharper, reusable question.
Read more
Daniel Steinberg opens with a quote heard repeatedly from people leading enterprise SaaS and legaltech sales: procurement and/or legal is my biggest hurdle these days.
Procurement is often where a deal sits parked while something else is resolved internally.
That is when "still aligning internally" appears, more stakeholders get pulled in, and edge cases multiply.
The post reframes the question: how often does "stuck in procurement" tell you where a deal is parked rather than what is slowing it down?
That reframe helps readers interpret a pipeline accurately.
For brands planning a campaign
Useful for content that separates surface deal stage from underlying cause. A sales-enablement company could build a piece around procurement as a symptom, giving sellers a way to interrogate their own stalled opportunities.
Answers "why do teams that agree on a purchase still disagree on whether it worked?" and states the underlying thesis connecting the other three posts.
Read more
Daniel Steinberg starts from the claim that people struggle to align on success because they never aligned on the problem.
The illustration: leadership says the company needs a new CLM, while IT sees tool sprawl, legal sees contract risk, sales sees slow approvals, finance sees revenue leakage, and procurement sees lack of visibility.
The same platform gets purchased and everyone appears aligned, but each function is solving a different problem and therefore measuring success differently.
Six months later, legal calls the rollout great, IT reports poor adoption, sales calls it a waste of time, and finance says it did not move the needle.
Nobody is wrong; they are evaluating against different definitions.
For brands planning a campaign
A strong anchor for a content angle on diagnosing stalled deals because it explains the failure before a deal closes and after it lands. It gives sales-enablement material a way to help buyers surface definitions of success early rather than reconcile them later.
Procurement as a parking spot rather than the cause2
Buying groups agree on a platform while disagreeing about the problem1
One internal message, several realities1
Deals that stay alive without progressing1
Buying groups agree on a platform while disagreeing about the problem
Steinberg's most developed argument is that cross-functional buyers can approve the same purchase while holding different definitions of the problem.
Read more
In the contract-lifecycle example, IT believes the problem is tool sprawl, legal believes it is contract risk, sales believes it is slow approvals, finance believes it is revenue leakage, and procurement believes it is lack of visibility.
The teams look aligned, then measure success against different criteria.
Six months later, legal calls the rollout great while sales calls it a waste of time and finance says it did not move the needle.
The conclusion: nobody is wrong because nobody started from the same problem statement.
A short department-by-department enumeration that shows the divergence, then projects forward to the six-month review.
For brands planning a campaign
For a sales-enablement audience, this supports content built around a pre-purchase alignment exercise: getting each department to write down its problem and success measure before selection. The angle is diagnosing disagreement before it becomes an adoption failure, not pitching a tool.
A memo titled "Operational Alignment Initiative" is followed through one morning.
Read more
Sales reads a logging requirement as lost autonomy and a slower close rate, finance reads centralized procurement as a CapEx-to-OpEx budget shift and expects departmental cuts next, and product reads a governance layer as more approvals and slower feature delivery.
The intended message, operational efficiency, is gone within hours.
A week later adoption stalls, workarounds multiply, and legacy tools stay open in browser tabs; six months later the rollout needs rework and consultants.
Steinberg's closing line is "Implementation follows interpretation," and the cost he emphasizes is thinner organizational trust ahead of the next initiative.
A time-stamped vignette across three departments with quoted dialogue, followed by seven-day and six-month consequences.
For brands planning a campaign
Useful for internal-comms, change-management, and software-adoption content. A campaign could take a stalled rollout and trace it to how each team read the announcement, rather than to the product itself.
Steinberg describes an enterprise account executive in legaltech who worked a deal for over a year: roadshow travel, stakeholder meetings across legal, IT, finance, procurement, and security, reworked decks, security reviews, internal champions, and patience through procurement.
Read more
The champion kept reporting strong momentum, then replies slowed from weekly to biweekly to "still aligning internally," and each answer produced another edge case about legacy agreements, sales bypassing intake, or international approvals.
The deal kept looking alive while sitting in a holding pattern.
Steinberg's closing questions are why everyone keeps engaging sincerely and why nobody says no.
A secondhand narrative told in short lines, punctuated by the champion's actual phrases, ending on open questions rather than a resolution.
For brands planning a campaign
Directly relevant to the enterprise-deal-cycle brief. It supports content built around a small set of diagnostic questions sellers can ask to separate a parked deal from a progressing one, and signals that a deal has quietly become a discussion rather than a decision.
Procurement as a parking spot rather than the cause
In a post drawn from several conversations with people leading enterprise SaaS and legaltech sales, Steinberg reports that "procurement and/or legal is my biggest hurdle" kept recurring.
Read more
Their observation is that procurement is often where a deal sits while something else is resolved internally.
That's when "still aligning internally" appears, more stakeholders get pulled in, and edge cases multiply.
Steinberg frames this as a question: how often does "stuck in procurement" tell you where a deal is parked without telling you what is slowing it down.
Steinberg presents this as a working hypothesis still under testing, not a settled finding. Campaign copy should not assert it as proven.
For brands planning a campaign
A caution for enablement content that treats procurement as the root cause. The angle is mapping the internal dependency behind the stall, which pairs naturally with the parked-deal diagnosis above.
Across these posts, Steinberg explains through specific situations rather than frameworks or checklists.
Read more
Three of the four are reconstructed scenes with time stamps, dialogue, and short declarative lines, and tend to close on a single principle or open question instead of a summary of takeaways.
The fourth is a compact diagnostic in list form.
The recurring move is to show how different functions experience the same event, then ask what that means for the seller or initiative owner.
Scene-setting with quoted dialogue and time markers; concrete numbers used as consequences rather than evidence.
For brands planning a campaign
A commissioned piece would fit a narrative-then-question structure: one concrete deal or rollout, told from inside, ending with a question the reader can apply. Briefs asking for listicles, product-led templates, or data-driven benchmarking sit outside the observed style.
Daniel Steinberg's posts do not document any brand relationships.
Read more
They discuss enterprise sales cycles, procurement stalls, and cross-team misalignment through unnamed or hypothetical companies: a legaltech employer referred to only as “a legaltech company,” a generic “new CLM” platform, and a fictional “Operational Alignment Initiative.”
No sponsor, affiliate, client, employer, owned business, investment, or named commercial partnership is stated.
Ask for disclosure of any relationships not stated in the posts.
Daniel Steinberg writes about why enterprise deals and software rollouts stall even when everyone involved appears to agree.
Read more
The reviewed work is a small set of LinkedIn posts that read as scenes rather than frameworks: a year-long deal that keeps circling, a company memo followed through one morning, and a purchase where five departments define the problem differently.
Start with the contract-lifecycle post, which lists what IT, legal, sales, finance, and procurement each think the problem is.
Then read the operational-alignment memo, where one announcement means lost autonomy in sales, a budget shift in finance, and more red tape in product.
Together, the posts raise a question worth carrying into any deal or rollout: what does each team believe the problem is?
The posts are undated; ask for publication dates to assess how current the theme is.
Johnson works the same seam as Steinberg: what sales reps learn in customer conversations and why it never reaches the systems a company uses to make decisions.
Read more
Both build a post around a concrete workflow gap and close with a question readers can apply to their own teams.
Johnson writes from the revenue-intelligence side and names a product built to close the gap, so the posts end in a tool pitch as much as a question. Steinberg stays with the seller's and buyer's experience of a stalled deal and does not promote a product.
Barnard covers the buying side of the enterprise software process Steinberg describes: procurement, approvals, and the gap between what a company thinks it spends and what it actually pays.
Read more
Both treat that gap as a process problem rather than a discipline problem.
Barnard writes as a finance leader inside a vendor and frames the answer as automated workflow logic, with product links at the end. Steinberg approaches the same process from the seller's view and leaves the diagnosis open.
Kerr covers the moments Steinberg analyzes: procurement pushing for a discount, a champion who turns out not to be one, and a deal that looks close but isn't.
Read more
Both diagnose why enterprise deals lose momentum.
Kerr offers first-person, prescriptive tactics, such as pausing for three seconds and asking, "when you say that, what do you mean?" Steinberg reconstructs a scene and asks what is really happening rather than teaching a script.
Daniel Steinberg’s posts address enterprise SaaS sales and cross-functional buying decisions, making them relevant to a campaign about stalled enterprise deals.
Read more
Before booking, request recent platform analytics and results for comparable enterprise-deal topics and formats. If the campaign depends on reaching people by role or seniority, ask for audience survey results or another documented source for those professional attributes.
Daniel Steinberg's four posts focus on enterprise SaaS and legaltech deal cycles: stalled procurement, cross-team misalignment and internal rollout friction.
Read more
They do not mention a sponsorship offer, paid partnership format or official inquiry route, and none includes a sponsor disclosure, a brand presented as a paid placement, a media kit, a rate card or a commercial contact.
The only public contact point is the LinkedIn profile where the writing appears, not a published partnership channel.
A brand would need to initiate a conversation and negotiate format and terms from scratch, with no published precedent to reference.
A B2B SaaS sales-enablement company wants content on enterprise deal cycles, especially diagnosing stalled enterprise deals.
Read more
This is a strong subject-matter fit.
The stalled-deal posts are the closest match: a legaltech enterprise rep works a deal for over a year, watches replies slow from weekly to biweekly to "still aligning internally," and keeps absorbing new edge cases about legacy agreements and international approvals.
The account ends on a question a seller can use: why does everyone stay sincere and engaged while nobody says no?
The procurement post sharpens the same territory by reframing "stuck in procurement" as a location rather than a cause.
The cross-team post adds the diagnostic layer: teams may agree on a platform while disagreeing on the problem, measure success differently, and call the same rollout both a success and a waste of time.
The writing approach also suits enablement content.
Steinberg builds scenes with time stamps, quoted dialogue, and short declarative lines, then closes on a single principle or open question rather than a list of takeaways.
That structure fits a long-form LinkedIn post, a newsletter piece, or a sales-team read-along, with a natural place for a seller-facing prompt at the end.
Before booking, ask for format, deliverables, and terms; the posts document no sponsorship offer, rate card, or inquiry route.
Ask for audience composition, seniority breakdown, and post-performance data to assess reach into enablement buyers.
When to choose a specialist
A B2B analytics vendor wants original benchmark research: a survey-backed report with charts, quantified industry benchmarks, and a scripted product demo video series built around hard ROI numbers.
Read more
This is a poor fit for the demonstrated work.
The four posts show no data collection, benchmarking, charting, or visual work; they are text on LinkedIn.
Numbers appear as consequence rather than evidence: the "millions disappear into friction" line in the memo post is a narrative beat, not a measured figure.
Defensible quantitative claims would require a capability the posts do not demonstrate.
The posts also show no video, transcript, or off-platform work, so a scripted demo series would rely on an unverified format.
Another poor fit is work that asserts procurement or legal as the proven root cause of stalled deals, or requires a product-led template or checklist.
The procurement post explicitly frames its claim as a question Steinberg is still testing, and the writing teaches through reconstructed scenes rather than frameworks, making a fixed-step template an awkward match.
Rapid, high-volume short-form output and consumer lifestyle subject matter also sit outside the observed range: the posts cover enterprise SaaS and legaltech buying, told at length.
A worked campaign example
Worked angle: "Parked or progressing?
How to tell a stalled enterprise deal from a slow one."
Open on a scene drawn from the legaltech account: the roadshow, stakeholder meetings across legal, IT, finance, procurement, and security, the reworked deck, and the champion's "strong momentum" updates.
Follow the drift: weekly replies become biweekly, then "still aligning internally," then a new edge case about legacy agreements or sales bypassing intake, followed by another from a different part of the organization.
End the scene on the uncomfortable observation that everyone is still meeting, everyone is still sincere, and nobody has said no.
Then turn to diagnosis.
Using the procurement reframe, separate where a deal is parked from what is slowing it down, and lay out signals that distinguish the two: repeated internal-alignment language with no named decision owner, edge cases arriving from new functions rather than the same one, and engagement that stays warm while the calendar keeps slipping.
Close with questions a seller or enablement lead can apply to live opportunities: who has written down what problem they think this solves, what each function will use to judge success, and what would have to be true for this to move this quarter.
The cross-team post shows why those questions matter: a buying group can approve one platform while holding five different definitions of the problem, so the six-month review produces five different verdicts.
Structure: one reconstructed deal scene, one reframe, one diagnostic set, one closing question.
Keep the procurement point framed as a working hypothesis rather than a proven finding, and end on a question the reader can reuse, as the source material does.
Avoid a checklist headline that promises a fixed formula, invented statistics, or product-led demo framing.
This angle works as a long-form LinkedIn post, a newsletter issue, or a session script for an enablement audience.
The diagnostic set can also be adapted into a buyer-facing worksheet, which would need to be produced for the campaign rather than drawn from existing published material.
For enterprise deal-cycle content focused on diagnosing stalled deals, choose Shawn Johnson when the assignment is about the seller's side of the cycle rather than the buying committee: how reps carry intelligence between meetings, why what a customer reveals on a site visit never reaches the CRM, and how a pipeline review misses the detail that actually predicts a deal.
Read more
Two posts make that case directly: a list of six things a top closer says in the hallway that never get logged, and a first-person account of scribbling three lines in a rental car after a buyer said the incumbent vendor had missed a deadline. For sales managers coaching forecast discipline, this speaks to their daily problem more than a reconstruction of multi-stakeholder ping-pong.
The trade-off is scope.
The work focuses on field visibility and CRM data quality, and the rental-car post ends by naming the tool built to solve the problem, giving it a product-led feel.
It spends less time on the buying-committee negotiation and internal alignment that make Daniel Steinberg's stalled-deal material useful.
A brief that needs to explore five competing definitions of the problem inside one account would get more from Steinberg's work.
For enterprise deal-cycle content focused on diagnosing stalled deals, choose Matt Barnard when the audience is in finance, procurement, or operations rather than on a sales floor.
Read more
The work is written from the buyer's seat: as a finance leader fielding "what's our AI spend, and what do we do about it?", and as the person who approved every software purchase at 50 people and became the bottleneck at 500. For an enablement vendor whose readers need to understand why a purchase stalls internally, or who sells to the function that gates the deal, this explains the approving side of the enterprise cycle in plain terms.
That vantage point is the trade-off: Barnard describes the problem from inside the buying organization, and both posts close on a product pitch.
The material teaches the procurement and finance decision rather than the seller's diagnosis of a stalled opportunity.
The seller-side signals Steinberg reconstructs — the champion going quiet, edge cases arriving from new functions, engagement that stays warm while the calendar slips — are largely absent.
For enterprise deal-cycle content with an angle on diagnosing stalled deals, choose Tom Kerr when the campaign wants sales-floor tactics and negotiation scripts with a strong narrative hook.
Read more
The posts are first-person and concrete: a deal where a discount demand was met by folding immediately, described as costing $55k in ARR, and the three-second pause plus "when/whats" questions adopted after it; and a pipeline-review piece on the gap between "I think so" and a real champion. For enablement content built around teachable moments and quotable lines, this is the closest register to the need.
The focus is on single-deal negotiation and champion-building rather than multi-stakeholder diagnosis.
The posts sell the method, and the dollar figures are personal anecdotes, not measured benchmarks; ask for benchmarked results if those are central to the brief.
Steinberg's work covers stalled deals, procurement framing, and cross-team problem definition, giving it a broader range.
This profile covers four complete LinkedIn posts by Daniel Steinberg on enterprise deal cycles, procurement stalls, cross-team problem definition, and how teams interpret a software rollout.
The posts are complete.
No publication dates appear with the posts, so it is not possible to say how far back these themes run or how they have changed; the posts cover the range of themes described here rather than every post.
The posts discuss unnamed or hypothetical companies and disclose no employers, clients, or sponsors, so no brand relationships could be listed.
No books, shows, video, transcripts, or other channels appear here, and no audience or post-performance data appears here.
Similar-creator comparisons in the topics module use dated posts from three other enterprise-sales writers.
