Know what you're agreeing to

Pricing and scope

The price depends on the workflow and the responsibility involved. Start with scope, then agree on costs in writing before work begins.

Scope-based proposals

We’re developing the managed-service offer through internal use and discovery conversations. We do not publish fixed packages or promise pilot availability.

A proposal would separate initial work, recurring management, and changes. It would also state any discovery or pilot fees. Do not assume an assessment, deliverable, or pilot is free.

Initial work

Depending on the agreement, initial work could include assessment and scoping, configuration, necessary integrations, testing, and team training.

The proposal should specify deliverables and acceptance criteria. It should make clear what you need to supply and which decisions need your approval.

Recurring management

Ongoing management would need its own defined scope. That could cover agreed maintenance, support, usage arrangements, and periodic review of the workflow.

Support hours and response expectations belong in the agreement. Recurring management does not imply 24/7 coverage, unlimited usage, or unlimited custom development.

Model usage and hosting may be allowances, pass-through costs, or accounts your business pays directly. The proposal must say which applies and who monitors spending limits.

Separately scoped changes

New workflows, major integrations, more users, higher usage, and substantial customization can change the cost and risk. Review and approve those changes before work starts.

A request outside the agreement is not automatically included in the recurring fee.

What affects cost

The complexity of the task and the number of systems involved.
Information sensitivity and required access controls.
Hosting, model choice, and expected usage.
Number of users and the training they need.
Review requirements, support expectations, and maintenance effort.

Company size alone is not enough to price a workflow. A narrow task with approved documents differs from a process that changes live business records.

What the written proposal should settle

Before committing, agree on inclusions, exclusions, billing responsibility, cost limits, service hours, and response expectations. Include pilot terms, cancellation, ownership, and offboarding.

Continuing after a pilot needs an explicit decision. Neither a successful demo nor a discovery conversation commits you to recurring management.