Enterprise Pitch Materials

This pack = the Q&A you (Ops manager / IT manager) need when pushing realvco internally and your IT, Compliance, and Finance departments start asking questions.

Many companies’ decision flows go: you see realvco, find it useful → propose internally → IT starts asking security questions, Compliance asks regulatory questions, Finance asks ROI questions. If you google each one on the spot, you’ll get steamrolled. This pack lists the 20 most common questions with answers you can paste straight into your proposal.

When this is useful:

• Your company wants to use a managed AI agent service, but IT hasn’t approved a similar service before
• You need to write an internal sign-off doc / purchase request
• You want to align with the CTO / IT director on details in one go

---

Why Your Company Should Use realvco (vs Self-Hosting on DigitalOcean / AWS)

In short: self-hosting looks cheap (low monthly fee), but engineer time is the hidden cost. An engineer spending 20% of their time maintaining the AI bot equals $4,000-8,000/month in labor cost. realvco internalizes that.

---

IT Department Common Questions (10 Q&A)

Q1: Is realvco self-hosted at our company, or SaaS?

A: realvco is SaaS (Software as a Service) — hosted on realvco’s cloud. Not self-hosted at your company.

That means:

• Your company doesn’t need servers, doesn’t need IT to deploy
• Data is stored on realvco’s cloud (location depends on subscription plan, currently mainly Asia-Pacific)
• Upgrades, backups, monitoring are handled by realvco

If your company’s internal policies mandate self-hosting (common in finance, government), realvco isn’t a fit — consider running OpenClaw yourself.

---

Q2: Is data encrypted in transit?

A: Yes. realvco services use HTTPS (TLS 1.2+) end-to-end:

• You logging into admin-panel: HTTPS
• AI bot communicating with Telegram / LINE / Slack: HTTPS (platform-mandated)
• AI bot calling LLM API (OpenAI / Anthropic): HTTPS (vendor-mandated)
• realvco internal service-to-service: within private network (VPC), not public internet

---

Q3: Is data encrypted at rest?

A: Yes. realvco uses Cloudflare D1 (SQLite over Workers) for configuration data; cloud disk-level encryption is provided by Cloudflare (AES-256).

• Configuration data, customer lists: D1 encrypted
• Conversation logs (if retained): D1 encrypted
• API tokens / secrets: separately encrypted via Workers Secrets

---

Q4: What’s the backup policy?

A: realvco does daily auto-backup with 5-day retention:

See Auto Backup Guide for details.

---

Q5: How is disaster recovery (DR) handled?

A: realvco provides two layers of recovery:

1. Restore points: Before upgrades or modifications, you can manually create restore points in admin-panel. One-click rollback to that timestamp when issues arise.
2. 5-day upgrade rollback: If an upgrade caused issues, you can roll back to the previous version within 5 days.

For more severe disasters (entire realvco cloud offline), realvco runs on Cloudflare’s global CDN — single data center outage doesn’t affect service. For full RTO / RPO numbers, contact realvco sales for the SLA document.

---

Q6: How is account management done?

A: realvco uses Magic Link (single-use email login link) for authentication, no passwords.

Flow:

1. Employee enters company email
2. realvco emails a login link
3. Employee clicks the link, valid for 30 minutes
4. After login, a session token is generated

Pros:

• No password to be stolen / phished
• When an employee leaves, disabling their company email blocks login
• No “weak employee password” problem

If your company needs SSO / SAML (Google Workspace, Microsoft Entra), it’s currently available only on enterprise plans. Contact realvco sales to confirm.

---

Q7: Where are realvco’s cloud data centers?

A: Depends on subscription plan. realvco runs on Cloudflare Workers’ global network, but primary storage layer is at:

• Standard plan: Asia-Pacific (Tokyo / Singapore)
• Enterprise plan: data center can be specified (EU / US / APAC)

If your company has data residency requirements (e.g., China PIPL, certain Taiwan PDPA industries), contact realvco sales for customization.

---

Q8: GDPR / CCPA compliance boundaries?

A: Under data protection regulations, the roles are:

Specifically:

• Your company obtains consent from your own customers for AI assistant conversation data processing
• realvco provides a DPA (Data Processing Agreement) for enterprise plan signing
• For customer deletion requests (GDPR right to erasure), your company executes deletion in realvco backend

realvco does NOT use your company’s customer data to train models.

---

Q9: SOC 2 / ISO 27001 certification?

A: Not yet.

Expected roadmap (placeholder — actual timeline pending realvco announcement):

• 2026 Q4: SOC 2 Type 1 certification (planned)
• 2027 Q2: SOC 2 Type 2 certification
• 2027 Q4: ISO 27001 certification

If your company mandates SOC 2 for procurement, realvco isn’t currently a fit. Consider waiting until certifications are complete.

For deeper security detail, realvco can provide a Security Whitepaper — contact sales.

---

Q10: What if realvco shuts down?

A: A reasonable concern. realvco’s exit protections:

1. Data export: You can download complete customer data (CSV / JSON) from admin-panel anytime
2. OpenClaw is open-source: realvco’s hosted core (OpenClaw) is open-source with public source code. If realvco shuts down, your company can stand up its own instance to continue service.
3. 30-day notice: realvco TOS commits to 30-day advance notice if service terminates, giving customers time to export / migrate.

See OpenClaw official resources.

---

Compliance Department Common Questions (5 Q&A)

Q1: Industry regulatory restrictions (Finance / Healthcare / Education)

A: realvco is currently not specifically designed for these industries. Evaluate before use:

If unsure, contact realvco sales + your company’s legal counsel jointly.

---

Q2: Liability for AI errors?

A: Per realvco TOS:

• realvco provides the tool, not liable for losses caused by AI errors
• Your company is the responsible party for “using AI assistants to serve customers”
• Recommend explicitly informing customers at conversation start: “This is an AI assistant — for important decisions, contact a human”

Safety nets realvco provides:

• Fallback mechanism: bot escalates to human when uncertain
• Disclaimer template: bot settings can include “I am AI, responses are reference only”
• Conversation log retention: for post-hoc traceability (retention period varies by plan)

---

Q3: Data leak liability?

A: Two layers:

Layer 1: realvco’s own security responsibility:

• realvco is responsible for the security of its own cloud infrastructure
• If a leak occurs due to a realvco vulnerability, compensation per TOS terms (cap typically equal to past 12 months of service fees)

Layer 2: Your company’s security responsibility:

• Employee password / Magic Link email being stolen: your company’s responsibility
• Mistakenly pasting customer data into AI bot conversation: your company’s responsibility
• API token leak: your company’s responsibility

Risk reduction recommendations:

• Employees use dedicated company emails with 2FA enabled
• Periodically review admin-panel login records
• Avoid putting sensitive data into AI bot conversations

---

Q4: Conversation log retention period?

A: By subscription plan:

If your company has regulatory minimum retention of N years (finance typically 5-7), choose enterprise + customization.

---

Q5: What if employees misuse AI for confidential data?

A: realvco provides safeguards (some features in development):

• Keyword filtering: bot settings allow a blocklist (e.g., ID numbers, credit card patterns) → bot auto-rejects responses on detection
• Conversation audit log: admins can review all conversations, trace who sent what when
• Permission tiers: different employees can only see conversations for customers they own

For deeper DLP (Data Loss Prevention) integration, contact realvco sales.

---

Finance Department Common Questions (5 Q&A)

Q1: Pricing transparency?

A: realvco charges two types of fees:

Key point: LLM API fees are paid directly from your company to OpenAI / Anthropic, not through realvco. realvco only collects monthly fees for the managed service.

Estimated monthly LLM costs:

• Light use (< 100 conversations/day): $10-30
• Medium use (100-500/day): $50-200
• Heavy use (500+/day): $200+

---

Q2: What if usage suddenly spikes (cost runaway)?

A: realvco + LLM vendor double-layer protection:

realvco side:

• Set monthly usage cap in admin-panel
• Auto-pause bot when cap is hit (avoid continuous token burn)
• Budget alert emails (50% / 80% / 100% triggers)

LLM vendor side:

• OpenAI / Anthropic both support monthly spending caps
• Recommend setting a cap directly in the LLM dashboard (e.g., $500/month)

With double protection, theoretical max monthly spend = realvco monthly fee + LLM vendor cap.

---

Q3: Annual discount?

A: Usually yes, varies by plan (placeholder — actual discount per official site):

Annual billing is paid upfront; if cancelled mid-term, remaining months refunded pro-rata (details per TOS).

---

Q4: What’s the SLA?

A:

For full SLA document, request from realvco sales.

---

Q5: Payment methods and invoicing?

A:

• Payment methods: credit card (Stripe), bank transfer (enterprise), PayPal (some regions)
• Invoicing: standard plans get electronic invoices; enterprise can get printed invoices with company name
• Currency: USD; Taiwan plan supports TWD

---

ROI Comparison (Self-hire Engineer vs realvco Annual Fee)

Scenario: Company wants a 24/7 customer support AI bot. Compare two options.

Option A: Self-hire engineer + self-host OpenClaw

Option B: realvco Pro plan

Comparison

Conclusion: Unless your company already has idle engineer time (and IT wants to learn OpenClaw), realvco’s ROI is significantly better than self-hosting in most cases.

---

Proposal Template (Paste into Word)

Below is a simplified internal proposal template. Copy-paste into Word / Google Docs and adapt to your company:

=== PROPOSAL START ===

Subject: Procurement of realvco managed AI agent service (annual fee $XXX)

[Background]
Our department currently faces [understaffed customer service / 24/7 customer
communication needs / repetitive Q&A consuming time]. To solve this pain
point, we propose procuring realvco managed AI agent service.

[Solution]
realvco (realvco.com) is a managed AI agent SaaS platform offering:
- 24/7 AI customer support bot (Telegram / LINE / Slack integration)
- Managed full deployment, upgrades, backups
- admin-panel back-end management interface

[Cost]
- realvco Pro plan annual: $948 USD
- LLM API cost (estimated): $1,200 USD / year
- Total: $2,148 USD / year

[ROI]
Compared to self-hosting (hire engineer + self-host VPS) at $19,440 / year,
saves approximately $17,000 / year.

[Risks]
- realvco is an emerging SaaS, currently no SOC 2 (roadmap targets 2026 Q4)
- Data stored on realvco cloud, DPA required
- Exit mechanism: data export available, underlying OpenClaw is open-source

[Recommendation]
Recommend procuring standard plan for 3-month trial, upgrade to Pro /
enterprise based on results.

[Attachments]
- realvco Security Whitepaper (request from sales)
- realvco DPA template
- realvco TOS

=== PROPOSAL END ===

---

Related Docs

• Subscription management
• Auto Backup Guide
• Support ticket system
• What is realvco