Software case studies with scope, evidence and outcome.

Public work where permission exists and anonymized context where confidentiality applies. Both explain what I owned and what was resolved.

Discuss a similar case

Three public projects

The brand or website is shown with explicit permission. Full case studies document problem, intervention, ownership and outcome.

Arafilum homepage screenshot with product catalog, checkout and store navigation.

Artisan e-commerce and D2C operations

Operational e-commerce for Arafilum

Read full case study Open public website

Problem: The brand needed to sell online, not just show a landing page: catalog, cart, payments, orders, shipping, emails, invoices and admin.
Outcome: A working store base with catalog, checkout, orders, invoices and admin connected in one flow.

B2B forestry technology, offline Android app and legacy back office

Technical diagnostic of +DERA for MaderaPlus

Diagnostic staging in place, 203 backend/API calls documented, 32 anonymized business requests, 115 issues/improvements reviewed and 23 prioritized actionable entries.

Read full case study Open public website

Integraleon homepage screenshot with electricity, domotics and automation services in Leon.

Local web, SEO and technical lead capture

Local lead-generation website for Integraleon

Integraleon has a fast website with its own domain, local SEO routes and direct contact by call, WhatsApp or form.

Read full case study Open public website

Experience under confidentiality

The technical context and outcome remain, while brands, people and sensitive details are omitted.

Digital identity and biometrics

SDK and partner integration experience

More than 50 client and partner integrations supported, with around 35% less integration support.

Mobile product with sensitive flows

Technical stabilization before production

The delivery gained stability and regressions dropped by around 30%.

Banking, loyalty and digital product

Senior support to turn roadmap into deliverables

More capacity to reach milestones and less technical blocking.

Invoicing · AEAT sandbox

VERI*FACTU validation against the AEAT sandbox

An anonymised technical case covering a product release that completed creation, cancellation, controlled rejection and correction before commercial use was enabled.

A case study helps determine whether the next delivery is comparable.

Share the objective, timing and main risk. I can tell you whether the scope is similar and what should be reviewed first.

Discuss a similar case