Software, read closely.
Pilcrow is a small London imprint. We write mobile apps and websites, lay out the interfaces people read them through, see them through the app stores and keep them in print afterwards.
The argument, in one paragraph
A pilcrow is the mark scribes used before paragraphs existed: a red sign inside a continuous run of text saying a new thought starts here. We took the name because most software problems are really problems of where one thought ends and the next begins — a screen that tries to say four things, a checkout that interrupts itself, a website whose structure no longer matches what the organisation does. Our work is to find those breaks and set them properly. Sometimes that means building a new app from the first line; sometimes it means editing an existing one until it reads cleanly; sometimes it means looking after a system patiently for years. In every case we explain what we are doing in sentences rather than slides.
Five things we set in type
The reading comes before the writing
Before we propose anything, we read what you already have: the app, the site, the support inbox, the spreadsheet someone keeps beside the system because the system does not quite work. That reading is written up as a short report in plain English — what is sound, what is fragile, what we would change first and why. You can take that report to anyone. We would rather you chose us because the reading was useful than because we withheld it.
No invented testimonials. No borrowed logos. No statistics we cannot show you the working for.
A proof for your project
Mark each statement that is already true. The proof reads back what is still missing — the questions we would ask in a first conversation. Nothing leaves this page.