What We Believe
A short set of ideas guides how Pogupo Kujaso is built. None of it is complicated, but it shapes every decision about what the platform surfaces and how.
Most content teams did not choose to run quarterly audits because it was the ideal way to catch decline. They chose it because nobody had time to check every article every week, and a spreadsheet review every few months was the version of "regular" that fit around everything else on the calendar. We think that trade-off deserves a second look.
Content is a maintained asset, not a one-time deliverable
An article published two years ago is still competing against pages published last month. Search intent shifts, competitors update their pages, and facts go stale. Treating a published article as finished work is the single biggest reason traffic erodes quietly.
Decline has causes, and causes sort into patterns
A drop in traffic is rarely random. It usually traces back to one of a handful of recognizable patterns: a competing article on the same site, a stale statistic, a lost backlink, a shift in what searchers are actually looking for, or a technical issue nobody noticed. Naming the pattern is most of the work of fixing it.
Small teams need signal, not more dashboards
A team of four does not have a dedicated analyst. Adding another chart to check does not help. What helps is a short, ranked list of what to do next, generated without someone having to go looking for it.
The right person should see the right task
A writer, an editor, and a strategist can look at the same declining article and each see a different fix. Sending everyone the same list means most of it gets ignored. Routing by role means the list that reaches someone is one they can actually act on.
Audits should run continuously, by default
Waiting for a quarterly review to notice a decline means months pass before anyone acts. Continuous, low-effort monitoring in the background changes the timeline from months to days, without adding a recurring task to anyone's calendar.
These beliefs turn into specific product decisions
- Alerts are written in plain language, tied to a specific likely cause, not a raw metric change.
- Every task is pre-assigned to a role rather than left in a shared inbox.
- Baselines are set per article, since a five-year-old post and a five-week-old post decline differently.
- The platform is scoped for teams publishing twice a week or more, where manual review genuinely cannot keep pace.
Built by people who were tired of the same quarterly scramble
The earliest version of Pogupo Kujaso came out of a recurring conversation between two people running content for small teams: every quarter, the same ritual of exporting reports, tagging a spreadsheet, and trying to remember what had changed since the last review. Neither of them enjoyed it, and neither trusted that it was catching problems early enough.
The product exists to remove that specific piece of work, not to replace editorial judgment. Alerts point at what changed and why it might have changed. What to do with that information still belongs to the team.
