Review path
CodeTechnical software review
Review existing software before maintaining or rebuilding it
FRAI reviews existing software, code, hosting, integrations, data, and documentation before deciding whether it can be maintained, fixed, migrated, or rebuilt.
Review path
HostingReview path
DataReview path
Risks01
When a technical review makes sense
This is for companies that already have software in production, but no longer know whether it can be trusted, changed, or maintained without creating new risk.
01
The old team is gone
The code exists, but context is missing, documentation is weak, access is unclear, and there is no safe release process.
02
The app works, but nobody wants to touch it
Dependencies are old, integrations are fragile, hosting is unclear, and every change feels risky.
03
Maintenance is being discussed too late
The company asks for maintenance, but the first question is whether the system can be recovered and controlled.
04
CRM migration or replacement is being considered
Before moving away from HubSpot, Salesforce, ActiveCampaign, spreadsheets, or an old custom CRM, the workflow, data, reports, automations, and integrations need to be checked.
02
What FRAI checks
The review is not a long report with no next step. It is used to decide what can be kept, what needs fixing, what should move, and what should be rebuilt.
- 01
Code, branches, dependencies, build process, and release process
- 02
Hosting, domains, SSL, credentials, logs, alerts, backups, and recovery
- 03
Database structure, data flows, integrations, APIs, forms, and automations
- 04
CRM fields, objects, permissions, reports, automations, exports, duplicates, and migration risk
- 05
Security risks, access control, exposed secrets, outdated packages, and missing controls
- 06
Documentation, release process, ownership gaps, and maintenance workload
- 07
What can be kept, what should be fixed, and what should be rebuilt
03
Possible outcomes
After the review, FRAI gives a concrete path: maintain the system, fix it first, or rebuild the parts that are too risky.
01
Maintain
The system is clear enough to bring under FRAI control and start maintenance.
02
Fix or migrate
The system can be recovered, but first needs work on dependencies, hosting, release process, documentation, or integrations.
03
CRM migration plan
The current CRM can be cleaned, connected, built around, or replaced with a managed custom CRM based on workflow fit and data quality.
04
Rebuild
The codebase is too risky, undocumented, insecure, or blocked by old choices. The safer path is to rebuild the critical flows.
04 — The boundary
First understand the system. Then choose the right next step.
FRAI reviews existing software to decide whether it can be operated safely. We do not accept blind handovers of third-party repositories to publish them without control. If FRAI cannot understand and control the system, we will not maintain it as it is.
FRAI does not take a third-party repository and publish it blindly. We first check whether the system can be understood, controlled, and operated safely.
05
Questions before the review
These questions usually come up when a company has an old system, an external repository, or a software supplier that is no longer available.
Can FRAI review an old software repository?
Yes. FRAI can review the code, dependencies, release process, hosting, integrations, data flows, documentation, and security risks before deciding the next step.
Can FRAI maintain software after the review?
Yes, if the review shows that the system can be brought under FRAI technical control. If not, the first step is stabilization, migration, or rebuilding the parts that need it.
Does FRAI publish third-party repositories without changes?
No. Publishing a third-party repository blindly is too risky. FRAI only publishes and maintains software it understands and can operate safely.
What if the software cannot be recovered?
FRAI will say so. If the repository is too risky or broken, the next step is to rebuild or migrate the critical flows instead of maintaining a weak base.
How much does a technical software review cost?
It depends on system size, code access, hosting, integrations, data, and documentation. FRAI defines the review scope before starting.
Can FRAI audit a CRM before migration?
Yes. FRAI can review HubSpot, Salesforce, ActiveCampaign, spreadsheets, or an old custom CRM before deciding whether to stay, build around it, migrate, or replace it.