| What the buyer gets | Specialized software for a defined function | A custom agent operation designed, deployed, and run by Marshal | Prebuilt for product access; Marshal for operational relief |
|---|
| Category expertise | Built around a common job such as support, recruiting, finance, or sales | Engineered around the client's actual workload, systems, policies, and approval boundaries | Prebuilt for standardized category depth; Marshal for business-specific operation |
|---|
| Time to first use | Often fast when the required system, content, and owner already exist | Days when access, business rules, and success criteria are clear | Prebuilt for standard activation; Marshal when setup must be delegated |
|---|
| Who configures the business context | Customer team | Marshal, with the client defining outcomes, policies, and approval rules | Marshal when internal configuration time is scarce |
|---|
| Who connects the surrounding systems | Customer team, vendor onboarding, or implementation partner | Marshal | Marshal when integration ownership is the constraint |
|---|
| Who prepares and maintains knowledge | Customer team | Marshal manages the operating context inside the agreed scope; the client remains authoritative on policy | Marshal when knowledge upkeep has become an operating burden |
|---|
| Who tests behavior and edge cases | Customer team | Marshal tests the managed scope and sets approval and exception paths | Marshal when the workload is production-critical |
|---|
| Who defines human handoffs | Customer team | Marshal designs and maintains the handoff process with the client | Marshal when exceptions cross teams or systems |
|---|
| Who monitors performance | Customer team uses vendor dashboards and analytics | Marshal monitors the managed operation | Marshal for day-to-day accountability |
|---|
| Who investigates failures | Customer team, with vendor support for product-level issues | Marshal diagnoses workflow-level failures and coordinates infrastructure support when required | Marshal when nobody internal should own recovery |
|---|
| Who fixes workflow drift | Customer team updates sources, rules, permissions, and configuration | Marshal repairs, retests, and improves the managed system | Marshal for month-six ownership |
|---|
| Who manages usage | Customer team monitors outcomes, credits, seats, or consumption | Marshal manages operating economics inside the scoped relationship | Marshal for one predictable operating relationship |
|---|
| Human control | Customer defines and implements approvals | Client holds approvals and rules; Marshal carries the work | Depends on the desired operating model |
|---|
| Cross-functional work | Usually strongest inside the product's category and ecosystem | Can span sales, support, operations, and visibility across the client's existing tools | Prebuilt for a narrow embedded job; Marshal for cross-system workloads |
|---|
| Internal labor cost | Administration, monitoring, troubleshooting, knowledge upkeep, governance, and improvement remain internal | Marshal absorbs the operating work inside the managed scope | Marshal when internal time is scarce or expensive |
|---|
| Main limitation | The buyer must supply the operator | Costs more than entry-level software and is not designed for DIY control | Depends on whether the buyer wants to operate agents |
|---|
