Pricing
Transparent starting investments with explicit assumptions
Public commercial prices make the first buying decision easier. The statement of work defines the final scope, acceptance, payment, responsibilities, and exclusions.
Commercial clarityCompare scope before price
- Purpose
- Review starting investments, timing, payment structure, and scope assumptions.
- Boundary
- Public pricing is a planning baseline, not a government rate card or outcome guarantee.
Commercial sequence
Facts first. Remediation second. Recurring oversight only when justified.
- Establish the facts.Use a bounded assessment, blueprint, or workshop.
- Address verified gaps.Implement only the evidence-backed next step.
- Maintain recurring judgment.Add an Architecture & Reliability Office when an ongoing function is valuable.
| Engagement | Best trigger | Decision produced | Duration | Starting investment | Payment structure | Scope |
|---|---|---|---|---|---|---|
| AI Production Readiness & Evidence Sprint | An AI feature, RAG system, copilot, reviewer, or agent is approaching production, enterprise review, or a consequential expansion. | Proceed, narrow, remediate, or stop - with a measured baseline and explicit release conditions. | 3 weeks | $20,000 | 50% at start; 50% at delivery | View scope |
| AI-Ready .NET & SQL Modernization Blueprint | A business-critical .NET or SQL Server system is difficult to change because behavior is hidden across code, stored procedures, reports, integrations, and workarounds. | What must be preserved, where reversible seams can be created, and how modernization should be sequenced. | 3-5 weeks | $30,000 | 40% at start; 30% at midpoint; 30% at delivery | View scope |
| AI Evaluation & Release-Gate Implementation | A measured baseline exists, but the team cannot reproduce evaluations, compare changes, calibrate reviewers, or block degraded releases consistently. | How quality, access, cost, latency, human review, and failure thresholds become an inspectable release process. | 6-8 weeks | $60,000 | 40% at start; 30% at midpoint; 30% at delivery | View scope |
| Architecture & Reliability Office | An initial assessment or implementation has exposed recurring architecture and reliability decisions that cannot be handled as occasional ad hoc advice. | Which risks, releases, vendors, and modernization priorities deserve attention each month and quarter. | 3-6 month initial term | $9,500-$12,500 per month | Monthly in advance | View scope |
| Joint Discovery & Architecture Workshop | A partner needs to test technical fit, client interaction, workstream boundaries, and the smallest credible next step without requesting extensive free presales. | Whether a specialist workstream is viable, how it should be bounded, and what proposal-ready next scope is justified. | 2 working days plus preparation and readout | $5,000 | Paid before scheduling | View scope |
Last reviewed: 2026-07-24
Typical scope assumptions
- A named decision owner and technical owner
- A bounded system, workflow, or workstream
- Timely access through an approved channel
- Representative evidence and domain reviewers
- Written change control for additional systems or implementation
Common scope-change triggers
- Additional applications, tenants, business units, or use cases
- Regulated or restricted data handling
- Custom implementation or production deployment
- Extensive remediation beyond the named outputs
- Travel, unusual support hours, security clearances, or solicitation-specific flow-downs
FAQ
Pricing, payment, and acceptance
What does the starting investment assume?
One bounded decision, timely access, representative evidence, named client reviewers, and the published client responsibilities. The exact statement of work controls.
What does the price not mean?
It is not a blank check, a guarantee, a day rate, unlimited implementation, 24/7 support, certification, legal advice, or a promise that the client will release or win procurement.
How are government and subcontract opportunities priced?
They are priced against the solicitation, period of performance, labor and deliverable structure, flow-downs, security requirements, workshare, and negotiated terms.
How does acceptance work?
Acceptance is tied to named artifacts for the agreed system state, not to future business outcomes or third-party approvals.
Next action
Bring the system, the trigger, and what cannot fail.
Start with public-safe context. Sensitive evidence moves only after fit, responsibility, scope, and an approved channel are clear.
Prefer a direct conversation? Call 1 (464) 274-1476