Home/About

About

We built this because the software kept assuming a journal

Manuscript Manager has run peer review for scholarly journals since 2001. In that
time we were asked the same thing repeatedly by funders, ethics committees and research teams: can it
do this for us? It could, mostly, as long as everybody agreed to call things by journal names.

500+Scholarly journals installed on Manuscript Manager
2001The year Manuscript Manager launched
25+Publisher customers, small and mid sized
EUOwned, hosted and run from Copenhagen

PeerPath is built by the team behind Manuscript Manager. Not a rebrand of it and
not a rewrite from nothing. The same people, the same operational experience, and a product that stops
assuming what you are reviewing.

Akron ApS, which builds both, has been self funded since it was founded in
2015.
No debt and no outside runway to burn through, which is a duller thing to say than most
software companies manage and a more useful one if you are choosing a system to live in for a decade.

What we think

Four things that shaped it

Review is not only publishing

The same process runs in funding bodies, ethics committees, procurement teams and corporate research. Most software in this space assumes a journal, and everyone else bends to fit. That assumption is the thing we set out to remove.

Flexibility should not mean a project

Configurable usually means somebody quotes for a change. Every setting on this site is one your own team can reach, on the day they need it, without raising a ticket.

We choose who we work with

Manuscript Manager refers to the standards of DOAJ, COPE and OASPA when considering partnerships, and PeerPath does the same. Peer review software that will take any customer is part of the problem it claims to solve.

Say the awkward part

There is no legacy file import. Reviews in progress should finish where they started. Some integrations need a subscription you hold. All of that is on the site rather than saved for a call, because finding out late is worse than knowing early.

The people

A small team in Copenhagen

Seven of us. Small enough that the person who configures your workflow is one of
the people who built the thing it runs on.

Photograph
Andy BearePartner, CEO

Skills in IT and publishing, and more than twenty five years in peer review.

LinkedIn
Photograph
Ulrich Biel GulløvPartner, CTO

More than thirty years in tech. Leads data management and research and development.

LinkedIn
Photograph
Peter OkholmPartner, CMO

Fifteen years in consulting, now heading business development.

LinkedIn
Photograph
Kasper MøgelvangPartner, strategic advisor

More than twenty years of consulting, adding senior strategic direction.

LinkedIn
Photograph
Martin NielsenPartner, developer

Front end specialist on the tech team.

LinkedIn
Photograph
Christian G. HansenFull stack developer

Everyday development, plus the AI work and the third party integrations.

LinkedIn
Photograph
Mike KellyCustomer support

A long time Manuscript Manager super user, now running the support desk.

LinkedIn

Seven people, and the photographs need to be real ones shot consistently. Stock
portraits on an about page are the fastest way to undo everything the rest of the site is trying to
establish.

Get started

Tell us what you review.
We will show you the workflow.

Send us the outline of your process and we will build it in a session with you.