MyDocSafe can support organisations whose requirements go beyond standard product configuration.
If you need bespoke workflows, integrations, enterprise controls, custom configuration or functionality that is not currently available, contact MyDocSafe Sales to discuss an Enterprise or custom deployment. This builds on our existing Enterprise delivery model.
When should I consider an Enterprise or custom deployment?
A custom deployment may be appropriate if you need:
complex onboarding or case-management workflows;
bespoke questionnaires or document-generation processes;
integrations with your existing systems;
SSO or other enterprise requirements;
significant workflow automation;
a process that cannot be delivered using standard MyDocSafe configuration;
new functionality required for a particular business process.
We normally start by understanding the business process and desired outcome, rather than immediately specifying software development.
How does the process work?
Most projects are divided into four stages.
1. Discovery
We begin with a short, usually fixed-price discovery phase.
During discovery we work with your business and operational stakeholders to understand:
the process you want to digitise;
users and user roles;
information that needs to be collected;
decisions and approvals;
documents that need to be generated or signed;
notifications and communications;
integrations;
exceptions and edge cases;
reporting requirements;
security and access requirements.
Discovery is deliberately a relatively low-risk first engagement. It allows both parties to understand the requirement properly before committing to a larger implementation project.
A typical discovery phase takes around 2–4 weeks, depending on complexity.
2. Workflow specification and quote
The principal output from discovery is an agreed workflow specification.
This describes what MyDocSafe will build or configure and provides the basis for the implementation project.
The specification may cover areas such as:
workflow stages;
questionnaires and forms;
user journeys;
client portals;
document templates;
e-signatures;
approvals;
notifications;
integrations;
permissions;
required bespoke development.
Once the specification has been agreed, we provide a formal quotation.
The quote will normally distinguish between:
Implementation costs — configuration, integration, development and project work.
Ongoing costs — MyDocSafe licences and any agreed recurring services or usage charges.
This means you should have visibility of both the cost of delivering the project and the expected ongoing licence commitment before moving into implementation.
3. Implementation
Once the specification and commercial proposal have been approved, we move into implementation.
This normally involves a mixture of:
configuring existing MyDocSafe components;
creating workflows;
creating forms and questionnaires;
configuring portals;
creating document templates;
implementing integrations;
developing agreed bespoke functionality;
internal testing.
A typical implementation phase is around 4–12 weeks, although the actual timetable depends on the scope and availability of customer stakeholders and integrations.
One of the advantages of the MyDocSafe approach is that many requirements can be assembled from existing reusable workflow components rather than requiring an entirely bespoke software application to be developed from scratch.
4. User testing and launch
Once implementation is substantially complete, the solution moves into user acceptance testing (UAT).
Selected customer stakeholders test the agreed workflows and provide feedback.
This stage is used to:
confirm that the agreed process works;
identify configuration changes;
test realistic scenarios;
verify permissions and user journeys;
prepare for rollout.
The testing phase will normally culminate in approval for launch.
For many projects, allow approximately 2–4 weeks for testing and preparation for go-live.
The overall journey is therefore:
Discovery → Workflow specification → Quote and approval → Implementation → User testing → Launch
What happens after launch?
A custom MyDocSafe implementation should not leave you dependent on us for every small change.
Following handover, customers can normally control many of the day-to-day elements of their workflows themselves, including items such as:
questionnaires;
document templates;
content and configuration supported by the platform.
MyDocSafe remains available where you need help refining workflows, introducing additional use cases or developing new functionality.
This means a deployment can evolve as your business processes change rather than becoming a fixed, one-off software project.
Typical timescales
Phase | Typical duration |
Discovery and specification | 2–4 weeks |
Implementation | 4–12 weeks |
User testing and launch | 2–4 weeks |
These are indicative rather than guaranteed timescales. Complex integrations, new software development, procurement requirements or delays in customer feedback can extend the timetable.
Why start with discovery?
The discovery model is intended to reduce risk for both sides.
Instead of asking you to commit to a large project based on a high-level description, we first invest time in understanding the process and producing an agreed specification.
At the end of discovery you should have:
a clear description of the proposed solution;
an agreed workflow specification;
an understanding of implementation requirements;
a project timetable;
a formal implementation quote;
visibility of ongoing MyDocSafe licence costs.
You can then make an informed decision about proceeding with the implementation.
How to start
Contact MyDocSafe Sales with a brief description of the process or problem you want to address.
It is useful to include:
your organisation;
approximate number of internal users;
approximate number of clients/end users involved;
description of the process;
existing systems that may need to integrate with MyDocSafe;
key outcomes you want to achieve;
desired implementation timeframe.
We can normally determine from an initial conversation whether the requirement can be handled through standard MyDocSafe configuration or whether a formal discovery project would be more appropriate.
