As is traditional at this time of year, we’re looking back over 2017. It does give me a more than mild sense of vertigo to think about how much we’ve done. And whilst, at times, the tumultuous happenings in the wider world have felt overwhelming, Bibliocloud continues to be a meaningful and tangible thing that I can do to help make the world better. We are honoured to be able to bring more organisation, more fluency, and more time to be creative to our publishers. And by freeing them up to do the work that matters, we can know that we’re helping them produce more of the sorts of books that will steer the world towards something better.

Books matter. It matters to us that we’re helping in their creation, and that the way we go about helping is something to be proud of, in itself. To those ends, our big moments of 2017 were oriented towards our goal of making our customers successful, and doing it in style.

Sara O'Connor joined the team!

As part of our plan to build a crack team of the best programmers in publishing, in April Sara O'Connor joined us as a full stack developer, bringing our technical team count to four and giving it a pleasing two-women, two-men gender balance. Sara was formerly editorial and digital director of Hot Key Books, a Bonnier imprint, who retrained as a programmer at Makers Academy, before working for business data company Exceedra. Domain knowledge is one of the hardest parts of programming: finding a team member who knows publishing and programming is rare and brilliant. Sara hit the ground running, first reviewing and improving the test suite for our royalties functionality and then diving into a hugely ambitious long-term project to allow user-controlled contact, product and other data uploads to Bibliocloud. The fruits of her labours will be revealed in early 2018, but for now it’s enough to say that it’s a dream come true for me to be able to watch people such as Sara reskill and reorient their whole career towards something they know makes a difference.

Sharpening our focus on customer success

Throughout 2017, one of our main ambitions has been to get better and better at delivering customer success. The year started with a bang as we won the IPG GBS Services to Independent Publishers award in February, as nominated by our own customers, so it was nice to know that we were heading in the right direction.

In March, Emily instigated a rota for our online ticketing helpdesk, making sure that there was always a team member dedicated primarily to managing queries, and over the course of the year we have better than halved our response times to support tickets. It was great to talk later in the year in October at Frankfurt with many of our customers, all of whom reported that things are going great. Vidisha at Zed Books, for example, credited Bibliocloud with underpinning their recent amazing success, which makes you tingle all over. (The link takes you to their stunning new website, proudly fed from Bibliocloud via our API). And then, as we close the year in December, the results of our latest Net Promoter Survey are coming in, and they’re looking really good. (More in the new year about those results and feedback, and how it’s driving our plans for 2018.) We’re so pleased that our efforts are helping you succeed.

Listening

Because we’ve orientated ourselves towards customer success, we’ve also got better at listening. By hearing where customers have had twangles, ideas and troubles, we have been able to focus our efforts on the work that really matters to them. All in all, our stats show that we deployed 200 discrete pieces of work, ranging from maintenance tasks such as THEMA code updates and new integrations; small improvements such as adding fields to API feeds; the occasional bug fix; and major features such as:

And coming in early 2018 are the fruits of our most recent efforts:

  • universal data importers that feed back on data quality and validations
  • a new default advance information sheet, designed by Tom Spindlow
  • a better schedules page: Screen shot 2017 12 18 at 15.36.29
  • and more! You can always follow along on our change log, and you can flip between old and new versions of code when we’re doing a big development, providing feedback whilst development is still ongoing.

Using tools and partnerships to improve our own processes

We’re in the business of writing tools which help our customers run their companies more effectively, so it stands to reason that we would try to be as efficient as possible in our own work. A festive shout out to the partners who help us support you: Graham at Editeur, IPAC, Nielsen, BDS, the completely brilliant NBNi, ALPSP and the IPG. And to the tools that help us make Bibliocloud better:

  • JIRA, which we use to manage our programming work
  • Bitbucket, where we store versions of our code
  • Codeship, which runs our tests before deploying code
  • Heroku, which hosts our applications
  • New Relic, which reports on how the applications are running
  • Zendesk, which keeps the conversation flowing between us and our customers
  • ReadMe, which provides our user and API docs
  • AWS, which provide database, storage and backup functions

We know that Bibliocloud sits as one more application in your landscape of tools and services, and we try our hardest to be among the best, in terms of usefulness, beauty and support.

Out and about

We’ve attended some banging events this year, and we plan to do more of that next year, whether as speakers or delegates. There were the trade shows: the London Book Fair in March and Frankfurt in October.

There was the new: the amazing Brighton Ruby conference in July and the Life Time Value conference in April, and the OpenTech conference in May. There was the annual IPG Spring and Autumn conferences (click that link for a brilliant reflection on the day by Emily), and the digital quarterlies.

As well as attending events which helped us reframe and reconsider some publishing truths, we contributed as much as we could to help other people find the joy of code. We ran our sell-out Try Coding for Publishers course in conjunction with Book Machine in April, which raised over £200 for Save The Children:

And we are regular and cheerful coaches at Railsgirls London.

Each day, getting better

We get our kicks from being competent in a field that matters. So it was a source of real pride to launch the Bibliocloud Component Library in May, hand-rolled by Andy and used throughout the year and into next as we increasingly standardise the interface. Screen shot 2017 12 18 at 15.45.46

We have also made great strides with our ONIX provision. We have sent 5700 ONIX files this year alone, containing 571,000 ONIX product fragments, totalling 20GB of data. Phew!

We also find time to pursue personal projects, having instigated a new Side Project Friday afternoon initiative. On Friday afternoon, when the clients tend to go a little quiet, we crack open our personal projects. Andy is learning React and Electron by building a rules viewer for tabletop games. Sara is working on her family bingo app, which she uses herself at events that attract 100 players. Emily introduced herself to SQL. Dave contributed to a number of open source libraries, such as the LISBN gem. And I wrote my makeourbook.com schools publishing app. Whilst that sounds nice but not very relevant, it is actually a fantastic way to hone and grow our programming skills and try out new ways of working. It’s an easy, motivational and interesting way to ensure we undertake ongoing professional development and cross-fertilise new ideas across the team.

And helping more publishers!

We were delighted to welcome seven new clients to Bibliocloud in 2017, who will be joined by 13 (and counting) in 2018. We plan to grow at a slow and steady rate and are glad to be able to curate close relationships with the sorts of publishers we feel best able to support, and most proud of helping. So a festive wave to these new clients: the Institute of Physics (– read our case study), Purdue University Press, Leuven University Press, the British Museum, What on Earth?, Innova Press, Rethink, and to those joining us in the spring. They join a fleet of publishers that we burst with pride to call our customers, who include:

Screen shot 2017 12 18 at 17.06.29

Although it’s lovely to work with new clients, you might be interested to know that our internal bonus scheme is based on renewals: 5% of the licence fee revenue from renewing clients is paid to non-director staff as a bonus. To be honest, our enthusiasm for Bibliocloud means that we’re pretty good sales people. However, it’s one thing to to sell software to new clients; it’s quite another to have them want to keep using it, a year later. So I’m delighted to report that, in 2017, all of our active clients renewed their licenses. It’s a real measure of success, I think, and we’re hugely grateful to our customers for sticking with us.

And so, to 2018

So here’s to continuing the hard work and customer focus into 2018 and beyond. We will be in touch with all our customers at the end of January to update them on our firm plans for the year, based on their feedback in our survey. (If you’re a client, and you’ve not yet responded, please do – it’s a great chance to shape Bibliocloud to your priorities, so it’s worth the five minutes!)

Thank you once again to our brilliant and important clients for 2017. This is all for you, and your books, and we hope you thrive and flourish in 2018 with us.

Archives

    Most popular

  1. Ruby code and why you should care
  2. A quick look at data visualisation and analysis
  3. Menial publishing jobs are destroying our future
  4. It's us in the industry who need to be able to code
  5. A manifesto for skills
  6. Learning how to code, the long way around
  7. Company news

  8. New website
  9. 2018 Customer survey report
  10. 2017 in review
  11. Sara O'Connor to join the team!
  12. And now we are five
  13. Prizes galore
  14. Product news

  15. 'Continuing to solve real problems': Futurebook 40, London Book Fair 2018 and the Works page
  16. How many authors is too many?
  17. Better ONIX fragments
  18. Advanced advance information!
  19. Schedules page
  20. Publishers hack their own bibliographic data
  21. Case studies

  22. Burleigh Dodds Science Publishing
  23. Zed Books
  24. IOP Publishing
  25. Code

  26. A publisher’s guide to APIs
  27. What publishers need to know about Ruby on Rails
  28. How APIs can make publishing more efficient
  29. A day in the life of a programmer
  30. eCommerce

  31. To go direct, publishers must mean business
  32. Don’t outsource your publishing business away
  33. Who has the balance of power over data?
  34. Inbound marketing
  35. The business case for going direct
  36. Why publishers must use direct sales
  37. ONIX

  38. A hidden benefit
  39. Thema Subject Codes Update November 2017
  40. ONIX. Not very standard
  41. Three ways to do more with ONIX
  42. A non-technical, beginners’ guide to ONIX for Books
  43. ONIX Changes
  44. BIC, Thema and artificial intelligence...
  45. How to create a catalogue automatically using ONIX and InDesign
  46. Skills

  47. Embrace the code
  48. Mechanical sympathy
  49. Publishers can learn a few things from programmers
  50. A taste of code
  51. Strategy

  52. Rejuvenation
  53. Why ‘easy’ publishing solutions hardly ever are
  54. The right tool for the job
  55. No computer system can fix a broken publisher
  56. Five things I've learned since moving into enterprise product management
  57. Managing expectations
  58. Start with Why – How to refine your publishing mission
  59. The real price of a strategy shift
  60. Technical debt
  61. Decisions, decisions
  62. Creative industries and the division of labour
  63. A company of one's own.
  64. Responsibility, Authority, Capability
  65. Sometimes, size matters
  66. The search for publishing's holy grails