Software studio · Guatemala City — V·02

Software,
to the point .

// MISSION

rem designs and ships web, backend and mobile systems for founders and operators across Latin America. No middle-agencies, no vague promises, no deliverables that don't compile.

~/rem.lat / engine
buildwatchdeploy
compilednode 22.4⏱ 4.21slisto para producciónready for production
Based in GT· Guatemala City Zona 11 · Colonia Mariscal · GMT-06
Commitment < 4h · biz GMT-6 · 09:00–18:00
Disciplines 3/ web · be · mb full stack, no handoffs
Languages 2/ es · en bilingual docs
Model Studio/ small team sprint-based contracts
i n. lat.

"The thing", the matter in its most concrete form. Ad rem: straight to the point, no detours.

ii n. tech.

Relative typographic unit: the base size everything else scales from. A root.

iii v. studio

To build software as if the thing actually mattered: engineering without theatre, design without fashion, deliveries that compile.

// 02 — Disciplines

Three disciplines,
one thing only.

// web · backend · mobile

// 02 · 01 i Web · Product

Web,

Full user-facing products. Marketing sites with narrative, dense dashboards, internal panels, e-commerce. Modern rendering: SSR, streaming, edge.

Stack Next · ts · tailwind
LCP target 1.4s p75
Avg lead 6 wks
A11y AA · WCAG 2.2
Next.jsReactTypeScriptTailwindVercelCloudflare
// 02 · 02 ii Backend · Systems

Backend,

APIs, internal systems, integrations. Postgres taken seriously, GraphQL where it fits, events when justified. Spring Boot or Node, case by case.

Runtime Node · postgres
p99 target 200ms
Uptime SLO 99.9%
Coverage ≥80% int.
Spring BootNodePostgresGraphQLAWS
// 02 · 03 iii Mobile · Apps

Mobile,

iOS / Android apps when the use case earns it. Native when performance leads; React Native / Expo when iteration speed wins.

Stack Expo · rn · swift
Targets iOS · android
Crash-free 99.7%
Cold start ≤2s
iOSAndroidReact NativeExpo
// 03 — Telemetry

What we measure.

// default targets · reviewed each sprint

// p · 01 web · core
1.4s LCP · target
Good UX≤ 2.5 s
MethodCrUX

Largest Contentful Paint — how long the main content takes to render. Good UX is ≤ 2.5 s.

// p · 02 api · latency
≤ 200ms p99 · target
Industry≤ 300 ms
Sampleall routes

p99 latency — 99 % of requests respond faster than this. Target: ≤ 200 ms.

// p · 03 slo · uptime
99.9% Uptime · SLO
Cap~43 min/month
Window90 days

Uptime against our 99.9 % SLO — ~43 min downtime per month cap.

// 04 — Verticals

Each business,
its own language.

// SEO + UX per industry · no two sites the same

// 04 · 00 — Posture

A photographer's site shouldn't be designed like a SaaS dashboard. A rental listing doesn't rank like a clinic. Each vertical has its own search intent, its own conversion patterns, its own technical priorities. We build it that way — from schema markup down to the first tap.

SEOtechnical + content UXvertical-specific CWVLCP · CLS · INP SchemaJSON-LD
// 04 · 07 — Common floor

What we always ship, whatever the vertical.

Core Web Vitals
LCP · CLS · INP green, measured with real CrUX
Schema · JSON-LD
right type per vertical, validated in Search Console
Sitemap + robots
dynamic, with real priorities, not boilerplate
OG + Twitter cards
page-specific image, not the homepage one
i18n hreflang
if there's ES/EN, we declare it correctly
Useful analytics
intent-level events, not empty pageviews
WCAG 2.2 AA
contrast, visible focus, keyboard navigation
Readable privacy
cookies + data in plain language
// 05 — Process

How we work.

// operating principles · no ceremony

PRINCIPLE · 01

Small.

Small teams, fast decisions. You talk directly to whoever writes the code. No project managers forwarding emails.

PRINCIPLE · 02

Honest.

If something is going to take 8 weeks, we say 8 weeks. If an idea isn't going to work, we say so before charging for it.

PRINCIPLE · 03

Durable.

Code your next team can read. A stack that won't need archaeology in 18 months. Documentation that actually exists.

// AI · stance

We use AI where it accelerates the work: types, tests, scaffolding. Not where it compromises product quality. The final call is made by someone who signs with their name.

// 06 — Let's talk

Starting
is the hard part.

Tell us what you're building, what stage you're in, and what you'd need to make it work. No long form: a clear reply, within 24 business hours.