Why a software company should publish its claim boundary
Marketing pages often collapse several different ideas into one sentence: an interface contains an export button, the export produces a file, the file conforms to a specification, and every retailer accepts every manuscript. Those are not the same claim. A product screenshot can demonstrate workflow and visible controls. A versioned output plus validator report can demonstrate properties of that sample. A customer case study can document one real production outcome. Only the platform decides whether a submitted title is accepted.
This register keeps those layers separate. Each capability lists the public evidence available, the statement that evidence supports, the boundary we will not cross, and the next stronger proof asset. That makes the website less reliant on unsupported superlatives and gives buyers a clearer basis for comparison. It also creates a product-marketing backlog: the missing evidence is visible instead of being papered over with copy.
What the current product images establish
The main application image shows a manuscript structure, an editing surface, and a composed book page within one desktop interface. That supports a direct claim that writing and page review coexist in the workflow. The interior-selection image shows a library of coordinated book designs. It supports the existence of multiple starting interiors. The protected download workflow and product copy document Windows, Apple Silicon Mac, and Intel Mac distribution targets.
These are meaningful buying facts because they distinguish Cambric’s local desktop model and integrated production view. They do not establish how every DOCX imports, how every font behaves, or whether an arbitrary illustrated manuscript passes a retailer. The purchase page says that plainly. A buyer gets a 30-day guarantee to test the actual workflow rather than being asked to treat a screenshot as proof of every possible result.
The evidence assets that matter next
The most valuable next asset is not another generic blog post. It is a versioned specimen package: a public test manuscript, import notes, screenshots of the composed result, the exported print PDF and EPUB, a PDF preflight record, and an EPUBCheck report. That package would let an author inspect the output and let technical reviewers reproduce the claims. A short screen recording would connect the input, edit, preview, and export stages.
The next layer is real customer evidence with permission: project type, manuscript constraints, workflow before Cambric, time or error reduction, released formats, and a public artifact where possible. We will not manufacture those stories. Until permission and evidence exist, the site should use product demonstration, transparent limitations, and the refund window instead of fake testimonials or anonymous numerical claims.
How this strengthens organic growth
Search engines and answer systems need stable, first-party facts they can retrieve and reconcile. A structured register with dates, explicit capabilities, and limitations is easier to cite than a collection of pages making inconsistent claims. It also reduces leakage on comparison pages: Cambric can argue from its own evidence rather than building the competitor’s feature narrative. The product remains the subject, and external platforms appear only where their submission rules define the buyer’s job.
Evidence also improves conversion quality. A high-intent visitor wants to know whether the tool runs on their computer, fits their kind of book, keeps control of the source, and produces the required output types. Answering those questions precisely is more persuasive than repeatedly saying “professional.” The register turns proof into an acquisition asset and gives future release work a clear place to land.