How Ethos Lending retired Salesforce, Bamboo, DocuSign & WordPress— and owned every line of code

On every ticket the governing instinct is: find what already exists before writing anything new. Where does this behaviour live today? What already satisfies it? What is genuinely missing? Which files and database objects change? Only then does code get written — and only the minimum.

We build brownfield, and treat it as a discipline rather than a limitation. That habit is why a system this size still has one contact search, one email sender, one audit log — instead of four of each.

Nothing is built off the cuff. Work is sequenced against a live roadmap the system generates from its own activity record, not from a slide. Phases are frozen before the next one opens — Phase 1 closed and locked before Phase 2 scope was written.

A request arriving mid-phase is recorded first, then folded in, so scope never quietly drifts. Business language is mapped to the tables, functions, policies and screens that already own it, and only the delta is built — so new requirements land as small, structurally sound additions instead of parallel systems.

Fourteen roles scoped by branch and team, a role-conflict matrix, reasons recorded on grants, and expiry enforced in the database — not in memory.

Personally identifiable information is masked through safe views by default. The open path is the exception, never the rule.

Audit trails are written by database triggers, not application code, so they cannot be skipped. The record exists because the change happened.

Feature flags fail closed with a single emergency switch. Every module carries a preflight mapping the change to requirements, RBAC, PII and rollback.