# Web application development | Slash Digital Lab, Bogotá

Source: https://slash-digital.io/en/web-applications/

Digital product & software Platforms that operate: e-commerce, portals, event platforms and owned SaaS. Performance, accessibility and security by default.

- Performance Core Web Vitals
- Accessibility WCAG 2.2 AA
- Cases Chanel · Paperless

Start a project
See real work

In short
Slash Digital Lab builds production web applications from Bogotá, and a web app is measured on three things: speed on mobile, stability under load and traceability of what happens. We build platforms to that standard, from e-commerce to internal systems.

Evidence: the Paperless platform at JCDecaux Mexico, the payments work with Chanel EMEA, the B2B and B2C wine e-commerce of UVAS Trading in Madrid and the official app of Colombia Tech Week 2026. When the web is part of a full product, we run it as a digital product, with a mobile app when needed.

What we deliver

## What platforms we build

We pick the stack case by case and write the decision down.

01

### E-commerce & payments

Catalogue, checkout, local payment methods (Klarna, Adyen) and reconciliation.

02

### Internal platforms

SSO, approvals, dashboards and audit (see Paperless).

03

### Event platforms

Agenda, networking, chat and maps that survive event-scale peaks.

04

### Owned SaaS

Full-stack product with multi-tenancy, roles and billing.

How we work

## How we ship production web

-

### Architecture

Stack, performance and security decisions documented before coding.

-

### Build

Sprints with demos; per-page performance budgets.

-

### Testing

Accessibility, load and edge cases on low-end phones.

-

### Launch

Deployment, monitoring and an incident-response plan.

Scope and deliverables

## What the project delivers

- **Performance:** Per-page budgets and Core Web Vitals targets.

- **Security:** OWASP, headers, dependency reviews.

- **Accessibility:** WCAG 2.2 AA verified.

- **CMS:** Frictionless self-service content management.

- **Integrations:** Payments, CRM, ERP and own APIs.

- **Observability:** Logs, metrics and alerts from day one.

Proof in production

## Platforms in production

Read more

Chanel · EMEA

### Local payment methods: a method to launch them in days

With Chanel EMEA we opened the path to integrate local payment methods (such as Klarna) on Chanel.com without depending on the worldwide roadmap: an autonomy diagnosis, Hybris and Adyen analysis, and a secure proxy architecture on a shared Adyen merchant account.

Learn more →

Read more

IB Group · Planet Fitness Mexico

### One room-booking app, deployed for three offices

A door tablet for every room and an admin console, synced with Exchange. First for Planet Fitness Mexico, then for IB Group's Fashion Depot and Grimatex: 22 rooms across three deployments.

Learn more →

Read more

JCDecaux Mexico

### From paper to a secure internal platform

Paperless centralizes purchasing, inventory, work orders, advances and refunds for JCDecaux Mexico in an internal platform with Single Sign-On, approvals and audit-ready traceability.

Learn more →

Read more

Remittance network · Colombia → Venezuela

### From a legacy Web Forms app to an owned remittance platform

We replaced the ASP.NET system of a Colombia → Venezuela remittance network: 8 roles, mandatory MFA, every money movement in Postgres functions and 132 automated tests, in about six weeks.

Learn more →

Frequently asked questions

## The questions we hear often

**Modernize legacy or start fresh?**
Both; discovery shows where rebuilding pays and where modernization is enough.

**Headless or SAP Commerce?**
Yes; the proxy architecture we designed with Chanel EMEA is an example.

**Can our team edit content?**
Yes: a CMS for content changes without developer dependency.

**How long is a portal?**
Discovery to production typically runs 8–16 weeks by scope.

**What about post-launch growth?**
Yes: two months of support included after delivery; then a version plan, monitoring and a priority-driven backlog on the support plan you choose.

**What technology do you build with?**
Mostly with Next.js, Node.js and Python; the case decides, and the decision is documented before coding. What doesn't change is the standard: per-page performance budgets with Core Web Vitals targets, verified WCAG 2.2 AA accessibility and OWASP security with dependency reviews. We integrate payments such as Klarna or Adyen, CRM, ERP and your own APIs.

**How do you protect the platform and user data?**
With security by default: OWASP, headers and dependency reviews; SSO, approvals and audit on internal platforms; logs, metrics and alerts from day one, and an incident-response plan at launch. When you need it, our own pentest practice tests the platform.

**Where do you host the application and the data?**
Mainly on Supabase (database, authentication and storage), OVHcloud and Microsoft Azure. We pick the provider and region based on the data residency your case requires and what your company already uses, and we handle personal data under Colombia's Law 1581 of 2012 and the GDPR in Europe.
