Next platform deadline: Amazon EKS Nov 26, 2026  

All 14 deadlines

For IT leaders and procurement

Everything your approval chain will ask, on one page.

Contracting, vendor onboarding, governance, escalation, risk and the business case, for the people who sign. No prices on the web; a fixed fee in every statement of work.

Company facts

Who you would be contracting with

The details supplier onboarding usually asks for first. Anything not shown here is provided during onboarding, on request.

Capabilities statement (PDF)

View it as a web page

Legal entity
SRASH Digital LLC
Entity type
Limited liability company
State of formation
Provided on request
Location
San Diego, California, United States
Mailing address
11440 W Bernardo Court, Suite 300, PMB 3006, San Diego, CA 92127
Tax form
IRS Form W-9, provided on request
UEI / CAGE
Provided on request
NAICS
Provided on request
Insurance
Certificate of insurance provided on request
Payment and invoicing
By milestone or monthly, as set in each SOW; terms provided on request
Working hours
US Pacific business hours, Monday to Friday, with overlap for every US time zone

Vendor onboarding pack

Ready for your supplier process.

Ask for the full pack in one email and we send what your process needs, usually within one business day. Request the pack

DocumentWhat it coversHow to get it
Capabilities statementOne-page PDF: services, differentiators and company data.Download PDF
W-9 and entity detailsLegal name and tax ID matching the contract and invoices.On request
Certificate of insuranceCurrent certificate; additional-insured wording where your MSA requires it.On request
Security questionnaireYour questionnaire, SIG Lite or CAIQ, answered truthfully; no certifications claimed.On request
Mutual NDA, MSA and SOW templatesShort templates for your legal team, or we review your paper.On request
Data processing agreementFor scopes that involve personal data; a BAA reviewed where health data is in scope.On request
Bank detailsConfirmed by phone on a number you already hold, never changed by email alone.On request

Contracting

From NDA to kickoff, in order.

Paperwork runs in parallel with planning, so work can usually start within one to two weeks of a signed SOW, depending on your approvals and access.

  1. 01

    Mutual NDA

    Signed before we see anything about your systems. Yours or ours.

  2. 02

    Free 30-minute review

    A senior engineer, not a salesperson. A short written summary follows.

  3. 03

    MSA

    Commercial and legal terms once: liability, IP, confidentiality, insurance, termination. Your paper or ours.

  4. 04

    SOW per engagement

    Scope, deliverables, acceptance criteria, schedule and fixed fee, approved before work starts.

  5. 05

    Vendor onboarding

    W-9, insurance certificate, security questionnaire and bank verification, run in parallel with the SOW.

  6. 06

    Kickoff

    Named engineer, access plan, cadence and escalation path agreed in week one.

Commercial terms

How we contract, without the fine print.

Fees are fixed and stated in each SOW after the free review. We do not publish prices, because scope drives the fee. Sample SOW outline

Engagement models

Fixed-fee sprints, phased fixed-fee projects, managed reliability by the month, or embedded senior engineers. No percentage-of-savings deals. Compare models

Change control

Changes to scope, schedule or fee are agreed in a signed change request before the work is done. Nothing appears on an invoice you did not approve.

Acceptance

Each deliverable has written acceptance criteria. You review and sign off; anything that misses the criteria is corrected within the fee.

Intellectual property

Deliverables, code and documentation are yours on payment, in your repositories. We keep only pre-existing tools and general know-how.

Subcontracting

None without your written approval and named individuals, all under the same terms.

Confidentiality and data

NDA first, data stays in your environment, no client data used to train AI models. Security practices

Liability and insurance

Set in the MSA and negotiated with your legal team. Insurance certificate on request.

Termination and transition

Notice periods in the MSA. On exit we hand over work in progress, revoke access and confirm deletion in writing.

Governance

Reporting and escalation

Weekly status with the RAID log, a steering review monthly or at each phase gate, and a close-out report at the end. Full cadence.

Sample status report
Sample RAID log

Escalation path

  1. Level 1

    Lead engineer

    Day-to-day questions, blockers and technical decisions. Reply within one business day; same day during agreed change windows.

  2. Level 2

    Engagement lead

    Schedule, scope or quality concerns not resolved at level 1. Raised in the weekly status or by email at any time.

  3. Level 3

    SRASH principal

    Commercial or relationship issues, or anything you want resolved at the top. Contact through the MSA notice address.

Risk

How we reduce the risk of choosing us.

The questions a risk or vendor-management review raises about a specialist firm, answered directly. When a large firm is the better choice

Delivery risk

Paid assessment before any large commitment, phase gates with your sign-off, rehearsed and reversible changes. Methodology

Key-person risk

Work, decisions and runbooks in your repositories from day one; replacement or backup engineers introduced for your approval.

Security risk

Read-only first, least privilege, named MFA accounts in your identity provider, data never leaves your environment.

Commercial risk

Fixed fees agreed in writing, change requests before extra work, assessment fee credited to delivery.

Lock-in risk

Open, documented work in your tools; knowledge transfer built into every SOW; no proprietary platform to rent.

Continuity risk

Business-hours managed reliability with extended hours by written agreement. We do not promise 24x7 cover we cannot staff.

Business case

Measures you can take to your CFO.

We help you build the case from your own numbers: the cost of doing nothing (extended-support fees, incidents, idle spend), the cost of the work and the measures we will report against. We do not use invented benchmarks or other clients' results.

Data & Databases

  • Support exposure removed: Instances moved off end-of-support versions, and the extended-support fees avoided, calculated from the vendor's published rates and your own inventory.
  • Downtime per change: Planned downtime measured in rehearsal, then reported against the actual window after each cut-over.
  • Recovery proven: Restore time and data-loss window (RTO and RPO) tested, not assumed, and written into the runbook.
  • Performance against baseline: p95 latency, throughput and resource use for your critical queries, before and after.

All Data & Databases measures

Data Engineering & Analytics

  • Data freshness: Time from a change in the source to the number in the dashboard, measured against the freshness target agreed for each data product.
  • Pipeline reliability: Failed and late runs per week, and time to detect and fix them, before and after.
  • Reconciliation: Tables and reports matched between old and new platforms, with any difference explained and signed off before cut-over.
  • Platform cost: Credits, DBUs or capacity units per workload against the baseline agreed at the start, from your own usage data.

All Data Engineering & Analytics measures

Cloud & Platform Engineering

  • Spend against baseline: Monthly cloud spend by team or product against the baseline agreed at the start, from your billing export.
  • Cost allocation: The share of spend that is tagged and allocated to an owner.
  • Delivery performance: Deployment frequency, lead time, change failure rate and time to restore (the DORA measures), before and after.
  • Support status: Clusters, node images and managed services inside standard support, tracked against published dates.

All Cloud & Platform Engineering measures

AI & Automation

  • Quality against threshold: Score on an evaluation set built with your experts, against a pass mark agreed before building.
  • Groundedness: The share of answers that cite the right source, measured on the evaluation set.
  • Cost per task: Model and infrastructure cost per answer or per completed task, with daily limits.
  • Time saved: Time per task measured with real users in a pilot, not estimated from a vendor benchmark.

All AI & Automation measures

Security and compliance

What we do, and what we do not claim.

We hold no SOC 2 or ISO 27001 attestation and do not claim any. We work inside your environment and controls, so access stays under your own identity provider, logging and approvals.

Security and confidentiality practices

Questionnaires we complete

  • Your own supplier security questionnaire
  • Shared Assessments SIG Lite
  • Cloud Security Alliance CAIQ
  • Data processing agreements, and BAA review where health data is in scope

Answers are limited to what we can truthfully commit to and evidence.

Questions IT leaders and procurement ask

Straight answers on contracts, risk and governance. Anything else, ask us.

Ask a question

Are you SOC 2 or ISO 27001 certified?

No, and we do not claim to be. We work inside your environment and controls, complete your security questionnaire truthfully and put our data-handling commitments in the contract. If your policy requires an attested supplier for this scope, we will tell you on the first call.

Can you work on our paper?

Yes. We are happy to review your NDA, MSA and SOW templates. If you prefer, we provide a short mutual NDA, MSA and SOW for your legal team to mark up.

Who owns the deliverables?

You do, on payment: code, infrastructure definitions, runbooks and documentation. We keep only general know-how and tools we had before the engagement.

Do you subcontract?

Only with your written approval, naming the engineer in advance. Anyone working on your systems signs the same confidentiality, security and data-handling terms.

What if the engineer leaves or is unavailable?

Everything lives in your repositories and the RAID log from day one, so the work does not depend on one person's memory. A replacement engineer is introduced for your approval, and on longer engagements we can name a backup engineer at the start.

How do we exit?

Either party can end an engagement on the notice set in the MSA. You pay for work accepted to date, we hand over everything in progress, revoke our access and confirm deletion of working material.

Can you provide references?

We do not publish client names or logos. Where clients have agreed to it, reference conversations can be arranged during procurement. A paid assessment, credited to the project, is the lowest-risk way to judge our work directly.

How do you handle conflicts of interest?

We resell no licences or cloud capacity and take no referral fees from vendors, so recommendations follow your evidence. If a conflict arises, we disclose it in writing.

Start with the paperwork or the problem.

Request the vendor onboarding pack, or book a free 30-minute review with a senior engineer. We sign your NDA first.