Methodology

Review Methodology

Paepae Stack evaluates tools and training resources by audience fit, stack or learning role, workflow clarity, cautions, official source notes, owned evidence when available, and affiliate-term transparency.

The goal is not to name a universal winner. The goal is to explain which software or training path fits a specific creator or small-business workflow, what tradeoff the buyer is accepting, and which claims are supported by current evidence.

Recommendation standard

A recommendation has to answer five practical questions: who the tool or training resource is for, who should avoid it, what job it should perform in the stack or learning path, what should be checked before buying, and which alternative path is simpler. Options are not recommended only because they have generous affiliate terms.

Testing and review tiers

Paepae Stack uses review labels so readers can see the evidence basis before trusting a page.

• Documentation-based: the page is based on official product pages, pricing pages, affiliate program documents, product materials, and Paepae Stack editorial analysis.
• Limited hands-on evidence: Paepae Stack has captured owned setup screenshots or direct workflow notes, but has not completed enough testing to claim full workflow performance.
• Hands-on tested: Paepae Stack has direct testing notes and owned evidence for the core workflow being described, such as signup, setup, publishing, delivery, export, or support behavior.

Documentation-based reviews

Product and training pages are documentation-based unless marked otherwise. They use official product pages, training pages, pricing pages, affiliate program documents, and product materials. A page may be marked as limited hands-on evidence when Paepae Stack has captured owned setup screenshots or notes but has not completed the full workflow test. Paepae Stack marks a page as hands-on tested only after direct testing notes and owned evidence support the core claims.

Evidence policy

Owned screenshots, workflow notes, and source links are used to support narrow claims. A setup screenshot can support that a feature exists in the interface; it does not prove deliverability, conversion rate, uptime, support quality, payment reliability, or long-term business results.

Screenshots are reviewed for personal, account, billing, customer, API, domain, and payment details before public use. If evidence is incomplete, the page should say what was not tested instead of implying more certainty than the evidence supports.

Pricing and source freshness

Pricing snapshots describe billing model, starting-point checks, plan caveats, source URLs, and last-verified dates. Paepae Stack avoids exact price claims unless the page displays a source and a recent verification date. Readers should always confirm current pricing, plan limits, and feature availability with the official source before buying.

Source checks prioritize official pricing pages, plan-limit pages, terms, product documentation, public affiliate-program materials, and first-party product screens captured during owned testing. Third-party commentary can help identify questions to investigate, but it should not be the only support for a product claim.

Priority scores

Priority scores are internal editorial and monetization priority signals. They are not product ratings and should not be presented as user review scores.

Claim policy

Pricing and major product claims include source links and last-verified dates where practical. Paepae Stack does not use fake ratings, fake testimonials, or unsupported price claims.

Affiliate independence

Paepae Stack is free to use, has no display ads, and may earn commissions from some links. Affiliate approval does not guarantee placement, and a tool or training resource can remain public as a non-monetized editorial recommendation when it is useful for comparison. Declined or blocked affiliate programs should not be pushed onto public pages unless the editorial strategy changes.

What earns a recommendation

A tool or training resource has to fit a specific workflow: launch, email capture, course delivery, hosting, automation, CRM, support, AI workflow, client delivery, or operator skill development. The recommendation should explain who should use it, who should skip it, and what tradeoff the buyer is accepting.

What changes a recommendation

A recommendation can change when pricing, limits, ownership, exports, support paths, product focus, affiliate status, source evidence, or owned testing evidence changes. A product can move up when it becomes a clearer fit for a workflow, and it can move down or disappear when the setup burden, limitations, buyer risk, or evidence gap becomes too large.

New affiliate approval is not enough by itself. Before a product gets public placement, it still needs a fit reason, source review, disclosure posture, route QA, and conservative copy that matches the evidence available.

What does not earn a recommendation

Paepae Stack should not recommend a product only because the affiliate program is generous. Weak-fit tools, hype-heavy training programs, and broad self-improvement offers should stay out of the core recommendation path unless they solve a concrete operator problem with clear evidence and reasonable buyer expectations.

Corrections and updates

When a source changes, an affiliate status changes, or a reader reports an error, Paepae Stack should update the affected page, preserve conservative wording until the claim is rechecked, and refresh the last-verified date where appropriate. Send corrections to hello@paepaestack.com.