Architecture: built around your stack
We write custom code against the systems you already run: your CRM, EHR, ERP, ticketing, document stores, and phone system. There is no CloudNSite platform between you and your data. Typical delivery is 4 to 8 weeks. If your RFP says the vendor must not replace existing systems, we meet that requirement by default.
Data handling: private deployment and regulated scope
Regulated data can run on a private LLM deployment inside an environment you control, and the data does not leave that boundary. Healthcare architecture is HIPAA-ready: built to support a BAA and the associated controls, with scope confirmed during discovery. Controls map to the framework you already operate under: HIPAA, SOC 2, NIST, GLBA, or PCI. Compliance is a property of a specific deployment and its agreements, and we scope it upfront, not after the build.
Human oversight: review and escalation are designed in
Every production workflow defines which decisions require human approval and where exceptions go. Review points are written into the statement of work, not added after an incident. Operations-scale builds include permissions, human review, and audit trails as standard scope.
Quality: evaluation before and after launch
Every build ships against a defined acceptance test. Focused builds include workflow-specific evaluation. Operations-scale builds ship an expanded evaluation and regression suite that runs before releases. The suite transfers to you with the rest of the work product.
Ownership: set in the agreement, with no lock either way
Ownership is set in the agreement before build work begins. By default CloudNSite owns and operates the codebase as a managed service, and the agreement can instead be structured so you own the production source code, the prompt configurations, the evaluation suite, and the deployment runbooks. Build pricing and operations pricing are separate pages because they are separate decisions. You can buy the build and run it with your own team, or keep us on to operate it under a monthly agreement. Both are normal. Handover support is scoped into every contract, so moving the system to your team or to a new vendor is planned, documented work. We do not disappear after launch, and we do not hold your code to keep a retainer.
Support model: operate with us, or take it over
After launch you choose. Managed Care, from $1,500 per month, covers bounded business-hours care. Managed Operations, $4,000 to $7,500 per month, owns production reliability and releases. Critical Managed Operations runs on a custom service schedule. Or your team operates the system with the runbooks and a scoped handover.
Commercial terms: published, one-time, no seats
Prices are published. The Current State Assessment is $999 fixed. A Defined Automation Build starts at $8,000. Focused Custom Automation runs $12,000 to $20,000. Operations Automation runs $25,000 to $60,000. Business-critical work and work that needs private infrastructure get a custom proposal. Regulated work is quoted from the same published lanes. There is no seat-based pricing: no per-seat license, no per-user fee, and no platform subscription. A build is a one-time price. Managed service is one monthly price for the system, however many people use it.
Discovery: paid, fixed, and first
Discovery comes before any build and has a fixed price. The Current State Assessment is $999, delivered in as little as 3 to 5 business days, and hands over two documents together: the current-state map of how the workflow runs today, and the Automation NSite with the proposed build, the architecture, and the proposal. It ends in a defensible go, no-go, or defer recommendation, and the $999 is credited toward an implementation SOW of $12,000 or more signed within 30 days. RFPs name this step Phase 0, paid discovery, or a discovery sprint; ours is the Current State Assessment. Organizations still deciding where AI should operate start instead with the AI Readiness + Governance Sprint, from $7,500.
What we do not do
We do not resell licenses or place contractors. We do not claim certifications we do not hold: HIPAA-ready describes the architecture, and compliance attaches to a specific deployment and its agreements. We do not quote a price for unassessed scope. We do not run more concurrent builds than a small senior team can deliver.