Introduction
PG Systems Lab publishes practical guidance about B2B SaaS, marketing, CRM, email marketing, automation, workflows, and growth systems. The site is operated by Project Gardens, which retains final editorial responsibility for publication, corrections, and commercial decisions.
Our aim is to help readers distinguish documented facts, bounded hands-on observations, and editorial judgment. We explain what a source or test supports, what it does not support, and where a reader should verify current information before making a purchase or operational decision.
Source Standards
We prefer current primary sources, including:
- Vendor product documentation and official help materials
- Current pricing and plan pages
- Product terms and program terms
- Official support responses where relevant
- Affiliate-program documentation
- Other sources published by the organization responsible for the information
Vendor pages are not the only source we may need. Pricing, limits, feature availability, contracts, promotions, and program conditions may require checking terms, documentation, and support responses together.
These details are date-dependent, so an older article, screenshot, or research note may not reflect the current position.
Secondary sources may help with context, discovery, or comparison, but they are not a substitute for a primary source when a claim depends on a vendor’s current product, price, terms, or policy.
If we cannot verify a material claim, we do not present it as confirmed. We may label it as:
- Unknown
- Unverified
- Plan-dependent
- Requires official confirmation
Hands-on Testing
When practical, we use synthetic data and operator-controlled accounts or inboxes. We avoid unnecessary use of personal data, customer data, or live lists.
A test record should identify:
- The relevant date
- The account or plan state
- The setup
- The scope
- The observed result
- The limitations
- The items that were not tested
Hands-on evidence describes a particular test. It does not automatically establish general deliverability, ease of use, conversion, reliability, security, support quality, or business results.
One message in one inbox is not a universal inbox-placement result. One draft workflow is not proof that an automation will fire or perform successfully in production.
Screenshots and other visual evidence require additional care. Before publication, we consider:
- Freshness
- Context
- Accuracy
- Whether account-specific information has been removed
- Whether personal data has been removed
- Whether credentials or identifiers have been removed
- Whether private URLs or test-inbox details have been removed
Internal test materials remain private unless the article-level review permits a specific, properly masked use.
Reviews and Comparisons
Reviews should state the criteria and scope used.
Comparisons should use the same conditions, dates, and intended reader where that is reasonably possible. We do not create fictional feature differences, price differences, test results, or competitor statements.
Terms such as “best,” “easy,” “better value,” and “recommended” require evidence and a stated use case. We do not use them as universal conclusions without a suitable method.
A product may fit one team and not another. When a comparison is incomplete or asymmetric, that limitation should be visible to the reader.
Affiliate Relationships
Affiliate compensation does not guarantee:
- Inclusion
- A positive evaluation
- A higher ranking
- A recommendation
A commercial relationship does not prevent us from describing limitations or explaining why a product may not fit a reader’s needs.
We do not describe an affiliate program as approved merely because it has been researched, discussed, or considered.
When an active commercial relationship exists, we disclose it through the Affiliate Disclosure.
The presence or absence of an affiliate link does not determine the editorial conclusion.
AI-Assisted Production
AI tools may assist with:
- Research organization
- Outlining
- Drafting
- Editing
- Formatting
- Comparison matrices
- Workflow support
AI-generated output is not treated as verified fact. It may contain:
- Errors
- Unsupported claims
- Invented citations
- Stale prices
- Incorrect features
- Fabricated experiences
Project Gardens remains responsible for final review, publication decisions, corrections, and commercial decisions.
We do not publish AI-generated facts, quotations, prices, features, or experiences unless they have been independently checked against appropriate evidence.
AI assistance does not mean that every article is automatically verified or that every error can be prevented.
Corrections and Updates
We may correct:
- Factual errors
- Broken links
- Outdated prices
- Changed features
- Material omissions
Material changes may be reflected through an updated date or an explanatory note.
Minor spelling, formatting, or style edits may not receive a separate correction notice.
Readers may send correction requests through the Contact page.
A request is reviewed against the available evidence. Submitting a correction request does not guarantee that it will be adopted.
Product information may also be updated when official sources change.
Independence and Conflicts
Vendor, affiliate-network, advertiser, partner, trial, demo, or review access does not guarantee a favorable conclusion.
We do not change an editorial result merely because a company or commercial partner requests it.
If sponsored content is published, its commercial nature will be made clear to readers.
This policy does not invent a general rule about gifts, payments, discounts, or free products. Any such arrangement would require case-specific review and clear disclosure where applicable.
Publication Limits
PG Systems Lab provides practical editorial guidance, not legal, tax, financial, medical, or professional security advice.
Readers should consult an appropriately qualified professional for decisions that require such advice.
We do not replace a vendor’s customer support.
For account recovery, billing disputes, product access, delivery problems, or other service issues, contact the relevant vendor through its current official support channel.
Before purchasing or signing a contract, readers should check the provider’s current official information, terms, pricing, and limitations.
Contact and Feedback
Questions about a correction, source, evidence boundary, or commercial relationship can be sent through the Contact page.
Information submitted there is handled according to the Privacy Policy.
Questions about affiliate relationships are also addressed in the Affiliate Disclosure.
Last Updated
Last updated: August 1, 2026