How we build
Discovery → Blueprint → Build with accelerators → Integrate/Migrate → UAT & Training → SupportDiscovery → Blueprint → Build with accelerators → Integrate/Migrate → UAT & Training → Support
At a glance
Outcome-first
Define success metrics early; measure as we build.
Small, shippable slices
No “big bang.” Value drops every 1–2 weeks.
Ownable tech
your code, your infra, your IP.
Secure by default
RBAC, audit logs, encryption, and compliance checklists.
Operable from day one
CI/CD, monitoring, runbooks, and on-call hygiene.
Phase 1
Discovery (3–5 days)
Goal
Align on problems, success metrics, and constraints.
Activities
- Stakeholder interviews, task shadowing, system walk-throughs
- Process maps (happy path + edge cases) and data/field inventory
- Integration inventory (APIs, file drops, RPA needs, SSO)
- Success metrics: e.g., “dispatcher time −30%”, “first-attempt delivery +15%”
Deliverables
- Discovery brief (2–3 pages): goals, personas/roles, must-haves
- Current-state diagram: systems, data flows, pain points, risks
- Initial backlog: epics → user stories with acceptance criteria (AC)
Exit criteria
- Agreed problem statement & success metrics
- Prioritized MVP scope with non-goals listed
Phase 2
Blueprint (1–2 weeks)
Goal
Make delivery predictable with a lean, testable design.
Activities
- Domain model & field dictionary (validation, dependencies)
- Wireframes of key screens (forms, tables, states, error/empty/offline)
- Target architecture: services, data, security baseline, SLAs
- Integration specs: API contracts, events, webhooks, file bridges
- Estimation & plan: slices by sprint with demo checkpoints
Deliverables
- Blueprint pack: domain model, wireframes, sequence/architecture diagrams
- MVP plan: 6–12 week schedule with sprint goals and demo dates
- Risk register: assumptions, mitigations, fallback options
Exit criteria
- Stakeholder sign-off on scope, AC, and success metrics
- Fixed quote (for MVP) or sprint budget (for evolving scope)
Phase 3
Build with accelerators (2–8 weeks, incremental)
Goal
Ship the smallest thing that proves value, fast.
Activities
- Implement slices with component library & templates (our accelerators)
- API-first contracts, type-safe clients, background jobs/queues
- Mobile offline patterns where needed (local queue + safe retries)
- Storybook tokens/components; unit/integration tests as we go
Deliverables
- Working features behind flags; demo every sprint
- Test suite (unit, integration, contract tests)
- Reusable components & design tokens (light/dark ready)
Exit criteria
- Feature slices meet AC, pass tests, and hit performance budgets
- “Ready for integration” checklist passed
Phase 4
Integrate & Migrate (in parallel)
Goal
Make the app useful in your ecosystem.
Activities
- API/webhook integration (accounting, carriers, PACS, SSO, etc.)
- Data migration scripts (CSV/ETL), dedupe rules, mapping tables
- Idempotent jobs, retries, dead-letter queues, backoff strategies
Deliverables
- Connectors with contract tests & sandboxes
- Migration plan + dry-run results & reconciliation report
Exit criteria
- End-to-end path works in staging with realistic data
- Rollback/compensation documented (SAGA where applicable)
Phase 5
UAT & Training (1–2 weeks)
Goal
Validate with real users and prepare teams.
Activities
- UAT scripts aligned to AC; capture feedback as tickets
- Role-based training: short videos/quick guides/checklists
- Access setup: roles/permissions, audit settings, data retention
Deliverables
- UAT sign-off, training collateral, cutover checklist
- Support playbook: how to triage, escalate, and measure
Exit criteria
- Go/no-go review passed; rollback plan rehearsed
Phase 6
Launch & Support
Goal
Make delivery predictable with a lean, testable design.
Activities
- Domain model & field dictionary (validation, dependencies)
- Wireframes of key screens (forms, tables, states, error/empty/offline)
- Target architecture: services, data, security baseline, SLAs
- Integration specs: API contracts, events, webhooks, file bridges
- Estimation & plan: slices by sprint with demo checkpoints
Deliverables
- Blueprint pack: domain model, wireframes, sequence/architecture diagrams
- MVP plan: 6–12 week schedule with sprint goals and demo dates
- Risk register: assumptions, mitigations, fallback options
Exit criteria
- Stakeholder sign-off on scope, AC, and success metrics
- Fixed quote (for MVP) or sprint budget (for evolving scope)
Governance & cadence
Weekly delivery review
Demo, metrics, risks, decisions
Daily sync (optional)
15 minutes for blockers
Board
Live backlog with priorities, AC, and definitions of done
RACI
sponsor (business), product (scope), tech lead (architecture), PM (cadence), QA (AC/tests), DevOps (SRE)
Engineering standards
CI/CD
Testing
Unit, integration, contract, and smoke; accessibility checks
Performance budgets
LCP/INP targets (web), TTI; p95 API latency and error rates
Observability
Logs/metrics/traces, alerts with runbooks, SLOs/SLIs
Security
RBAC/ABAC, SSO (OIDC/SAML), secret management, encryption in transit/at rest, audit logs, threat-modeling checklist
Data
Event taxonomy, warehouse/ELT approach, KPI definitions, governance
Change control
(so scope doesn’t slip)
No Surprises
Change requests are logged with impact on cost/timelineFlagged releases
New features gated until AC is metVersioned contracts
Integrations don’t break on deploy
What we need from you
Decision-maker & product owner identified
Sample data (sanitized), system access, and vendor contacts
UAT users (5–8) and quick feedback windows
Typical timelines
8–12 week MVP:
- Discovery/Blueprint (1–2 wks)
- Build + Integrations (5–8 wks)
- UAT/Launch (1–2 wks)
Phased rollout
Advanced modules (analytics, portal, WMS) follow in 2–4 week sprints
FAQ
Yes-code and deploy assets can be assigned to you.
Fixed for scoped MVPs; milestones/sprints for larger programs.
Cloud-first; on-prem bridges supported for PACS/ERPs/file shares.
Local queues + background sync + conflict rules.
HIPAA/GDPR-aware patterns, audit logs, data retention, SSO.
