Search services, domain expertise, technology and proof.
Proof
Evidence from systems built under real operational pressure.
The useful proof is not a polished screenshot. It is the path from a messy workflow, fragile integration or risky legacy system to software that teams can operate, observe and keep changing after launch.
Manual cleanup, drifting data, blocked releases, brittle APIs or legacy code made the operating cost visible enough to act.
Move
What changed in the system
We shaped the data model, integration boundary, migration path, infrastructure or delivery loop around the constraints already in production.
Signal
How the result became visible
Cleaner handoffs, fewer hidden failures, safer releases, clearer ownership and systems that can be explained after the first launch.
Operational pressure
Technical move
Production signal
Domain context
Next step
Proof with context
The same shape recurs across domains, which is what makes it checkable.
Marketplace sync, structured knowledge, modernization and operational platforms look different on the surface, but the underlying move repeats. The domain cards below name where the context is already in hand.
Named domains
Marketplace data, Rails modernization, CMS and knowledge systems, operational tooling.
Inspectable craft
Public work such as 555 EUCRiders can be looked at directly, structure and all.
Confirmed scope
Client work is described at a level of involvement we can stand behind.
Where a project is not public, we describe the domain and the technical move rather than the client.
Evidence map
Six production patterns that show how the work becomes trustworthy.
Each pattern starts with pressure that was already visible inside operations. The useful part is the technical move that made the system easier to operate, recover and change.
Tens of thousands of products, large vendor feeds and category changes were crossing channels with too much manual cleanup.
ShippedRole-aware workflows, reviewable changes, documentation, stability improvements and production support.
MeaningDelivery stays practical without pretending sensitive domains are just normal CRUD.
Rails
RBAC
Docs
Review
Proof across domains
Domains where we have shipped real systems.
The common thread is operational complexity: messy data, external systems, roles, workflows, production infrastructure and software that has to keep working long after launch. These are the domains where we can build, extend, rescue or scale a system with the context already in hand.
Marketplace operations and product synchronization
Marketplace operations and product synchronization
We have built large product and category synchronization flows for marketplace operations: tens of thousands of products, structured feeds reaching hundreds of megabytes, normalization, delta sync, reconciliation, category-tree modeling, taxonomy and parameter mapping. The work also covered adapter-based marketplace architecture and authenticated panel automation where official APIs were not enough.
storefront -> catalog -> order -> back officecheckoutinventory
Commerce platform integrations
We connect storefronts, commerce APIs, checkout flows, product search, inventory and product data into back-office workflows a team can actually run. Shopify can be part of that picture, but the real work sits in the integration layer around orders, catalog data, third-party services and day-to-day commerce operations.
We have built and extended multilingual CMS and content platforms with media import, asset handling, metadata, SEO and Open Graph fields, localization, structured JSON content models, version tracking and admin UX. Public work includes 555 EUCRiders, a multilingual knowledge platform with a TypeScript specs database, JSON-LD, Turtle, Pagefind search and AI-assisted publishing workflows.
AI-assisted content and structured knowledge workflows
Our AI work sits on top of real domain data and editorial or operational processes, not generic vector search. That includes AI-assisted content pipelines, translation workflows, research workflows, quality monitoring, voice guides, prompt engineering and integrations with LLM APIs.
We have worked with financial-domain systems where maintainability, roles, authorization, process state, integrations and auditability all matter. Reverse factoring is a familiar shape: suppliers, buyers, invoices, documents, decision states, financing workflows and third-party integrations.
Healthcare and dental applications usually need careful workflow design more than flashy UI: forms, surveys, patient and specialist-facing interfaces, documentation, secure access, role-based permissions, communication and admin panels. We keep the claim practical: reliable business software for sensitive domains, without overclaiming undocumented compliance.
Research platforms, grants and institutional tools
We help turn complex expert knowledge into usable web products, clear information architecture and maintainable data models. That can mean scientist-facing tools, grant-related systems, review workflows, structured knowledge presentation, long-form content and institutional requirements.
We have worked with Decidim, the Ruby on Rails participatory democracy framework originally built for the City of Barcelona. The experience is close to public-sector-grade work: citizen participation, consultations, assemblies, proposals, participatory budgeting, documentation, security improvements, Linux server setup, stability and code review.
We extend web applications with the real-time features teams rely on every day: WebSockets, Action Cable, chat and messaging flows, notifications, SolidQueue background jobs, admin panels and CRUD interfaces. The goal is practical operational software that gives people a dependable place to work.
We stabilize and modernize existing systems: Rails upgrades including Rails 8 paths, older frontend migrations into React 18 and Vite, PostgreSQL performance work, Linux production setup, NGINX, SSL, Puma, background workers, queues and deployment flows. This is where senior judgment matters: keep what works, replace what blocks progress and make production calmer.
