BUDGET / FIRST PASS
Planning ranges by product shape.
Early budgets need room for uncertainty. Use these USD ranges to decide whether the project fits the business case and which version deserves a detailed scope. They are planning ranges, not Async quotes.
A narrow workflow can cost more than a broad-looking dashboard when it touches old data, regulated decisions, or software that was never designed to integrate. The estimate should state those assumptions rather than hide them inside one total.
Methodology: these editorial examples were prepared in August 2026 to illustrate how roles, data, integrations, assurance, and operating responsibility can change a custom build. They use round USD figures for a professional remote team covering discovery, design, engineering, quality assurance, and launch. They are not a market survey, a record of Async project prices, or a replacement for a scoped proposal.
| Scope | Planning range | Typical shape | Common budget pressure |
|---|---|---|---|
| Focused internal tool | $20,000-$50,000 | One team, one main workflow, a small data model, and limited integration with existing systems. | Unwritten business rules, spreadsheet edge cases, or an API that has not been inspected. |
| Operational v1 | $50,000-$150,000 | Several roles, approvals, reporting, a customer or staff portal, and multiple integrations. | Data migration, permissions, exception handling, and the admin tools needed to run the system. |
| Multi-system platform | $150,000-$400,000+ | Connected business units, complex rules, substantial migration, custom infrastructure, or sensitive data. | Compliance, high availability, legacy replacement, phased rollout, and change across several teams. |
PROJECT EXAMPLE / ASYNC MANAGEMENT
The rules behind our own management platform.
We built Async Management CRM for our internal operations. It combines staff workflows with a sales pipeline. The project illustrates the scope behind a custom platform; it is not a customer price example.
An overnight shift must belong to the correct workday. Imported leads need duplicate handling. Accepted and rejected quotes lead to different next actions. Staff records and financial actions need separate permissions. Each rule adds decisions, implementation and tests that a screen count alone will miss.
For your project, separate the first usable workflow from later modules before asking a team to estimate it. List the records that move between systems, the exceptions a person handles today and who can approve changes. Those details make a proposal more useful than a price attached to the word "dashboard."
Start with one complete workflow
For a sales system, define how a lead becomes a customer record, how a quote is decided and what happens after acceptance.
Estimate the rules and integrations
Permissions, overnight timing, imports and financial calculations each need implementation and verification alongside the visible interface.
WORKED EXAMPLE / ASSUMPTIONS
Turn a first-release scope into a budget.
For a smaller starting point inspired by our CRM workflows, consider a web tool for one sales team. Assume two access roles, a CSV lead import with duplicate review, customer records, quote acceptance or rejection, a change history and a basic status report.
This is a hypothetical planning exercise, not the price or duration of Async Management CRM. The hours and $75 blended hourly rate below are arithmetic inputs chosen for this example, not an Async rate card or market-rate benchmark. Replace them with a supplier's scoped estimates.
| Workstream | Included work | Assumed hours | Example cost (USD) |
|---|---|---|---|
| Discovery | Map the workflow, inspect a sample import and agree acceptance checks. | 40 | $3,000 |
| Design | Design the import, customer record and quote-decision screens, including error states. | 48 | $3,600 |
| Engineering | Build the data model, access rules, import handling and quote workflow. | 240 | $18,000 |
| Testing and corrections | Test permissions, duplicate records and quote transitions; resolve defects. | 104 | $7,800 |
| Launch and handover | Set up deployment and backups, rehearse the import and document operation. | 48 | $3,600 |
| Build subtotal | The five workstreams above. | 480 | $36,000 |
| Planning reserve | 20% of the build subtotal for uncertainty within this scope. | Not additional committed hours | $7,200 |
| Illustrative build budget | Build subtotal plus planning reserve; operating costs are separate. | Not a delivery schedule | $43,200 |
SUPPLIERS / COMPARABLE PROPOSALS
Compare the total cost of outsourcing software development.
Compare proposals against the same workflow and acceptance checks. A lower hourly rate can still produce a higher total if the estimate leaves out testing, migration or the work your own team must do. Ask which roles the quoted rate includes and whether design, project coordination and quality assurance are separate charges.
For an international engagement, agree on invoice currency and payment milestones, overlap hours for decisions, and who holds access to code and hosting accounts. These questions apply whether you buy from the US, UK, Australia or Germany. Supplier location alone does not establish the scope or quality of a proposal.
Fixed-price proposal
Check the included workflows, acceptance criteria and exclusions. Ask how the supplier prices changes and handles assumptions that fail during discovery.
Time-based proposal
Ask for estimated effort by workstream, the team allocation and a spending limit or review point. Agree how you will see progress and approve more work.
SCOPE / COST DRIVERS
The expensive parts often sit behind the screen.
Roles and permissions
Each role adds visibility rules, allowed actions, approval paths, and test cases. A manager, customer, operator, and auditor should not see the same product.
Business rules
Pricing, eligibility, scheduling, approvals, and exceptions must become explicit enough for software to apply them without relying on hallway knowledge.
Data and migration
Duplicate records, missing identifiers, inconsistent formats, and undocumented spreadsheets require decisions before a new system can trust the imported data.
Integrations
Stable APIs reduce uncertainty. File exports, vendor limits, old databases, and manual handoffs increase engineering and operational work.
Security and assurance
Sensitive data may require stronger access controls, audit history, retention rules, security review, or evidence for a customer's procurement process.
Operating model
Monitoring, backups, support tools, documentation, incident ownership, and deployment access determine whether the team can run the product after launch.
BUSINESS CASE / OPTIONS
Compare custom development with the full cost of buying.
Off-the-shelf software fits when the workflow is common, configuration covers the important differences, and a vendor can meet the security and integration requirements. A subscription also gives you updates and support without owning a software team.
Custom development can fit when the workflow creates a competitive advantage, several systems need one coherent process, or workarounds consume enough time and attention to justify ownership. The business case should value avoided manual work, fewer errors, faster service, or a new source of revenue.
| Cost area | Buy and configure | Build custom |
|---|---|---|
| Upfront work | Setup, configuration, migration, integration, and training. | Discovery, design, engineering, migration, and rollout. |
| Ongoing cost | Subscriptions, premium modules, support tiers, and usage fees. | Hosting, maintenance, support, monitoring, and planned improvements. |
| Process fit | The team adapts to the vendor's model and limits. | The product can reflect the business rules worth preserving. |
| Control | Vendor roadmap, pricing, export options, and contract terms apply. | You own the roadmap and carry responsibility for operating the system. |
| Switching cost | Data export, retraining, and replacement integrations. | Documentation, code ownership, infrastructure access, and maintainability. |
ESTIMATE / WORKSTREAMS
A credible estimate explains where the work goes.
A single number is hard to test. Ask suppliers to separate product discovery, design, engineering, quality work, launch, and post-launch support. The split shows whether two bids cover the same responsibilities.
- Discovery: workflow mapping, user research, requirements, priorities, and technical investigation
- Product design: flows, prototypes, interface states, content, and accessibility
- Engineering: frontend, backend, data model, permissions, integrations, and admin tools
- Quality: automated checks, manual testing, security review, performance, and recovery paths
- Launch: migration rehearsal, production setup, monitoring, documentation, and training
- Operation: support ownership, maintenance capacity, response expectations, and planned iteration
RISK / DISCOVERY
Inspect data and integrations before fixing the price.
Integration estimates based on a vendor name are weak. The team needs the API documentation, authentication method, rate limits, test environment, and examples of the data that moves between systems. Some vendors charge for access or restrict which records a partner can change.
Migration also needs a sample. Ten thousand clean records can be easier than five hundred records assembled by different teams over several years. Profile the data, define the source of truth, and rehearse the migration before the launch window.
A paid discovery phase can resolve those questions and produce a narrower build estimate. Our custom software development service starts by mapping users, decisions, data, and exceptions around the workflow.
Ask the vendor
Request API access, sandbox credentials, limits, support contacts, data-export options, and the contract terms that affect integration.
Ask the business
Name the owner of each dataset, decide how conflicts are resolved, and document which historical records the new system must preserve.
DELIVERY / PHASING
Fund one complete operational improvement first.
A first release should solve a complete problem for a defined group. An operations tool might accept a request, apply routing rules, collect approval, and record the outcome. That journey creates value and exposes the next useful investment.
Horizontal platform work still matters, but it should support a release someone can use. Long infrastructure programs without a working slice make scope and value harder to test.
- Write a measurable baseline for time, errors, delays, or revenue before development starts.
- Choose the smallest user group and workflow that can produce a complete outcome.
- Prototype uncertain rules and interfaces before building the full system.
- Test risky integrations and migration samples during discovery.
- Release to a controlled group, observe usage, and fund the next phase from evidence.
PROCUREMENT / CHECKLIST
Questions a software proposal should answer.
- Which users, workflows, business rules, and integrations are included?
- Which assumptions still need technical investigation?
- Who provides data access, subject-matter decisions, content, and approvals?
- How will the team test permissions, migration, accessibility, and failure recovery?
- Which source code, cloud accounts, documentation, and deployment access will you receive?
- Which licenses, hosting charges, vendor fees, taxes, and support costs sit outside the price?
- How are scope changes estimated and approved?
- Who owns incidents and maintenance after launch?
OUR WORK / SCOPE EVIDENCE
See the systems behind these scope questions.
Internal business workflows
Our Async Management CRM project shows staff operations, quote decisions and role-based access. The screenshots conceal private records. We do not publish a project price or savings claim.
Connected equipment and operations
Our Async EMS project covers device polling, alerts and controlled configuration changes. Its web console and mobile companion show why integration and permissions belong in the scope. EMS is an Async-owned product.