Our content is written and checked by a small team of product people and writers at Proposal Expert.
The content on Proposal Expert is written by a small team of product people and writers who work at Proposal Expert. We write from conversations with customers, from the anonymised aggregates in the Data Lab and from published research. Because the same team also builds the product, our guides describe how the tool actually works rather than how a tool should work in theory. Every step in a how-to has been walked through in the product by us.
During the beta we publish without individual bylines. The Proposal Expert editorial team is accountable for every article, product page and comparison on this site. Before a text goes live it is read by a writer and by someone who knows the subject matter. That keeps the responsibility with the team rather than with a single name. Questions about an article can be sent to the editorial team through the contact form. We respond to every substantive question.
Every claim that contains a number has a source, or is explicitly a worked example. If a percentage or an amount appears in an article, we state where it comes from or that it is a fictional example used to show a calculation. Product claims are checked in the live product before publishing. If we write that a feature does something, we have performed that action ourselves in the current version of Proposal Expert.
Legal topics such as eIDAS and electronic signatures are described as general information, not as legal advice. Before publishing we read such texts against the text of the regulation itself, so that terms and article numbers are correct. If you want to know what a rule means for your situation, consult a lawyer. In comparisons with other tools we only state what the vendor documents publicly. What a vendor does not document itself, we leave out.
In the Academy we cite peer-reviewed research and industry reports by name and year, so you can look up the source yourself. For legal topics we use the text of the regulation itself, such as Regulation (EU) 910/2014 on electronic identification and trust services. We also draw on the anonymised aggregates of our own Data Lab and on interviews with customers. Research articles end with a Sources list that names every publication used.
Every article shows a published date and a date of the last update. Product pages are reviewed as soon as a feature ships, so that the description matches what you see in the product. Corrections are made visibly. When the substance of an article changes, we add a short note to the article stating what was changed and why. If you see an error or an outdated claim, report it through the contact form. We review every report.
Spotted an error or a missing source? Let us know through the contact form.