Our Editorial Standards

FintechSpecs exists to help readers make better decisions about the fintech tools and trends shaping their businesses. That only works if our content is trustworthy. This page explains how we work — what we cover, how we research, how we test, how we handle mistakes, and how we use AI in our workflow.

We update this page as our process evolves.

How We Pick What to Cover

We choose topics based on what our readers are actively researching, building, or trying to decide on. That usually means one of three things:

  • Reader signal. Questions we get over email, gaps we notice in search results, and patterns in what fintech operators are asking about.
  • Market shifts. New regulations, pricing changes, product launches, acquisitions, or category shifts that affect how people build or buy fintech products.
  • Topics we know well. Areas where we have direct experience or strong familiarity, so we can add a perspective that goes beyond surface-level coverage.

We do not cover topics just because they are trending. If we cannot say something useful, we wait until we can.

How We Research

Every article goes through a research phase before any drafting begins. Depending on the topic, that includes:

  • Reading official documentation, pricing pages, and product changelogs
  • Reviewing recent independent coverage, regulatory filings, and primary sources
  • Checking community discussions on Reddit, Hacker News, Indie Hackers, and relevant Slack or Discord groups to understand how real users feel about a product
  • Looking at G2, Capterra, Trustpilot, and other review platforms for patterns in feedback
  • Cross-referencing claims across multiple sources before treating them as facts

If a number, feature, or pricing detail cannot be verified through a credible source, we either leave it out or flag the uncertainty in the article.

How We Test Products

For reviews and comparisons, we test products ourselves whenever it is practical to do so. That typically means:

  • Signing up for a free trial or paid plan
  • Walking through onboarding and setup
  • Trying the core features the product is known for
  • Testing edge cases relevant to the audience we’re writing for
  • Noting where the experience matches the marketing and where it falls short

When hands-on testing is not possible — for example, with enterprise-only products or platforms requiring a long sales cycle — we say so clearly in the article and rely on documentation, customer interviews, and verified third-party reviews instead.

We do not pretend to have used something we have not used.

How We Handle Corrections

We aim for accuracy, but fintech moves quickly and mistakes happen. When we get something wrong, we fix it.

Our correction process:

  • Minor edits (typos, formatting, broken links) are made silently.
  • Factual corrections (pricing, features, claims) are updated in the article with a short note at the bottom explaining what changed and when.
  • Significant changes (revised recommendations, retracted claims) include a clear correction notice at the top of the article.

If you spot something that looks wrong, email us at contact@perkisolutions.com and we will look into it.

How We Disclose Paid Relationships

We take disclosure seriously because reader trust is the only thing that makes this blog worth anything.

  • Affiliate links are disclosed in the article and in our Privacy Policy. We may earn a small commission when readers sign up for or purchase a product through these links, at no additional cost to them. Our editorial opinions are never influenced by whether a link is affiliated.
  • Sponsored content is clearly labeled at the top of the article. The sponsor can suggest topics and review the draft for factual accuracy, but they do not get to dictate our opinion or rewrite our analysis.
  • Free trials, demo accounts, or product access provided by a company for testing purposes do not buy a positive review. We disclose when we have received access, and our assessment remains independent.
  • Partnerships of any kind that affect what or how we cover something will be disclosed in the relevant article.

If you ever see something on FintechSpecs that looks like undisclosed sponsorship, please flag it. We will investigate and correct it.

When We Use AI in Our Workflow

We use AI tools as part of our content process, the same way most modern writers and researchers do. Being transparent about how matters more to us than pretending we do not.

Where AI helps us:

  • Research synthesis — pulling together information from multiple sources faster
  • Drafting outlines and structuring long-form articles
  • Editing for clarity, grammar, and consistency
  • Generating initial drafts that we then heavily revise, fact-check, and rewrite in our own voice

What we do not do with AI:

  • Publish AI-generated content without human review, editing, and fact-checking
  • Use AI to fabricate quotes, statistics, case studies, or testing experiences
  • Replace human judgment on what to recommend or how to evaluate a product
  • Skip the work of verifying claims because an AI said so

Every article published on FintechSpecs is reviewed and edited by a human before it goes live. AI is a tool in our workflow, not a replacement for the thinking, testing, and judgment that makes our content worth reading.

Questions or Feedback

If you have questions about how we work, or you want to flag something that does not meet the standards above, please reach out.

Email: contact@perkisolutions.com Address: New York, NY 10022