Sales battlecard template with dated evidence

Filled preview

Illustrative example. Names, volumes, dates and outcomes are fictional; replace them with approved evidence before use.

Sources: WorkOS Directory Sync documentation

Compare one job, not two companies

Define the decision as a workload, such as ‘provision employees from a directory into a B2B application.’ Compare documented capabilities, operating conditions and unknowns. Avoid broad scores like ‘better security’ unless an agreed criterion and evidence support them.

WorkOS documents Directory Sync as a way to connect directory providers and receive user, group, and access-rule changes through its integration and events. That is a product capability, not proof that it is the best fit for every identity architecture.

Sources: WorkOS Directory Sync documentation

How to answer the competitor objection

Write: ‘If you need user and group changes from a directory through one integration, verify that workflow with the documented Directory Sync API and your target provider. If your requirement is a different identity boundary, record the gap first.’

The response names what to test, where the documentation is and when the answer changes.

Refresh the card when a pricing page, API, packaging term, or customer requirement changes. A source date lets a seller know when an old comparison needs review.

Sources: WorkOS Directory Sync documentation · WorkOS pricing

Battlecard quality check

• Each claim names its source and check date.
• The scope is one buyer job and named evaluation condition.
• Unknown is a permitted result.
• The fair-fit section describes conditions, not marketing language.

Sources: WorkOS Directory Sync documentation