Capabilities before screens
A module is an interface into a capability, not the capability itself. That distinction keeps business rules useful across Studio, public portals and agent-facing experiences.
The foundation is the product.
Eight years building a business platform where identity, operations and automation belong to the same system.
Visit project ↗The problem worth solving.
Business software becomes difficult when every capability brings its own identity, rules and version of the truth. Alliance Business Suite is my long-term answer: a common business foundation that can support specialised experiences without rebuilding the fundamentals every time.
My role
I have spent eight years building the platform, shaping its architecture and developing its foundations. I work across the architecture: the business model, service contracts, application surfaces and the execution infrastructure that connects them.
Alliance Business Suite / Architecture
One foundation. Many responsibilities.
Business platformRelationships, not a deployment diagram
People & agents
Web, desktop, portals
People
Agents
WebDesktopPortals
Business capabilities
Distinct models. Deliberate ownership.
Governed execution
Commands, events, evidence
CommandsExplicit business intent
EventsBusiness facts
EvidenceReviewable outcomes
Across the systemShared identityTenant boundariesPolicyDurable delivery
Relate
A customer, supplier and employee can be different roles of a relationship. I model those distinctions without turning every product into an isolated address book.
CRM owns parties and profiles. Marketing and Content own their respective campaigns and publications.
Contact / Profile / Campaign / Content- Customer relationships
- Contacts & profiles
- Marketing campaigns
- Lead management
- Social engagement
- Content & publishing
Inside one operation
Issue invoice. Follow the boundary.
Main flowConditional path
Read the full flow, or select a stage.
Solid paths describe the main flow. Dashed paths depend on configuration or an explicit condition.
Enter
Person / API
Own tenant + permission
Agent / workflow
Also requires approval bound to the draft
Check
- Only the tenant’s own invoice
- Already issued? No change.
- Check draft fingerprint when required or supplied
Commit
One transaction- Draft
- Signed
- Amounts locked
Number the invoice
In the same transaction, if the tenant uses a numbering range
Corrected only by a credit or debit note
Save the transaction
After commit
In-process notification
Best effort, never a delivery guarantee
Business event envelope
When business events are enabled
Accounting command
Delivery when the outbox is enabled
The transaction ends before notifications and downstream delivery begin. Dashed branches depend on configuration; this diagram makes no claim about deployed settings.
Decisions that shape the system.
Own the boundaries that matter
Identity, tenant scope, permissions and durable work must remain coherent as the platform grows. Shared contracts make those boundaries reviewable instead of leaving every feature to invent its own.
Build for more than one interface
Service boundaries separate the business model from any single application. The same foundation can support people in a browser and software carrying out a bounded action.
Architecture earns its place when it makes the next product easier to build without making the rules easier to bypass.