Custom software — Intranet & extranet

Secure custom intranet and extranet development

A workspace where your teams find documents, procedures and approval flows, and where your clients or partners access a partitioned space of their own. We design, build and maintain secure intranets and extranets for companies in Paris and Île-de-France — relying on your Microsoft 365 environment or on a custom platform, depending on how you work.

What holds you back

The patterns we keep seeing.

01

Scattered information, uncontrolled versions

File server, mailboxes, improvised shares: documents exist in several versions and nobody knows which one is authoritative. Procedures are written down but nowhere to be found, and every new employee starts from scratch.

02

Client exchanges by email attachment

Deliverables sent by email, oversized files, versions going back and forth with no traceability: exchanges with your clients and partners escape any control, including for sensitive documents.

03

Access rights that no one controls

Shares pile up over the years, departures are not reflected in access rights, and it becomes impossible to say who can see what. An audit or an incident always reveals it too late.

What we cover

The scope of the service.

01 / DOCUMENTS

Document management and internal communication

A structured document repository where documents have a defined place, a reference version and an identified owner.

  • Document libraries with versioning
  • Filing plan designed with your teams
  • Search across document content
  • News pages and internal communication
  • Shared document templates
02 / WORKFLOWS

Workflows and approval flows

Requests that used to travel by email become structured flows: the people involved know what they need to approve, and decisions are traced.

  • Approval flows: purchasing, leave, contracts, expense reports
  • Business forms with business rules
  • Automatic notifications and reminders
  • Decision history and traceability
  • Cross-tool automation with n8n where relevant
03 / ACCESS & SECURITY

Access rights and security

Access defined by role and by space, backed by your company directory, with traceability that shows who did what.

  • Single sign-on (SSO) backed by Entra ID
  • Multi-factor authentication (MFA) on sensitive access
  • Rights by role, by space and by document
  • Logging of access and actions
  • Periodic rights review with your designated contacts
04 / EXTRANET

Client and partner spaces

A portal carrying your brand where your clients, suppliers or partners exchange documents and track their cases, with access partitioned by account.

  • External accounts partitioned by client or partner
  • Secure document upload and exchange
  • Tracking of cases, orders or projects
  • Interface matching your brand guidelines
  • Hosting and maintenance managed over the long term
How we proceed

From scoping to follow-up.

The exact scope, deliverables and timelines are formalised in the proposal, before any commitment.

1
Usage scoping

Workshops with your teams: mapping existing documents and flows, defining roles, the internal scope and external access.

2
Architecture choice

Microsoft 365 foundation (SharePoint, Teams) or custom-built platform: a reasoned decision based on your uses, your licences and your constraints.

3
Design and development

Structure, mock-ups of the key screens, then iterative development or configuration with regular validation points with your designated contacts.

4
Content takeover and go-live

Sorting the existing content, migrating the retained documents in batches with checks by your teams, configuring rights, training users and administrators.

5
Maintenance and enhancements

Fixes, security updates and functional enhancements at the pace of your needs, within the scope defined in your service contract.

Frequently asked questions — custom software

The answers describe how the service works. Quantified commitments are formalised in your contract.

An intranet is reserved for your employees: internal documents, procedures, communication, approval flows. An extranet opens part of the platform to third parties — clients, partners, suppliers — with dedicated accounts and partitioned rights. Both can rest on the same technical foundation; what sets them apart is the scope of access.
If your teams already work with Microsoft 365, SharePoint and Teams often cover document management and internal communication with limited implementation effort. Custom development is justified when your workflows are specific, when the extranet must carry your brand with your clients, or when deep integrations with your business tools are required. We compare both options during scoping, with a reasoned recommendation.
Yes, subject to a prior audit: an inventory of the content, identification of duplicates and obsolete documents, and definition of the target filing plan. Migration then runs in batches, with validation by your teams as the batches progress. Taking over the existing content as-is would reproduce today's disorder: sorting is part of the project.
The functional scope (document management, workflows, external portal), the number of internal and external users, the takeover of existing content, integrations with your business tools, and the security and hosting requirements. The chosen architecture — Microsoft 365 foundation or custom development — also affects the balance between licences and development. Pricing is established after scoping and formalised in the specific terms of your contract.
The timeline depends on the scope: a document foundation is up and running faster than an extranet with workflows and integrations. We favour a staged go-live, to deliver value early and adjust what comes next to actual usage. The schedule and milestones are formalised during scoping, then in your service contract.
Rights are defined by role and by space: employees, managers, clients, partners. When your company uses Microsoft 365, authentication relies on Entra ID, with single sign-on (SSO) and multi-factor authentication (MFA). External accounts are partitioned, access is logged, and a periodic rights review is organised with your designated contacts.
The platform is designed to fit the applicable obligations: access rights management, logging, retention periods, information for data subjects. The General Data Protection Regulation (GDPR) also imposes organisational measures that go beyond the tool itself. The legal qualification of your setup remains to be validated with your counsel or your data protection officer.
It depends on the chosen architecture: a SharePoint intranet lives in your Microsoft 365 tenant, while a custom platform is hosted on dedicated infrastructure whose operations we manage. In both cases, corrective maintenance, security updates and functional enhancements are covered within the scope defined in your service contract.
Your content, your accounts and the project documentation belong to your company. The hand-back and reversibility arrangements — data export, transfer of access, handover of the source code or configuration depending on the chosen architecture — are formalised in your service contract. It is a point we recommend you demand from any provider.

An audit, then a clear plan.

Describe your need in a minute. We come back with an assessment and prioritised next steps.

Secure intranet and extranet development | Dalena