ooligo is a small, independent reference site for the people who run operations inside modern companies — RevOps, Legal Ops, and TA/Recruiting Ops in particular.
What's on the site
ooligo organizes ops content into a few overlapping shapes: a tools catalog (vendor profiles with category, pricing model, and integrations), comparisons (side-by-side breakdowns of tools that solve the same problem), workflows (multi-step automations and the tools that run them), stacks (the bundles of tools that work well together in a given vertical), and a learn section (definitions, frameworks, and FAQs).
Everything is grouped by the three verticals the site covers — RevOps, Legal Ops, and TA/Recruiting Ops — plus a cross-cutting layer of shared concepts that show up in all three.
How content is produced
Pages are drafted from primary sources — vendor documentation, public pricing pages, the operators who use these tools day-to-day — and then reviewed before publishing. Where AI tooling is used in drafting, the output is treated as a first pass that has to be fact-checked against real sources, not as the final product.
Every page records a `last_updated` date in its frontmatter so you can see how fresh the information is. When something changes meaningfully — a vendor's pricing model shifts, a new tool enters a category, a workflow gets a better automation primitive — the page gets revisited and the date bumped.
Build in public
The site's source code lives in a public GitHub repository under the MIT license. The full architecture, content schema, and roadmap are linked from the footer. Corrections are welcome as pull requests or as a note via the contact page; the goal is for the catalog to be more accurate after your visit than before it.