Portals and extranets

Custom client portal and extranet development

A private space for your clients, partners or teams.

Your clients, partners or teams need access of their own. We design custom portals and extranets with accounts, roles and properly separated data.

  • Free scoping in 3 meetings
  • Role-based access
  • Maintained over time

What we build

A portal that saves everyone time.

Fewer emails and fewer files sent by hand. Everyone finds what concerns them in one place.

  1. Accounts and roles

    Each user sees what concerns them. Admins, teams, clients or partners each have their own rights.

  2. Dedicated spaces

    One space per client, organisation or team, with its own content and data.

  3. Dashboards

    Progress, statistics and indicators kept up to date for you and for your users.

  4. Documents and content

    You publish documents, training or news and your users find them without having to email you.

  5. Connectors

    The portal talks to your existing tools such as your management software or your CRM.

  6. Secure access

    Authentication, role-based rights and separated data are designed in from the start.

A real example

FUUZ, the training platform built for Mosh.

For the Mosh agency we built FUUZ, a private e-learning platform. It shows well what a custom portal can do.

  1. Teams and organisations

    Each organisation has its own space with its teams, roles and learning paths.

  2. Built-in AI agents

    Tutor, coach or automated grading. Configurable AI agents support the learners.

  3. Real-time tracking

    Progress, skills and engagement are tracked on dashboards for administrators.

Portal, extranet or customer area

A private space that replaces emails and attachments.

A client portal gives your customers access to their files, documents, orders or progress without going through you. An extranet opens the same kind of access to your partners, franchisees or suppliers. An intranet does it for your own teams. Technically we build them the same way, with accounts, roles and data kept apart.

The heart of a portal is permissions. Who sees what, who can edit and who approves. We model them during scoping because they are what makes the tool safe and easy to evolve. When permissions flow through teams or organisations, a graph database becomes very handy. We explain why in our article on Neo4j.

The portal connects to the tools you already use, such as your custom management software or your CRM, so nobody types anything twice. It can also include AI agents, like the tutors and coaches in FUUZ shown below.

Our method

Your project in 3 meetings.

No need to show up with a 50-page specification. You come with your idea and we build the framework with you.

  1. Meeting 11 h

    We listen.

    You tell us about your company, your business and your idea. We ask the right questions and tell you what is possible. You have nothing to prepare.

    You leave withyour needs understood

  2. Meeting 22 h

    We present the specifications and the mockups.

    Between the two meetings we break your idea down into concrete features and draw the mockups. We go through each point with you and adjust until everything matches your vision.

    You leave withdetailed specifications and the mockups

  3. Meeting 330 min

    We quote and agree.

    We present the schedule, the milestones and the budget. The price is fixed and there are no bad surprises.

    You leave witha fixed-price quote

The 3 meetings cost you nothing.

Neither do the specifications and mockups we prepare for you. Trust starts before the quote.

See the method in detail

Your questions about portals and extranets

Tell us about your idea.

At the first meeting we listen. It's free and you have nothing to prepare.

Or call us on +33 4 58 14 15 50