Evaluate tools against your team's capacity

Type your answers, or print it blank and write by hand. We make Crow, so Crow is listed like every other option. This worksheet does not score or rank anything.

Your worksheet

Nothing is saved. Your notes stay in this browser tab only. They are not sent anywhere or stored. Print or Save as PDF before you leave or reload this page. Choose A4 in your print settings.

Free, no account needed

1. Your options

Your name or team (optional)

Date

Add the tools you are weighing. Tick any option you want to keep on the list. Nothing is preselected.

Shortlisted tool 1

Shortlisted tool 2

Shortlisted tool 3

Shortlisted tool 4

Other options to consider Crow Keep existing tools or manual workflow

Why these options?

For each answer below, name the option it relates to. Apply the same requirements to Crow, other vendors and your existing tools. Leave unknowns unanswered and ask for written confirmation.

2. Workflow requirements

Workflow. Where the work starts and where it ends decides how many tools and hand-offs you carry.

Workflow: your notes

Which steps must happen in one place, and which can stay elsewhere?

3. Team capacity

Team capacity. Match the tool to the people who will run it every week, not the people in the demo.

Team capacity: your notes

Who on my team does the first month of work, and how many hours is that?

4. Implementation responsibilities

Implementation effort. A tool nobody has time to set up produces nothing, however capable it is.

Implementation effort: your notes

Who installs and maintains tracking, tests and pages?

5. Quoted limits and pricing

Volume limits. Caps on traffic, pages or responses change which plan you actually need.

Volume limits: your notes

What does the plan I need cost in my currency, for my traffic, after tax?

What are the limits on traffic, pages, users, domains or responses, in writing?

Currency, tax, billing term and overage rules as quoted

6. Reporting needs

Reporting. Decide who must read the results and what they need to see.

Reporting: your notes

Who must read the results, and what do they need to see?

7. Exit and export

Switching risk. The cost of leaving is easiest to ask about before you sign, not after.

Switching risk: your notes

If I leave, what can I export and in what format?

Contract term and exit terms

8. Option-specific call questions

Use only the prompts relevant to your shortlist. These questions come from the comparison guide, not verified answers; confirm current plans directly. Add your own vendors and questions in the follow-up notes.

Crow

Which plan covers my number of pages and tests?
What does the report show, and can I share it with a client?

Crow: answers, source and date

VWO

Which plan includes the targeting and analytics I need?
Who installs and maintains the tracking?

VWO: answers, source and date

Unbounce

Does my plan include A/B testing?
What happens when I pass the traffic or domain cap?

Unbounce: answers, source and date

Optimizely

What is packaged in my quote and what is extra?
What engineering time does a first test need?

Optimizely: answers, source and date

Typeform

What happens at 100 responses on Basic?
Which plan do I need for drop-off tracking?

Typeform: answers, source and date

Keep existing tools or manual workflow

Which requirements can we already meet, and what work would close the gaps?
What are our current costs, provider limits and exit dependencies?

Existing tools: answers, source and date

9. Buyer evidence and follow-up

Can I speak to a customer with a similar team size and goal?

Evidence you have gathered, and where it came from

Questions still to ask, and who will ask them

Follow-up notes

Crow buyer worksheet. Questions adapted from the Crow comparison guide.