How to engage RG INSYS

1. Choose an engagement model

Most buyers walk in with a goal but no clear preference between models. The four below cover 95% of engagements. Pick by how clear the scope is, how predictable the budget needs to be, and how long the work will run.

Not sure which model fits? The build vs buy calculator and in-house vs offshore TCO calculator help. You can also book a 30-minute call and we will recommend a model based on your scope.

2. Ballpark the cost

The cost of a project depends on scope, team size, complexity, and compliance overhead. The table below gives realistic ballparks for common engagements. These are floors, not ceilings — complex regulated work runs higher.

For a personalised ballpark on your specific project, use the project cost calculator (browser-only, no email needed) or read the full pricing page for tier inclusions and assumptions. Most buyers want a written estimate before they commit — we send one within 48 business hours of a brief.

3. Our delivery process

Every project follows the same six phases regardless of engagement model. The full process page goes deeper on each, including a sample 8-week plan and a RACI matrix. The summary:

1. Brief and free scoping call (30 min)

   You share the problem, constraints, and timeline. We ask hard questions about success criteria, integrations, and compliance. Output: alignment on 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. You can shop this estimate against other vendors.

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

   Paid technical deep-dive: API spike, data model draft, UX wireframes, security review. Reduces estimate risk before a larger commitment.

4. Build sprints (2-week cadence)

   Sprint planning, daily standups, mid-sprint sync, sprint demo on Thursdays. Working software in your environment from week one, not just slides.

5. Stabilisation and handover

   Bug-fix-only sprint after feature freeze. Documentation, runbooks, on-call training, and knowledge transfer to your team.

6. Warranty and incident support

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

Inside each sprint we follow 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. Your engineering manager can hold us to the standards in writing.

4. Contracts, NDA, and IP

We use a standard contract bundle but accept your templates if they are reasonable. The bundle covers four agreements:

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

All IP and code is assigned to you on payment. We never retain copies after handover except for what is required for support (in your repos, on your accounts). Sub-processors used during delivery are listed in the security page and you can object to any.

5. Onboarding — week 1

From signed SOW to first production-quality commit usually takes 5 to 10 working days. Inside week 1 you can expect:

• Day 1: Engineer added to your Slack, Jira, GitHub. Repo access and dev environment confirmed. Internal NDA copy lodged. Backup engineer briefed.
• Day 2: Architecture and codebase walkthrough with your tech lead. Local dev environment running end-to-end. First trivial PR raised for repo-access sanity-check.
• Day 3–5: First substantive ticket picked up. Pair-programming session with your senior engineer for codebase context. CI/CD and test pipelines verified.
• Day 6–10: First feature-level PR raised. Demo to stakeholders on the second-week Thursday. Retrospective and feedback to RG INSYS account manager.

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 business 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

You can end an engagement with one month 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.
• We run a 2-week handover sprint with your incoming team — pair sessions, runbooks, and a written knowledge-transfer document.
• Final invoice settles only the work delivered up to the exit date. No exit penalty.
• 30-day post-exit warranty covers regressions on delivered code at no charge.

If you are unhappy, escalate to your account director — we would rather fix it than lose you. If you still want to leave, we will help you leave well. Bad references hurt us more than the lost revenue.

8. What to do next

Three concrete next steps depending on where you are:

• Still deciding what to build? Read our free resource downloads — RFP template, vendor scorecard, AI readiness audit, legacy modernization checklist, project cost estimator.
• Comparing vendors? Check the what we don't do page first — it disqualifies us early if we are not a fit, and lists the kinds of vendors we recommend instead.
• Ready to talk? Book a free 30-minute scoping call. We send a written estimate within 48 business hours. No commitment to engage.