Start with a unit of work
Choose a routine the team can demonstrate from beginning to end, such as checking a document or preparing a quote. Record monthly volume, minutes per execution, people involved and exception frequency. Include busy days in the sample.
Count each person's active time separately from waiting for a customer. If two people work for ten minutes each, the execution uses twenty minutes of capacity. Split the estimate when the process varies by customer type.
- Input: what starts the routine and in which system?
- Output: what must exist at the end and who checks it?
- Exception: when must someone stop or make a decision?
- Evidence: where can the completed task be verified?
Separate implementation from operation
Initial work may include discovery, design, integration, data cleanup, configuration, acceptance checks, documentation and training. Ask the proposal to state what is included, what depends on your team and what counts as a scope change.
Recurring costs may include hosting, model usage, channel fees, licenses and support. An implementation fee alone is not the cost of using the workflow. Providers and volumes change the calculation; ask for assumptions and limits.
- Period cost = implementation + recurring costs over the period + contracted changes.
- Record currency, applicable taxes, included volume and how excess usage is handled.
What increases the work involved
An authorized, documented integration offers different conditions from a system with no integration interface. Duplicate records, free-text fields, external dependencies and unclear permissions add work. Finding a constraint early makes it possible to reduce scope or choose another route.
Actions with lasting consequences require additional care. Sending a proposal, charging a customer or changing inventory needs rules, authorization, traceability and recovery. Human review is part of the cost and must remain in the estimate of time still required.
Freed capacity and cash are different measures
Potentially freed time is an operational estimate. Multiplying it by hourly cost helps compare options, but it becomes expense reduction only if actual spending changes. It may instead enable more work or shorter queues, which require separate observation.
Use the calculator below as a scenario. Enter data from your routine and an assumed reduction in active time. It does not measure your operation, predict outcomes or calculate additional revenue. Validate the assumption through a pilot and include new review and maintenance tasks.
Compare proposals on the same basis
A proposal should specify the delivered workflow, integrations, acceptance criteria and volume limits. Confirm who handles failures, how to export data, what access is required and how the work continues after handover.
Agree an assessment using representative examples, including errors, duplicate inputs and an unavailable system. Evaluate quality alongside speed: a fast execution that frequently needs correction can increase total cost.
- Which scenario demonstrates that the delivery can be accepted?
- Who approves sensitive actions and handles exceptions?
- How do costs and failures become visible to the owner?
- What is the plan for pausing or reversing the workflow?
Prepare a conversation that produces a scope
Bring a process walkthrough, a list of systems, known volumes and the person who owns the routine. Remove personal data that is not needed. If there is no reliable baseline, start by collecting one.
This makes it possible to assess a simple integration, AI automation, an existing product adaptation or custom development. Timing and price must reflect that scope. Nellia discusses those conditions before proposing implementation.