A business operations platform, starting with mortgages
Mortgage operations involved linked data, documents, people and actions that a simple task list could not model.
I modelled organizations, divisions, roles and operation sequences around reusable document types, fields, formulas and templates. Process stages connect calculated and printable forms with tasks, external mailboxes, email templates and notifications. Hourly and piece-rate compensation, transactions and document-driven movements belong to the same operational model.
Business event
Rules & documents
Calculations
Actions & history
The initial business was mortgages, but I designed the underlying model around organizations, divisions, people, roles and process stages. The aim was to express a company’s operations through shared building blocks so another business could use the same core. This carries the modelling approach from my ERP experience into a Python web platform.
A document is a typed business entity with data, links, state and rules. Dynamic, nested and repeatable fields combine with calculated fields, formulas and calculators; templates produce the forms needed by a particular process. Printable output is one representation of that business object, while its structured data continues to drive the workflow.
Process stages and operation sequences connect documents with tasks, notifications and automation rules. A change in a document’s stage can become the condition for a calculation, a task or a transaction. Explicit relationships between those actions make the business sequence understandable and leave a history of what changed.
External mailboxes, message templates and sending services are connected to the operational data. For example, a document stage can determine when a prepared message goes to a realtor. The template, recipient and trigger belong to the same workflow as the document and the next task, rather than requiring manual movement between separate tools.
The platform includes hourly and piece-rate employee compensation alongside transactions and financial movements. Work performed and document states therefore have financial consequences within the operational model. This is the same connection I worked with in ERP: the business action, its document and its accounting effect must describe one coherent event.
Mortgage workflows gave the platform its first concrete business use case. The reusable core was deliberately designed to support other organizations and processes through configuration, documents and rules.
A role, a product, or a technical challenge. Share a little context.
To use the form, enable JavaScript. You can also write to me directly on Telegram.
Write on Telegram