A&A · DECISION GUIDE
Existing software vs a custom workflow: when branch figures disagree
Consistent definitions matter before dashboard appearance. If existing software supports the required definitions and operating process, adding a custom system needs a separate justification.
By A&A editorial · Updated
The decision in front of you
An owner combines sales, bookings and membership spreadsheets across locations. Monthly meetings are consumed by reconciling conflicting numbers instead of deciding what to change.
Compare the actual work
Typical scope to check in a proposal; individual providers may combine both approaches.
| Dimension | Existing software | Custom workflow |
|---|---|---|
| Staff effort | Configuration, migration and adapting work to the product. | Explain the current process, agree definitions, test outputs and review changes. |
| Output | Available features within the product’s supported configuration. | A system tailored to agreed reconciliation, reporting and integration work. |
| Source data | Check fields, exports, history and access controls. | Required data must be obtainable; development cannot recreate information that was never captured. |
| Implementation | Suitable existing integrations reduce construction, but fit must be demonstrated. | Custom matching and integrations are possible, with responsibility for later specification changes. |
| Operating owner | Internal configuration and input owners plus product support. | An internal owner of metric definitions plus a maintenance provider. |
| Contract checks | Plan limits, integrations, exports, cancellation and migration. | Integration scope, acceptance data, maintenance and data/code handover. |
A hypothetical example
Hypothetical example: location A reports revenue by booking date and location B by visit date. A new dashboard still misleads until that definition is aligned. Test existing software with consistently defined data, including cancellations. If it handles those cases, it is a candidate. If only customer-ID matching between two systems is missing, development can target that connection instead of replacing the entire dashboard.
What changes the business outcome
Measure report preparation and reconciliation effort, and whether decision-ready figures arrive on time. Visibility alone does not create profit. Define the action the figures should change, such as filling unused capacity or investigating customer retention.
Which conditions favor each option?
Existing software
Choose existing software when it handles relevant exceptions and the team can accept the process changes. Test more than ideal records during the trial.
Custom workflow
Consider custom work when valuable reconciliation or integration problems remain and their resolution justifies maintenance. A full replacement interface may be unnecessary.
Compare the cost structure
Software cost includes seats, locations, features, connections and migration. Custom cost includes requirements, development, maintenance and adapting to upstream changes. Compare the same operating period and include residual manual work and eventual data transfer.
Before signing
- Do all locations use the same dates and definitions for revenue and members?
- Did the trial include cancellations, duplicates and records crossing a month boundary?
- Can the company export the information it needs when the contract ends?
Source facts and A&A analysis
Anthropic’s engineering article recommends adding complexity only when necessary. Applying that principle to branch reporting is A&A analysis; the source does not evaluate branch-management products.
The comparison, conditional recommendations and scenarios are A&A’s analysis as a provider of advisory and development. They are not client results, independent vendor rankings or claims that the cited authors endorse A&A.