The roles
We identify who views, who contributes and who approves.
A permissions matrix to approve.Intranet and extranet
PROPUL / SOLUTIONSA shared place to find documents, track requests and work together, with access tailored to each role.
A single project can bring together several stakeholders. This example shows the documents and requests each one can access, depending on their role.
The scope
We identify who views, who contributes and who approves.
A permissions matrix to approve.Information is organised by record and by use.
Team, client or partner spaces.Requests and documents have a status, an owner and a next step.
A history and useful notifications.A well-scoped investment
A quote should help you decide. It sets out what will be built, what remains to be defined and what you will receive.
The scope, content and connections selected determine the price. We define them before costing.
Decision document
We identify who views, who contributes and who approves.
Information is organised by record and by use.
Requests and documents have a status, an owner and a next step.
We price a precise way of working, with its limits.
Points to clarify
Which files to carry over, in what state, with which consistency checks?
Which connections are available, necessary and included in the initial scope?
Who uses the tool, who approves the rules and which access rights need to be distinguished?
These assumptions are discussed before the build.
What you receive
A permissions matrix to approve.
Team, client or partner spaces.
A history and useful notifications.
Handover terms are clarified from the outset.
Sample document structure. No quote is generated here.
Your starting point
Your context, your constraints and a first priority.
Together, we'll define the right next step.