A two-call working session: business problem, regulatory frame, data surface, success criteria. We do not pitch on discovery calls; we listen and ask.
A working session with the customer's technology, data, and security leads. We review system architecture — data flows, integration design, control logic, observability, and exit posture. AI engagements additionally cover model selection, agent design, and human-approval thresholds.
Vendor-diligence pack under NDA: our adopted policy set, Intercompany Services Agreement, Sub-Processor Register, and DPA template reviewed by customer security and risk.
A scoped SOW under our MSA covering deliverables, milestones, fee model, data-handling addendum, and exit provisions. Scopes AI delivery, governed software foundations, or a phased roadmap — the contract structure is the same regardless.
Engineering pod stood up; access provisioning; security training acknowledgements; environment setup. Typically four to six weeks of contract signature, subject to customer onboarding pace.
Two-week sprints: written sprint plan, daily standup, weekly customer demo, sprint review document. Auditability rule from sprint one — for AI components, every agent action emits a structured trace; for software systems, approval records and decision logs are captured on the same principle.
Monthly steering: scope, schedule, risk register, compliance posture, exception log. Quarterly executive review on business outcomes and contract health. Both written, both retained.
Every change reviewed by a Sense7ai engineer who is not the author. Test coverage and observability are not optional. We do not deploy on a Friday.
Production cutover with a documented runbook. Incident response per S7AI-RB-001 — one-hour internal containment, 72-hour customer notification, or per DPA. Support cadence agreed in the SOW.
Code, documentation, runbooks, training, and credentials transferred to the customer. Sense7ai retains nothing beyond the agreed retention window. This is in every SOW from day one.
Scope determines price. Here is how we think about it.
Sense7ai engagements are scoped per-customer rather than rate-card-driven. Pricing reflects the scope, complexity, integration surface, and regulatory burden of the work, and is presented as a fixed-scope or time-and-materials proposal at the close of discovery. We do not publish hourly rates because they obscure the only price that matters : the price of the outcome you need.
