Skip to main content
p.—2026·06·06 · 20:55 CR
Continuity & Reliability

What happens if
Alvin is unavailable?

An honest answer — and the systems we have built so that "unavailable" never means "stopped."

Honest Disclosure

We are a principal-led studio. We do not pretend otherwise.

SOTO⟂DEV is structured as a lean, founder-directed practice. Alvin Soto is the principal engineer and primary contact on every engagement. What we have built is a continuity system — documented, tested, and shared with clients before an engagement starts — so that a temporary absence never becomes a delivery failure. Every engagement ships with a runbook a vetted contractor can execute without the principal present.

Delivery Model

Every engagement is continuity-ready from day one.

Written scope before code

Every engagement starts with a signed scope document. What will be built, what will not, delivery milestones, escalation contacts. Signed before any code is written. Changes in writing only.

Operator runbook on every system

Every delivered system ships with an operator runbook tested before delivery. A vetted contractor or the client's own team can take over operations from the runbook alone, without Alvin present.

Credential escrow

All credentials, API keys, environment secrets, and access documentation are escrowed in a secure vault and transferred to the client at delivery. No single point of access failure.

Weekly written status

Weekly progress updates, milestone-gated delivery, issues escalated in writing within 24 hours. Nothing moves without a written record.

Service-Level Commitments

What you can expect, in writing.

Communication

Initial response< 4 business hours

Mon–Fri, US & EU time zones

Emergency response< 2 hours

Critical production issues

Project status updateWeekly, in writing

Every Friday

Milestone confirmationSame day

On delivery of each milestone

Delivery

Scope change response< 48 hours

Written impact assessment

Issue escalation< 24 hours

Written incident report

Backup operator activation< 5 business days

From confirmed principal unavailability

Runbook handoffAt delivery

With every shipped system

Contractor & Advisor Network

The extended network behind every engagement.

SOTO⟂DEV maintains a vetted network of specialists with direct knowledge of our systems, standards, and delivery process. These are not generic contractors — they are engineers who have reviewed our methodology and can step into an active engagement with context.

Backup Principal Engineer

Senior engineer with SOTO methodology access and all engagement runbooks. Can assume active delivery within 5 business days of activation.

AI / ML Specialist

LLM integration, prompt engineering, and AI agent architecture. Available for deep technical engagements and model optimization work.

Frontend Engineer

React + TypeScript specialist for UI-intensive engagements and overflow on design-heavy phases.

Data & Visualization Lead

Intensive data modeling, GIS, and statistical analysis for ATLAS and Civic engagements beyond standard scope.

Operations Advisor

Senior advisor with enterprise operations background. Available for strategic reviews on complex or multi-team engagements.

Legal & Compliance Counsel

Contract review, data processing agreements, and regulatory guidance for engagements requiring formal compliance posture.

Escalation Path

Four levels. Every engagement has all four, documented before we start.

L1

Direct to Alvin

rs@sotoprojdev.com or WhatsApp. Response in < 4 business hours. Primary contact for all active engagements.

L2

Scheduled escalation call

For unresolved issues or scope discussions. Booked within 24 hours of written request via cal.com/alvin-soto.

L3

Backup operator activation

If principal is unavailable > 5 business days. Vetted contractor assumes active delivery with full runbook access and engagement context.

L4

Client-directed handoff

Full credential + documentation package transferred to client or their nominated team. Documented and executable without SOTO involvement.

Operational Processes

How the studio runs, phase by phase.

Pre-Engagement

  • Signed scope document
  • Engagement brief + constraints
  • Communication channels documented
  • Milestone schedule established
  • Escalation contacts listed in writing
  • Credential vault initialized

During Delivery

  • Weekly written status update
  • Milestone-gated delivery gates
  • Scope changes in writing, signed
  • Issues documented within 24 hours
  • Async-first, synchronous on schedule
  • Change log maintained continuously

At Delivery

  • Operator runbook delivered
  • Recovery procedure tested
  • Credential package escrowed or transferred
  • Change log finalized
  • 30-day post-delivery support window
  • Stakeholder walkthrough documented

Post-Delivery

  • 90-day maintenance window available
  • Monthly system health reports (opt-in)
  • On-call retainer available
  • Annual system audit available
  • Runbook updates on change events
  • Upgrade path planning available
What We Cannot Promise

Limits we state in writing.

We are not a 50-person firm

We will not claim otherwise. The continuity system above is what a lean, disciplined practice looks like when it takes operational risk seriously. It is designed to be honest, not impressive-sounding.

Backup activation takes up to 5 days

A warm handoff to a vetted contractor takes time to execute properly. We cannot promise instant replacement. We can promise a documented, tested process that activates within that window.

Not SOC 2 certified today

We do not hold formal SOC 2 Type II certification as a studio. We build on certified infrastructure (Vercel + Supabase, both SOC 2 Type II). Our enterprise readiness roadmap targets formal certification within 24 months.

Continuity documentation available on request.

For enterprise engagements, we share the full continuity plan — including backup operator contacts, runbook examples, and escalation procedures — in writing before the engagement starts. No commitment required to review.