Case studies with ownership and outcome

Public work where permission exists and concrete evidence when a project is protected by NDA or white-label terms.

Case index

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

Artisan e-commerce and D2C operations

Operational e-commerce for Arafilum

Problem

The brand needed to sell online, not just show a landing page: catalog, cart, payments, orders, shipping, emails, invoices and admin.

Intervention

I built the MVP end to end with public store, checkout, customer account, admin panel, PDF invoices, emails, shipping and multi-channel base.

Ownership

Full-stack development, e-commerce, payment integrations, operations and admin.

Outcome

A working store base with catalog, checkout, orders, invoices and admin connected in one flow.

What an agency can buy

A functional e-commerce delivery with admin, payment, email, invoicing, logistics and operational base.

Context

Artisan brand with direct sales, its own catalog and order operations.

Frame

Direct client with authorization to show and link the work.

Role

Full stack, e-commerce, payment integrations, operations and administration.

Visibility

Public case linked with authorization.

Stack and working frame

Stack and working frame: Next.js, TypeScript, database, payments, email, PDFs and deployment.
Duration: MVP by phases until sales, operation and minimal administration were covered.
Applied judgment: For a small e-commerce, showing product is not enough: the system has to charge, register, communicate, ship and invoice.

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

Local web, SEO and technical lead capture

Open public work

Local lead-generation website for Integraleon

Problem

A broad technical service offer had to become a clear website for homeowners, businesses and SMEs in Leon.

Intervention

I defined the commercial structure, wrote services, prepared local SEO, public routes, contact and static deployment with a custom domain.

Ownership

Web development, static architecture, technical SEO, commercial content and deployment.

Outcome

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

What an agency can buy

A local service website ready to publish, with SEO structure, commercial copy, contact path, deployment and domain.

Context

Local technical service for homes, businesses, SMEs and light industry.

Frame

Direct client with authorization to show and link the work.

Role

Static web, local SEO, commercial content and Cloudflare Pages publication.

Visibility

Public case linked with authorization.

Stack and working frame

Stack and working frame: Next.js App Router, static export, TypeScript, CSS, JSON-LD, sitemap, robots, Cloudflare Pages and GitHub Actions.
Duration: Fixed project with deployment, public validation and domain adjustment.
Applied judgment: A local service website works better when it quickly explains what is solved, where the team works and how to request a quote.

B2B forestry technology, offline Android app and legacy back office

Open public work

Technical diagnostic of +DERA for MaderaPlus

Problem

MaderaPlus needed to understand the real state of +DERA: field Android app, offline synchronization, backend/API, legacy website and release process before investing in evolutives.

Intervention

I rebuilt the technical map, set up local staging, tested the app, backend and web with anonymized data, reviewed the historical issue log and turned the findings into a 30/60/90 roadmap.

Ownership

Senior technical diagnostic, staging QA, evolution architecture and backlog prioritization.

Outcome

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

What an agency can buy

Executable technical audit, reproducible staging, app/backend/web testing, issue prioritization and roadmap to sell or decide the next phase with less uncertainty.

Context

B2B forestry technology with field app, web back office, API and offline/online synchronization.

Frame

Direct client with permission to show brand, logo and public website.

Role

Technical diagnostic, staging, QA, prioritization and roadmap.

Visibility

Public case with brand and website; no internal screenshots or private +DERA materials.

Stack and working frame

Stack and working frame: Android Java, SQLite and offline sync, CakePHP/JSON API, Joomla/PHP legacy, MySQL, Docker Compose, staging fixtures and Kotlin/KMP, Compose, Ktor and React recommendations.
Duration: Scoped diagnostic with documentation delivery and review session.
Applied judgment: Before selling evolutives on a live legacy product, uncertainty should become evidence: environment, tests, releases and agreed priorities.

Digital identity and biometrics

SDK and partner integration experience

Problem

Sensitive integrations had to become easier without turning onboarding into a support bottleneck.

Intervention

I improved APIs, examples and integration decisions to reduce repeated support.

Ownership

Senior support on integration experience, APIs, technical documentation and external team support.

Outcome

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

What an agency can buy

An SDK/API integration surface with clearer docs, examples and reduced repeated questions.

Context

B2B platform with sensitive integrations for partners.

Frame

Live product with pressure on adoption and support.

Role

APIs, integration architecture and usage experience.

Visibility

Anonymized case due to product and commercial context sensitivity.

Stack and working frame

Stack and working frame: Kotlin, Android, SDKs, REST APIs, integration contracts, examples and documentation.
Duration: Phased work inside a live product, with evolution and partner support.
Applied judgment: Integration is not sold only as code: it is also clarity, examples and less dependency on the technical team.

Mobile product with sensitive flows

Technical stabilization before production

Problem

The project carried quality-control risk and too much cost from regressions.

Intervention

I introduced contract tests, quality gates and a more stable production release path.

Ownership

Mobile support for stabilization, technical QA, contract review and release preparation.

Outcome

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

What an agency can buy

Pre-production review, bug fixing, critical-flow QA and publication support.

Context

App with critical flows and high cost of error.

Frame

Team under delivery pressure and needing better quality control.

Role

Contract tests, quality control and production release.

Visibility

Anonymized case due to operational and product sensitivity.

Stack and working frame

Stack and working frame: Android/Kotlin, contract tests, CI, critical flows, publication checklist and regression control.
Duration: Stabilization sprint and release close focused on reducing risk before publication.
Applied judgment: Before publishing, it is better to buy less uncertainty, not only more development hours.

Banking, loyalty and digital product

Senior support to turn roadmap into deliverables

Problem

Teams under business pressure needed to move forward without constant supervision.

Intervention

I worked as technical support across mobile product, web and integrations.

Ownership

Senior full-stack support to turn backlog, dependencies and technical pieces into closed deliverables.

Outcome

More capacity to reach milestones and less technical blocking.

What an agency can buy

Senior capacity to deliver web, app, backend or integration work without expanding the permanent team.

Context

Banking, loyalty and digital product teams under business pressure.

Frame

Work blocks with direct clients and white-label contexts.

Role

Support across mobile product, web and integrations.

Visibility

Groups several real contexts without exposing brands or commercial relationships.

Stack and working frame

Stack and working frame: Web frontend, Android/Kotlin, backend, APIs, integrations, technical review and coordination with existing teams.
Duration: Milestone-based work blocks and punctual continuity depending on product or agency load.
Applied judgment: Support works better when there is an owner, a priority and a technical piece with a defined exit.

Useful proof is not a gallery. It shows what was resolved.

If your delivery has a clear objective, timing and risk, I can assess a comparable scope.

Discuss a similar case