CCM consultancy · TypeScript and React
Customer communications, done properly.
Double Byte builds the letters, statements and bills that land on people's doormats and in their inboxes, for insurers, banks, energy companies and print bureaux, with experience going back to 2004. Over the last few years we've also developed our own software for it: ByteDocs to create customer documents, and ByteCompare to prove they're right.
01 · What we do
Twenty years of document work, and the code around it
Most of our work is hands-on CCM: building, fixing and moving document estates. The rest is the data and software that surround them.
CCM development
Letters, statements, bills and policy documents in Exstream, Inspire, Messagepoint and more.
Migrations and print
Moving document estates between platforms, print houses and the cloud.
Data and pre-processing
Getting the data into shape before it reaches the document.
TypeScript and React
Web applications and portals, from a clickable prototype to production.
Reviews, standards and training
A second pair of eyes on your estate, your standards and your team.
02 · Our software
Two tools we always wanted on client sites
Built from the ground up, from real experience. Over the last few years we've developed our own software, shaped by the problems we kept running into on other people's platforms.
ByteDocs · Customer communications
Your customer communications, built properly.
ByteDocs is our own CCM platform. It turns your customer data into personalised letters, statements and notices, as PDF for email and archive or AFP for the print room. Write the wording once, design the page once, and let the data decide what each customer gets.
- Shared page templates and wording, changed in one place
- Documents picked from the data: a DOC_ID, a flag or a calculated value
- Where used for everything, so you know what a change touches
- PDF and AFP from the same design, with approval built in
ByteCompare · Document comparison and testing
Prove the output is right, page by page.
ByteCompare puts two versions of your documents side by side and shows every difference between them: wording, layout, fonts, colours, lines and images. AFP, PDF, HTML or text, in any combination, from a single letter to a whole print run.
- Any output against any other: AFP, PDF, HTML or text, in any combination
- Letters paired by account number, so a missing page or customer doesn't throw the rest out
- Flag, accept or ignore each difference, with a report for sign-off
- The same checks on the command line, for every release
03 · Toolkit
What we work with
The composition platforms you're likely to have, the languages that hold them together, and the modern web stack we build in now.
Composition
- OpenText Exstream
- Quadient Inspire
- Messagepoint
- DOC1
- PReS
- ByteDocs
Output
- AFP
- HTML email
- SMS
Languages
- TypeScript
- JavaScript
- React
- Go
- Python
- Perl
- PL/SQL
- COBOL
Platforms and testing
- Red Hat Linux
- AWS
- Git
- Jira and Confluence
- ByteCompare
04 · How we work
Real output early, no surprises late
Document projects fail at the end, when the output finally gets compared with what went out last year. So we compare from the start.
- 01
Understand
We start with your documents and your data as they are today, not as the specification says they should be.
- 02
Show
You see real output early: a document for a real customer, or a screen you can click, so problems surface while they're cheap.
- 03
Build
Small steps, checked against the old output where there is one, with progress you can see every week.
- 04
Hand over
Documentation, standards and training, so your team can run it after we leave.
Got a document problem?
A migration, a rebrand, a deadline, or a platform you'd like to get away from. Tell us about it and we'll tell you honestly how we'd approach it.