Category Comparison
Boundaries between Arn and adjacent systems.
Category Comparison
This page defines target product boundaries. It avoids vendor-specific claims because those change over time and should be verified before being used in public competitive material.
Category position#
| Category language | Use now? | Why |
|---|---|---|
| Relationship operations | Directionally | Concrete enough for product strategy, but not implemented yet |
| Implementation operations | First planned wedge | Narrow enough to validate with source-backed status and ownership |
| B2B OS | Vision | Useful long-term ambition, too broad as a first purchasing category |
CRM#
CRMs are the right place for pipeline, revenue forecasting, sales process, account ownership, and go-to-market reporting.
Arn should eventually add source-backed relationship state, implementation context, customer communication state, and approved CRM updates.
Support tools#
Support tools are strongest when the primary unit of work is a customer issue, conversation, ticket, SLA, or support queue.
Arn should eventually operate at the relationship and workstream level: implementations, escalations, vendor dependencies, contract obligations, files, decisions, and multi-party coordination.
Project management#
Project management tools are useful for internal task planning, dependencies, and team execution.
Arn should eventually add external-facing work coordination, permissioned status, source-backed updates, and system sync for work that starts outside the project plan.
Customer onboarding tools#
Customer onboarding tools are closest to the first planned wedge. They usually help teams manage plans, milestones, tasks, customer portals, resources, timelines, and delivery execution.
Arn should only compete where it can be more communication-driven and evidence-backed:
- ingesting status from existing communication and systems
- stitching conversations and files into workstreams
- producing implementation briefs that cite sources
- separating internal status from customer-visible status
- syncing approved status, risks, and commitments back to systems of record
Procurement and vendor systems#
Procurement systems own intake, approvals, sourcing, supplier onboarding, spend controls, POs, invoices, compliance, and supplier lifecycle workflows.
Arn should support vendor relationships only where vendor communication and dependencies affect relationship execution. It should not start as a source-to-pay system.
Document and contract systems#
Document repositories store files. Contract systems manage legal workflows. Arn should eventually connect them to relationship operations:
- Which contract applies to this customer or vendor?
- Which obligation affects implementation?
- Which file is missing?
- Which signed date conflicts with a system field?
- Which document can this external participant access?
Current status#
The current repository does not implement the relationship operations category yet. It implements the app and API foundations required to start building it.