How I Test Software

At StuartKerrs.com, I test and evaluate digital marketing software with a single goal:
to help readers understand what actually works, what does not, and who a tool is really suited for.

This page explains how I approach testing, what I look for, and how recommendations are formed, so you can interpret reviews and rankings with full transparency.


My Testing Philosophy

I do not believe in “perfect” software.

Every platform has strengths, trade-offs, and limitations. My role is not to sell tools; it is to explain them clearly, based on real usage and practical understanding.

I focus on:

  • Real-world usability
  • Long-term value, not just feature lists
  • Fit for specific use cases, not hype

If a tool is popular but flawed, I say so.
If a lesser-known tool performs better in practice, I highlight it.


What I Test (and What I Don’t)

I only test and review software that falls within these categories:

  • Web hosting and server infrastructure
  • Website builders, CMS, and e-commerce platforms
  • Email marketing, automation, and CRM tools
  • Analytics, SEO, advertising, and marketing platforms
  • Digital marketing training and online course platforms

I do not review:

  • Unrelated consumer products
  • Tools with no clear market use
  • Platforms that exist purely for affiliate arbitrage

How Testing Is Performed

Testing depth varies depending on the type of software, but typically includes a combination of the following.

Hands-On Access

Where possible, I use:

  • Free trials
  • Demo accounts
  • Entry-level paid plans
  • Sandbox or staging environments

This allows me to evaluate onboarding, usability, and feature access rather than relying on marketing claims alone.


Feature Evaluation

I assess:

  • Core features vs advertised features
  • Feature depth, not just availability
  • Limitations that affect real users
  • Gated features hidden behind pricing tiers

Features are evaluated based on practical usefulness, not checklists.


Ease of Use and Onboarding

I pay close attention to:

  • Setup friction
  • Interface clarity
  • Learning curve for beginners
  • Documentation quality

A powerful tool that is difficult to use may not be suitable for most people.


Pricing and Value

Pricing is evaluated in context.

I look at:

  • Entry pricing vs realistic usage costs
  • Feature restrictions across plans
  • Long-term pricing sustainability
  • Refund policies and upgrade pressure

Cheaper does not always mean better value, and expensive does not always mean premium.


Performance and Reliability

Depending on the software category, this may include:

  • Speed and responsiveness
  • Uptime and stability
  • Feature reliability
  • Consistency over time

I also consider how well a tool scales as needs grow.


Integrations and Ecosystem

Modern software rarely works in isolation.

I assess:

  • Native integrations
  • API availability
  • Compatibility with common tools
  • Lock-in risks

Tools that integrate poorly often create hidden costs later.


Support, Updates, and Longevity

I review:

  • Support channels and response expectations
  • Update frequency
  • Product roadmap signals
  • Signs of active development or stagnation

A tool that looks good today but shows signs of neglect is flagged accordingly.


Comparisons and Rankings

When tools are compared or ranked, placement is based on:

  • Overall value for the stated use case
  • Balance between features, usability, and cost
  • Realistic suitability for most users
  • Clear strengths relative to competitors

There is no universal scoring formula.
Context matters more than raw numbers.


“Best For” and “Not Best For”

Every recommendation is framed around fit.

I aim to clearly explain:

  • Who a tool is best suited for
  • Who should avoid it
  • What alternatives may be a better match

This is often more useful than declaring a single “winner”.


Updates and Re-Testing

Software changes frequently.

I revisit and update content when:

  • Pricing changes materially
  • Features are added or removed
  • Tools are acquired, rebranded, or discontinued
  • Market conditions shift

Updated articles may display refreshed dates to reflect meaningful revisions.


Affiliate Links and Objectivity

Some links on StuartKerrs.com are affiliate links.

This does not affect how tools are tested or ranked.

I do not:

  • Adjust rankings to favour higher commissions
  • Omit drawbacks to increase conversions
  • Promote tools I would not personally recommend

Affiliate revenue supports ongoing testing and maintenance, but editorial judgement always comes first.


Final Word

Testing software is not about perfection; it is about clarity.

My aim is to help you understand:

  • What a tool does well
  • Where it falls short
  • Whether it fits your specific needs

Every review and comparison is written with that responsibility in mind.

Last updated: 01 January 2026