01
Your ERP isn't standard
You have a proprietary, vertical, legacy, or custom ERP system that does not have a published connector for the stack. The team evaluates the available API or integration mechanism and builds a custom bridge.
SERVICE
From the stack to your business.
Custom extensions and integrations.
We develop custom extensions for the DOQSOFT stack —including MPS, Gespage, Chronoscan, and Docuo —and build custom integrations with your business applications: ERPs (SAP, Oracle, Dynamics), CRMs, industry-specific systems, identity providers, and electronic signature solutions.
Print
MPS · Gespage
AI Capture
Chronoscan
ECM
Docuo
YOUR BUSINESS
ERP · CRM · Identity
When does it apply?
When Is It Best to Use
for Custom Development?
The DOQSOFT stack covers most cases out-of-the-box through standard configuration. These are the four situations where custom development makes sense—and where the Development team adds the most value.
02
Workflow specific to your business
You have a unique document workflow that isn't covered by the standard configuration of Docuo or Gespage—a specific approval workflow, validation based on specific business rules, or an integration between two systems with custom logic.
03
Published vertical system without a connector
You need to connect the stack to an HIS, SIS, case management system, notary system, or vertical ERP that does not have a published connector—but exposes data via REST API, SOAP, flat files, or a direct connection.
04
MFP app or specific AI template
Do you want a workflow embedded in your multifunction printer's control panel (scanning to a custom destination, capturing specific metadata) or an AI extraction template trained on your specific document type (a specific invoice, a quality sheet for your industry, or your own format)?
How We Develop
Two tracks.
Just one installment.
Development at DOQSOFT isn't just run-of-the-mill development—it's deeply rooted in the tech stack. We work on two parallel tracks: product extensions (Track 01) and integrations with your business applications (Track 02). Almost all projects combine both.
Track 01
Stack Extensions
Overview of the four products in the DOQSOFT stack. Each product has documented extension points—we leverage these to build capabilities specific to your business without altering the core.
- Workflows and Business Rules in Docuo — for Your Specific Use Case (Legal Case Management, Medical Records, Industrial ECO, Corporate Contracts)
- AI data capture templates in Chronoscan — trained using your documents (specific supplier invoices, quality sheets from your industry, custom formats)
- Embedded MFP Apps in Gespage — custom workflows on the MFP panel (scanning to workflow, metadata capture, specific authentication)
- Dashboards and Reports in MPS — metrics specific to your operation, integrated with the KPIs your team already monitors
Track 02
Integrations with Your Business Applications
The stack connected to your world. We feed data from the stack into your ERP, CRM, or line-of-business system—and bring the data the stack needs to operate (vendor master data, identity, catalogs, process statuses) into the stack.
Typical categories:
- ERPs — We can build custom integrations with SAP, Oracle, or Microsoft Dynamics by evaluating the available APIs for each system, as well as with other common ERPs
- CRMs and sales systems — we can integrate Salesforce, HubSpot, Microsoft Dynamics CRM, and others based on the API provided by each platform
- Vertical systems in your industry —HIS, SIS, case management systems, electronic RPPs, notarial management systems—via REST API, SOAP, or direct connection, as applicable
- Identity and Electronic Signatures — Active Directory, Entra ID, Okta, SAML/SCIM + integration with third-party providers of legally valid electronic signatures (eIDAS / QES and global equivalents; local requirements such as NOM-151, depending on the jurisdiction)
Almost all projects combine both tracks—stack extensions that send and receive data to and from your business systems. The native integration between tracks That's what sets a comprehensive development apart from one that only covers half the ground.
How We Work
Analysis. Development.
Implementation. And monitoring.
Four stages we apply to every project—from the free initial session to ongoing support after go-live. The idea is that you always know where your project stands and what’s next.
01
Analysis
Free initial session: We’ll understand your business objectives, the systems involved, and any constraints (technical, regulatory, and time-related). We’ll come up with a concrete proposal—scope, deliverables, pricing model, and timeline.
02
Development
A dedicated project team, sprints with biweekly demos, a shared repository with your IT team, documented code, and unit and integration tests. Iteration with business stakeholders to ensure the deliverable reflects the real-world scenario.
03
Implementation
Deployment to a staging environment, UAT with your team, final adjustments, and a coordinated go-live. We provide an operations manual, training for your IT team, and documentation for each component—so you can take over operations from day one.
04
Monitoring
After go-live, the team closely monitors the rollout, makes rapid adjustments, and hands off to the Support team for ongoing maintenance. For recurring projects, there are monthly retainer models that keep the team involved.
Other Services
Additional services:
, where applicable.
Three additional services that aren't the norm—but that work well with extensions and integrations when the situation calls for it.
Mobile Access
According to the project, we can provide access to the stack from tablets on the factory floor, smartphones used by field personnel, or remote operator terminals.
- Mobile access developed in accordance with the scope of the project
- Secure connection to the stack based on the available API
- Data synchronization when necessary
Cloud Deployment Support
If you prefer not to manage on-premises infrastructure or use Stratus, depending on the project, we can support the deployment of the stack in the cloud that your organization already uses.
- Support for deployment on the cloud of your choice
- Coordination with your IT team during the rollout
- Documented best practices for backup and recovery
Turnkey Projects
Full implementation: DOQSOFT stack + custom extensions + integrations with your business applications + team training + handoff to Support. One provider, one contract, one point of responsibility.
- DOQSOFT Stack licensed and configured
- Custom development (extensions + integrations)
- Training + Transition to Ongoing Support
Metrics
The Development Team, "
" in Numbers.
Fifteen years of expanding the DOQSOFT stack for international clients and cross-border projects.
Custom-made
Extensions and integrations delivered per project on the DOQSOFT stack
15+ years
deploying DOQSOFT solutions and integrating them with business systems
ERP · CRM
Custom integrations with business systems, vertical systems, and identity providers
4
DOQSOFT stack products as an extensible platform (MPS, Gespage, Chronoscan, Docuo)
Get started with a free analysis
Let's talk about your
extension or integration.
Frequently Asked Questions
's Most Frequently Asked Questions About Development.
If your question is specific to your project, systems, or technology, schedule an analysis session—our development specialists will assist you directly at no cost.
When is a custom development approach preferable to a standard stack configuration?
The DOQSOFT stack (MPS, Gespage, Chronoscan, Docuo) covers most document and printing use cases out-of-the-box through configuration. Custom development is required when: (a) you have a business-specific workflow not covered by the standard configuration, (b) you need to integrate the stack with an ERP, CRM, or vertical system that lacks a published connector, (c) you require an app embedded in MFPs with a workflow unique to your operations, or (d) your document volume or type requires a specifically trained AI capture template. The initial analysis session (at no cost) serves as the first screening step: if the issue can be resolved with standard configuration, we’ll let you know.
How do integrations with SAP, Oracle, Microsoft Dynamics, or other ERPs work?
The Development team can build custom integrations with SAP, Oracle, or Microsoft Dynamics by evaluating each system’s available API or integration mechanism (REST, SOAP, flat files, direct database access). The same applies to custom systems, legacy systems, or vertical ERPs without a published connector: if your ERP has a way to expose data, we can build the integration. The scope and effort are assessed during the analysis phase.
What is the typical duration of a development project?
It depends on the scope; the following timeframes are estimates and are subject to the final scope. A simple extension (a workflow in Docuo, an AI capture template in Chronoscan, a dashboard in MPS) is estimated to take 2–6 weeks. An ERP integration project is typically estimated to take 8–16 weeks. A turnkey project that combines extensions, integrations, and operations can be estimated to take 3–6 months. The exact timeline is determined during the analysis phase and is included in the proposal before work begins.
How is software development billed—as a fixed-price project, time and materials, or a retainer?
Three models are available: (1) Fixed-price project — the most common; a quote is provided after an initial analysis that defines the scope, deliverables, and timeline. (2) Time & materials — for exploratory or iterative projects where the scope cannot be defined upfront. (3) Monthly retainer — for clients with a continuous stream of extensions and integrations; a dedicated team that operates as an extension of the client’s IT department. The initial analysis session is free of charge and concludes with a recommendation for the most appropriate model.
What does post-implementation maintenance include?
The project always delivers documented code, unit and integration tests, an operations manual, and training for the client’s IT team. Subsequent maintenance can be contracted separately: bug fixes and minor adjustments with a specific SLA, updates when the DOQSOFT stack or the integrated system releases new versions, and functional enhancements under a retainer model. For clients with a DOQSOFT Support plan, bugs in the delivered code are handled through the same omnichannel workflow.
What if our ERP or system doesn't have a published connector?
We can evaluate proprietary ERPs, legacy systems, lesser-known vertical ERPs, and custom client systems. The bottom line is the same: if your system has a way to expose data (REST API, SOAP, flat file, direct database connection, messaging), we can build a custom integration. The analysis phase evaluates the available mechanisms, risks, and effort—and concludes with a concrete proposal. If the system truly cannot expose data by any means, we’ll let you know and propose alternatives.
