Building FactSpot and Simbion — article quality, and people's voices

日本語版はこちら: Japanese version

For the past few years I’ve worked across media and regional projects. Two kinds of “blindness” kept bothering me. First, I could only feel — not know — whether the articles we shipped were any good. Second, the people I worked with had problems and needs that never got collected properly; they just slipped by.

FactSpot and Simbion are the two tools I built to fix each.

Why two products

I first tried to make it one tool. But “raising article quality” and “collecting voices into insight” use different data and happen in different moments. Forcing them together makes both mediocre. So I split the roles clearly.

FactSpot is a tool for the quality of what you ship. Paste a URL and it machine-scores SEO, AI-readiness, and E-E-A-T, then returns AI editorial diagnosis, counter-evidence, and rewrite plans end to end. The aim: editors, writers, and PR teams can decide what to fix next, instantly.

Simbion is a tool for understanding people. Decide who to ask and what to learn, and it designs the questions, collects responses, structures them, and turns them into an insight report. The more you analyze, the more it grows into a knowledge base you can search across by theme and tag.

One handles quality before and after publishing; the other, understanding people. Each works alone, but together they get stronger.

Who FactSpot is for

Head of editorial

Quality depends on each writer’s skill, and review feedback varies by reviewer. You can’t put “a good article” into words, so training doesn’t scale. FactSpot applies the same 25-plus machine checks and AI diagnosis to every article, so standards align as numbers. Reviews get faster, newcomers hit a baseline, and you can return from line edits to strategy.

In-house owned-media lead

You outsource SEO/AI work, so cost and timing depend on others and no know-how accumulates internally. Bake pre-publish checks and improvement suggestions into your own cycle, and you cut spend while taking back control. The know-how stays with your team, and the risk of losing it to turnover drops.

Freelance writer

Revisions come after delivery; rework is high and rates stay flat. Diagnose your draft in FactSpot and fix weak points before delivery, and more pieces pass on the first try. With outlet-tuned writing support, being “the writer who needs few edits” turns into higher rates and repeat work.

PR / comms

You can’t tell whether a press piece lands until it’s out. FactSpot surfaces hard-to-read spots before publishing so you can polish first. Pickup and response rates improve, and you can explain to stakeholders why something works — with evidence.

Editorial desk

Articles pile up and you guess which to fix for traffic, with too little time. The rewrite-priority scan (upside x traffic x trend) decides the order instantly, so you start with the pieces that move. Same effort, more traffic, and the team agrees on the call.

Regional media operator

A tiny team, lots of articles, none fully reviewed; quality is left to chance. Domain scan batch-scores recent articles so you fix the weakest first. You lift the whole site without adding headcount, and move toward a trusted local outlet people actually read.

Who Simbion is for

Community builder

You can’t see what members struggle with or can offer, so matching and programming rely on gut feel. Simbion auto-designs questions, collects voices, and structures struggles, the unresolved, and what people seek/offer. With needs and resources laid out, you can match accurately and run programs that land.

Product manager

User truths and friction come only as anecdotes, so decisions become guesses. The design → respond → analyze → follow-up loop lets you test hypotheses fast. You gain grounds for decisions, explain priorities more easily, and miss less often.

UX researcher

Question design and transcript analysis eat your time, capping how many studies you run. Design a full question set from a theme and material, and auto-structure responses into a report. Per-study effort drops, so the same hours cover more voices and research turns faster.

Regional project lead

Residents’ and movers’ voices get buried in paper surveys and never reach policy. Collect via named and open modes, accumulate as insight, and connect across the knowledge base. “We gathered voices but couldn’t use them” becomes “policy grounded in voices,” and you can account for it to residents.

Marketer

You only see article/product reception as numbers (CV, CTR) and can’t grasp why it doesn’t land. Opinion mode draws out reception, what resonated, concerns, misunderstandings, and improvement requests. Now you know what to fix in words — from hunches to reasoned improvement.

Founder / business development

Customer understanding lives in one person’s head and vanishes when they move on. Simbion grows a knowledge base as analyses accumulate, and cross-synthesis answers “what do our customers struggle with?” Personal intuition becomes organizational knowledge you can hand over.

Combining the two

This is the part I find most exciting.

• Polish before publishing: collect reader opinions in Simbion to validate direction, diagnose quality in FactSpot, then ship. Hit the target before publishing, not after.
• Fix weak articles with voices: find high-upside articles in FactSpot, collect those readers’ opinions in Simbion, and decide a rewrite plan from what isn’t landing.
• Voices into content strategy: continuously collect members’ problems in Simbion and build knowledge, while FactSpot keeps quality high, so you produce programming grounded in voices.
• Monitor reception: track stakeholder reception in Simbion and check how press and articles land in FactSpot.

Suggested workflows

Content improvement loop:

1. Plan: decide the target reader and theme
2. Simbion: validate the hypothesis by collecting opinions, find the angle that lands
3. Write: based on the validation
4. FactSpot: check quality with article analysis and improve
5. Publish, then confirm impact with integration data
6. Simbion: collect reader voices and return to planning

Customer-understanding loop:

1. Design interviews/opinions in Simbion and collect continuously
2. Auto-structure responses and generate an insight report
3. Accumulate tagged in the knowledge base; answer questions with cross-synthesis
4. Reflect into action; keep output quality high with FactSpot
5. Pass impact and new voices to the next cycle

What I keep in mind

Across both, what matters most: you learn the tool just by using it, you get better as you use it, and your assets grow the more you use it. In Simbion, the knowledge base thickens as analyses accumulate and you can answer across it. In FactSpot, the more you diagnose and improve, the more editorial standards become second nature. I want the product itself to carry the value.

Both are free to try. The first three days unlock all Pro features, so you can confirm the value before deciding to continue. No card required.

Try it

• Start FactSpot: https://factspot.app/login
• Start Simbion: https://simbion.app/login

Role-by-role use cases are also collected on each product’s use-cases page (FactSpot / Simbion). Start from whichever entry point speaks to you.