Services

Structured to get you out. Delivered in a fraction of the time.

Four service tiers. Each one designed to de-risk the next. A demo-able artifact every day, working software in your hands every week, every merge to production through the same gate.

Engagement path

Tier 1

Assessment

2–3 weeks · Low commitment

Tier 2

Module Migration

4–8 weeks · One module

Tier 3

Full Platform

8–16 weeks · Complete escape

Tier 4

Managed Service

Multi-year contract

Tier 1

SaaS Escape Assessment

Sized in the Assessment

2–3 weeks · Typical hours: 70–120

The entry product. Low commitment. Designed to be approved without a full committee process. The Assessment is the primary event: it produces the go/no-go recommendation, the phased roadmap, and the business case that drives all downstream work. If the economics don't support migration, we'll tell you here — not after you've spent $2M.

Deliverables

  • Current state TCO analysis — license, add-ons, SI partner fees, admin headcount, customization cost
  • 5-year TCO projection: status quo vs. custom-built equivalent
  • Discovery workshop outputs: domain map, bounded contexts, shadow system inventory
  • Module Sweep: every module classified into one of six paths (retire, retain, rebuild, automate, integrate, federate)
  • Working sample slice of the future system, built against the spec
  • Data audit — volume, quality, export feasibility, dependency ordering
  • Integration inventory with complexity scoring
  • Risk rating: Red / Amber / Green per dimension
  • Recommended phased roadmap with milestones
  • Go / no-go recommendation

Tier 2

Module Migration

Sized in the Assessment

4–8 weeks · Typical hours: 445–890

One production-deployed custom module replacing one SaaS capability. Hours scale with integration count, data volume, and user count. Example modules: CRM Core, Deal Management, Support Desk, Marketing Automation, Reporting and Analytics. Generation is fast and exploratory; specifications and code mature together and every merge runs through Argus by default. Migration is incremental and your existing system stays live throughout the transition.

Deliverables

  • Production-grade module, delivered through the gate
  • Anti-Corruption Layer — translates between SaaS domain model and your domain model during migration
  • Data migration — extraction, transformation, validation, cutover
  • Integration wiring to all existing systems
  • Parallel running period alongside existing SaaS module
  • Phased cutover — 10% → 25% → 100% of users with go/no-go at each stage
  • User training and full documentation
  • Continuous evolution under the MSA from day one of cutover

Tier 3

Full Platform Deconversion

Sized in the Assessment

8–16 weeks · Typical hours: 890–2,200

Complete replacement of the primary SaaS platform. Structured as a series of Tier 2 module engagements in milestone-gated sequence. Hour estimates agreed per milestone before work begins, not a single fixed commitment for the full engagement. Actual scope is sized in the Assessment to your platform, integrations, and module count. Includes executive steering committee, biweekly checkpoints, transparent progress reporting, and change control for scope changes.

Deliverables

  • Everything included in Tier 2, repeated per module across the full platform
  • Full platform architecture design and cross-module integration design
  • Enterprise security and compliance review
  • Change management program using the ADKAR framework
  • Stakeholder mapping engagement strategy: the informal influencers who determine whether migrations succeed
  • Post-migration handoff program — training, documentation, and knowledge transfer

Tier 4

Managed Service Agreement

Sized to the system

Multi-year contract

Everything your SaaS vendor bundled into the subscription — infrastructure operations, security, compliance maintenance, incident response, and ongoing development — under a contract with defined SLAs. The MSA gives you an engineering team without the overhead of hiring one, and keeps your system ahead of the technology curve as AI tooling evolves.

MSA tiers

Managed Standard

2-year minimum

Infrastructure ops, security patching, monitoring, incident response (business hours), 120 dev hours/year.

Managed Growth

2-year minimum

Everything in Standard, plus 360 dev hours/year, quarterly architecture review, priority incident response, compliance maintenance.

Managed Enterprise

3-year minimum

Everything in Growth, plus 24/7 incident response, dedicated engineer, annual pen test, AI agent evolution.

The Assessment is the formal front door. A conversation is the informal one.

Most engagements start with the Assessment because it produces the go/no-go and the roadmap a board can act on. If a conversation is the right place to start, start there.

Our limits

What We Will Not Do

We don't take every engagement. If the economics don't support migration, we'll tell you in the Assessment — not after you've spent $2M. Aligned incentives mean we only win when you win.

  • We will not recommend migration if the ROI is unclear or the risk rating is Red without explicit terms.
  • We strongly recommend completing the Assessment before quoting a Module Migration. If you prefer to skip it, we build conservative contingency into our estimates and document scope assumptions in writing. You carry more uncertainty — we make sure you know exactly how much.
  • We will not leave you without ongoing support after migration. The Managed Service Agreement is proposed in every Tier 2 and Tier 3 engagement.
  • We will not start work without a clear scope definition and agreed hour estimate. Scope changes are documented and re-estimated before work continues.