Skip to main content
SaaS Directory Info

Reference edition 2026.47

Sign in

What Belongs on a SaaS Fact Sheet

Reference · 9 min read ·

The fields a software-as-a-service fact sheet should carry, how to word each one precisely, and which gaps make buyers and AI assistants distrust a page.

Illustration: A clean reference-handbook page with a muted teal header band and a two-column specification table, footnote numbers in the margin, technical sans-serif labels

A fact sheet is the most useful page a software company can publish and one of the least often written well. Buyers want to compare tools quickly. Reviewers want to check a claim without emailing sales. Search engines and AI assistants want to lift a clean statement and repeat it. A good fact sheet serves all three because it does one thing: it states what is true, in a form that can be checked.

This guide lists the fields a software-as-a-service fact sheet should contain, explains how to word each one, and shows where vague wording causes trouble. It is written as a handbook entry, so you can work through it with your own product open beside it.

What a fact sheet is and is not

Software as a service, in the usual definition, is software that a provider hosts and customers use over the internet, normally on a subscription. That definition matters because it tells you which facts a buyer cannot see for themselves. They cannot inspect the servers. They cannot read the code. They cannot watch how the provider treats data. They are relying on what the provider says, so the provider's statements carry unusual weight.

A fact sheet is not a brochure. A brochure persuades; a fact sheet informs. The tone is flat on purpose. Where a brochure might say "enterprise-grade security", a fact sheet says which controls exist, which independent reports have been issued, and where the buyer can read them. If a statement cannot be followed by a link, a date or a named document, it probably belongs in the brochure instead.

A fact sheet is also not your documentation. Documentation explains how to use the product. The fact sheet sits above it, summarising scope and pointing down into the detail.

The eight blocks

Most software products can be described completely in eight blocks. Keep each block separate, give it a heading, and keep one fact per line.

1. Identity

State the product name, the legal entity that operates it, the country of registration, the year the product first became available to customers, and a contact route. Use the registered company name exactly as it appears on the official register, because mismatches between a trading name and a legal name are one of the first things a careful buyer notices. Add the product's own web address and, where it exists, the public documentation address.

2. What it does

Write one sentence that names the user, the job and the category. For example: "A scheduling tool for small clinics that books appointments, sends reminders and exports calendars." Then give three to six capability lines, each starting with a verb. Avoid adjectives. "Imports contacts from spreadsheets" is a fact; "powerful import" is an opinion.

Schema.org defines a vocabulary for exactly this kind of description. Its SoftwareApplication type has properties for the application category, operating system, offers and more. You do not have to mark up your sheet to benefit from the discipline, but doing so forces you to decide what the single correct value of each field is.

3. Pricing model

Describe how you charge, not what you charge. Say whether the price is per user, per usage unit, per workspace or flat; whether a free tier or trial exists; whether billing is monthly, annual or both; and where the live price list lives. Link to it. This keeps the sheet true when a price changes, which is the point.

4. Integrations

List each integration once, with its type: native, built on the public interface, or through a third-party automation service. Say whether it is two-way. A separate guide on this site covers integration documentation in detail; for the sheet itself, a short table with name, direction and link to setup instructions is enough.

5. Security and compliance

List what you hold, with dates. If you have an independent audit report, name the framework, the type of report and the period it covers. If you do not hold a certification, do not imply it; instead list the controls you operate, such as encryption in transit, single sign-on support and role-based access. Link to the page where a buyer can request the report.

6. Hosting and data

Say where customer data is stored, which infrastructure provider hosts it, whether customers can choose a region, and how long data is retained after account closure. These are among the questions procurement teams ask first, and an unanswered one often ends the conversation.

7. Support and limits

State support channels and hours, the response targets you actually meet, and the main technical limits: rate limits on the public interface, maximum file sizes, user caps by plan. A limit that is documented is a fact; a limit discovered in production is a complaint.

8. History and status

Give a link to the changelog, the status page and the roadmap if you publish one. Add the date the sheet was last reviewed. That last line is small but it is the most trusted element on the page, because it tells the reader how old the facts might be.

Wording rules that make facts checkable

Good wording has a few habits.

  • One fact per line. "Hosted in the EU and UK with daily backups retained for a month" is three facts. Split it.
  • Name the unit. Say "per user per month" rather than "per seat".
  • Use dates, not "recently". "Audit report period ended in March" can be checked; "recent audit" cannot.
  • Say what is not offered. "No on-premises edition" saves a buyer a call and shows confidence.
  • Avoid superlatives. "Fastest", "most secure" and "best" have no verifiable meaning.
  • Link every claim that has evidence. The link is the proof.

Google's guidance on helpful content asks authors to show who is behind a page and how they know what they claim, and to provide original, substantial information rather than a summary of other pages. A fact sheet that cites its own documents does this naturally.

A worked example

Suppose a team builds a small invoicing product. Their first draft of the security block reads: "Bank-level security keeps your data safe." There is nothing wrong with the intent, but nothing in it can be checked, and an assistant asked "does this product encrypt data" cannot find a clear answer.

A revised block reads:

  • Data in transit: encrypted using current transport security.
  • Data at rest: encrypted by the hosting provider's storage service.
  • Authentication: password plus optional second factor; single sign-on on higher plans.
  • Independent audit: none held at the time of review; a security questionnaire is available on request.
  • Last reviewed: the date of the check.

The revised block is less impressive and more useful. Buyers who need an audit report will move on quickly and politely; buyers who only need the basics will trust the rest of the page more because it is candid about the gap.

Common mistakes

Copying the homepage. If the sheet repeats the homepage in a different layout, it is not adding facts. Remove every sentence that has an adjective in it, then see what is left.

Burying facts in images. Specification tables saved as pictures cannot be read by crawlers or assistive technology. Use real tables and real text.

Listing planned features as existing ones. Put planned items in a clearly labelled roadmap section with no dates you cannot keep.

Ignoring the second reader. Besides the human, a machine reads your page. Structured data, clear headings and one value per field help both. Google documents how structured data helps its systems understand a page, and it recommends keeping the markup consistent with what the page visibly says.

Never reviewing. The sheet drifts quietly. Add a recurring reminder to review it, and make one named person responsible.

Keeping the sheet and the listing consistent

If your product is listed on a directory, the listing and the fact sheet should say the same things. Use the same category, the same one-line description and the same pricing-model wording. Where a directory lets you describe your pricing, link to your live pricing page instead of repeating figures. On this site, the submit page starts a listing whose core fields you edit from your account, the categories page shows where the listing will appear, and the developers page describes the free interface for reading listings in your own tools. When a buyer sees the same facts in three places, each place is more believable.

Putting it into practice

  1. Open your homepage and highlight every sentence that contains a claim.
  2. For each claim, decide whether it is a fact, an opinion or a promise.
  3. Move the facts into the eight blocks and attach a source.
  4. Delete or relabel the opinions and promises.
  5. Add the review date and a named owner.
  6. Ask someone outside the team to answer five buyer questions from the sheet alone. Where they hesitate, add the missing field.

The exercise usually takes an afternoon and leaves you with a page that your sales team will start sending to prospects unprompted. It also produces something every comparison site and assistant can quote without paraphrasing, which means fewer errors about your product in the places you do not control.

Summary

A SaaS fact sheet earns trust by being checkable. State identity, function, pricing model, integrations, security, hosting, support and history, each in plain flat language with a source. Describe the model and link to live prices rather than typing numbers. Mark the review date. Keep the sheet consistent with every listing that mentions you, and review it on a schedule. The result is small, unglamorous and exactly what the people who decide whether to try your product are looking for.

Questions and answers

What is a SaaS fact sheet?
A short, structured page that states the checkable facts about a software product: what it does, who makes it, how it is priced, where data is hosted, what it integrates with and how it handles security.
How long should a fact sheet be?
As short as the facts allow. A good sheet fits on one screen per topic, uses tables for specifications and links each claim to a longer page or document.
Should a fact sheet include prices?
It should describe the pricing model and link to the live pricing page. Typing a figure into a fact sheet creates a second copy that will go out of date.
Why do AI assistants care about fact sheets?
Assistants quote what is easy to extract and unambiguous. Labelled fields with one value each are far more likely to be repeated correctly than prose that mixes facts with marketing.
How often should it be reviewed?
Whenever a fact changes, and on a fixed schedule even when nothing seems to have changed, because quiet drift is the commonest cause of stale specifications.

Sources

Related guides

Questions?