Work-Bench is a NYC-based $160M enterprise software Seed stage VC fund. If you are or know anyone thinking about founding an enterprise/vertical AI or infrastructure startup - we’d love to meet! Please reach out to chat.
💡 THE TIP
The SaaS industry built pricing pages for humans: three tiers, a comparison table, and a “Contact Sales” button for enterprise. It worked because the buyer was a person who could be guided into a demo.
AI agents don’t sit through demos. When an agent is evaluating vendors on behalf of a procurement team, it needs structured, machine-readable pricing, not a gated PDF. If your pricing lives behind a form fill or a sales call, you’re invisible to the fastest-growing buyer in B2B. While agents aren't making software purchases yet, it's plausible that they'll be more integrated in the process over the next couple of years, given the speed of AI innovation.
Teams building in this agent-first world: publish your pricing in structured formats (APIs, JSON, clear HTML) that an agent can parse without human intervention. The companies that do this first will win the deals that agents are shortlisting.
Special shoutout to Kyle Poyar for this tip! Check out his Linkedin post on it here.
✅ THE TO-DO
Go to your pricing page right now and try to extract your pricing tiers, feature limits, and per-seat costs using only copy-paste into a spreadsheet. If you can’t do it cleanly in 60 seconds, neither can an agent. That’s your gap.
If you found this tip helpful, please share with a fellow b2b founder 😎
🤖 THE CLAUDE SKILL
Paste your current pricing structure and let Claude make it machine-readable.
Here's our current pricing structure:
[PASTE YOUR PRICING — tiers, features per tier, per-seat costs, usage limits,
add-ons, enterprise pricing if you have it. Include anything that's currently
behind a "Contact Sales" gate.]
Do three things:
1. Convert this into a structured JSON object that an AI agent could parse
to evaluate our product against competitors. Include: tier names, prices,
billing frequency, feature lists per tier, usage limits, and any
conditional pricing (volume discounts, annual vs. monthly, etc.)
2. Write a clean, parseable HTML pricing table that could replace our current
pricing page — designed for both humans and machines to read. No
"Contact Sales" gates on information that could be structured.
3. Flag what's missing: what pricing information would an AI procurement agent
need to shortlist us that we're currently hiding or making ambiguous?
(e.g., implementation fees, overage rates, contract minimums, SLA tiers)Do you have a GTM protip? Send our way here to feature in an future issue! If you try any of these tips and found them helpful, let us know - we’d love to hear from you.