Insights

Ideas to build and operate better.

Guides, analysis and lessons on product, artificial intelligence, growth, communications and cloud.

Editorial themes

Software and SaaS development

Digital products that solve, scale and evolve.

AI, automation and data

AI systems for real-world processes.

Marketing, ecommerce and marketplaces

Demand, catalogue, partners and conversion.

Communications and customer care

Every conversation in the right channel.

Cloud, infrastructure and operations

Available, observable and ready services.

results

14 results

Diagram of an API using an idempotency key to recognize retries and prevent an operation from being duplicated.

Integraciones, APIs y sistemas conectados7 min

Idempotency in APIs: How to Prevent Duplicates Without Hiding Errors

An idempotency key lets you retry sensitive operations without repeating their effects. Learn how to define its scope, handle concurrency, and respond to errors.

↗

Diagram of shared identifiers between a CRM, an ERP, and an ecommerce platform.

Integraciones, APIs y sistemas conectados7 min

Identifiers in integrations: how to decide which ID to share between systems without creating duplicates

A practical framework for choosing, preserving, and reconciling identifiers across CRM, ERP, ecommerce, and custom applications without confusing entities.

↗

Diagram of inventory reservation statuses across ecommerce, payment, ERP, and warehouse

Marketing, ecommerce y marketplaces6 min

Inventory Reservation in Ecommerce: How to Decide When to Commit Availability

Choosing when to reserve inventory prevents overselling and inventory lockups. This framework helps define timing, expiration periods, priorities, and operational controls.

↗

Diagram of one-way and two-way integration between ecommerce, ERP, and CRM

Integraciones, APIs y sistemas conectados7 min

One-Way or Two-Way Integration: How to Choose the Synchronization Direction Without Creating Data Conflicts

Decide which systems should create, read, and update data to choose synchronization that is secure, manageable, and aligned with each process.

↗

Shared state diagram connecting multiple systems in a request process.

Integraciones, APIs y sistemas conectados7 min

Shared Process States: How to Avoid Different Interpretations Across Systems

A shared state model prevents discrepancies between applications, clarifies ownership, and helps detect stalled processes before they affect customers.

↗

Conceptual diagram of an integration event with included data, references, and connected systems.

Integraciones, APIs y sistemas conectados8 min

How to Decide Which Data to Include in an Integration Event

A practical framework for deciding which data travels in an event, which data is retrieved later, and how to avoid dependencies, stale data, and security risks.

↗

Decision diagram comparing real-time integration and batch processing for connected systems.

Integraciones, APIs y sistemas conectados8 min

How to Decide Between Real-Time and Batch Integration Without Compromising Operations

Choose between real-time and batch integration based on the cost of delay, volume, available recovery options, and operational capacity.

↗

Conceptual diagram of data authority across CRM, ERP, ecommerce, and customer support.

Integraciones, APIs y sistemas conectados8 min

How to Decide Which System Is the Source of Truth for Each Business Data Point

A practical framework for assigning authority to each data point, reducing conflicts between systems, and designing traceable, sustainable integrations.

↗

Web form follow-up diagram from receipt to closure

Comunicaciones y atención6 min

From form submission to first contact: how to design a traceable sales follow-up process

Design a web form follow-up process with validation, deduplication, assignment, retries and traceability to reduce missed requests and duplicate contacts.

↗