The modern publishing management platform. Find out more

Build the software that powers publishing, literacy and the dissemination of knowledge.

Books make the world better – through story, research, long-form narrative, education, expert research and literacy. So we work to make our web app, Consonance, the best publishing management system in the world. We are ten years old in 2021, we’ve bootstrapped ourselves to profit – and we’re growing.

Current jobs.

Our business.

We started about ten years ago, with a system built to meet the needs of a single publisher, and initially grew by working mostly with trade publishers. More recently we have gained a strong customer base of academic and professional publishers, who tend to need management of much more complex data.

Our clients’ users work in editorial, production, marketing, and sales departments of book publishers, and our aim is to let them all work together as a single team. The book publishing domain is very complex, requiring a well structured and complex back end and a well-crafted user interface.

This is not a VC-ish operation, and client fit is much more important to us than achieving someone else’s growth target.

We’ve bootstrapped ourselves to profit, have solid cash reserves, and think of ourselves as a small and stable business offering expertise to our specialist clients. Our client retention and industry reputation are both excellent.

What we care about.

We are advocates of technical literacy in publishing, particularly for junior publishing staff, which leads us to initiatives such as running a Day of Code to empower publishing staff, running and connecting the worlds of tech and writing with Our corporate charity is also one of our clients: the literacy charity Our, ahem, “corporate” website has examples of our work in this area, as well as a showcase of some of the side-projects we work on individually. We have two sister book publisher companies, and, and we are an active member of the Ruby community, including publishing an edition of _why’s Poignant Guide for the Brighton Ruby 2020 conf.

Our brand promise is to make publishers better by sharing our expertise, and we communicate our expertise at scale through our app, and through writing and speaking.

GitHub actions

Our technologies. is a conventional Ruby on Rails (currently version monolith, which allowed us to rapidly develop to cover a lot of functionality.

Now we’re migrating complex interface requirements to React, with a GraphQL API to also allow clients to develop their own integrations.

  • 500+ models. It’s a complex business domain.
  • One main shared application, some single-client deployments.
  • Hosted on Heroku.
  • PostgreSQL. We solve a lot of performance problems with advanced SQL skills.
  • AWS: RDS, S3, SES, SQS, a little Lambda.
  • The existing interface is mostly ERB, with some React, mounted by Stimulus.
  • Complex interface areas are migrating to React (currently on React 17.0.2).
  • GraphQL API for React and client integrations, with Apollo client.
  • RSpec, Cucumber, React Testing Library and Jest.
  • Github, including Actions and new Projects.

Slack for chat, voice and video calls. Basecamp, VSCode, Skylight, Git Kraken, and Freshdesk. The vast majority of our work is on the app. ~10% is on implementations and integrations.

Our team.

We’ve been a team of four or five for the past few years, with a pretty even gender split and a tendency towards full-stack skills. We are re-orienting a little towards specialisation by tier, enabled by the adoption of GraphQL as an API.

Two of the three founders work full time as programmers and business managers.

All staff are full time employees, and we work as a distributed team across the UK. We dropped office life at the beginning of the pandemic, and it’s worked well for us, so we no longer have an office at all. When circumstances return to normal, we’ll have in person meetups.

On a daily basis, we put a “stand-up” onto Basecamp first thing in the morning, have midday meetups on Slack, and collaborate for advice and pair programming as needed.

As a team, we:

  • share design thoughts
  • take inputs and ideas from others, with final decisions made by technical practitioner directors
  • update each other regularly on progress
  • prioritise delivery over perfection
  • prioritise maintainability over everything

We work a four day week (Monday to Thursday), without overtime or out of hours pager duty. We’re flexible on hours - 7.5 working hours a day.

We aim for calm and steady working practices, through things such as an absence of deadlines, very rare meetings, only supporting the latest browser versions, only hosting our app on Heroku, minimising custom developments, not maintaining a backlog, and doing flexitime depending on how family, work and life best fit together.

Sounds interesting?

You will thrive here if you… .

  • Want to work long-term on a product which makes a positive difference to the world.
  • Think that books are good.
  • Enjoy collaborating.
  • Want to learn from your co-workers.
  • Want to help your co-workers learn.
  • Want to work 4 days a week, in a 100% distributed team, at a steady pace.

Working for us comes with….