Trust and transparency

Editorial Policy

Last updated: September 14, 2026

Our mission

Small Tool Guides helps small business owners understand software, AI tools, and digital platforms so they can make more deliberate decisions. We aim to publish accurate, useful, and readable guidance grounded in the needs of real business operations.

The publication was created by Alan Pierre Vieira, who is identified as its founder and creator. Editorial articles are published under the organizational byline “Small Tool Guides Editorial” so the page distinguishes publication responsibility from an unsupported claim of individual professional credentials.

How we select topics

We prioritize recurring decisions that affect a small business’s cost, customer experience, security, or operating workload. Search demand can reveal a question, but it does not determine the answer. A topic must support a useful framework, explanation, or tool—not merely a keyword-shaped page.

Research and writing

We begin with the business problem and the decision a reader needs to make. Research favors primary sources: official product documentation for product behavior, government guidance for regulatory or security basics, and published standards for accessibility or technical practice. Secondary market research may provide context, but we identify it and avoid presenting a single estimate as universal.

Guides are written under the organizational byline “Small Tool Guides Editorial.” The byline does not represent a named expert or imply credentials that have not been disclosed. Drafts are checked for a clear decision process, material tradeoffs, unsupported factual claims, and an actionable next step.

Product evaluation and testing

We use these terms deliberately:

• Researched means the guide was developed from cited sources and editorial analysis.
• Reviewed means information or a draft was checked editorially; it does not mean a product review or expert certification.
• Compared means options were evaluated against stated criteria, usually from documented capabilities and constraints.
• Hands-on tested is used only when the publication directly used the product or process under described conditions. We do not currently apply that label to a guide unless its method is stated on the page.

A “best” or “top” label requires a defined audience, criteria, and sufficiently current evidence. When that evidence is not available, we publish a selection framework instead of a ranking. We do not fabricate ratings, prices, users, market statistics, or performance results.

Lab experiments

The Small Tool Guides Lab publishes working prototypes and documented experiments. A completed experiment states its question, hypothesis, implementation, method, test date, observed results, and limitations. We make the work reproducible when the format and available materials allow it.

• Metrics must come from the stated measurement process. We never invent a score, timing, improvement, or comparison.
• A metric that cannot be measured reliably is omitted or marked “Not measured.”
• Tools named as used must have been part of the actual build, test, or measurement.
• Fictional products and demonstrations are identified and are never presented as client work.
• Material implementation or result changes should be reflected in the test record and update date.
• In-progress and planned work is not presented as a completed result and is excluded from public search and the sitemap.

Technical guides derived from a Lab experiment separate reusable implementation guidance from the experiment report. They may use confirmed code, logs, media properties, measurements, failures, and screenshots from that work. They do not turn local build evidence into claims about real users, production performance, conversion, or commercial outcomes.

Updates and corrections

Software products, policies, pricing, and features change. We update a guide when the decision logic, source material, or practical usefulness materially changes. The published date records first publication; the updated date changes only after a substantive editorial revision. Cosmetic fixes do not justify a fresh date.

Readers can report a possible error through our contact page. We evaluate the cited passage and supporting evidence, correct confirmed errors, and update the article date when the correction materially changes the guidance.

Editorial independence

Commercial considerations do not determine our conclusions. Advertising, sponsorships, free access, or affiliate relationships—if introduced—will not guarantee favorable coverage. We will clearly identify material commercial relationships where appropriate.

Affiliate links

Some pages may contain affiliate links. Small Tool Guides may earn a commission when a reader purchases through one of those links, at no additional cost to the reader. Affiliate availability does not decide whether a product is covered or the conclusion of a comparison. Affected pages carry a visible disclosure. Learn more in our affiliate disclosure.

Reader responsibility

Our articles are educational. A useful guide can narrow the questions to ask, but it cannot account for every organization’s contracts, security obligations, legal environment, budget, or workflow. Readers should verify important details and seek qualified professional advice when needed.