Rebecca Martins leads marketing work at SpendHound, sharing practical perspectives on software-spend benchmarks and how finance, procurement, and IT teams can assess AI costs and value.
3.4K followersAI ROIBased on 10 posts · latest Oct 2026
Rebecca Martins is most useful for practical software-spend benchmarks and AI cost and ROI content for finance, procurement, and IT buyers.
Best for
A B2B SaaS procurement platform wanting a co-marketing webinar on software spend and AI ROI.
Not for
A consumer app or general-interest tech brand seeking broad reach with guaranteed impressions and paid placements.
Key takeaways
OpenAI Enterprise has no published price list, so buyers benchmark comparable deals instead.
Only 6% of finance and procurement leaders say AI cut headcount.
Mid-market companies overspend 20 to 30 percent on software, and the problem is timing.
Check first: Confirm with Rebecca Martins audience data, engagement figures, and whether collaboration must run through SpendHound.
Main ideas
Vendor pricing is negotiated in the dark, so buyers need peer benchmarks · Software overspending is a timing problem, not only a visibility problem · Measure AI by the work it moves, not the jobs it removes
Rebecca Martins leads marketing work at SpendHound and writes about software-spend benchmarks and the costs and value of AI.
Her posts connect procurement and finance questions to concrete buying decisions: what comparable companies pay, when pricing data can help before renewal, and how to assess AI beyond headcount reduction.
Follow her for a practical view of how benchmark data can inform software purchasing and AI investment.
Martins makes abstract cost and ROI questions easier to act on by tying them to specific decisions.
In one post, she explains why OpenAI Enterprise buyers cannot rely on a published price list and argues that comparable deals can provide a better renewal reference.
In another, she contrasts survey figures on AI reducing headcount with AI moving employees to higher-value work, shifting the ROI question beyond job cuts.
Her posts also show how benchmarks can be put to work before a contract is signed, including through a SpendHound partnership that placed data in Zip's procurement workflow.
The set includes event and team updates as well as research-led posts, so her work is not limited to analysis.
The supplied material does not establish a signature book, show, or earlier body of work.
Rebecca Martins writes about software and AI spending from the buyer's side of the deal.
Read more
The recurring argument is that vendor pricing is opaque — negotiated contract by contract, with no public list — so the only useful anchor is what comparable organizations actually pay.
From that premise follow the priorities that run through the material: get benchmark data in front of buyers before they sign rather than after, judge AI by the work it moves rather than the jobs it removes, and treat AI cost as a problem that spreads across a technology stack rather than one that sits inside a single tool.
The work is aimed at finance, procurement, and IT leaders, and it is backed by survey research and peer pricing data rather than by opinion.
Vendor pricing is negotiated in the dark, so buyers need peer benchmarks
Take OpenAI Enterprise as the example: there is no published price list, and every contract is built from scratch, with licenses, committed usage, and API consumption negotiated deal by deal.
Read more
Two similarly sized companies can therefore sign very different agreements depending on deployment size and how the deal is structured.
The failure mode named is a buyer arriving at renewal anchored to the wrong number — a per-seat figure or something heard secondhand from a peer — or with no anchor at all.
Knowing what comparable organizations pay is presented as the fix.
A peer benchmark view inside the SpendHound platform showing where a customer's pricing lands against similar deals, with a linked guide breaking down average ChatGPT costs by company size and what drives the gap between similar buyers.
Software overspending is a timing problem, not only a visibility problem
Mid-market companies overspend 20 to 30 percent on software, and most do not find out until renewal — by which point there is no leverage left to change the price.
Read more
Pricing data that arrives after a contract is signed cannot change what was paid, so the argument is about when the information reaches the buyer, not just whether they can see spend at all.
A partnership with Zip that places SpendHound benchmarks inside Zip's procurement workflow, sourced from a vendor dataset of more than 10,000 vendors and based on what more than 1,500 companies actually pay, starting with the highest-spend software categories.
Measure AI by the work it moves, not the jobs it removes
Two survey results are set against each other: 6 percent of finance and procurement leaders say AI has reduced finance headcount, while 37 percent say it has let them move employees to higher-value work.
Read more
The gap between the replacement narrative and what leaders report is treated as the more interesting finding, and it opens a different way of thinking about AI's return. The proposed approach is a short set of questions finance leaders should ask to assess value.
The headcount-versus-redeployment contrast itself, drawn from survey responses and used to reframe AI ROI around work shifted rather than roles cut, with the four assessment questions carried in a separate article.
AI cost is a stack problem, not a per-tool problem
IT is described as caught between enabling AI adoption and managing complexity that moves faster than budgets.
Read more
Capabilities emerge and overlap quickly, usage and costs scale unpredictably, and one new AI tool can drive up consumption and cost somewhere else in the stack. The implication is that AI spending has to be assessed across the whole environment before the next commitment, not tool by tool.
SpendHound research setting out five things IT leaders should consider before committing to their next AI investment, aimed at a technical buying audience rather than the procurement audience most of the other posts address.
Peer data is the answer when AI questions outnumber answers
The premise is that organizations currently have more AI questions than answers, which is why peer insights and benchmarks carry weight.
Read more
The response is survey-backed research rather than vendor claims, giving buyers a picture of how comparable organizations are actually behaving on budgets, governance, and return.
An AI Spend Report covering how 172 finance and procurement leaders approach AI budgets, vendor management, governance, and ROI.
Show up where procurement teams gather, and attach the cause to the booth
A standing priority is physical presence at procurement events, with the pricing demo as the draw and a charitable or giveaway mechanic attached to the presence.
Read more
The same posts document an event-heavy working rhythm — a nor'easter, a conference in Boston, an onsite in New York in one week — and name the SpendHound marketing team behind it, which shows how the research and event calendar feed each other.
SpendHound at Booth 403 at ProcureCon East, comparing attendee SaaS, AI, and Cloud pricing against benchmarks across more than 10,000 vendors, with SpendHound and the conference matching donations raised during the event for the Alliance of Therapy Dogs, plus a YETI cooler and StubHub tickets giveaway.
This is the clearest statement of the problem the creator's data set exists to solve: you cannot negotiate software or AI pricing if the vendor publishes nothing and you have no comparison group.
Read more
A newcomer gets both the premise and the product logic in one post.
The post opens with a flat claim: OpenAI Enterprise has no published price list, and every contract is built from scratch, so licenses, committed usage, and API consumption are negotiated deal by deal.
Martins' point is that two similarly sized companies can sign very different agreements depending on deployment size and how the deal is structured.
Most teams, the post says, arrive at renewal anchored either to the wrong number — a per-seat figure or something heard secondhand from a peer — or to no anchor at all.
The fix it proposes is knowing what comparable organizations actually pay, and it shows a SpendHound peer benchmark placing a customer's pricing against similar deals.
A linked guide covers average ChatGPT costs by company size and what drives the gap.
For brands planning a campaign
The strongest hook for a benchmark report or webinar.
The negotiated-pricing premise is specific and gives a procurement audience a concrete reason to bring real numbers to a session rather than listen to general advice.
Note that the actual benchmark figures sit in a platform view and a guide outside the retained evidence.
This is the recurring argument in miniature: AI value should be judged on work shifted, not jobs removed.
Read more
A reader who wants to know what this creator argues about AI spending will find the thesis here first.
The post puts two survey results side by side and lets the contrast do the work: 6% of finance and procurement leaders say AI has reduced finance headcount, while 37% say it has let them move employees to higher-value work.
Martins calls the gap interesting and says it opens new ways to think about AI's return, then points to an article covering four questions every finance leader should ask to assess AI value.
The numbers are in the post; the four questions are not.
For brands planning a campaign
A natural co-marketing angle on measuring AI ROI, and the headcount-versus-redeployment contrast is quotable. The four-question framework would need to be sourced from the linked article before it can anchor a webinar, since the retained post does not contain it.
It shows how this creator's benchmark data travels: not only as reports, but embedded in another procurement product.
Read more
That is the practical answer to how a brand would actually work with them.
The post leads with a figure — mid-market companies overspend 20 to 30 percent on software — and reframes it as a timing problem rather than only a visibility problem, because pricing data that arrives after a contract is signed cannot change the price. It then describes a partnership with Zip that puts SpendHound benchmarks directly inside Zip's procurement workflow, sourced from a 10,000+ vendor dataset based on what 1,500+ companies actually pay, with coverage starting on the highest-spend software categories.
For brands planning a campaign
Direct precedent for the proposed collaboration — a data partnership placed inside a procurement platform's workflow, not just a one-off content swap. Useful when scoping a benchmark report: the terms described here (vendor dataset size, number of contributing companies, category coverage) are the kinds of specifics a partner would need to agree on.
It identifies the survey asset and the size of the audience this creator can convene on AI spending questions — the population a research-led campaign would be built around.
Read more
A short post built on a premise rather than a finding: everyone has more AI questions than answers, which is exactly why peer insights and benchmarks matter.
It points to an AI Spend Report drawn from 172 finance and procurement leaders covering how they approach AI budgets, vendor management, governance, and ROI.
The post is a pointer; the substance is in the report itself.
For brands planning a campaign
The report is the reusable asset.
A co-branded follow-up survey or a session walking through the findings is the obvious extension.
Anything built on the specific numbers would need the report itself, which is not in the retained evidence.
It widens the picture of who this creator writes for.
Read more
The procurement angle is obvious; this shows the same cost-control argument being pitched to IT buyers, with costs treated as system-wide rather than per-tool.
The post frames IT as caught between two jobs: enabling AI adoption and managing complexity that moves faster than budgets.
New capabilities overlap and arrive quickly, usage and costs scale unpredictably, and one new AI tool can push up consumption somewhere else in the stack.
It points to SpendHound research listing five things IT leaders should consider before committing to their next AI investment.
The five items are not in the post.
For brands planning a campaign
Broadens a collaboration's audience beyond procurement. The argument that AI spend leaks across the stack is a specific, testable webinar topic, though the five considerations would need to be pulled from the linked research.
It shows the event-marketing style in one short post — what a booth is used for, how the team talks to attendees, and how a partner or cause gets attached to the presence.
Read more
An event post: SpendHound at Booth 403 at ProcureCon East, showing how SaaS, AI, and Cloud pricing compares against benchmarks across 10,000+ vendors, with SpendHound and the conference matching donations raised during the event for the Alliance of Therapy Dogs, plus a YETI cooler and StubHub ticket giveaway. It records how the team runs an in-person presence: a benchmark demo at the booth, a cause tie-in, and a draw.
For brands planning a campaign
If the collaboration has an event component, this is the template already in use: a live benchmark demo plus matched charitable giving. It is a useful reference when deciding what a partner gets at a booth versus in a report.
It shows the team behind the benchmark content, how the event calendar drives the work, and how Martins writes about colleagues, which matters for judging tone in a co-marketing arrangement.
A personal recap: a week that started with a nor'easter, moved through ProcureCon US East in Boston, and ended with a YipitData onsite in New York. Martins names members of the SpendHound marketing team — Sam Voshall, Emily Jeffords, Xanthe Hsu, Sarah Reece — and notes colleagues and contractors not pictured, describing the building of the marketing organization at SpendHound as one of the hardest and most rewarding professional efforts so far.
For brands planning a campaign
Signals the team and cadence around events and onsites, which matters if a partner wants named people and follow-through rather than a single deliverable. It also indicates the marketing function is newly built and openly staffed, so a new collaboration would land with a small, active group.
Rebecca Martins frames mid-market software overspending as a timing problem: companies overspend 20 to 30 percent and usually find out at renewal, when there is no leverage left.
Read more
The approach is peer benchmarking — SpendHound data drawn from a 10,000+ vendor dataset based on what 1,500+ companies pay — delivered inside Zip's procurement workflow so the pricing view arrives before the contract is signed.
Peer benchmark data placed inside a partner's procurement workflow rather than reported after the fact.
For brands planning a campaign
A joint webinar or benchmark report on software spend is a direct extension of work already being published; the strongest angle is pre-renewal timing, since that is the gap Rebecca Martins keeps naming.
Using OpenAI Enterprise as the example, Rebecca Martins notes there is no public price list and that every contract is negotiated deal by deal, so two similar-sized companies can end up with very different agreements.
Read more
The stated failure mode is showing up to renewal anchored to the wrong number — a per-seat figure or a peer's secondhand number — or with no anchor at all, and the recommended fix is knowing what comparable organizations actually pay.
Vendor-by-vendor pricing analysis backed by a peer benchmark view inside the SpendHound platform.
For brands planning a campaign
A vendor-pricing teardown or an anonymized 'what peers actually pay' dataset is a format already in use and would carry a co-marketing partnership without inventing a new one.
Rebecca Martins highlights the gap between the replacement narrative and what leaders report: 6 percent of finance and procurement leaders say AI has reduced finance headcount, while 37 percent say it moved employees to higher-value work.
Read more
The piece turns that into four questions every finance leader should ask to assess AI value.
For brands planning a campaign
An AI ROI benchmark report or webinar aimed at finance leaders fits the audience and framing Rebecca Martins already writes for, and the four-question structure could anchor the session.
Rebecca Martins describes IT teams as being asked to enable AI adoption while capabilities emerge and overlap quickly, usage and costs scale unpredictably, and one new AI tool can raise consumption and costs elsewhere in the stack.
Read more
The response is a set of five considerations for IT leaders before committing to their next AI investment.
Checklist-style guidance drawn from SpendHound research and aimed at a technical buying audience.
For brands planning a campaign
A technical-audience session on AI cost control and stack-wide consumption is well matched to the IT-facing material, and gives a second audience beyond finance and procurement for the same collaboration.
Rebecca Martins positions peer insights and benchmarks as the answer to the open AI questions organizations currently have, pointing to an AI Spend Report covering how 172 finance and procurement leaders approach AI budgets, vendor management, governance, and ROI.
Read more
Survey of 172 finance and procurement leaders reported as a benchmark publication.
For brands planning a campaign
A co-branded benchmark survey is the highest-leverage collaboration here because the format is already established; the 172-leader sample gives the resulting report a credibility figure to cite.
Rebecca Martins documents a week moving from a Nor'easter into ProcureCon US East in Boston and a YipitData onsite in New York, and promotes a SpendHound booth at ProcureCon East with a charity match for the Alliance of Therapy Dogs and a YETI cooler and StubHub tickets giveaway under the ProcureCon procurement hashtag.
Read more
The same posts introduce the SpendHound marketing team by name and role.
In-person conference booths, giveaway mechanics, and matched charitable fundraising paired with public team introductions.
The team names and roles in the conference post describe SpendHound's marketing organization; they are not evidence of Rebecca Martins' own seniority or scope beyond the posts.
For brands planning a campaign
A procurement-conference sponsorship or booth collaboration is a low-friction route into the audience, and the charity-match mechanic is an existing template a partner could join.
Rebecca Martins' documented brand relationships run through SpendHound, the software-spend benchmarking company where she states she leads marketing.
Read more
Her posts name SpendHound as her employer and describe the team she built there.
The commercial partnerships visible in the material — a benchmark integration with Zip and a conference presence at ProcureCon US East — are presented as SpendHound's, with Martins' personal role unstated.
Mentions of vendors such as OpenAI and ChatGPT appear as subjects of SpendHound pricing research, not as relationships.
SpendHound
Employment
Martins states that she leads marketing at SpendHound, calling it "my SpendHound marketing team" and describing the work of "building the marketing organization and motion at SpendHound" as one of the hardest and most rewarding things she has done professionally.
Read more
SpendHound's software-spend benchmarking platform is the source of the pricing data she posts about.
SpendHound exhibited at ProcureCon East at Booth 403, showing benchmark comparisons across 10,000+ vendors, with SpendHound and the conference both matching donations raised at the event for the Alliance of Therapy Dogs.
Read more
The post describes an event presence; no sponsorship, fee, or contract is stated.
Rebecca Martins posts from inside a software spend management company (SpendHound), which shapes what is worth following.
Read more
Three strands run through the work.
Pricing evidence is the first: peer benchmarks on what companies actually pay for SaaS, AI, and cloud, including an integration that places those benchmarks inside a procurement workflow so the price picture arrives before a renewal is signed.
AI economics is the second: survey findings on whether AI cuts finance headcount or moves people to higher-value work, four questions finance leaders should ask to judge AI ROI, five things IT leaders should weigh before the next AI commitment, and an AI Spend Report covering budgets, vendor management, governance, and ROI.
Where the work gets shared is the third: procurement conferences, booth activity, charitable fundraising, and the benchmark reports the posts point to.
A reader new to the name should start with the OpenAI Enterprise post, which gives the clearest worked example of negotiated, list-price-free contracts and the wrong-anchor failure at renewal, then read the Zip partnership post for how timing changes the outcome, then follow whichever thread matters more — benchmark data or AI cost and return.
Both publish survey-backed pricing research for B2B software buyers.
Read more
Rivera reports that 68 percent of AI buyers rank predictable total cost as their top pricing priority and that buyer priorities shift by company size, drawing on hundreds of buyer responses; Rebecca Martins reports benchmark pricing based on what more than 1,500 companies pay and an AI Spend Report built on 172 leader responses. The shared idea is that peer and benchmark data, not vendor claims, is what makes an AI or software purchase defensible to the finance function, and both write in short, question-led posts that end by asking the reader to test their own position.
Rivera writes for the selling side: usage-based pricing models, whether a buyer can estimate a bill before signing, what happens when usage spikes, and whether the metric tracks customer value.
Rebecca Martins writes for the buying side — finance, procurement, and IT — on benchmarking what peers pay and getting that number before a renewal is signed.
Rivera's frame is the pricing design a CFO can defend; Rebecca Martins's frame is negotiation timing and spend-category control inside a procurement workflow.
Portnoy argues that partnerships leaders will not get executive funding until the function tracks the numbers a CFO already expects — win rate, sales cycle, ACV, cost per dollar sourced — and Rebecca Martins makes the equivalent argument about procurement pricing data that must arrive before the contract rather than at renewal. Both write short posts built on conversations with executives (Portnoy at a GTM conference, Rebecca Martins at procurement events and in survey reports) and both frame the same gap: decision-makers will not invest in something they cannot model.
Portnoy's subject is partner-led revenue and making a channel forecastable, and the answer offered is an agentic playbook for partner teams.
Rebecca Martins's subject is software and AI spend, and the answer offered is peer benchmark data embedded in procurement tools.
A reader following Portnoy gets channel and partnerships strategy; following Rebecca Martins gets pricing and procurement economics.
Both write short, concrete posts for procurement teams about treating a spend category as serious money rather than an operational afterthought.
Read more
Dorban's case is workforce accommodation: centralising the spend creates savings before anyone counts the hours lost to searching, rebooking, and fixing problems.
Rebecca Martins's case is SaaS, AI, and cloud: overspending of 20 to 30 percent goes unnoticed until renewal, and benchmark data is what makes the category visible.
Both use a single cause-and-effect claim per post and define the problem in procurement's own terms.
Dorban writes from the operational side of procurement about a moving requirement — fixed rates and defined volumes that fail when project dates or headcount change — so the remedy is contract structure. Rebecca Martins's remedy is pricing evidence and pre-renewal timing, with data drawn from more than 10,000 vendors, and the argument moves between procurement, finance, and IT audiences rather than staying with procurement practitioners.
For a co-marketing webinar or benchmark report on software spend and AI ROI, the evidence points to a small, clearly professional LinkedIn audience rather than a measured one.
Read more
The supplied account record shows 3,438 followers as of 8 October 2026, and every reviewed post is written for people who buy, renew or govern software and AI tools — finance, procurement and IT roles.
That is a reasonable topical match for the brief.
What the packet does not contain is any measured audience composition: no geography, seniority, industry, employer-size or engagement breakdown.
A buyer can treat the follower figure as an indication of reach inside a niche professional following, not as proof of who is listening.
What the posts establish is who the content is aimed at, which is a weaker claim than who actually reads it.
Selected examples: a September 2026 post contrasts the 6% of finance and procurement leaders who say AI has reduced finance headcount with the 37% who say it freed staff for higher-value work, and links to an article on measuring AI ROI; a post aimed at IT leaders lists five things to weigh before the next AI investment; one reports peer benchmarks drawn from 172 finance and procurement leaders on AI budgets, vendor management, governance and ROI; another explains why OpenAI Enterprise pricing is negotiated deal by deal and why renewal anchors matter.
Two posts show the same buyer world in person — a ProcureCon East booth at Booth 403 promoting SaaS, AI and cloud price benchmarking across 10,000+ vendors, and a week that took in ProcureCon US East in Boston, an on-site at YipitData and a SpendHound marketing team introduction.
Post titles and links show intended audience and subject matter; they do not measure audience make-up, and no supplied post reports impressions, reactions or comments.
A concrete next step before committing to a joint webinar or benchmark report: ask for audience research that speaks to professional attributes — a reader or attendee survey, registration data from the events above, or any other documented source showing job function, seniority, company size and region.
Platform follower demographics, if an export exists, would answer geography, age and gender but would not verify employer, occupation or seniority.
Alongside that, request recent engagement figures for spend-benchmark and AI-ROI posts so the two sides can judge likely attendance and response before building the collaboration.
LinkedIn followers
3,438
LinkedIn profile account record for linkedin.com/in/rebecca-martins-3731538, supplied in the source packet · 2026-10-08
The reviewed material documents no partnership or sponsorship formats offered by Rebecca Martins in her own name.
Read more
The collaboration activity it describes belongs to SpendHound, the software-spend benchmarking company where she leads marketing: benchmark data embedded in the procurement platform Zip's workflow, and a booth presence at ProcureCon East paired with a matched charity fundraiser for the Alliance of Therapy Dogs.
Her visible role in that work is editorial and promotional, writing and sharing SpendHound research such as the AI Spend Report, the ChatGPT pricing guide, and an analysis of how finance teams measure AI return.
No media kit, rate card, sponsorship policy, or partnership contact appears anywhere in the reviewed posts.
That is an absence in this evidence, not a finding that she never accepts sponsorship.
The practical consequence for a buyer weighing a co-marketing webinar or benchmark report on software spend and AI ROI is that the shape of any collaboration would have to be settled with SpendHound rather than as an independent creator deal, and nothing in the reviewed material states those terms.
A useful next research step is to check SpendHound's own site for a partner or media page, since the company-level route is the one this evidence points to.
Strong fit, with the commercial route and the audience numbers still to be confirmed.
Read more
Brief
A B2B SaaS procurement or spend-management platform wants a co-marketing webinar or benchmark report on software spend and AI ROI, aimed at finance and procurement buyers.
Reasons
The proposed subject is already the work. Across the reviewed posts, Rebecca Martins publishes exactly this material: why mid-market companies overspend 20–30 percent on software and usually discover it at renewal, when there is no leverage left; why OpenAI Enterprise has no published price list and every contract is negotiated deal by deal; and why the fix is knowing what comparable organizations actually pay.
There is a repeatable research asset to build on. A SpendHound AI Spend Report draws on 172 finance and procurement leaders covering AI budgets, vendor management, governance and ROI — the same survey-plus-report format a joint benchmark study would use, with a credibility figure already attached to the approach.
There is a working template for a data partnership. The Zip collaboration put SpendHound benchmarks inside a procurement platform's workflow, sourced from a 10,000+ vendor dataset based on what 1,500+ companies pay, starting with the highest-spend software categories. That is a closer precedent for this brief than a one-off content swap, because it shows how a partner's product and the benchmark data were joined.
The AI ROI framing is already written for the buyer. The contrast between the 6 percent of finance and procurement leaders who say AI cut finance headcount and the 37 percent who say it moved people to higher-value work, turned into four questions for finance leaders to assess value, gives a webinar a ready-made opening argument. A separate post addresses IT leaders weighing their next AI investment, where usage and costs scale unpredictably and one new tool raises consumption elsewhere in the stack — a second audience segment for the same session.
Distribution beyond the report exists. A ProcureCon East booth demonstrated how the team runs an in-person presence: live benchmark comparisons across 10,000+ vendors, a matched charity fundraiser, and a giveaway. The week around it took in ProcureCon US East and a client onsite in New York. If the collaboration has an event component, the mechanics are already in use.
Checks
The reviewed following is 3,438 on 8 October 2026, and no audience breakdown by job function, seniority, employer size or region is measured. Before committing to a joint webinar, ask for attendee or reader data, event registration figures, or a documented audience survey.
No engagement figures for the benchmark or AI-ROI posts were supplied, so likely attendance and response cannot be judged from this evidence.
The reviewed material documents no partnership or sponsorship formats offered by Rebecca Martins in her own name; the visible collaborations are SpendHound's. Any terms would be settled with SpendHound, and nothing in the reviewed posts states them.
When to choose a specialist
Poor fit on this evidence. The mismatch is in reach, audience and commercial route, not in writing quality.
Read more
Brief
A brand outside the software-buying world — for example a consumer app or a general-interest technology brand — wants a broad-awareness, high-reach creator campaign with guaranteed impressions and paid placements across video, audio and social formats.
Reasons
The reviewed material shows a narrow professional readership, not a mass one. Every reviewed post is written for people who buy, renew or govern software and AI: finance and procurement leaders, IT leaders, and procurement conference attendees. A campaign whose value depends on scale among a general audience has nothing here to stand on.
Reach evidence is thin and unmeasured. The account record shows 3,438 followers as of 8 October 2026, with no impressions, reactions, comments or engagement rates in the packet. Promising guaranteed impressions would mean guessing.
There is no documented commercial vehicle for an independent creator deal. The reviewed posts contain no media kit, rate card, sponsorship policy or partnership contact; the collaboration activity they describe — the Zip benchmark integration, the ProcureCon East booth and charity match — belongs to SpendHound. A brand expecting a self-serve creator placement would be negotiating with an employer's marketing function instead.
No video, audio or transcript assets appear in the reviewed evidence. A brief built on video or podcast deliverables cannot be assessed from post text alone.
The AI and software-cost arguments depend on benchmark data and research reports. A general-awareness brief would strip out the peer-comparison substance that makes the content distinctive and leave only slogans.
Checks
Do not read the absence of a media kit in these seven posts as a finding that Rebecca Martins never accepts sponsorships. It is an absence in the reviewed material.
If a broader-reach campaign is still of interest, request platform demographics and engagement data first, and establish whether the collaboration must run through SpendHound.
A worked campaign example
Angle
"There is no price list" — a co-branded renewal-anchor benchmark report and webinar that gives finance and procurement teams a peer number to bring into software and AI negotiations.
Gaps to close before building
The actual benchmark figures, the report bodies, the guide on ChatGPT pricing, and the four AI-ROI questions are referenced in posts but not present in the reviewed evidence. They must be obtained before the report leans on them.
No partnership terms, rate card or contact route exist in the reviewed material; the commercial shape has to be settled with SpendHound, and this brief cannot assume an independent creator arrangement.
Audience composition and engagement data are unmeasured, so registration and attendance targets need an agreed baseline rather than a projection from the 3,438-follower figure.
Why this angle
The reviewed posts supply the premise, the audience and the format. The OpenAI Enterprise post states that no public price list exists, that contracts are negotiated deal by deal, and that teams arrive at renewal anchored to a per-seat figure or a secondhand peer number, or to nothing at all. The mid-market post states the stakes — 20–30 percent overspend, discovered at renewal — and frames it as a timing problem rather than only a visibility problem. The AI Spend Report shows that a survey of finance and procurement leaders is an established output here, not an invention for this campaign.
Worked plan
Research input: run a joint survey of finance, procurement and IT leaders on what they pay for high-spend software categories — SaaS, AI and cloud — and what anchor they used at their last renewal. The 172-leader AI Spend Report is the closest existing model for scope and reporting.
Report: a co-branded benchmark publication showing anonymized price bands by company size and category, with the OpenAI Enterprise example opening it as the case where no list price exists and peers are the only anchor.
Webinar: a 45-minute session split into two buyer views already present in the content — a finance segment on measuring AI return using the headcount-versus-redeployment contrast and the four questions finance leaders should be asking, and an IT segment on AI cost governance, where one new tool raises consumption elsewhere in the stack.
In-product placement: model distribution on the Zip integration by placing the benchmark view inside the partner platform's procurement workflow, so pricing data arrives before the contract is signed. Coverage should start with the partner's highest-spend categories, as that partnership did.
Event option: if the collaboration includes a conference, reuse the booth format — live benchmark comparisons, a matched charity element, a draw — with the report findings as the booth demo.
Roles: Rebecca Martins' team supplies the research and the vendor benchmark dataset described in the posts; the partner supplies distribution to its procurement customer base and the product surface for the embedded benchmark view.
Measurement to agree up front: survey completions, report downloads, webinar registrations and attendance against the prior SpendHound survey baseline, benchmark lookups inside the partner platform, and resulting pipeline.
Pick Marcos Rivera when the collaboration needs pricing-design help for a software vendor rather than a buyer-side view of what peers pay.
Read more
Rivera's posts work the vendor's problem.
One reports that 68% of AI buyers rank predictable total cost as their top pricing priority while only 19% care about a lower entry price, then argues that Atlassian's usage-based expansion leads with visibility and spend controls, and that making usage visible is not the same as making it predictable.
It closes with three questions any vendor shipping a usage-based model has to answer: can a buyer estimate the bill before signing, what happens when usage spikes, and is the metric tracking customer value or infrastructure cost.
A second post splits the same issue by company size, with 77% of companies under $50M ranking predictable total cost in their top three against 63% above $1B, while ease of justifying spend to Finance and the CFO climbs from 44% to 55%.
If the partner is a software company deciding how to price or meter AI features, Rivera's survey data and 480+ cited pricing engagements answer the question the campaign is actually asking.
The buyer rotates from procurement to the vendor's pricing and finance team, and the deliverable changes.
Rivera's material is survey evidence used to advise sellers on how to structure a price, drawn from 292 B2B software buyer responses in one post and 296 in the other, built with Benchmarkit.
Rebecca Martins's material is the mirror image: what comparable organizations actually pay, anchored by vendor benchmarks covering 10,000+ vendors based on what 1,500+ companies pay, plus renewal leverage before a contract is signed.
A partner selling procurement software to finance buyers would get a pricing-strategy session from Rivera, not a peer price band it can hand to a customer.
Pick Greg Portnoy when the campaign goal is partner-led revenue instead of procurement spend.
Read more
His posts address the same underlying problem in a different budget line: executives want to fund channels they can model.
One reports asking dozens of CEOs, CROs and CMOs at GTM2026 what would make them invest more in partnerships, and finding that most believe partnerships can work but hold back because they do not know what good looks like.
Portnoy locates the gap in data, listing ROI, framework, performance and benchmarking data as missing, and calls on partnerships leaders to track win rate, sales cycle, ACV and cost per dollar sourced.
The other post previews a Pavilions GTM Conference talk on an agentic playbook for predictable partner revenue, on the argument that partner-led deals carry higher win rates, lower CAC and better retention, but no CFO funds something they cannot model.
The format transfers well to a survey-based benchmark and a conference webinar, so the briefing structure used for Rebecca Martins can be reused.
If the partner sells partner-management or channel software, Portnoy is the closer match.
The spend category, the audience and the data asset all move.
Portnoy is addressing partnership and channel leaders and their executive sponsors; the benchmark brief is aimed at finance and procurement buyers deciding what to pay for software and AI.
His evidence is qualitative, from an executive interview round, and names the metrics partnerships teams should collect rather than supplying a vendor pricing dataset.
A campaign built on peer price bands would have to source that data elsewhere, and the working template for embedding benchmarks in a procurement platform has no equivalent in these posts.
Pick Greg Dorban when the collaboration is about a specific indirect category where standard procurement practice breaks down, such as workforce accommodation, travel or temporary housing.
Read more
One post argues that a procurement process can be run well and still produce a bad accommodation outcome: fixed rates, defined volumes, clear milestones and tight contract terms are all sensible until project dates move, headcounts change and the priced accommodation is no longer available.
Dorban's conclusion is that the fault is not procurement but the application of a fixed procurement model to a moving requirement.
The other post describes more procurement teams taking control of workforce accommodation because of the hard cost on the table, with centralised spend creating savings before counting the hours lost to searching, changing bookings and fixing problems, and treats accommodation as a serious spend category at scale.
Choose Dorban when the partner's product governs travel or accommodation spend, or when the session is about adapting procurement models to volatile demand.
The subject narrows to one operational services category.
Dorban's posts carry no software, AI or cloud pricing material, no peer benchmark dataset, and no AI return-on-investment research, so the central asset in the Rebecca Martins brief, anonymised price bands for high-spend software and AI, would have to be built from nothing.
His argument is also category-governance rather than vendor negotiation: it explains why a fixed model fails against a moving requirement, not what a buyer should expect to pay or how to anchor a renewal.
This profile draws on seven LinkedIn posts published from Rebecca Martins's account, including two addressed to specific buying groups: a set of four questions for finance leaders assessing AI value, and five considerations for IT leaders weighing a next AI investment.
Also reviewed were posts on negotiated enterprise pricing for OpenAI, a SpendHound benchmark integration with Zip, an AI Spend Report built on responses from 172 finance and procurement leaders, and a ProcureCon East booth appearance.
The account was observed on 8 October 2026, when it showed 3,438 followers.
Several works the posts point to — the ChatGPT pricing guide, the AI Spend Report, the article on measuring AI ROI, and the IT investment guidance — were not supplied as full text, so their frameworks and figures are treated as gaps rather than summarized.
No engagement statistics, audience breakdown, media kit, or partnership terms appeared in the reviewed material, and none was sought elsewhere.
Comparisons with other creators rest on retained posts from three LinkedIn accounts supplied alongside this one.
The reviewed material documents no signature book, show, or earlier body of work, so the profile does not claim one.
Recent engagement
Across their last 6 LinkedIn posts, the median post got 22 reactions and 4 comments. Checked 2026-11-02.
