1. Decide what is worth building
If an existing product covers the workflow and supports the necessary integrations, configuring it may be a better fit than starting from scratch. Consider custom software when available tools cannot reasonably cover your rules, access needs or user experience.
Compare options using the same workflow: what the user does, where information ends up and how errors are resolved. Include subscriptions, provider dependencies and administration effort alongside initial delivery.
Configure an existing product
Useful when the workflow is standard and the product supports the required roles, exports and connections. Check plan limits and per-user costs.
Connect current applications
Useful when existing tools work but the team copies data between them. The estimate depends on APIs, matching rules and error handling.
Build a custom application
Useful when the process requires specific features or rules. Include testing, documentation, operation and future changes as well as the interface.
2. Understand the actual cost drivers
Two applications with the same number of screens can require very different amounts of work. A basic form differs from one with approvals, version history, attachments and permissions for multiple roles. An estimate should specify the behaviour covered by each workflow.
- Users and permissions: who can view, create, approve or change each piece of information.
- Integrations: documented APIs, test access, limits, synchronisation and recovery from failures.
- Data: sources, quality, duplicates, migration and verification in the receiving system.
- Interfaces: steps, mobile and desktop layouts, accessibility and error states.
- Quality and launch: testing, a review environment, backups, rollback and training.
- Operation: hosting, third-party services, monitoring, updates and support.
One idea, two different scopes
Illustrative example, not a price quote: “a customer request portal” could describe two different projects. The scopes below show why a price without defined deliverables is not comparable.
A bounded first release
Customers submit a request, see its status and receive a response. The team handles requests and updates their status. One defined workflow, agreed roles and a verified initial import.
An expanded version
Multiple approval stages, versioned documents, two-way ERP synchronisation, several organisations and reporting. Each adds rules, exceptions and checks.
- Separate the first release from features that can wait.
- Define acceptance: the user completes the workflow and correct data reaches the agreed destination.
- Record dependencies: API access, data examples, team decisions and availability for reviews.
3. Compare proposals against the same deliverables
Ask each proposal to state its included features, assumptions and exclusions. A lower total may cover a different scope. Check whether migration, integration testing, documentation and launch support are included.
For an existing application, a code and environment assessment may be needed before a firm estimate. Unknowns should become investigation steps rather than disappear inside a promised delivery date.
- What does each stage deliver, and who accepts it?
- What information and access must your team provide?
- How are new requirements and changes to the agreed scope handled?
- What access to source code, infrastructure and documentation is included in the agreement?
- Who handles defects, updates and incidents after launch?
4. Include the costs after launch
Separate discovery and implementation from subscriptions, hosting, external services and maintenance. Ask what changes as user numbers, data volumes or synchronisation frequency increase.
Agree who manages access, backups, updates and recovery. Data exports and a handover procedure belong in the continuity discussion. Specific terms are established in the project agreement.
5. How an estimate starts at ESolutionMedia
Tell us which process you want to improve, who uses it and which applications are involved. You can start without a technical specification; the concrete problem and desired outcome are the useful inputs.
We clarify what can remain in current tools, scope a first release and identify unknowns. Then we propose the next step: an assessment, an integration or a development stage with testable deliverables. We do not publish a universal price that would hide these differences.
ASSESS ONE WORKFLOW
Is automation worth the cost?
Compare the time spent today with the full workflow after automation, including review and corrections. Then subtract additional running costs. Use measured pilot results when available; otherwise treat the inputs as assumptions to test.
How the estimate works
- Hours released per month = tasks × (minutes before − minutes after) ÷ 60.
- Monthly value after costs = hours released × hourly value − additional monthly costs.
- Simple payback = implementation cost ÷ positive monthly value after costs. With a zero or negative monthly value, this model has no payback.
- 12-month balance = monthly value after costs × 12 − implementation cost.
Illustrative example, not a quote or client result. 500 tasks per month, reduced from 8 to 3 minutes, release about 41.7 hours. At 60 EUR per hour and 500 EUR in extra monthly costs, the model gives 2,000 EUR per month. A 6,000 EUR implementation would have a simple payback of 3 months, if that value is realised.
Released time is capacity, not automatically a cash saving. Payback assumes you can use that capacity productively or avoid a real cost. This simple model holds monthly volume and costs constant; it excludes ramp-up, taxes, financing and changes in revenue or quality. It is not a project price or an approval to implement.
Next, test the assumptions: use a typical month, include review time and recalculate with less time saved or higher running costs. Quality and access checks still need to pass before rollout.
Discuss the assumptions for your workflowREADY FOR A CONVERSATION
Prepare a short project brief
Use these prompts to describe the project. Download the plain-text template, fill it in locally and share only the context needed for the first conversation. You can also start with a short message.
- Problem and desired outcome
- Users, roles and the person accepting delivery
- Main workflow from start to outcome
- First-release scope and features that can wait
- Applications to connect and available APIs or exports
- Existing data, approximate volumes and migration needs
- Acceptance criteria, exceptions and access requirements
- Target date, constraints and available budget range
- Preferred responsibilities for hosting, source code, updates and support
The template is free and does not require an email address. Do not include passwords, confidential files or other people’s personal data.
Discuss your scope and estimate