Skip to main content
NoSaveNoPay
About NoSaveNoPay How it works Methodology Pricing Authors Offices

Fort Lauderdale HQ · New York · London · Stockholm

Pricing
Get free estimate
Editorial Standards · Updated June 2026

Editorial Standards & Corrections Policy

What we publish has to be trustworthy. Our readers make multi-million-dollar contract decisions on the strength of it. This page sets out exactly who writes our content, how we research and source it, who reviews it, how we keep it current, and how we correct it when we get something wrong.

It complements our savings methodology, our About page, and our author profiles. If you spot an error, we want to hear about it — see the corrections policy below.

Who writes our content

Every article on this site is bylined to a named, real author — never an anonymous "admin" or "staff" account. Our authors are former vendor-side executives and negotiators who have sat on the other side of the table at companies like Oracle, Microsoft, SAP and the major cloud providers. Each author has a dedicated profile listing their role, areas of expertise, years of experience and a link to their LinkedIn profile. You can see them on the authors page.

We assign topics to the author whose hands-on background fits the subject. Cloud and Microsoft EA topics are led by our cloud practice; Oracle, SAP and audit-defence topics by the advisors who have run those negotiations. We do not put a generalist byline on specialist content.

How we research and source content

Our content is built from primary sources, not rephrased blog posts. In order of preference, we rely on:

  1. Vendor pricing and contract documents — published price lists, program terms, and the actual proposals and contracts we encounter in live engagements (used in anonymised, aggregate form only).
  2. First-hand negotiation experience — what we have personally seen work, and fail, across hundreds of enterprise software and cloud negotiations.
  3. Our anonymised engagement data — benchmark ranges drawn from comparable buyers, never tied to an identifiable client.
  4. Official vendor and primary-source references — where we cite a figure, term or rule, we point to the authoritative source.

Claims about savings, discounts and price increases are stated conservatively and framed as ranges, because every contract is different. We do not promise outcomes we cannot stand behind.

How content is expert-reviewed

Substantive guidance — anything a reader might act on in a negotiation — is reviewed by a named co-founder with relevant licensing expertise before and after publication. Where a page has been reviewed, the reviewer's name, role, credential and the review date are shown on the page itself (for example, "Last reviewed by Morten Andersen, Co-Founder & Head of Cloud Practice"). The reviewer is accountable for the accuracy of the guidance.

Editorial accountability for the site rests with the co-founders, Fredrik Filipsson (Co-Founder & Principal Advisor) and Morten Andersen (Co-Founder & Head of Cloud Practice).

How we keep content current

Enterprise software pricing changes constantly — new metrics, new AI add-ons, mid-year price rises. Stale advice is untrustworthy advice. So:

  • Every article shows a clear published date and a last-updated date.
  • Pricing and program pages are reviewed on a recurring cycle and after any material vendor change.
  • When we update a page, we revise the last-updated date and, where the change is material, note what changed.
  • Content that is no longer accurate is corrected or removed rather than left to mislead.

Accuracy and use of tools

We aim for content that is accurate, specific and free of errors. Where we use research, drafting or analysis tools in the production process, a qualified human author and reviewer verifies every published claim and is accountable for it. No page is published on the strength of an automated draft alone.

Independence, transparency and conflicts of interest

NoSaveNoPay is independent of the software vendors we write about. We take no commissions, referral fees, resale margin or sponsorship from any vendor. We are paid only by our clients, and only on a 25% gainshare of verified savings — if we save you nothing, you owe nothing. We have no incentive to favour one vendor over another, and our content is written accordingly. This site does not run third-party advertising and does not publish sponsored or affiliate content. If that ever changes, we will disclose it clearly and prominently.

Corrections policy

We correct errors openly. If you believe something on this site is inaccurate, out of date, or unclear:

  1. Email info@nosavenopay.com with the page URL and the specific issue (a source or document helps).
  2. We investigate every report. A named author or reviewer assesses it against primary sources.
  3. Where a correction is warranted, we update the page, refresh the last-updated date, and — for anything material — note what changed and when.
  4. We aim to acknowledge correction reports within two business days.

Spotted something we should fix?

Send us the page and the issue. A named author or reviewer will look into it and get back to you.

Report an Issue → Meet Our Authors

Editorial Standards FAQ

Who writes NoSaveNoPay content?

Every article is bylined to a named author and written by former vendor-side executives. Authors are listed on dedicated author pages with their role, expertise and LinkedIn profile.

Is the content expert-reviewed?

Yes. Substantive guidance is reviewed by a named co-founder with relevant licensing expertise, and the reviewer and review date are shown on the page.

How do I report an error?

Email info@nosavenopay.com with the page URL and the correction. We investigate every report and, where a correction is warranted, update the page and its last-updated date.

Is NoSaveNoPay independent of software vendors?

Yes. NoSaveNoPay takes no commissions, referral fees or resale margin from any software vendor. We are paid only by clients, on a 25% gainshare of verified savings.