A more considered way to handle letters.

The correspondence workflow in practice.

The plan is deliberately broader than online postage. People should be able to keep letters they received elsewhere, organise correspondence around a person or matter and return to the exact version that was issued.

For organisations, the emphasis extends to permissions, approvals, references, documented delivery events and useful audit history. We are designing those features carefully because no software should claim to prove more than its records can actually establish.

A recognisable product also needs an understandable philosophy. We want the interface to feel familiar enough that a person can file one important letter without training, while being structured enough for an organisation that handles large volumes of formal correspondence. That is why the visual direction is calm and corporate, with compact dashboards, clear navigation and accessible reading layouts rather than decorative complexity. Good design is measured by whether people can confidently complete a task.

The project also takes evidence claims seriously. A unique reference helps identify a record, a cryptographic fingerprint helps check a file, and a verified delivery event describes a particular external action. These are useful capabilities, but they are not interchangeable. We want Epistles to explain those differences plainly and retain the right records so customers can make their own informed decisions. That careful approach underpins both the planned software and the public information on this website.