01
Build for a real org, not a demo
Every org has a custom object somebody invented three years ago, a field nobody dares rename, and a process that made sense at the time. Software that assumes otherwise breaks in week one.
In the product: Any object, standard or custom, five levels of lookups deep
02
Say what a thing costs before it bites
Salesforce caps Notes & Attachments at 25 MB. We would rather show you an awkward limit at the moment you choose than defend a support ticket about it later.
In the product: The 25 MB warning, shown the moment you pick that store
03
Prove it in a sandbox first
Nothing should be tested for the first time in production. The first real document should never also be the first experiment.
In the product: Every feature behaves identically against a sandbox
04
Fail loudly, never silently
A protection that cannot be applied stops the send and says why. A connection whose credentials cannot be read shows a badge instead of pretending to work. Silent failure is the expensive kind.
In the product: An unresolvable signer password blocks the send outright
05
Test what we ship
The document engine is the part customers cannot afford to have wrong, so it is the part with the most coverage - written after the fact, deliberately, because it had none.
In the product: 54 automated tests across the document engine alone
06
Audit our own work honestly
We keep a standing production-readiness audit that scores this product against enterprise expectations rather than against other small products, including the parts that score badly. It is how we choose what to build next.
In the product: Scored on nine dimensions, weak areas published, not hidden