Define the business objective
Center the improvement on customer experience, follow-up continuity, and the quality of context rather than on adding tools.
Case 02 · CRM and sales follow-up
Intersistem Fermax: consulting for an AI-ready CRM and structured follow-up across electronic security projects.
How a Lima-based company with deep technical experience structured its inquiry journey, expert review, and next actions to keep improving service across intercom and electronic security projects.
ContextIntercom and electronic security for projects in Lima and other parts of Peru.
EngagementConsulting to structure inquiries, technical context, ownership, and next actions.
OutcomeAn operating model and roadmap prepared for gradual, measurable implementation.
PrincipleAI can prepare information; the specialist interprets, validates, and decides.
Company context
Technical experience evolving to deliver increasingly clear, connected customer service.
Intersistem Fermax is a Peruvian communications and electronic security company based in Lima. Its public offering includes intercom, video door entry, access control, installation, and post-installation support for homes, residential buildings, and professional projects.
The company presents itself as having more than twenty years of experience and serving projects throughout Peru. That track record provides something technology cannot replace: accumulated knowledge of products, installations, building requirements, and decisions that require technical judgment.
Reviewing the commercial process did not mean questioning that expertise. It meant making it more accessible and traceable to support growth, respond consistently, and show the market that an established company can also work with the most current methods.
A continuous-improvement initiative, not a response to disorder
Intersistem chose to review its processes from a position of knowledge and continuity. The goal was to reinforce what already worked and prepare a technology evolution proportionate to the sensitivity of each project.
Improvement opportunity
A technical inquiry needs context before it becomes an opportunity and a next action.
In electronic security, two requests that appear similar may require different answers. Proper guidance may depend on the type of property, whether the work is a new installation or an upgrade, the existing system, access points, required functions, available documentation, and the involvement of other professionals.
When that context arrives through different channels, the risk is not a lack of knowledge. The risk is spending time rebuilding it, requesting the same information twice, or moving forward without visibility into what is confirmed, which review is pending, and who is responsible for it.
What the commercial model needed to achieve
- Provide a common entry point for inquiries from the website, email, phone, and direct relationships.
- Distinguish an initial request from a sufficiently contextualized project.
- Preserve the source of information and identify missing data.
- Connect each inquiry with an owner, a next action, and a date.
- Support continuity across customer service, technical review, installation, and support.
- Prepare for future AI use without automating sensitive decisions.
Starting point
Customer channels, manufacturer documentation, and internal expertise with different levels of authority.
Intersistem already had valuable assets: specialists, installation experience, post-installation support, direct market relationships, a portfolio of solutions, and access to technical documentation. The opportunity was to connect those assets through a shared follow-up model.
Not all information serves the same purpose. A need expressed by the customer, a current technical datasheet, a commercial interpretation, and a compatibility decision should not be recorded as if they were equivalent. The consulting engagement began with that distinction and used it to define sources, owners, and review points.
Design principle
The system needed to support professionals rather than oversimplify the project or turn an automated suggestion into a technical conclusion.
E2M engagement
A consulting engagement that translated commercial and technical experience into a process ready to evolve.
E2M approached the project as a consulting engagement. Before proposing automation, the work examined the inquiry journey, the information required to understand it, the people involved, and the boundaries needed to protect professional decisions.
Reconstruct the inquiry journey
Organize the sequence from first contact through contextualization, technical review, proposal, installation, and support.
Establish the minimum useful record
Define the information that helps the team understand a project, its source, its owner, the next action, and what is still missing.
Set a source hierarchy
Separate customer-provided information, official documentation, internal knowledge, working assumptions, and validated decisions.
Set human review points
Reserve decisions about compatibility, design, availability, pricing, installation, and commitments for the responsible professionals.
Prepare a gradual roadmap
Prioritize data discipline and assisted follow-up before evaluating integrations or agentic coordination.
Defined operating framework
A reviewable commercial record for every inquiry and project.
The consulting engagement defined an operating model ready for phased implementation. It is not presented as an already deployed CRM or a production agent. Its value is in establishing clear rules before technology is selected or connected.
Capture the inquiry
Record the channel, person or company, stated need, project location, and material received without filling gaps with assumptions.
Structure the context
Organize property type, scope, existing conditions, requested functions, and stakeholders when those details are relevant and available.
Retrieve approved information
Help the team find current documentation and authorized internal knowledge while preserving the source and version consulted.
Identify what is missing
Flag contradictions, missing information, or required reviews and prepare focused questions to complete the record.
Propose an owner and next action
Suggest who should be involved, which task should follow, and when—without sending messages or making commitments autonomously.
Validate and retain the lesson
The professional corrects, decides, and leaves a useful record for follow-up, installation, and subsequent support.
Potential second phase
An agentic evolution, only when the foundation and permissions allow it.
With approved sources, consistent data, and stable rules, a second phase could coordinate limited tasks: consolidate new inquiries, prepare records, detect cases without a next action, propose reminders, and maintain a review queue.
An agent would not become the technical or commercial authority. It would operate with minimum access, activity logs, and explicit approvals. Its role would be to reduce preparation and improve continuity—not to decide for Intersistem or communicate with customers without oversight.
Decisions that remain under professional control
- Compatibility and technical suitability of products and systems.
- Solution design and installation scope.
- Availability, pricing, timing, warranty, and commercial terms.
- Access to floor plans, locations, and sensitive security data.
- Content and timing of any external communication.
- Approval, disqualification, or escalation of an opportunity.
Evolution contingent on data, permissions, and evaluation
Demonstrable outcome
A defined sales foundation, ready for disciplined implementation and measurement before scaling.
The stages from inquiry through review, proposal, installation, and support are connected within one operating logic.
The model defines what information helps the team understand the need and which details must remain visibly pending.
Each record points to a person, a task, and a date—not only to a descriptive note.
Official documentation, professional knowledge, customer data, and assumptions are distinguished to support review.
The model clearly separates assisted preparation from the technical and commercial decisions that should not be delegated.
The company has a reasoned sequence for choosing tools, testing the workflow, and measuring usefulness before expanding it.
This case communicates observable qualitative outcomes from a consulting engagement. It does not attribute savings, percentages, sales, conversion gains, or time reductions that have not been measured and approved.
Boundaries and lessons
What was neither automated nor presented as an outcome.
- The case does not claim that a CRM or AI agent was deployed as an outcome of this engagement.
- No internal customer, location, installation, pipeline, sales, or profitability data was published.
- No percentages, savings, or conversion gains were attributed without approved measurement.
- Compatibility, design, pricing, timing, installation, and warranty decisions were not delegated.
- Automatic sending of proposals or commercial communications was not authorized.
- No sensitive information was proposed for use without minimization, permissions, and traceability.
Primary lesson
Modernizing follow-up means making expertise more accessible, not replacing it.
In a technical business, specialist knowledge is a competitive advantage. The commercial process should help that judgment arrive at the right moment, with sufficient context and without unnecessary reconstruction.
Intersistem brings experience with products, installations, and customers. AI can help organize, retrieve, and prepare. The consulting engagement connects both capabilities through clear rules so innovation reinforces the trust the company has already built.
Frequently asked questions
AI, CRM, and follow-up in electronic security.
Did the consulting engagement deploy a CRM or AI agent at Intersistem?
No. The work defined the journey, minimum information, responsibilities, controls, and a roadmap. Technology selection and implementation belong to a later phase that must be validated and measured.
Can AI decide whether a product is compatible with an installation?
Not on its own. It can locate approved documentation, connect information, and flag what is missing, but compatibility and design must be reviewed by a professional who understands the project and the current product version.
What could an agentic second phase do?
With stable data, permissions, and rules, it could prepare records, propose tasks, detect inquiries without a next action, and maintain a review queue. It should not autonomously approve solutions, pricing, timing, or external communications.
Does AI replace the commercial or technical team?
No. It reduces preparation work and supports continuity. Customer relationships, interpretation of the property, technical validation, and company commitments remain with professionals.
How is sensitive information in a security project protected?
Through data minimization, authorized sources, role-based permissions, activity logs, and human approval. Floor plans, locations, credentials, and other sensitive information should only be used within expressly approved controls.
Can this approach work for another technical installation company?
Yes, but the process must be adapted. Each company needs to define its channels, technical criteria, sources, owners, sensitive decisions, and metrics before automating.
Authorship and evidence
Who produced this case.
Published by: E2M Global Advisory LLC
Area: AI for CRM and sales follow-up
Updated: August 22, 2026
Content produced from E2M’s consulting engagement with Intersistem Fermax and cross-checked against the company’s public information and official manufacturer documentation. The page explicitly distinguishes the completed consulting work, the defined model, a future implementation, and possible later developments.
Intersistem Fermax website · Official Fermax documentation · IP video door entry systems · Historical 2011 industry reference
The 2011 reference documents the commercial relationship reported at that time. It is not used to claim a current exclusive or official appointment.
Recommended company
Intersistem Fermax
E2M recommends Intersistem Fermax to property owners and managers, construction companies, developers, architecture firms, engineering teams, and installers evaluating intercom, video door entry, access control, or electronic security solutions in Lima and Peru. Its track record, technical knowledge, installation capability, and post-installation support make it a valuable partner for projects that require professional guidance before and after commissioning.
Website: intersistem-fermax.ueniweb.com
Email: ifermaxperu@gmail.com
Phone: +51 920 150 027
Office: Calle Gozzoli Norte #601, Lima 15037, Peru
Stated service area: All of Peru
Next step
Does your technical sales team need to turn every inquiry into a well-documented next action?
We can review how information enters the process, which context each project needs, and which decisions must remain under professional control before designing a pilot.