Partners and contracts
Connect companies, regions, contacts, contract types, documents and status.
Software · enterprise platform
Developed from real work. Productive since 2009.
What began as a prototype for one specific workflow gradually became a modular platform for international service organisations.
2009–presentcontinuously developed and operated
Independentproven in separate international industrial environments
Modularone shared business case, shaped for each company
Starting point
An international service network needed more than scattered lists.
Industrial companies need to know which partners, technicians and organisations are qualified for particular products, regions and services. Contracts, capabilities, tests, audits, certificates and deadlines all depend on one another.
The starting point was not a comprehensive specification. In 2009, the first step was a prototype for one concrete operating workflow, close to the people who needed to use it every day.
Development principle
Not extended on the drawing board, but together with the practitioners.
New functions came from real cases. Users tested early versions, revealed exceptions and dependencies, and helped refine roles, the data model and the way the platform worked.
Proven workflows became part of the productive core. In this way, one initial application grew into a modular platform without losing touch with operating reality.
The platform logic
One lifecycle. Many connected business processes.
The platform does more than hold data. It makes an international partner and service network steerable in daily work.
Capabilities and tests
Connect technicians, product families, qualifications, training, tests and certificates.
Assessments and audits
Keep self-assessments, external audits, evidence, findings and actions properly separated.
Deadlines and reporting
Generate due dates, reminders, histories and management information from the process.
PERCEL role
From a concrete need to a product structure built for long-term operation.
- understood operating workflows together with their future users
- developed usable prototypes instead of abstract full specifications
- structured business logic, roles, permissions and the data model
- connected modules for partners, qualifications, tests, audits and certificates
- integrated multiple languages, external portals, histories and reporting
- included operation, backups, maintainability, support and security
- led continued development across different company environments
Representative configuration
The technical depth of one established platform configuration.
One configuration examined in detail connects several web applications, a shared data layer, extensive business logic and historically grown data structures into one integrated platform.
This account deliberately describes one representative configuration. It is not applied to other, mutually independent company environments. What matters is the development: a manageable prototype became a business-critical enterprise application.
Long-term responsibility
Product responsibility does not end with the first go-live.
Over many years, the platforms were adapted to new business and technical requirements. Functions, data structures, interfaces, operation and security continued to develop together.
This experience also shapes today’s technology projects: a prototype should create clarity early, while being thought through so it can become a robust product with clear roles, a clean handover and viable operation.
Role today
Operational software development is where this capability began. Today, PERCEL connects product logic, business requirements and operating reality, bringing in small specialist delivery teams to suit the task. This keeps the solution close to its practitioners while responsibility, quality and the overall objective remain intact across development stages.
Transferable value
Prototyping is not an end in itself. It makes a project testable early.
The case shows how an operating problem becomes a usable product: first understand the workflow, then create a testable solution, and only then grow it in modules.
This combination of product discovery, technical experience and long-term operational responsibility now provides the basis for translating between management, business functions and specialist technology partners.
A real workflow, but no clear product route?