Questions seriousbuyers ask.
Pricing, diagnostic, security, timeline, ownership, approval rules, and what live actually means.
Straight answers before a fit call.
Built from the Agentra offer brief: qualification, diagnostic economics, proof honesty, deployment rules, and ownership.
Fit and qualification
Who is Agentra for in the first 90 days?
US: B2B services, IT services/MSPs, agencies, staffing/recruitment, and sales-led SaaS teams with 100-2,000 employees or $10M-$250M revenue. India: IT services, education/admissions, healthcare chains, and finance-heavy manufacturing/distribution teams with 300-5,000 employees or ₹100Cr-₹2,000Cr revenue.
Who should not book a fit call?
Teams with no senior business owner, no measurable KPI, no willingness to grant system/data access, no production intent, chatbot-level budget expectations, or a junior innovation sponsor without approval authority.
What makes a workflow deployable?
It should meet at least four of six conditions: frequent, time-consuming, uses existing data, has repeatable rules, has a senior owner, and can be measured through time saved, revenue recovered, cost reduced, or risk lowered.
Diagnostic and pricing
Is the diagnostic just a paid PoC?
No. A PoC builds a throwaway demo to prove the technology works. The Workflow Deployment Assessment produces a decision document: workflow map, ROI estimate, data and system readiness, governance requirements, and a fixed-price deployment proposal. Nothing is thrown away.
Why is the diagnostic paid?
Because it has standalone value. You keep the Workflow Deployment Assessment even if you never hire Agentra. It de-risks a $35K-$100K or ₹18-75 lakh deployment decision and is credited against the pod if you proceed within 60 days.
Do you discount the diagnostic to zero?
No. Paying is part of qualification. Free discovery turns Agentra into the free-PoC shop it refuses to be.
How does pricing localize?
USD is the global default. Visitors can switch the display between USD and INR from the footer currency control.
Deployment and ownership
Can Agentra deploy more than one workflow?
Not in the first pod. Agentra deploys one workflow first, then expands through AgentOps after production proof.
What does live mean?
Live means the workflow is connected to agreed systems, handles real cases, includes human approval and exception paths, has audit logs, trained users, a KPI baseline, and a clear ownership path.
Do humans stay in control?
Yes. Human approval rules, exception paths, and audit logs are designed before the workflow goes live.
What does the 45-day clock depend on?
The clock starts after kickoff, workflow selection, system access, and client-side process owner availability are confirmed.
Proof, security, and EEAT
What if Agentra has limited external client case studies?
Agentra labels proof honestly. Internal Vinove deployments and representative workflow cases are not presented as client wins until validated. The proof standard is before/after KPI, two-minute screen recording, one-page case note, real systems, and real approval logs.
Why trust Agentra before broad market proof exists?
Agentra is backed by Vinove's operating reality: 20+ years, real engineering teams, and live sales, finance, delivery, and support workflows to deploy internally before client scale.
Do you deploy AI without human approval?
No. Material workflow actions require human approval rules, exception paths, and audit logs. A workflow may include chat, email, WhatsApp, or voice, but Agentra rejects disconnected standalone-bot thinking.
How do you handle system access and security?
The diagnostic identifies required systems, data, permissions, approval roles, logging expectations, and blockers before build. Production access, retention, and security controls are governed in the deployment agreement.