Lucia Ramirez
Editor
Leads CRM and operations comparisons. Before we recommend a product, she stress-tests public pricing pages, API limits and what a real data migration looks like—not just the demo path.
Editorial
Who we are and how we publish
Stackmeter Journal is written by people who have spent years choosing software for small teams. We are not a generic content farm: we publish what we would use ourselves, and we are explicit when we have not battle-tested a feature in production.
What makes this publication different
We say no to rewritten paragraphs from other sites and to raw AI drafts without a human editor.
When we cite policy or market context (for example EU late payment rules), we link to the official source so you can verify it.
If we ever add affiliate links or ads, we label them on the page. Editorial fit still comes first.
What we cover
Billing and collections, CRM for lean sales teams, project coordination and pragmatic automation (including applied AI for docs and reporting).
We avoid endless tool grids. A few well-argued picks beat twenty interchangeable logos.
How we review
For public SaaS we combine vendor documentation, trial accounts when available, and a fixed editorial scorecard (onboarding, permissions, data export, language support).
If we cannot test something deeply, we say so in the article. Honesty beats pretending we ran an enterprise audit we did not run.
Editorial team
Daniel Hunt
Research Lead
Focuses on billing, collections and implementation risk. He translates vendor marketing into weeks of actual work for a small team.
Sources and policy context we lean on
For late payments in the EU we often point to the EU prompt payment context. For editorial quality bar we align with Google's helpful content guidance (real experience, not filler).
Spotted a factual issue or want to pitch a topic? Reach us via contact.