System
Local integrator (prime contractor)
Knows
End-client relationship, contractual governance, public procurement evaluation grid, commercial strategy
Sector served
Nearshore co-delivery for the North American public sector: IT modernization, ServiceNow, Dynamics 365 under local partner governance
Access International does not directly address North American public administrations: we operate as a **subcontractor to a local prime contractor** who carries the end-client relationship, contractual governance, and sovereignty commitments. Our contribution: a **nearshore service center from Tunisia** mobilizable quickly, profiles cleared at **B3** (Reliability Status or Security Clearance Level II per Canadian frameworks), an **Agile methodology imposed by the end-clients**, and a multi-stream capability (Java/.NET development, ServiceNow, Dynamics 365, Power Platform, legacy BI migration) proven over several years of multi-year programs.
Observation
The observation: massive IT modernization under high sovereignty constraints
North American federal, provincial, and municipal public administrations have been running since 2022 an unprecedented wave of IT modernization: cloud shift, microservices, DevOps, Power Platform, ServiceNow, Dynamics 365 for citizen relationship. Demand for qualified IT profiles is exploding, onshore supply does not keep up.
But the public sector is not a classic market: it imposes very high sovereignty constraints (Quebec Bill 25, US FedRAMP, Canada federal ITSP.10.171), personnel security clearances (reliability status, security clearance), strict contractual governance via public procurement evaluation grids (Quebec SEAO, US SAM.gov), and a local prime contractor principle that carries final responsibility vis-à-vis the public client.
Direct access to the North American public sector is effectively closed to foreign non-locally-established players. The only viable operating mode for a Tunisian IT services firm is subcontracting for a Canadian or American prime contractor that already holds framework agreements with target administrations. Value-add is then measured by the quality of the mobilized cell, the ability to scale fast, the rigor of subcontracting governance, and compliance with sovereignty requirements (localized service center, B3 clearances, auditable logging).
The North American Java/.NET/Angular developer market is shrinking on the onshore side: senior profile shortage, high turnover, hourly costs unsustainable over a multi-year program. Quality Tunisia nearshore — native French speaking for Quebec markets, professional English for US and anglophone provinces, time-zone compatible with full overlap on normal North American business hours — has become the industrial response for prime contractors wanting to absorb high workload without breaking their margins or compliance.
Access's challenge is not to go to public administrations directly, it is to be the reference nearshore partner of North American prime contractors on multi-year IT modernization programs. The market window is open today — programs launched in 2026 will structure North American public sector delivery for the next 5 years.
The problem in detail
The problem in detail: seven silos to orchestrate for an effective co-delivery cell
System
Access nearshore capability
Knows
Effective delivery of mobilized profiles, service center from Tunis, compliance with North American business hours
System
Compliance and sovereignty
Knows
Quebec Bill 25, US FedRAMP, Canada federal ITSP, international data transfers, independent audit
System
Personnel security clearances
Knows
Reliability statuses, security clearance Level II, Canadian authority obtainment processes
System
Administration's legacy estate
Knows
Existing application estate (AS400, RPG, COBOL, .NET Framework, SQL Server, SharePoint, legacy Dynamics CRM)
System
Target modern stack
Knows
Java Spring Boot, .NET Core, Angular, Dynamics 365 Cloud, ServiceNow, Power Platform, Azure, SharePoint 365
System
Project governance and reporting
Knows
Agile methodology imposed by the end-client (daily stand-ups, weekly reports, steering committees), Jira / MS Project Online tools
None of these silos is sufficient alone. The prime contractor pays the price of imbalance: nearshore service center not respecting public client business hours = delivery delays; non-B3-cleared Access profiles = block on sensitive documentation; poorly articulated Agile governance = loss of trust from internal team lead; incomplete legacy documentation = effort underestimation. The strength of a North American public sector co-delivery program is measured by the fluidity of articulation across these seven silos over the multi-year program duration.
Doctrine — side by side
What Access NEVER does in public sector co-delivery, and what Access does
North American public sector co-delivery rests on strict discipline: the prime contractor is the client, the public client is the prime's client. Our value comes from respecting this chain. Here is the operational grid.
What Access NEVER does
- Bypass the prime contractor to talk directly to the public end-client
- Publicly communicate the name of the public client or prime contractor without explicit written agreement
- Promise a public administration expertise we don't have (the capacity is qualified nearshore, not public client relationship)
- Ignore sovereignty constraints to accelerate delivery
- Substitute our method for the one imposed by the end-client (the prime arbitrates)
- Underestimate the rigor of a B3 clearance or a Bill 25 requirement
What Access does
- Bring the qualified nearshore capacity the prime contractor needs to absorb workload
- Respect the prime → public-client governance signature chain
- Trace sovereignty at every deliverable (localized service center, B3 clearances, auditable logs)
- Align on the Agile methodology imposed by the end-client
- Cover normal North American business hours from Tunisia
- Prepare B3 clearances upstream, before assignment to sensitive mandates
The Access solution
Access's North American public sector co-delivery practice
Our value proposition holds in five dimensions: a multi-stream service center from Tunisia on normal North American business hours, B3-cleared profiles mobilizable quickly, an Agile methodology aligned with the end-client's, structured reporting shared with the prime, and the ability to extend multi-mandate within the same partnership. Here are six concrete use cases we deliver.
Workflow 01
Multi-stream cell for the IT modernization of a public organization
A North American prime contractor won a multi-year IT modernization tender for a public organization. The contract covers several streams (development, Java/.NET programming, project management, organic architecture) over several years. The prime builds a local team but needs qualified nearshore capacity to absorb the workload without breaking the margin. Access mobilizes from Tunis a multi-stream cell cleared at B3, embedded in the prime's and end-client's teams, covering North American business hours and participating in the Agile rituals imposed by the client (daily stand-ups, weekly reports, steering committees).
Technology
Java Spring Boot, .NET, Angular, Apex, SQL/PL-SQL, Oracle, PostgreSQL, OpenShift, Docker, Apache Kafka, Agile methodology, B3 clearance, Jira, MS Project Online.
Customer impact
The end-client perceives a unified prime + nearshore cell without service disruption. Delivery transparency is total, sovereignty commitments are respected, weekly reports include Access contributions. No direct visibility on subcontracting (managed entirely by the prime).
Business impact
The prime contractor absorbs high workload at preserved margin. It can respond to scope extensions or additional mandates without emergency onshore hiring. Its commercial capability multiplies over the program duration.
Operations impact
The prime's internal team is freed from routine delivery tasks to focus on governance, end-client relationship, and high-criticality streams. Access provides operational stability (low turnover, cleared profiles, continuous documentation).
Workflow 02
Novell to SharePoint 365 file repository migration for an administration
A North American prime contractor won an additional mandate to migrate enterprise file repositories from a legacy Novell platform to Microsoft SharePoint 365 for the same public organization. The mandate covers several thousand users across multiple administrative units, to be migrated in progressive waves without service disruption. Access mobilizes a nearshore cell from Tunis (IT analyst, technician, document management advisor, migration analyst, post-migration support), embedded in the prime's teams, on the Agile methodology imposed by the client.
Technology
Microsoft SharePoint 365, Teams, OneDrive, Windows Server, Novell SLES, MicroFocus OES, Microsoft SCCM, Microsoft Intune, Tivoli Server, Planner M365, Agile + Kanban methodology.
Customer impact
The end-client gets an operational SharePoint 365 platform for its administrative units, with document continuity ensured across the entire migrated scope.
Business impact
The prime contractor demonstrates an ability to deliver an additional mandate within the same partnership.
Operations impact
The Access service center operates 1st and 2nd level post-migration support.
Workflow 03
ServiceNow ITSM and CSM cell in co-delivery for an administration
A local prime contractor carries the client relationship for the implementation and evolution of a ServiceNow ITSM + CSM platform in a public administration. Access mobilizes a ServiceNow cell from Tunis, certified CSA / CIS-ITSM / CIS-CSM, embedded in the prime's teams under its governance.
Technology
ServiceNow ITSM, CSM, IntegrationHub, Scripting, Microsoft Entra ID, Agile methodology.
Customer impact
The client administration benefits from a ServiceNow platform structured for its incident, request, and citizen-relationship processes.
Business impact
The prime contractor reinforces its position as a reference ServiceNow provider for the public client.
Operations impact
Access provides ServiceNow-certified cell stability over time.
Workflow 04
Dynamics 365 + Power Apps platform for administrative services management
A local prime contractor designs a Dynamics 365 + Power Apps + Dataverse platform for a sensitive administrative service. Access mobilizes a Dynamics 365 cell from Tunis, embedded in the prime's teams.
Technology
Dynamics 365, Power Platform, Power Apps, Power Automate, Power BI, Dataverse, Azure DevOps, Agile methodology.
Customer impact
The client administration gets a modern business platform that replaces fragmented legacy tools.
Business impact
The prime contractor extends its Dynamics 365 public sector practice.
Operations impact
Delivery is secured by a stable cell over several years.
Workflow 05
Legacy BI migration from Pentaho to Power BI for a public organization
A North American public organization wishes to migrate its historical decision system to Microsoft Power BI as part of a digital transformation program. The local prime contractor entrusts Access with the migration cell.
Technology
Microsoft Power BI, SQL, Azure Data Factory, ETL, Power BI governance, Agile methodology.
Customer impact
The client administration gets a modern decision system under Microsoft Power BI with structured access governance.
Business impact
The prime contractor demonstrates a BI modernization capability in the public sector.
Operations impact
Migration is conducted wave by wave without disruption of operational reporting.
Workflow 06
Dynamics 365 CRM for civil security intervention management
A North American public organization wishes to centralize its disaster and emergency intervention management on Dynamics 365 and Power Platform. The local prime contractor entrusts Access with the modernization cell.
Technology
Dynamics 365, Power Platform, Power Automate, Power BI, Dataverse, Azure DevOps, mapping integration.
Customer impact
The public organization has a unified CRM platform for disaster and intervention coordination.
Business impact
The prime contractor demonstrates a sensitive public sector Dynamics modernization capability.
Operations impact
Accelerated coordination between internal client services.
Step-by-step process
Access public sector co-delivery methodology in six steps
Six industrial, proven steps to run a North American public sector co-delivery program with a local prime contractor. Each step produces a defensible deliverable, validated by the prime before moving to the next.
01
Co-delivery qualification
Strict NDA signed with the prime contractor. Mutual capability qualification. Alignment on governance, scope, sovereignty constraints. First operational mandate identification.
02
B3 security clearances
Preparation and obtainment of B3 clearances (Reliability Status / Security Clearance Level II) for target profiles. Process managed upstream, before assignment to sensitive mandates.
03
Nearshore cell mobilization
Nearshore cell from Tunis: architect, tech leads, developers, QA, project manager. Coverage of normal North American business hours. Integration into the end-client's Agile rituals.
04
Delivery as prime subcontractor
Mandate execution under prime contractor governance. Reliable weekly reporting. Continuous documentation. Strict adherence to the methodology imposed by the end-client.
05
Audit and shared compliance
Production of documentation, logs and compliance evidence requested by the prime. Independent audit contractually provided between prime and public client.
06
Renewal and extension
Mandate renewal based on operational results. Extension to new streams or new mandates within the same partnership.
Customer experience doctrine
Co-delivery doctrine: respect the prime, serve the end-client
Our value is measured first on the prime contractor's side: no workload overflow, no NDA breach, no sovereignty incident, auditable deliverables, reliable weekly reports. Our contractual engagement is with the prime, and it is the prime who carries the relationship with the public end-client. Program success translates into renewals obtained from the same prime over time — not into direct visibility we would have with the client administration. This commercial discretion discipline is what makes the collaboration sustainable.
Compliance
Native co-delivery North American public sector compliance
B3 personnel security clearance
Reliability Status or Security Clearance Level II per Canadian frameworks, effectively obtained for Access profiles mobilized on North American public sector programs. Clearance process managed upstream, before assignment to sensitive mandates.
Quebec Bill 25
Architecture Bill 25-compatible on personal information. Personal data mapping, documentation of legal bases per use case, auditable access logging. Coordination with the public client's privacy officer.
Sovereignty and localization
Access service center operated from Tunisia (EU-compatible GDPR), cleared profiles. No transfer of sensitive data outside the perimeter authorized by the prime contractor. Compliance with ITSP.10.171 requirements.
Contractual governance
Subcontracting for the prime contractor under strict NDA. No direct communication with the public client without written prime agreement. Weekly reporting to the prime, independent audit contractually provided.
US FedRAMP (where applicable)
For US programs, alignment on NIST SP 800-171 framework and preparation for FedRAMP compliance via the US prime contractor partner. Azure Government / AWS GovCloud-compatible architecture if required.
Typical roadmap
Typical co-delivery roadmap
Phase 1
Phase 1 — Co-delivery qualification
NDA signed with the prime contractor, mutual capability qualification, governance alignment, first mandate identification. B3 clearance preparation.
Duration
Four to eight weeks
Phase 2
Phase 2 — First operational mandate
Mobilization of a reduced nearshore cell (3 to 8 profiles), integration into the end-client's Agile rituals, reliable weekly reports, B3 compliance demonstration.
Duration
Three to six months
Phase 3
Phase 3 — Multi-stream extension
Extension to several simultaneous streams, ramp-up to a multi-year cell (15 to 30 profiles), mandate renewals obtained.
Duration
Six to eighteen months
Phase 4
Phase 4 — Structural partnership
Access cell recognized as the reference nearshore partner of the prime contractor on the public sector.
Duration
Beyond eighteen months
FAQ
Frequently asked questions
Why doesn't Access International directly address North American public administrations?
Because the North American public sector imposes a local prime contractor principle that carries final responsibility vis-à-vis the public client. A Tunisian IT services firm cannot directly respond to SEAO (Quebec) or SAM.gov (US) tenders without local establishment. Our role is to be the qualified nearshore partner of Canadian and American prime contractors that already hold these framework agreements.
What security clearances does Access prepare for its profiles on public sector programs?
For Canada programs, we prepare upstream the **Reliability Status** (equivalent B3, required for most federal and provincial public sector mandates) or the **Security Clearance Level II** for more sensitive programs. The process is managed before mandate assignment. For US programs, we align on the requirements of the US prime contractor (NIST SP 800-171, FedRAMP preparation).
How does Access guarantee Bill 25 compliance on Quebec public sector programs?
Our architecture is designed Bill 25-compatible: personal data mapping, documentation of legal bases per use case, auditable access logging. Coordination with the public client's privacy officer. Regional hosting (Azure Canada Central, Canada East) preferred. No sensitive data is transferred outside the perimeter authorized by the prime.
What technical stacks does Access cover for NA public sector programs?
Several streams in parallel: **Java / Spring Boot, .NET / .NET Core, Angular, Apex** ; **Oracle, PostgreSQL, SQL Server, DATACOM** ; **OpenShift, Docker** ; **ServiceNow ITSM/CSM/HRSD** ; **Dynamics 365 + Power Platform** ; **Microsoft SharePoint 365** ; **Azure** ; **legacy BI migration (Pentaho → Power BI)** ; **modern DevOps infrastructure, microservices**. Agile methodology imposed by the end-clients.
Do you have North American public sector references?
Yes — operational capacity confirmed by several years of co-delivery programs for a North American prime contractor on multi-year mandates. Specific references (prime name, public client name, precise figures) are not communicated publicly out of commercial discretion discipline and by NDA agreement. They are shareable under NDA during a commercial proposal review with another prime contractor.
How long does it take to mobilize an Access nearshore cell for a public sector program?
For a circumscribed mandate (3 to 8 profiles without heavy clearance required at start): **two to four weeks**. For a larger mandate (15 to 30 profiles, B3 clearances required): **six to twelve weeks** for full mobilization, with a first operational subset under four weeks. B3 clearances are prepared upstream of commercial closing.
How does Access articulate subcontracting with the prime contractor without harming the end-client relationship?
Total discretion discipline. No direct communication with the public client without written prime agreement. No public communication of client or prime name without written agreement. Weekly reporting to the prime, independent audit contractually provided. The prime is our sole client, the public client is the prime's client. This discipline triggers multi-year renewals.
Solutions already deployed in this sector
Solutions already deployed in this sector
1 product is already delivered at our clients in this sector.
Solutions addressable to this sector
Solutions addressable to this sector
6 products are available for deployment in this sector.
09
DeliveredDesktop AI Terminal — Unified local interface
Analyst productivity on local workstation, sensitive contexts mastered.
Desktop application integrating multiple AI models and business tools in a unified interface. Local confidentiality for contexts where data must not transit through the cloud.…
View product →
13
In progress / availableEnterprise document RAG
AI-augmented search on your document heritage — no hallucination, with sourced citations.
RAG (Retrieval-Augmented Generation) platform connected to your internal sources (legal, HR, technical, contracts, regulatory, finance, accounting). Sourced responses with document…
View product →
15
DeliveredHITL Framework — Human validation loop for AI
Keep humans in the decision on critical cases, at scale.
Industrial Human-in-the-Loop framework: human validation interface on AI outputs, case queue to arbitrate, confidence scoring, human/AI agreement metrics, continuous learning from …
View product →
21
DeliveredATLAS Legacy — AI-assisted modernization of COBOL, Delphi, and BizTalk applications
Read, understand, and rebuild critical legacy code with proven functional parity — AI-assisted, human-validated.
Productized application of Access International's ATLAS methodology (10 steps, 9 principles, 56 learnings, 19 pitfalls) to legacy modernization: COBOL mainframe, Delphi desktop, Bi…
View product →
23
DeliveredAgentic workflows — Multi-agent AI orchestration in production
Run multiple specialized AI agents together, on real business task chains — without breakage and without rogue agents.
Design and operation of agentic workflow chains: several specialized AI agents (research, writing, validation, publishing) coordinated around explicit orchestration (n8n, Airflow, …
View product →
24
Internal testLotus Notes / HCL Domino estate recovery
Recover and make usable a Lotus mail history that nobody in the company can open any more.
Many companies keep a Lotus Notes / HCL Domino server on life support for one reason only: years of exchanges, decisions and attachments are locked inside it. The usual reflex — gr…
View product →
Functions covered
Functions covered
Want to explore these solutions for your sector?
Free initial scoping. We assess your context and identify the most relevant solutions.