Software and SaaS development
Digital products that solve, scale and evolve.
Insights
Guides, analysis and lessons on product, artificial intelligence, growth, communications and cloud.
Editorial themes
Digital products that solve, scale and evolve.
AI systems for real-world processes.
Demand, catalogue, partners and conversion.
Every conversation in the right channel.
Available, observable and ready services.
Event sourcing stores changes as events, while a traditional model stores the current state. Compare requirements, costs, and risks before choosing an approach.
↗
Agreeing on precision, rounding rules, and a system of record helps prevent discrepancies across ecommerce, payments, invoicing, and accounting. This guide offers practical criteria and tests.
↗
A practical framework for deciding which business rules teams can edit, which require approval, and which changes need technology review, testing, and controls.
↗
A useful error message explains what happened, what information was saved, and what to do next. Learn how to write and validate messages in your product.
↗
Learn how to choose between a preorder, reservation, and backorder based on replenishment certainty, realistic timing, and your ability to deliver on the promise.
↗
Choose a prototype based on the uncertainty you need to resolve, from a sketch that checks understanding to a technical test that helps uncover risks.
↗
Learn what record removal means, how to propagate it across connected systems, and which exceptions to plan for so synchronization does not restore records or disrupt workflows.
↗
Compare uploads routed through your application server with direct-to-storage uploads. Choose an approach based on file size, security, user experience, and operational capacity.
↗
Prioritize technical debt using evidence of impact, risk, and the cost of delay. Decide whether to fix, mitigate, monitor, or temporarily accept each issue.
↗
Evaluate each request by its need, impact, and alternatives to decide whether to add it, swap it for another task, defer it, or decline it.
↗
Design SaaS invitations with clear states, expiration rules, safe resending, and consistent handling of duplicate emails, existing accounts, and permission changes.
↗
Define what information each agent needs to resolve a case, and how to limit, retrieve, and log access without replicating unnecessary data.
↗