EFICSA
Nearshore Freshservice managed services for US and Canadian CIOs
Same Americas business day, a written scope, and AI governance you can describe without borrowing a certificate.
The cost that is not on the license
This guide is for a CIO or VP of technology in the United States or Canada who is tired of a Freshservice program that only moves when a coastal consultancy is awake. EFICSA is a Freshworks Services Partner, Sales Consultant and Authorized Reseller with offices in Guatemala City and Panama City. The work happens in the Americas time zone. A question asked in the morning does not wait for the next business day on another coast.
Nearshore, in the way EFICSA uses the word, means the engineering team sits in Guatemala and Panama, works the same business day as a large part of the United States and Canada, and stays on the instance after go-live. It does not mean a ticket queue in a far time zone with a local accent on the status call. The people who configure the catalog are the people who answer when a workflow breaks.
Cost is a commercial argument, not a measured benchmark. EFICSA's position is that a closed Freshservice scope, delivered in weeks and followed by Care Plus, lands at a fraction of the cost of a large United States consultancy engaged for a multi-month program. That is how EFICSA frames the procurement conversation. It is not an analyst study, and it is not a promise that your number will match a percentage. The comparable items are calendar, the number of dedicated roles, and whether the invoice can be explained.
Care Plus is the operating model after go-live: 16 hours a month of senior engineering for USD 2,000. The hours cover workflows, the REST API, webhooks to SAP, Oracle, Microsoft Entra ID or a banking core, and the Device42 CMDB when asset discovery is in scope. Buying or moving annual licenses with EFICSA includes 30 to 60 days of those hours at no cost, so the first real tickets shape the build instead of a slide.
ITIL shows up as concrete objects. Incidents restore service. Problems look for cause. Changes are approved before production moves. The catalog publishes what HR, Finance, Legal and IT are actually allowed to request. Employee onboarding is a catalog item. EFICSA does not start by copying every module of a heavier suite. The first six to ten weeks have a written list. What is not on the list is not promised.
A commercial argument about shape, not a benchmark.
| Piece | EFICSA nearshore | A long US consultancy program |
|---|---|---|
| Calendar | Weeks with a closed scope | Months before the first service |
| After go-live | 16 hours a month | Another statement of work |
| AI | Approach aligned to ISO/IEC 42001 | Often an annex with no owner |
What is being compared
Device42 is added when a hand-maintained CMDB has already gone stale. It discovers assets and dependencies and links them to the ticket. FireHydrant covers the critical incident: on-call, a Slack or Teams war room, and a written root cause. Neither tool replaces the everyday desk. ServiceNow can do more of this inside one platform, usually with more program months. Jira Service Management is comfortable for engineering teams and thin when the whole company expects a catalog. EFICSA states, as a commercial claim, that total cost of operation can land up to 40% lower than a heavier platform for a mid-market scope. Read that as a claim, not as an audit.
AI governance is part of the managed service, not a footnote. Freddy AI Agent, Copilot and Insights are used with an approach aligned to ISO/IEC 42001. There is an owner, a scope of what the assistant may say, and a review when an answer was wrong. EFICSA does not write that the organization is ISO certified. A CIO should be able to tell an examiner the difference. Payment data, full identity numbers and decisions that only a person may take stay outside the automatic scope.
What a United States or Canadian buyer should ask on the first call. Who signs, whether the invoice should be in USD, which product is in the first weeks, and whether an instance already exists. EFICSA bills in GTQ or USD from Guatemala or Panama. MXN, COP and BRL facilities exist for groups that also operate in those markets. An international card is the path EFICSA is trying to replace, because the withholding and the unexplained charge show up after the books are closed.
How the week is structured. One working session fits inside the alignment hours. The build is reviewed against the written scope, not against a growing wishlist. A production change waits for the change practice you asked to have. If the wishlist grows, it is scheduled into a later month of Care Plus or explicitly added to the implementation. Silent scope is how a weeks-long project becomes a quarter.
Security and identity. Microsoft Entra ID, or the directory you already run, decides who sees Finance and who sees only their queue. Shared logins are treated as an incident waiting for a date, not as a shortcut. EFICSA would rather spend hours on identity in week two than explain a leaked queue in month four.
How it runs afterward
What nearshore is not. It is not a promise to undercut every domestic firm on an open-ended staff-augmentation contract. It is not overnight coverage dressed up as a follow-the-sun slogan unless the SLA you bought actually says that. Care Plus publishes first-response targets on the service page. Those clocks are first response, not a promise of resolution, and they should be read that way in a contract.
A practical test before you sign. Pick one painful service — laptop request, access removal, or a vendor onboarding — and ask EFICSA to show it as a catalog item, with the approval and the identity check, in the Americas business day. If that demonstration needs a six-month discovery, the scope is not the scope of this guide. If it can be drawn in the first conversations, the weeks-long plan is real.
The pages that carry the offer are the English Freshservice page, the Care Plus page and the partner page. This article is the argument for a CIO who has to explain, internally, why the engineering team is in Guatemala and Panama and why that is a feature of the operating model: same day, a written scope, a local invoice, and an AI practice that can be described without borrowing a certificate the company does not hold.
A staffing comparison a CIO can actually take upstairs. A domestic program often prices a project manager, a platform architect and two configurators for several months before the first catalog item is live. EFICSA prices a closed list of services, a go-live counted in weeks, and then 16 hours a month. The fraction-of-cost argument lives in that shape: fewer roles, a shorter calendar, one invoice. If your scope truly needs the larger program, say so and do not force it into Care Plus. Pretending a banking-core integration is a two-hour task helps nobody.
What the 16 hours are not. They are not an unlimited developer on call. They are not a help desk for every employee laptop. They are senior Freshworks engineering: workflows, APIs, webhooks, the CMDB link, and the root cause of a repeated incident. Overflow is a conversation, priced apart, not a surprise on the invoice. The USD 120 conversation for hours beyond the 16 belongs in the proposal, in writing.
What is not promised
Language. The operating language of a US or Canadian stakeholder can be English on the status call and Spanish with the team that will click the catalog. EFICSA works in both, and in Portuguese when the same group also runs Brazil. The catalog labels should be the words employees already use. A perfect ITIL noun that nobody types is a failed form.
Evidence a board will accept. Keep the commercial claims labeled as claims. «Up to 40% lower TCO» and «a fraction of a US consultancy» are how EFICSA sells the shape of the program. They are not a measured benchmark and they should not be pasted into a filing as if they were. What you can attach is the written scope, the invoice currency, the names of the people in the weekly session, and the list of what Freddy is allowed to say.
Failure modes EFICSA would rather name now. The internal team never shows up to the weekly session, so hours are spent guessing. The wishlist doubles after week two and nobody updates the list. Entra ID access is promised by security and arrives in month three. Each of those is a calendar problem, not a product defect. The remedy is to stop building until the missing input arrives, and to write that pause down.
A 90-day picture. Days 1 to 10: catalog of the painful services, groups, SLA, identity. Days 11 to 30: the first integration that removes a spreadsheet, and a rehearsal of one critical incident with FireHydrant if that tool is in scope. Days 31 to 60: the included Care Plus window, using real tickets. Day 61: a decision, with evidence, on whether the USD 2,000 month continues. That picture is the one EFICSA will put next to a multi-month domestic proposal so the comparison is about calendar and roles, not about adjectives.
If you want the engineering relationship without buying a story about certificates, start with the English Care Plus page and the Freshservice page. Bring the service that hurts. Leave the hundred-page RFP for the scope that truly needs it.
Continue on the same-language pages: See Freshservice · See Care Plus · See the partner page.
FAQ
Is the cost comparison a benchmark?
No. A fraction of a large US consultancy's program cost is EFICSA's commercial argument about calendar and roles, not a measured study.
Are you ISO 42001 certified on this page?
No. Freddy is used with an approach aligned to ISO/IEC 42001. That is not a certification claim.
What does Care Plus include?
Sixteen senior hours a month for USD 2,000: workflows, APIs, webhooks and root cause, in the Americas time zone.