How can a research team try or get started with ReadCube?

Updated

A research team can start with ReadCube by using the free trial offered on about.readcube.com, then choosing a plan through the site's Pricing page. This path suits research-driven companies and academic teams that want to test literature discovery, PDF annotation, AI-assisted answers, and review workflows before committing. The site does not publish plan prices in the material reviewed here, so cost and contract terms need to be confirmed on the Pricing page.

What the free trial lets your team evaluate

The trial is framed around the full platform rather than a single feature. According to the site, the platform covers literature management, an AI assistant, literature monitoring, and literature review in one place. A useful trial means testing each of these against your actual project, not just clicking through menus.

Discovery and library setup

  • Search access is described as 123M+ indexed papers from the Dimensions research database, with AI answers drawn from 165M+ publications and 182M+ patents.
  • Imports are said to arrive with citations, supplemental data, and full text, so you can check whether metadata quality meets your citation needs.
  • Tags, custom fields, and Smart Lists are the tools for keeping a growing library sorted and shareable.

Try this during the trial: import a set of references you already know well and confirm that authors, dates, and full text match your originals. This is the fastest way to judge whether the library will hold up for a real review.

Reading and annotation

Highlighting, underlining, drawing, notes, and sticky comments are all done directly on the PDF. Test this on a paper with complex figures, since annotation on dense PDFs is where tools often disappoint.

AI assistant behavior

The AI assistant answers in plain language and links each answer to the exact passage in the source. It can chat with one paper or a whole library, and compare up to 20 papers at once to surface patterns, gaps, and contradictions. It also converts a plain-language request into structured search queries, so teams can skip Boolean strings.

One detail worth checking early: an AI Access Indicator flags, per paper, whether publisher terms permit AI use. If your institution has strict rules on AI and publisher content, review this indicator during the trial rather than after rollout.

Monitoring new research

You can save a recurring search so new papers on a topic are added to your library, with alerts by email on a daily, weekly, or monthly schedule. The site also says AI reads each new result against your criteria and filters out non-matches. Set up one saved search on a topic you follow closely and judge the relevance of what arrives over a week or two.

Systematic review and PRISMA

For teams running structured reviews, the platform supports dual-reviewer abstract and full-text screening with conflicts flagged automatically, custom data extraction forms, AI Autofill of extraction fields linked to sources, and PRISMA flow diagrams with audit trails that are export-ready. These are the features most worth a hands-on test, because screening and extraction are where review timelines are won or lost.

A practical getting-started sequence

  1. Open the trial from about.readcube.com. The homepage invites visitors to try for free and explore options.
  2. Pick one live project, not a demo. Choose a review or literature scan your team is actually working on so the trial produces usable evidence.
  3. Invite a collaborator and share a library. The site states that shared libraries keep collaborators working from the same evidence. Confirm that permissions and updates behave as your team expects.
  4. Run a small screening exercise. Assign two reviewers to the same set of abstracts and check that conflicts are flagged for resolution.
  5. Build one extraction form. Define the fields your review needs and test AI Autofill, confirming each pre-filled answer links back to its source.
  6. Review the Pricing page. Compare plans against team size and the features you actually used, then decide.

Who this fits, and what to confirm first

Question What the site supports What to verify yourself
Is there a way to try before buying? Free trial and an "explore options" path on the homepage Trial length and any feature limits
Who is it built for? Research-driven companies and research teams Whether your institution's security review allows cloud libraries
What does it cost? A Pricing page exists Actual plan prices, billing terms, and seat counts
Can teams collaborate? Shared libraries, dual-reviewer screening, conflict flagging How many collaborators your plan includes
Is AI use permitted on papers? Per-paper AI Access Indicator Your funder's or publisher's specific AI terms

The main open items before adoption are price and plan limits, both of which sit on the Pricing page rather than in the public descriptions reviewed here. Teams with strict data-governance requirements should also confirm hosting and access policies before importing sensitive unpublished work.

Bottom line

Start with the free trial, run it against one real review with at least two reviewers, and use the Pricing page to match a plan to what your team actually used. If dual-reviewer screening, sourced AI answers, and PRISMA-ready exports are central to your workflow, the trial will show quickly whether ReadCube replaces several separate tools or adds another one.