A client once sent me a broad business proposal and asked:
“How much will this cost?”
Before giving an estimate, I realized the real issue was not pricing.
The workflow was still unclear.
The core entities and state transitions had not been defined.
The MVP scope was too...
Many backend integration projects don’t fail because the API is hard.
They fail because the business flow is unclear.
A customer books an appointment.
Then submits a digital form.
Then the bank processes the transaction.
Then a PDF is generated.
Then WhatsApp or email...
I just added a new work to my portfolio:
Finding the Domain Core Inside a B2B SaaS Workflow
This is a product-systems analysis based on my Domain Core–Driven Design (DCDD) approach.
The idea is simple:
Before designing APIs, data models, or automation logic, we need to understand...
I keep coming back to the same thought when looking at early-stage platform products:
sometimes the product does not need more features yet.
It needs to become more real first.
I wrote a short note on why discovery, trust, supply density, and platform depth often matter before the...
A lot of integration problems are not really about the API call itself.
They show up when the external system is delayed, duplicated, partial, or wrong — and your internal workflow still needs to stay reliable.
That’s where backend design starts to matter:
- clear state transitions
...
