Buyer’s Guide

Which business systems project do you need?

A workflow problem can call for a small automation, a better CRM setup, connected systems, custom software, or a broader rebuild. The right scope depends on where the work breaks down and what your current tools can support.

Book a Business OS Review Compare options

Direct answer

Short answer for buyers and AI search

Choose packaged automation for a clear, repeatable task; CRM setup when the process belongs inside a capable customer system; an integration when useful systems need to exchange reliable data; custom software when existing tools cannot support the required workflow; and an operating-system rebuild when several connected processes need to be redesigned together. Start with the smallest scope that solves the business problem.

Comparison table

Options, limits, and when each one fits

Compare the scope, tradeoffs, and situations each approach fits.

Option

Best for

Limitations

Choose when

Packaged automation

A stable, repeatable task with clear inputs, rules, and outcomes, such as copying an approved record or sending a reminder.

It follows the process you give it. It will not resolve unclear ownership or a changing workflow, and someone must monitor failures and maintain it.

The process is already understood, exceptions are limited, and an existing platform can handle the task safely.

CRM setup and configuration

Managing customer records, pipeline stages, task ownership, and follow-up in a CRM your team can adopt.

A CRM may not cover work that extends into delivery, production, billing, or specialized approvals. Poor data and unclear process rules can carry into the new setup.

The CRM can support the process, but fields, stages, permissions, automations, or staff practices need work.

Integration project

Moving agreed information between useful systems so staff do not have to enter or reconcile it by hand.

An integration connects systems; it does not make a poor process fit. Data ownership, duplicate handling, failures, and ongoing monitoring still need clear rules.

The systems each serve a purpose, the workflow is stable, and you know which system owns each important record.

Custom software

A focused application or workflow that existing products cannot represent well, such as a specialized intake, approval, or production process.

You take on design, build, hosting, support, security, and future maintenance decisions. Scope and acceptance criteria need to be explicit.

The workflow is important and specific enough that configuration or integration cannot meet the requirement at a reasonable cost.

Operating-system rebuild

Redesigning several connected processes, systems, roles, and information flows as one phased operating platform.

It requires leadership and staff time, careful migration, adoption planning, and a phased budget. It is usually too broad as a first build without discovery.

The same handoff, data, or ownership problems span multiple core processes and small fixes keep moving the problem elsewhere.

Decision criteria

How to choose the right approach

How much of the process is unclear?

If owners, handoffs, decisions, or exceptions are still disputed, map the work before buying or building. Automation is easiest to scope after the process is understood.

Can current systems support the desired workflow?

Check whether configuration or a reliable integration can close the gap. Custom software makes sense when the required behavior does not fit the tools you want to keep.

What will your team need to operate afterward?

Compare setup and build costs with licenses, support, monitoring, training, data cleanup, and staff ownership. Choose a scope the business can maintain and measure.

FAQ

Common questions

Should we automate first or map the workflow first?

Map the current work and agree on the desired result first. You may find that a procedure or CRM change solves the issue without a new automation.

When does an integration project become custom software?

An integration moves agreed data or events between systems. Custom software is useful when the workflow, rules, screens, or permissions themselves are not supported by the systems you plan to keep.

Do we need to replace our current systems for an operating-system rebuild?

Not necessarily. A rebuild can keep useful systems and connect them to new workflow software. The recommended sequence depends on the process, data, and limits of each system.

What does a Business OS Assessment cost?

The Business Ops Forge assessment is a fixed-fee $3,500 engagement covering one core process, up to three stakeholder interviews, and up to three principal systems or data sources. Production implementation is scoped and quoted separately.

Illustrative inquiry workflow redesign →Custom software development →Business OS Assessment →