Custom internal tools development
FRAI designs, builds, and operates internal software for SMEs that need reliable data, controlled permissions, structured approvals, and connected day-to-day work across their CRM, ERP, and existing systems.
01 — Documented result
The name is withheld to protect the confidentiality of the client’s internal processes.
Information had grown across large spreadsheets, OneDrive, WooCommerce orders, WhatsApp quote requests, and email communication. Free-text statuses made it difficult to maintain a consistent view of active customers, expiries, and pending work.
FRAI migrated approximately 9,000 records and structured the complete lifecycle, from quote and order through documents, follow-up, and expiry. The team can now see the complete pipeline, who performed each action, how long it took, and the economic result of the work.
The client attributes a 28% increase in closed sales during adoption to the new pipeline visibility and control. The owner and sales director validated the operational result: opportunities no longer disappear inside the pipeline. We do not publish a time-saving percentage because no comparable baseline was recorded.
First usable version in approximately 3 months · approximately €6,000 plus VAT, including analysis, design, development, migration, website integration, deployment, and training.
02 — Keep, buy, integrate, or build
Use the smallest solution that controls the process.
Best fitThe process is simple, stable, low-risk, and owned by one person.
Watch forDo not build without a real need.
Best fitAn existing product covers about 80% without creating parallel sheets.
Watch forCheck export, permissions, and integrations.
Best fitThe tools are useful, but data and handoffs remain fragmented.
Watch forMonitor failures, duplicates, and retries.
Best fitThe process is critical, multi-user, and needs its own rules or integrations.
Watch forBegin with one complete useful flow.
03 — Project fit
Company size matters less than operational load and the ability to make decisions about the process.
The process generates revenue or controls business-critical data.
Information is dispersed and the company already pays for several disconnected tools.
The process needs states, permissions, traceability, or integrations that are currently managed by hand.
A named owner can validate decisions and adoption.
The task is occasional, low-risk, and handled by one person.
Existing SaaS covers the need without parallel sheets or expensive workarounds.
The process changes constantly or no one can decide how it should work.
There is no budget to build and operate the system after launch.
It makes sense when bringing a revenue-generating or data-critical process under control outweighs the cost of continuing with disconnected tools. First phases start at approximately €6,000 plus VAT and managed operations at €450 per month plus VAT. The recommendation may still be to keep, buy, or integrate.
04 — Decision tool
Answer six questions for an immediate, practical recommendation.
How it works: choose an answer to continue. We do not store your data.
05 — Possible scope
The whole ecosystem rarely needs replacing. An internal tool can work as a back office, portal, extension, or operational layer between existing systems.
Back office, requests, and approvals
Customer or supplier portals
Quotes, orders, and tracking
Operational dashboards and reporting
Documents, inventory, and traceability
CRM, ERP, permissions, and useful AI
06 — What the client receives
The deliverable includes decisions, controls, and operating conditions. The interface is only one part.
Current map, target flow, and one complete outcome that users can validate.
Data model, migration, access, connections, and error handling.
Role-based interface, normal cases, exceptions, and controlled rollout.
Repository, access, deployment, backups, export, and transition conditions.
07 — Investment and timeline
You do not need a technical specification. FRAI defines the first useful flow, price, and timeline before work begins.
We review the process, data, users, integrations, and first-release scope as part of the commercial process.
As a reference, an internal tool may range from €6,000 to €40,000 plus VAT. Controlled production normally takes one to three months.
Larger systems are divided into phases with their own scope, price, and date; there is no generic upper limit.Includes Kubernetes infrastructure, security updates, incident handling, and the agreed backup and recovery scope. Improvements and broad migrations are quoted separately. Third-party licences, APIs, or services are the client’s responsibility when required; they are not normally needed.
08 — FRAI method
The work begins by understanding the operation and ends when the system has clear technical ownership.
We follow a request, order, incident, or case and identify waiting, duplication, and manual decisions.
We choose keep, buy, integrate, or build and fix the data, permissions, exceptions, and scope.
Users test real cases before more modules or automation are added.
FRAI can remain responsible for releases, monitoring, incidents, and evolution.
09 — After launch
FRAI can host, monitor, maintain, and improve the internal software. Incidents, backups, releases, integrations, and changes have a named owner.
Kubernetes hosting and infrastructure included
Security updates and incident handling
40 GB for backups: every 4 hours for one week and weekly for one month
Improvements, broad migrations, and third-party services quoted separately
10 — Ownership and exit
The proposal explicitly identifies what belongs to the client, which access is provided, what documentation is delivered, and how data can be exported or another provider can take over.
View the Trust Center →Business data remains the client’s property and is not used beyond the agreed operating purpose.
The proposal distinguishes project-specific code, reusable FRAI components, and third-party licences before work begins.
Repository, infrastructure, credentials, and account owners are documented in writing, with no critical dependence on personal accounts.
Export format, documentation, and provider-change conditions are defined in the proposal and contract.
11 — Frequently asked questions
Cost, timing, migration, ownership, hosting, integrations, and takeover.
First phases start at approximately €6,000 plus VAT. As a reference, an internal tool may range from €6,000 to €40,000 depending on processes, users, data, integrations, and scope. Larger systems are divided and priced in phases.
A first usable version can be available from one month after the project starts. Controlled production normally takes one to three months depending on scope, data, integrations, and validation speed.
We need to understand the process, who uses it, the data and documents involved, which systems must connect, and what the first version must achieve. This is normally defined in a two-hour meeting. The client must then provide the access, samples, and decisions needed to confirm scope.
Yes. FRAI can review, clean, structure, and migrate existing data. Before committing scope, we check volume, duplicates, inconsistent fields, related documents, and the rules required to preserve dependable information.
Business data remains the client’s property. The proposal distinguishes project-specific code, reusable FRAI components, and third-party licences, and defines repository, infrastructure, credential, documentation, and export access in writing.
FRAI can host it on managed Kubernetes infrastructure within the monthly operating scope. The proposal identifies infrastructure, accounts, access, backups, and responsibilities. Special infrastructure or third-party services are agreed separately when required.
Yes, after an audit of the code, data, hosting, dependencies, integrations, access, documentation, backups, and deployment process. FRAI accepts responsibility only when the system can be maintained and operated safely.
The design should define detection, retries, duplicate prevention, alerts, and correction. A critical integration should never fail silently.
12 — Related context
These pages explain how FRAI builds, audits, and operates the rest of a company’s software.
How FRAI builds business systems and remains responsible after launch.
02Build an internal tool connected to sales, customer, operational, and reporting data.
03Review an existing tool before maintaining, modernising, or taking control of it.
04Move a tool built by another provider under controlled technical responsibility.
05Monitoring, backups, updates, incidents, documentation, and continuous improvement.
First step
Show us how work happens today, where time is lost, and what must keep running. FRAI will help determine whether to keep, integrate, buy, or build.