Skip to main content
All publisher problems

It can't do what we need

How do we avoid buying a tool that can't do the job?

The short answer

Most gaps surface as missing integrations or undocumented workflows. Write down your non-negotiables first, then verify each one against published capability rather than a tailored demo.

Publishers have raised this 1,493 times across the mentions we analyse, naming 336 specific tools.

Find tools that do the job

We'll check the non-negotiables against published capability, not the demo.

Build my stack

What publishers reported

The tools this comes up about most, and what was actually said. Counted from public publisher mentions rather than our own verdict, and each quote is attributed to the tool it was about.

Apple Books31 mentions
“The JSON export currently includes the highlight text, color, timestamps, and book information, but no chapter, page, or location data.”
Omeda30 mentions
“Integration with Google Ad Manmager (GAM) for targeting & reporting | Omeda: xmark”
Muse24 mentions
“you asked for sessions and usage, and only sessions are done.”
OpenAI Ads22 mentions
“Openai CLI needs to have access to Openai Ads”
beehiiv21 mentions
“Unlike Substack, Beehiiv does not have its own app creating a wider network of readers and publications.”
Authorize.net17 mentions
“No Accept.js integration”
Mailchimp17 mentions
“I don't need a visual builder that creates an html monstrosity requiring a 6571x2536 resolution to be displayed properly.”
Asana17 mentions
“the platform has limited collaboration capabilities due to their single assignee feature. In Asana, you cannot assign a task to multiple team members.”
Klaviyo16 mentions
“Klaviyo pushed for a deep partnership and co-marketing a few years ago then announced their own review app right after.”
“I would like to be able to import my highlights and notes from Google Play Books.”

What to check before you sign

The questions that surface this problem while you can still walk away.

  • List the three workflows you cannot change, then verify each against the vendor's own docs
  • Confirm the integrations you rely on are native, not Zapier-only
  • Check the changelog, because a tool that stopped shipping will not close your gap
  • Ask for the roadmap in writing and treat it as a wish, not a commitment
Not sure which of these applies to you?
Answer four questions about your newsroom and we'll shortlist the tools that fit. We'll carry this problem across with you.
Build my stack
Next UpPerfect follow-up read