How to engage RG INSYS

1. Choose an engagement model

These four cover 95% of engagements: pick by scope clarity, budget predictability, and duration.

Not sure? Try the build vs buy calculator or in-house vs offshore TCO calculator, or book a 30-minute call and we will recommend one.

2. Ballpark the cost

Realistic ballparks for common engagements; these are floors, not ceilings, and complex regulated work runs higher.

For a personalized ballpark use the project cost calculator (browser-only, no email needed) or the full pricing page. Written estimate within 48 hours of a brief.

3. Our delivery process

Six phases, whatever the model; the full process page adds a sample 8-week plan and RACI matrix.

1. Brief and free scoping call (30 min)

   You share the problem, constraints, and timeline; we ask hard questions. Output: whether we are a fit.

2. Written estimate within 48 hours

   Scope, milestones, fixed price or rate, assumptions, exclusions, and a single-page risk register. Shop it against other vendors.

3. Discovery sprint (optional, 1 to 2 weeks)

   Paid technical deep-dive: API spike, data model draft, UX wireframes, security review. De-risks the estimate.

4. Build sprints (2-week cadence)

   Sprint planning, daily standups, demo every other Friday. Working software in your environment from week one.

5. Stabilization and handover

   Bug-fix-only sprint after feature freeze, then documentation, runbooks, on-call training, and knowledge transfer.

6. Warranty and incident support

   30 days of free bug-fix warranty post-handover. Optional managed L1 to L3 support thereafter.

Every sprint follows our public engineering methodology: trunk-based development, AI-assisted PR review, 80%+ test coverage, full CI/CD with security scans, and a strict Definition of Done.

4. Contracts, NDA, and IP

A standard bundle of four agreements; your templates accepted if reasonable:

• NDA: mutual by default, signed before any commercial-in-confidence disclosure. Your template is fine.
• Master Services Agreement (MSA): governs all work. Our sample MSA shows the standard clauses (IP assignment, liability cap, payment terms, governing law).
• Statement of Work (SOW): per-project schedule with scope, deliverables, milestones, fees, change-request mechanism.
• Data Processing Addendum (DPA): required if we process personal data. See our GDPR-aligned DPA template.

All IP and code is assigned to you on payment and lives in your repos and accounts; we retain nothing after handover beyond what support requires. Sub-processors are listed on the security page and you can object to any.

5. Onboarding: week 1

Signed SOW to first production-quality commit: usually 5 to 10 working days.

• Day 1: Engineer in your Slack, Jira, GitHub. Repo access and dev environment confirmed; backup engineer briefed.
• Day 2: Architecture walkthrough with your tech lead, local environment running end-to-end, first trivial PR as a repo-access sanity-check.
• Day 3 to 5: First substantive ticket, pair-programming for codebase context, CI/CD and test pipelines verified.
• Day 6 to 10: First feature-level PR, stakeholder demo on the second-week Friday, retrospective and feedback.

6. SLAs and response times

The SLA page has the full targets. Highlights:

• Sales response: within 4 business hours, UK / EU / US East business hours.
• Written estimate: within 48 hours of a complete brief.
• P1 production incident (managed support contracts): acknowledged within 30 minutes, engineer engaged within 60 minutes, root-cause communication within 4 hours.
• P2 incident: acknowledged within 2 business hours, engineer engaged within 4 business hours.
• Standard delivery SLAs: sprint demos every 2 weeks, written status update every Friday, escalation path published in the SOW.

7. Exit and handover

End any engagement with one month's notice (or per the SOW for fixed-price work). Exit is included, not extra:

• All code, infrastructure, and documentation is already in your accounts and repos.
• 2-week handover sprint with your incoming team: pair sessions, runbooks, written knowledge-transfer document.
• Final invoice covers only work delivered to the exit date. No exit penalty.
• 30-day post-exit warranty covers regressions on delivered code at no charge.

Unhappy? Escalate to your account director; we would rather fix it than lose you. If you still leave, we help you leave well.

8. What to do next

Pick the step that matches where you are:

• Still deciding what to build? Grab the free resource downloads: RFP template, vendor scorecard, AI readiness audit, legacy modernization checklist, project cost estimator.
• Comparing vendors? Read the what we don't do page first; it disqualifies us early if we are not a fit.
• Ready to talk? Book a free 30-minute scoping call. Written estimate within 48 hours, no commitment.