Competitor Research for Copywriters

Beside Oren's stage door hangs a whiteboard with one equipment check that has no name beside it. Oren is an invented theater manager, and Acornquay, the maintenance-planning tool we'll follow, is fictional, as are its rivals.

Your competitor spreadsheet probably lists software rivals. Oren's board needs a row too, because it's the system Acornquay would have to replace. The board's empty name field gives you a task to investigate before writing a claim about better maintenance planning.

Define the buyer's comparison

Start with Oren's task: see which maintenance checks need attention before opening night. Ask recent buyers what they considered, and people who declined what they kept using. Leave room for "the whiteboard" as a complete answer.

The board is already in the building, and everyone knows where it is. Moving to software would add work. Your map should leave space for that attraction alongside the trouble with the unnamed check.

A larger facilities tool may also belong if managers actually consider it. Ask what puts it on the shortlist. If the founders want it included because they admire its website, label that as a team assumption while you check whether buyers look at it.

Keep the inspection small enough to do properly. We'll work with the whiteboard and two software alternatives: Granitepip Suite, a broad facilities suite, and Velvetspanner, a room-checklist tool. Their differences show up best when you follow one task through each.

Don't count mentions as if you'd run a representative survey. A handful of interviews can point you to alternatives worth inspecting. Keep the original accounts next to your selection notes, with the size of the sample written on top.

Compare the same task on each site

Write the task at the top of the sheet: "Find maintenance due before the next production opens." For each alternative, read the product explanation and help material that cover it. Follow links about how tasks connect to dates, including any setup conditions.

Save the URL and access date with each observation. Keep exact source words in a marked quotation field, apart from your interpretation, so you can trace a draft claim back to what you actually saw.

Nielsen Norman Group's competitive-evaluation guidance separates expert inspection from watching users do tasks. Your desk review records what the pages show. If you need to know how managers understand an offer, ask them to try the task.

A repeatable inspection pass

1. Arrival

   Record the promise and audience on the page relevant to the buying task.

2. Evaluation

   Find the mechanism, examples, proof and information needed to judge fit.

3. Commitment

   Inspect pricing, terms and the next action, including what happens after the click.

4. Record

   Save the date, direct links and exact location of each observation. Mark unknowns explicitly.

For the whiteboard row, ask Oren to walk you through the unnamed check. Record where the production date lives and how someone takes the job on. He may have a perfectly workable habit that your software sheet hasn't captured.

When a site doesn't explain something, save the page you read and write the question for the vendor alongside it. A colleague can pick up from there and log the answer when it arrives.

Build a message map

Bring the observations together around that maintenance task. Keep each promise next to the evidence for it. Give the open-question column enough room to hold the exact question you'll send.

In the starting map below, keep each alternative's apparent attraction provisional. Ask Oren to explain which parts match his reasons for considering or keeping it, and note where his answer differs from your reading of the page.

In this example, Oren checks the production calendar, then reads the board before each opening and asks who can take the unnamed jobs. He keeps it because the crew already passes the stage door; he has to bring the date and task records together himself.

Label Acornquay's task-view screenshot with the version and action it demonstrates. It can show that an unassigned check appears in that view. For a claim about reliability, ask for records over time and keep those alongside the capture.

Look for repeated promises and neglected questions

Suppose the pages you read keep promising to keep venues organized. Oren wants something narrower: to see what's left before an opening date. Look for an explanation of that task in each alternative's material.

Use customer-desire research to check whether the question matters beyond Oren's theater. You might find that preparing records for import worries managers more than the date view. Let that finding change the recommendation.

Production-date planning: ask the vendor; owner and reply date pending.

Keep the unanswered question visible

Beside the room-based checklist example, add a research task: inspect the help material for production-date planning. If it remains unclear, ask the vendor or mark it unresolved. Save the answer with the page capture.

Write the gap as a task for your own page: explain how a manager sees maintenance due before opening night. Take that candidate line to the product team with the unanswered date question. Silence on the inspected pages leaves the competing products' capabilities unknown.

How do you test a candidate claim?

Put the proposed line alongside the map and the demonstration request. Use voice-of-customer interviews to check that managers care. Then ask the product team to show what happens to a maintenance task when the production date moves.

That demonstration could turn up an awkward limit. If dates don't move together, save that in the brief, because your copy will need to explain the manual step.

Draft a direction to challenge with the team

audience

Small-theater managers preparing for the next production.

alternatives

A shared spreadsheet, a backstage whiteboard, or a broader facilities tool.

differentiator

A maintenance view organized around production dates, if the product demonstration confirms it.

value

See the maintenance work due before the next opening.

proof

Request a demonstration with one unassigned check and a changed opening date. Record which tasks move and which need manual updates.

For an objective comparative claim, ask exactly what you're comparing and what evidence supports it. Under the US FTC's substantiation policy, you need that evidence before you publish. A dated page review alone won't support "the only tool for theaters."

Ask Acornquay's product team to check your description against the production view. Keep the recording beside the draft so another writer can see what supports the line.

Write your own argument

Assume the product team confirms that the production view shows linked tasks, including unassigned work. Write toward the check with no name: "See which maintenance checks still need an owner before opening night." Put the relevant view beneath that line.

The supporting explanation should say how to assign a person and see outstanding work. Check those actions in the demonstration before you include them, so Oren could follow them from the page.

Proof copy for the same direction

Unsupported comparison

Unlike every other tool, we make opening night stress-free.

Ask the author to identify the comparison set and evidence for the emotional promise.

A demonstrable explanation

Open a production to see linked maintenance tasks, assigned owners and outstanding checks.

Open the demonstrated screen and verify that each of these items is visible. Keep anything still unconfirmed out of the published line.

Put the demonstrated task view beside the promise it supports.

Keep the cost of switching visible. If equipment records need importing, show the supported formats and who does the import. Ask Oren what he'd lose from the familiar board as well as what he'd gain from a dated view.

Use customer-objection research to follow those concerns. A promise of easier maintenance feels thin while the reader is still wondering who'll type in years of equipment records.

Read your draft next to the competitor wording you saved. If an elegant phrase has drifted across, rewrite it from the demonstration, using the names and actions on Acornquay's own screen.

Keep a dated decision record

Save the map with your recommendation and its open questions. Include the pages you read and the demonstration behind the draft. For a product that changes, note which version you saw so a later writer knows what to recheck.

Write down what would change your recommendation. If a vendor answers the date question, update that row before anyone turns the old blank into a comparison claim.

The research-to-copy lesson and Research lessons can help you develop that recommendation. For Oren, keep the import question alongside the production view, since switching tools still means moving his equipment records.

Map the buyer's actual alternatives

Bring the unnamed check into the demonstration and give Oren the mouse. In this example, linked task dates move with the production; a separately dated check requires a manual update. Add that distinction to the draft's explanation of date changes.

Oren assigns an owner to the check from his board, then moves opening night to a later date. The linked check follows it. He opens the separately dated check and changes its due date by hand.