This work is a product-systems analysis based on my Domain Core–Driven Design (DCDD) approach.

The goal was to explore how a backend engineer can understand a B2B SaaS product before jumping into features, APIs, or implementation details.

Instead of analyzing the product as a list of features, I focused on the workflow behind it: the business object moving through different states, validations, actions, human review points, external integrations, and feedback signals.

The analysis explains why the domain core in many B2B SaaS systems is often hidden inside the workflow, and why backend systems should not only expose APIs, but also preserve the memory of the business process.

Key areas covered:

Identifying the business object moving through the system

Separating surface-level features from the real domain core

Mapping workflow lifecycle, states, and transitions

Thinking about automation boundaries before implementation

Understanding where human review and feedback loops should remain

Explaining why backend design should support traceability, reliability, and future integrations

This project reflects how I approach backend and API-heavy systems: I first clarify the core workflow, then design APIs, data models, state transitions, documentation, and integrations around it.