arlo/eng

~/services

// services

Five tracks.
One senior team.

We don't sell deliverables in isolation. Every engagement maps to one of five tracks — research, architecture, engineering, optimization, and operations — composed for the problem in front of you.

start a project→view process

// tracks

Each track, in detail.

// 01 — research

01

Research & Discovery

We start by understanding the system you actually have — not the one on the org chart. Stakeholder interviews, technical audits, and analytics teardowns produce a single document everyone can argue with.

auditux researchanalyticscompetitive

// deliverables

  • 01Stakeholder interview synthesis (8–12 sessions)
  • 02Technical audit: stack, perf, accessibility, SEO
  • 03Analytics teardown with named instrumentation gaps
  • 04Competitive + heuristic review
  • 05Prioritized opportunity register with effort estimates
  • 06Readout deck and 90-minute working session

// engagement

duration
2–4 weeks
team
1 strategist · 1 senior engineer
scope
fixed scope · fixed price

// sample outcome

Identified 3 conversion leaks worth ~$1.4M ARR for a B2B SaaS, fixed in the next sprint.

anonymized · representative

// 02 — architecture

02

Architecture & Strategy

Information architecture, content models, technical blueprints, and performance budgets — written so a new engineer can ship inside a week. We commit to constraints in writing before code is written.

iatech specsperf budgetdesign system

// deliverables

  • 01Site / product information architecture
  • 02Content model and editorial workflow
  • 03Technical RFC: stack, data flow, hosting, edge strategy
  • 04Performance budget per route (LCP, CLS, INP, JS bytes)
  • 05Design system foundations (tokens, primitives, motion)
  • 06Migration plan with rollback gates

// engagement

duration
3–6 weeks
team
1 architect · 1 designer · 1 engineer
scope
fixed scope · fixed price

// sample outcome

Replatform RFC accepted by a 40-person product org in one review — zero rework in build.

anonymized · representative

// 03 — engineering

03

Engineering & Development

Custom React and TypeScript builds, headless commerce, design systems, and server functions at the edge. Two-week increments, deployed continuously. You see real software in week one — not a deck.

reacttypescriptedgeheadlessdesign systems

// deliverables

  • 01TypeScript codebase, strict mode, 90%+ type coverage
  • 02Tailwind / Storybook design system with usage docs
  • 03CI/CD with preview deploys per PR
  • 04Edge-rendered routes with caching strategy
  • 05Type-safe API layer (tRPC, server functions, or REST + Zod)
  • 06Observability, error tracking, and runbooks at handoff

// engagement

duration
8–16 weeks
team
2–4 engineers · 1 designer · 1 PM
scope
fixed scope or time-and-materials

// sample outcome

Shipped a logistics dashboard in 11 weeks. Median TTI dropped 2.7s. Zero P1 incidents in first 90 days.

anonymized · representative

// 04 — optimization

04

Testing & Optimization

Conversion experiments, accessibility audits, and Core Web Vitals tuning until the numbers move. We don't ship vibes — every change ships with an instrumentation plan and a reviewable result.

a/bwcagcwvseo

// deliverables

  • 01Experimentation roadmap with hypothesis, MDE, and runtime
  • 02WCAG 2.2 AA audit with prioritized remediation
  • 03Core Web Vitals diagnosis and fixes (field + lab)
  • 04Technical SEO audit and structured data refresh
  • 05Per-experiment readouts with statistical significance
  • 06Quarterly performance regression report

// engagement

duration
6–12 weeks or retainer
team
1 engineer · 1 analyst
scope
scoped sprints or monthly retainer

// sample outcome

DTC migration: LCP 3.4s → 1.1s on mobile, +18% checkout completion in eight weeks.

anonymized · representative

// 05 — maintenance

05

Maintenance & Scale

Retainer engineering — observability, on-call, dependency hygiene, quarterly roadmaps, and continuous shipping. The relationship begins at launch, not ends there.

sreretainerroadmapon-call

// deliverables

  • 01Dedicated engineering pod with named owners
  • 0224/5 on-call with SLOs and incident review
  • 03Monthly dependency, security, and perf hygiene
  • 04Quarterly roadmap workshop and OKR alignment
  • 05Continuous deployment with automated rollback
  • 06Transparent monthly report: what shipped, what's next

// engagement

duration
ongoing · 3-month minimum
team
1–3 engineers · fractional design
scope
monthly retainer

// sample outcome

Fintech client: 99.99% uptime across 18 months, 240+ deploys, zero rollback incidents in Q4.

anonymized · representative

// engagement models

Three ways we work together.

Sprint

diagnostic

Teams that need a sharp answer fast: should we rebuild, repair, or replatform?

// duration

2 weeks

// includes

  • +Technical + UX audit
  • +Opportunity register
  • +RFC outline
  • +90-minute readout
from $18kstarting

Build

fixed scope

A defined product or website with a launch date and a budget that needs to hold.

// duration

8–16 weeks

// includes

  • +Discovery + architecture
  • +Design system + build
  • +Performance + a11y pass
  • +Launch + 30-day warranty
from $60kstarting

Retainer

ongoing

Live products that need senior engineering hands, on-call, and a roadmap.

// duration

3-month minimum

// includes

  • +Dedicated pod
  • +24/5 on-call + SLOs
  • +Monthly hygiene + reporting
  • +Quarterly roadmap workshop
from $9k / monthstarting

// faq

Things people ask before signing.

  • 01

    Q. How quickly can you start?

    Typically 2–4 weeks from signed SOW. Sprint engagements can sometimes start the following Monday if we have capacity.

  • 02

    Q. Do you work fixed-price or time-and-materials?

    Discovery and Sprint engagements are always fixed-price. Build engagements are fixed-scope by default; we'll switch to T&M for genuinely exploratory work and tell you which it is up front.

  • 03

    Q. Will you work with our existing designers / agency?

    Often, yes. We're happy to be the engineering pod inside a larger team and have a written collaboration model we'll share before kickoff.

  • 04

    Q. What's your stack?

    TypeScript end-to-end. React, Next.js or TanStack Start, Node, Postgres, edge runtimes (Cloudflare, Vercel). We pick stacks for fit, not for fashion — see the homepage stack section.

  • 05

    Q. Do you sign NDAs and MSAs?

    Yes. We have a standard MSA we can share, or we'll redline yours within five business days.

  • 06

    Q. What happens at the end of an engagement?

    A handoff document, a runbook, and a 30-day warranty period. Many clients move into a Retainer; that's a choice, not a requirement.

// 09 — engage

Don't rent a team.
Own an engineering partner

Tell us what your business needs its digital platform to do. We'll respond within one business day — with a senior engineer, not a sales script.

start a conversation→hello@arlo.eng

// engagement

platform engineering · min 6 mo

// response_time

< 1 business day

// accountability

one team · one platform · one outcome