Skip to main content
Services

Build, improve, or rescue a digital product.

Choose the problem closest to your work. I lead product thinking, UX, and frontend delivery; specialists join where the product needs them.

  1. Websites

    Clear, fast websites that explain the offer, show credible proof, and make the next step easy to find.
    Explore Websites
    Best fit
    For organizations that need a credible public presence, a campaign platform, or a product story that works across accessibility, search, answer engines, and real customer journeys.
    Expected outcome
    A fast, maintainable site with clear information hierarchy, useful conversion paths, technical SEO foundations, and content that supports discoverability.
    Typical delivery
    Information architecture, interface engineering, responsive media, semantic SSR content, technical SEO, structured data, internal linking, and deployment.

  2. Applications

    SaaS products, portals, booking flows, and PWAs built around a clear task and dependable application states.
    Explore Applications
    Best fit
    For new SaaS products or established applications whose workflows, interface architecture, mobile experience, or product reliability need to improve.
    Expected outcome
    A scalable frontend foundation with explicit state ownership, accessible workflows, resilient data states, PWA capability, and a coherent design system.
    Typical delivery
    Product flows, Vue/Nuxt architecture, authentication UI, dashboards, forms, real-time states, PWA-ready patterns, testing, and release support.

  3. Business systems

    CRM, ERP, dashboards, internal tools, and AI workflow automation designed around the work that keeps an organization running.
    Explore Business systems
    Best fit
    For teams replacing fragmented tools, automating repeatable document and data work, or improving a basic agent that has become unreliable or difficult to extend.
    Expected outcome
    Clearer workflows, less operational friction, better visibility, and reviewable AI automation for repeatable work.
    Typical delivery
    Workflow mapping, role-aware interfaces, tables and reporting, AI workflow automation or agent improvement, approval and recovery paths, and backend coordination.

  4. Interactive 3D

    Purposeful Three.js and WebGL experiences that explain, configure, or explore a product through space.
    Explore Interactive 3D
    Best fit
    For product explainers, configurators, simulations, launches, cultural work, or services where a 3D interaction communicates something a flat page cannot.
    Expected outcome
    A progressive-enhancement experience with semantic fallback, defined GPU budgets, accessible controls, and performance-aware capability gates.
    Typical delivery
    Interaction concept, procedural or asset-based 3D, performance tiers, fallback design, device testing, and production integration.

  5. Search visibility

    Technical SEO, answer engine optimization (AEO), generative engine optimization (GEO), and public evidence that make the business easier to understand and verify.
    Explore Search visibility
    Best fit
    For businesses that need a sound technical search base, clearer page and entity architecture, or visible answers that AI systems can interpret and verify.
    Expected outcome
    A clearer web presence with crawlable pages, distinct content roles, and verifiable answers, without guaranteeing a ranking, citation, or placement.
    Typical delivery
    Technical SEO, content and entity architecture, AEO question research, GEO evidence review, semantic SSR content, Schema.org, performance review, and internal linking.

  6. Vibe Code Rescue

    A focused audit and recovery path for rushed or AI-generated code that has become difficult to trust or release.
    Explore Vibe Code Rescue
    Best fit
    For founders and teams with a prototype or live product whose speed of creation has become code debt, unreliable behavior, unclear ownership, or a barrier to the next release.
    Expected outcome
    A practical recovery path: a truthful baseline, stabilized critical flows, cleaner architecture, safer feature delivery, and a rebuild recommendation only when rescue is no longer economical.
    Typical delivery
    Codebase audit, recovery roadmap, critical bug fixes, architecture cleanup, frontend and backend coordination, deployment hardening, feature delivery, documentation, and handoff.

One accountable delivery path

I stay accountable for product framing, UX, frontend quality, accessibility, performance, and discoverability. Backend and infrastructure specialists join when required.

  1. Understand the work

    Clarify users, workflows, evidence, dependencies, risks, and the smallest useful release.

  2. Shape and build

    Turn that context into an accessible, localized, performant interface with clear technical boundaries.

  3. Verify and release

    Check agreed flows, search foundations, integrations, ownership, and the production path before launch.

Tell me what needs to work better.

A short description of the users, current friction, and next decision is enough to start.
Start a project