Decision context: Zennify currently runs the majority of its AI capability on Claude (Projects, MCP connectors, custom skills, plugins) with Windsurf for developers. Auctor is a Y Combinator-backed startup (X25 batch, ~$500K raised, 5 employees) purpose-built as an agentic operating system for professional services and system integrators. The core question: does Auctor's delivery-specific UI and meeting listener justify adding a net-new platform on top of what we've already built, or does doubling down on Claude provide more flexibility, lower cost, and faster innovation?
Advantages
- Purpose-built UI for SI/PS workflows — requirements capture, SOW generation, artifact traceability from discovery through go-live
- Meeting listener joins calls live, captures context, extracts requirements, and feeds structured outputs directly into platform
- Forces adoption standards — shared delivery platform drives AI usage consistency, especially for less tech-forward team members
- Built-in analytics and metrics — usage dashboards, delivery tracking, knowledge-base learning from past projects
- Sales-to-delivery handoff alignment in a single system, reducing requirements drift
- SOC 2 Type II + ISO 27001 — enterprise security posture for client-facing compliance
Risks and drawbacks
- Unproven vendor — founded 2025, ~5 employees, $500K raised. Valiantys is their marquee reference. Longevity and roadmap execution unknown
- Net-new OpEx — does not replace anything. Pricing TBD but adds a new budget line with contract commitment
- Integration limits — Gong integration confirmed; Salesforce, Jira, Slack depth is unverified vs. our existing native build
- Overlap and redundancy — many capabilities (SOW drafting, requirements, knowledge base) already exist in our Claude ecosystem
- Vendor lock-in risk — institutional knowledge in a startup platform creates dependency on their survival
- Change management — two platforms to learn and manage instead of one
Advantages
- Lower total cost — no additional platform spend. Claude Team plan already in place. One vendor, one bill
- Already built and proven — Projects, MCP connectors, Account Intelligence plugin, Ziggy orchestration, and lifecycle agents are in production
- Innovation pace — Anthropic ships monthly (connectors, plugins, Code, deep research). Platform gets better without internal effort
- Maximum flexibility — MCP, API, and connector ecosystem is wide open. Integrate anything, customize freely
- No contract lock-in — month-to-month, scale seats up or down. Zero switching cost
- Single platform — one tool for the whole org reduces training complexity and creates unified AI culture
Risks and drawbacks
- No delivery-specific UI — general-purpose tool; no tailor-made views for requirements traceability or project-level artifact management
- No live meeting listener — requires manual upload of recordings/transcripts; no real-time call-join capability
- Usage cannot be enforced — opt-in by nature; adoption depends on culture and champion-driven enablement
- Maintenance burden — custom skills and integrations need ongoing effort. Mitigated: 2 resources, ~10 hrs/week at low cost
- No built-in delivery analytics — usage metrics at seat level only; project-level reporting requires custom build
- Knowledge reuse requires curation — no automatic learning loop without deliberate knowledge-base management
Head-to-head: key decision dimensions
| Dimension |
A — Auctor + Claude |
B — Claude only |
| Annual cost |
Claude Team + Auctor (TBD). Net-new OpEx line. |
Claude Team only. Maintenance via existing resources. Minimal incremental cost. |
| Meeting intelligence |
Live listener joins calls, extracts requirements in real-time into platform. |
Manual upload of recordings/transcripts. Functional but adds friction. |
| Delivery workflow UI |
Purpose-built for SI teams — structured requirements, artifact gen, handoff tracking. |
General-purpose chat and Projects. Capable but not delivery-centric. |
| Integration depth |
Gong confirmed. SF/Jira/Slack depth unverified. |
Deep, proven. MCP connectors to SF, Jira, Slack, Okta, Google, Zapier — all in production. |
| Adoption enforcement |
Structured platform can mandate workflows and measure compliance. |
Opt-in. Depends on culture and enablement. |
| Innovation velocity |
Startup pace but unproven roadmap. 5-person team. |
Anthropic ships aggressively — monthly releases, expanding ecosystem. |
| Vendor risk |
High. Early-stage, $500K raised, limited customer base. |
Low. Well-capitalized, growing rapidly. No lock-in. |
| Knowledge reuse |
Auto-ingests past projects into learning knowledge base. |
Manual curation required. More effort but more control. |
| Org complexity |
Two platforms to manage, train, maintain. |
One platform for everyone. Simpler onboarding. |
Build vs. buy: key consideration
Zennify has already invested heavily in build — custom Claude Projects, MCP integrations, Account Intelligence plugin, Ziggy orchestration, and lifecycle agents are all in production. Auctor would be a buy layer on top of existing build, not a replacement. The question is whether Auctor's meeting listener and structured delivery UI provide enough incremental value to justify a new vendor relationship, contract, and second platform — or whether those gaps can be closed with targeted investment in the Claude ecosystem.
Framing the decision
Choose Scenario A if: the meeting listener and enforced delivery adoption are considered critical differentiators that justify net-new OpEx and vendor risk — and if Auctor demonstrates deep Salesforce and Jira integration that complements what we've already built.
Choose Scenario B if: cost discipline, integration depth, platform simplicity, and innovation pace outweigh the convenience of a delivery-specific UI — and if the team can close meeting-listener and adoption-enforcement gaps through targeted Claude skill development.