A feature that addresses a real need.
Development begins with a specific gap in the workflow.
Development begins with a specific gap in the workflow.
Standard capabilities and configuration are considered first.
A new feature has clear scenarios and limits.
We account for updates, permissions and responsibility after launch.
Use the existing feature and verify roles and data.
Check an integration, ownership and error handling.
Agree a small extension and its maintenance.
Permissions, data and deployment matter more than a new menu.
A new menu is not an acceptance result. The responsible employee checks permissions, data and error handling; updates and ongoing maintenance belong in the agreed scope.
A working application for the agreed workflow, with verified access, deployment instructions and a clear maintenance boundary.
Review the workflow and what existing tools already cover.
Agree a small first scope and observable acceptance criteria.
Build and verify a usable step with the relevant users.
Test permissions and deployment, then hand over operation.
Sometimes changing the process, configuring roles or adding one data exchange is enough.
In another case, an existing tool genuinely does not support an important rule, interface or data model. We help distinguish these cases before a large project begins.
The user's task and responsibility boundaries are the basis of the solution.
The number of screens or technologies does not answer what a person will be able to do better and how that can be checked.
We define users, required actions, objects and exceptions.
We check permissions, change history and connections to existing systems. From the start we account for who corrects an error and how a clear data source is retained.
We prepare clear states, actions and messages.
Empty lists, denied access, waiting and unknown operation outcomes are addressed rather than left until later. Customer interfaces account for mobile use and accessibility; editors account for content manageability.
We choose the form for the task. Sometimes a small module for an existing platform is needed; sometimes a separate service with a limited interface.
We do not create a second system of record unnecessarily or duplicate features that already work reliably.
We agree acceptance criteria before implementation.
We test important scenarios and exceptions, prepare documentation and a controlled release. We define how the solution is updated, who owns access and what support includes.
Specific work approval. A team may need to retain an estimate version and separate authorisation for additional scope.
The customisation should support that rule, not rewrite the whole CRM.
An editor for repeated content. If standard blocks do not cover a confirmed scenario, we create a component that remains editable and does not break neighbouring pages.
Review standard capabilities, configuration and possible integration.
Name the user, data, starting event and result criterion.
Choose the simplest compatible extension rather than a general rewrite.
Exercise normal and error cases and document the version and support process.
We plan development around actual use.
We do not add features merely because large platforms have them. A small solution with a clear owner is often more useful than a complex product without resources for support.
Rights to code and materials, licences, access to external services, data processing, hosting and ongoing support.
A custom application does not mean there are no dependencies or that every third-party component is updated for free.
If an academy needs to allocate corporate places to specific learners under special rules, we first check the standard scenario and permissions.
If a supplier needs a separate process for handing serialised equipment to service, we compare configuration of existing applications with a small module. For Beauty, a specialist waiting list must not automatically charge money or reserve a resource.
pNet develops only the confirmed missing step: records, roles, interface, exceptions, integrations and acceptance criterion.
It may be an Odoo addon, connected service or separate interface; the choice depends on the task, version, licences and ongoing ownership cost. Code does not replace operational process configuration and team training.
After checking the selected feature, we agree release and support, access and exchange and further development.
Additional development is not a hidden part of every ready-made industry package.
All pNet business systems.
Scope, data migration, third-party services, ownership and ongoing maintenance are agreed before development. Further features are separate decisions.
Describe your systems, the problem and any known constraints. You do not need a complete technical specification. Please leave passwords, keys and customer data out of your message.
Yes. We choose one complete scenario and criteria for its usefulness. A prototype is not presented as a ready working system without the necessary checks.
We first examine its state, rights, documentation and the possibilities for safe change. We then determine a realistic scope.
Not necessarily. We compare actual limitations and total ownership cost, including support and data, not just a feature list.
We provide agreed materials and instructions. Support, updates and further development have a defined scope and terms discussed in advance.
Tell us which working step existing tools cannot perform. We will compare options and propose a first verifiable result.