The job
You need to choose between two SaaS tools, but their pricing pages use different units, different limits, and different definitions of “included.” You want one apples-to-apples view for your real usage, not two polished pricing tables that hide the expensive parts in footnotes.
Why this is hard without Sephir
Without Sephir, you bounce between tabs, copy fragments into a separate chat, and lose context fast. Pricing pages mix prose, tables, and tiny caveats, so manual comparison misses key constraints like seat minimums, overage rates, or feature gates. Standard chat workflows also force you to paste raw text, which strips structure and makes side-by-side reasoning less reliable across multiple iterations.
How Sephir does it
- Pin both pricing tabs so the agent reads the exact pages you care about.
- Open Sephir with
Cmd+Shift+Sand state your team size, usage, and must-have features. - Ask for a normalized comparison, or run
/pricing-diffif you already saved the workflow. - Watch the timeline show
extractPageText(tab 1)andextractPageText(tab 2)before synthesis. - Review the output table with plan assumptions, exclusions, and likely overage triggers.
- Save the successful trace to reuse this comparison flow on the next vendor short list.
The skill behind it
This skill uses Sephir’s tab-reading and comparison tools to turn mismatched pricing language into one structured output you can challenge, edit, and rerun with new assumptions.
What it costs
Sephir runs this recipe on your own ChatGPT Plus (via Codex OAuth) or API key. Typical token usage: ~3,000-8,000 input + ~500-1,500 output per run on Claude Opus 4, GPT-5, or Gemini 3 Pro. Sephir pricing is documented on : Free works for quick single-turn checks; multi-turn comparison is a Pro workflow.