Two companies, one team.
Let's shape your software together.
Proud partner:
Integrate our developers directly with your in-house team — collaborate, learn, and build together. Led by Oracle ACE Director Matt Mulvaney, based in London, with all engagements governed by English Law through Pretius Ltd.
Led by Oracle ACE Director Matt Mulvaney
Our UK co-creation engagements are led and overseen by Matt Mulvaney — one of only 17 Oracle ACE Directors in the world. Pretius Ltd is a fully registered UK entity (Company No: 147557660), governed by English Law. For UK enterprises concerned about IR35 off-payroll working legislation, this is the defining advantage: co-creation with Pretius is a clean, risk-free B2B partnership — not a contractor arrangement.
Matt Mulvaney
Pretius Ltd CEO / London-based leadership
♠ Oracle ACE Director — 1 of 17 worldwide · 5 Oracle ACEs on the team · 300+ in-house salaried specialists
What is co-creation?
Co-creation is Pretius's distinctive model of software development in which our engineers work directly alongside your in-house team — not for you, but with you. Together, both teams design and develop the solution, with continuous knowledge transfer happening throughout the project.
We frequently use this model in Oracle APEX and low-code projects, where the nature of declarative development makes knowledge transfer particularly effective. But co-creation can be adapted to any technology context: Java, React, custom web development, OCI infrastructure, AI integration, or any other domain where your organisation wants to build internal capability alongside the project deliverable.
Our aim is rarely simply to deliver software. We want to find the best possible way to address the underlying business problem that prompted the IT project. Sometimes that means choosing different tools or frameworks. In other scenarios, it means proposing a different architecture or technological approach. One thing remains constant: we focus on your needs, not our convenience.
We frequently use this model in Oracle APEX and low-code projects, where the nature of declarative development makes knowledge transfer particularly effective. But co-creation can be adapted to any technology context: Java, React, custom web development, OCI infrastructure, AI integration, or any other domain where your organisation wants to build internal capability alongside the project deliverable.
Our aim is rarely simply to deliver software. We want to find the best possible way to address the underlying business problem that prompted the IT project. Sometimes that means choosing different tools or frameworks. In other scenarios, it means proposing a different architecture or technological approach. One thing remains constant: we focus on your needs, not our convenience.
Why co-creation? The four outcomes that matter
01
A system perfectly aligned with your needs
The collaborative process ensures a deep understanding of your requirements, your workflows, your domain-specific constraints, and your business goals. The result is a highly customised system tailored precisely to how your organisation actually operates — not to a generic template.
For UK-regulated organisations, this alignment extends to compliance requirements.
Your legal, compliance, and risk teams can participate in shaping workflows, data governance, and audit trail structures alongside the developers building them — producing systems that satisfy FCA, DORA, and UK GDPR requirements as a first-order design goal rather than a retrofit.
02
Internal expertise for future maintenance and extension
By participating in the development process from day one, your in-house team gains genuine knowledge of the technology, architecture, code, and functionality of the new system. This empowers them to maintain, troubleshoot, and extend the software independently in the future — dramatically reducing long-term reliance on external support.
For UK organisations concerned about vendor lock-in, knowledge dependency, or the risk of key knowledge leaving with a supplier, co-creation is the structural answer.
The knowledge does not live in our team alone. It is transferred, embedded, and owned by your people throughout the project.
03
Valuable industry-specific knowledge for Pretius
ZDM is Oracle's own tooling. The migration runs Data Guard replication between the source and OCI target, validates the target against defined acceptance criteria, and executes a switchover that involves seconds of connection interruption rather than hours of downtime.
If our collaboration continues, we will already understand your sector, your systems, and your organisation deeply.
04
More effective business-IT collaboration
The team that participates in co-creation from your side does not need to be limited to technical staff. Business professionals can also engage as the system takes shape, learning to understand and articulate requirements more precisely, and making the business-IT feedback loop significantly more efficient.
This matters particularly for UK organisations in regulated sectors
— where business and compliance teams need to understand the systems they rely on and where system changes require documented sign-off from non-technical stakeholders. Co-creation makes that ongoing collaboration natural rather than transactional.
Why co-creation makes particular sense for UK enterprises
Eliminating IR35 risk — entirely
The UK's IR35 off-payroll working rules create significant complexity and risk for organisations that engage individual contractors. The question of whether an engagement is inside or outside IR35 is one that many UK HR, finance, and legal teams grapple with.
Co-creation with Pretius eliminates this question entirely. Every Pretius specialist is a full-time, salaried employee of Pretius Ltd — a registered UK company. The engagement is a B2B contract between your organisation and Pretius Ltd, with no off-payroll working, no intermediary arrangements, and no IR35 liability on your side. You get embedded expertise without the compliance burden.
Knowledge continuity — no key person risk
For UK enterprises with systems built or maintained by contractors, the departure of a key individual — whether a contractor finishing an engagement or an employee leaving — often takes critical knowledge with them. Co-creation addresses this structurally. Because knowledge transfer is the explicit goal throughout the project, the understanding of the system is distributed across your team before the project ends. A single person leaving does not create a knowledge gap.
Building UK-based capability — for the long term
Many UK organisations are acutely aware that their internal IT capability has been eroded by decades of outsourcing and reliance on contractors. Co-creation reverses this. Rather than outsourcing a problem and receiving a black-box solution, your team builds genuine technical skills alongside Pretius's specialists — skills that remain in your organisation after the engagement concludes.
For UK financial services firms managing FCA operational resilience requirements, having internal teams who genuinely understand the systems they operate provides a stronger foundation for the ICT risk management and business continuity documentation that regulators require.
Compliance built in from day one
In UK-regulated sectors, systems that are built without input from compliance, legal, and risk teams frequently require expensive rework when regulatory requirements are applied retrospectively. Co-creation's collaborative model means compliance teams participate in design decisions as they happen — shaping audit trails, access controls, data retention policies, and regulatory reporting capabilities before the code is written, not after.
How co-creation works in practice
Co-creation is not a fixed methodology but a flexible approach adapted to your project, your team, and your goals. Typically it involves:
01
Joint workshops and requirements definition
— business and technical teams from both sides collaborating on process mapping, requirements capture, and solution design. Your domain experts bring knowledge of what the system needs to do; our developers bring knowledge of what APEX or the chosen technology can do. The intersection is where the best solutions emerge.
02
Paired development
— Pretius developers work alongside your internal developers, not in isolation. Code reviews, architectural decisions, and design choices are made together, with explicit explanation of reasoning so your team understands not just what was built but why.
03
Incremental demos and feedback cycles
— frequent showcases of working software to both technical and business stakeholders, with structured feedback incorporated into the next sprint. Your team sees the system evolving in real time and has genuine influence over its direction.
04
Explicit knowledge transfer sessions
— regular sessions dedicated to explaining the system's architecture, data model, key design decisions, and technology-specific capabilities to your team. These are not afterthoughts; they are a planned deliverable of every co-creation engagement.
05
Handover planning from the start
— from the first week of the project, we plan for the moment our team steps back. What will your team need to know? Which modules require deeper explanation? What documentation should exist? The end state is a team that can genuinely own the system, not just use it.
Co-creation in context: when it works best
Co-creation is an option, not a requirement. The choice of engagement model is always yours. But co-creation tends to deliver its greatest value in specific circumstances:
Oracle Forms to APEX migrations
Where your team needs to own the APEX codebase after delivery — rather than depending on an external team for every change
Complex, long-term platform projects
Where the system will evolve continuously and internal capability is essential for sustainable operation.
Regulated environments
Where compliance, legal, and risk teams need genuine understanding of the systems they sign off on.
Organisations rebuilding internal IT capability
After years of outsourcing, seeking to reduce dependency on external vendors over time.
Projects where domain knowledge is critical
Where your team's deep understanding of the business processes is as valuable as the technical capability Pretius brings.
Pretius's commitment to knowledge sharing
Our approach to co-creation reflects a broader institutional commitment to knowledge transfer and education that is rare in the software development industry.
- We teach Oracle APEX development at technical universities, including WIT Academy and the Military University of Technology.
- Adam Kierzkowski's "How to become a developer?" Oracle APEX course on YouTube is one of the most recognised free APEX learning resources available.
- Our team members have co-authored books, published tutorials, and delivered conference presentations on APEX, PL/SQL, CI/CD, and cloud architecture at events including APEX World, ODTUG Kscope, and UKOUG.
- We run the Oracle APEX Monthly newsletter, curating the most important learning resources for the global APEX community.
This institutional culture of teaching and knowledge transfer is what makes co-creation work in practice. Our developers are experienced at explaining complex technical decisions in terms that business and non-specialist technical audiences can understand and engage with.
The Pretius UK advantage
Zero IR35 risk – clean B2B partnership
Every specialist is a full-time, salaried Pretius employee. Engaging Pretius Ltd — our registered UK entity — gives you a clean B2B partnership that eliminates all IR35 off-payroll working exposure. No contractor arrangements, no status determination requirements, no PAYE or NIC liability, no administrative burden.
Local UK accountability
Pretius Ltd is a fully registered UK entity (Company No: 147557660), headquartered in London, governed by English Law. Oracle ACE Director Matt Mulvaney leads UK engagements directly. Local contracts, local governance, local accountability.
Scale when you need it – 300+ specialists, zero recruitment delay
In the UK market, finding specialist Oracle APEX or enterprise software talent through recruitment takes months and costs significant fees. Co-creation with Pretius gives you immediate access to 300+ in-house salaried specialists — deployable within two weeks. No recruitment process, no probationary period, no risk of a hire not working out.
The London–Warsaw Hybrid Model
Strategic direction and client governance from our London office under Matt Mulvaney, combined with the engineering depth of our Warsaw Centre of Excellence. Co-creation teams are typically a mix of London-based strategic oversight and Warsaw-based engineering capacity — giving you senior UK leadership engagement alongside world-class technical expertise.
Rapid time to first value
Our agile methodology and low-code capabilities allow us to deliver working software in weeks, not months. In some cases, we build a basic PoC live during a discovery meeting — so your stakeholders see tangible progress before a full engagement is agreed. This "start small, think big" approach reduces the risk of large up-front commitments and builds confidence incrementally.
Genuinely technology-agnostic
We are Oracle experts, Java developers, React engineers, and Mendix specialists. We have no structural incentive to recommend Oracle APEX when something else fits better. Our recommendation follows your data, your team's existing skills, your regulatory environment, and your long-term strategy — not our commercial convenience.
By the Numbers
+ years
Powering market leaders
+
In-house specialists available – no recruitment required
+ projects
Successfully delivered
%
Of clients become long-term partners
+ years
Length of our longest client partnership
Oracle ACEs
On the team (including 1 ACE Director)
£
IR35 exposure for UK clients
ISO 27001 certified · UK GDPR compliant · DORA ready · IR35-compliant engagement
Curious how co-creation works in practice?
Book a free call and find out how we can build better software — together.
Case studies
Industry
Health insurance
Country
Greece
SYSTEM
Insurance management
Munich Re HealthTech – 4 Months to Modern SaaS
Migrating a legacy system to Oracle APEX to reduce costs, implement new features, and automate processes. Tasks that used to take days now only take a few minutes.
Sweco – Optimising infrastructure management for 120+ cities
Migrating the urban infrastructure management app to Oracle APEX and launching a DevOps team at Sweco streamlined operations and reduced costs of developing custom modules for various municipalities.
Industry
Engineering
Country
Netherlands
SYSTEM
Municipal asset management
Industry
Telecommunications
Country
Poland
SYSTEM
CRM
T-Mobile – Modern CRM for 11M clients
Thanks to the new CRM system, sales consultants at T-Mobile can work more effectively, quickly creating new sales offers. The modular, microservice architecture made the system more future-proof — every functionality can now be updated without shutting down the whole system.
What our Clients say
Bilal Ramadan
CEO – Munich Re HealthTech
The solution is secure, scalable, and compatible with most technologies used by our clients. It's also much cheaper to maintain, which was an important success criteria. Application licensing costs were largely reduced.
Adam Kasperowicz
CIO – VAN group
The new e-VAN system has become an innovative tool and work environment. The development team allows us to use the potential of the latest trends and technological solutions: web & mobile development, responsiveness, integrations, low-code, and cloud computing.
Marijn van den Berg
Team Manager – Sweco
Thanks to our collaboration with Pretius, we've made it easier for our clients to utilise Obsurv. Customising the application modules to their specific needs is now much quicker and more efficient. For us, this means shorter customer onboarding times and lower costs.
Zuzanna Świętorzecka
Head of Bancassurance – BNP Paribas
The communication throughout the project was very good as Pretius provided us with a Project Manager who always addressed our needs. The most impressive thing was how quickly the team developed a fully working, market-ready software solution for us.
Marek Samujłło
CIO – Emitel
What I like the most, as CIO, is that the people at Pretius care not only about technology itself but rather about how this technology can help your company achieve business goals.
Richard Coombes
Head of Engineering – Equals Money
They allowed us to deliver against our 20/21 roadmaps, launching new products to market and increasing company revenue by over 70%.
Gordian Ratajczak
Product Owner – Neuroflash
They effectively assess a project and allocate the matching resources, which gives confidence that you are in good hands. Issues and tasks are handled proactively and communication stands on a firm ground of mutual understanding and goals. You are not hiring an external resource, but you are gaining a team member.
Konrad Gałecki
Digital Manager – Philip Morris Distribution
Usually, you can either get a high-quality software solution or have it developed fast. However, thanks to choosing the right technology, the Pretius team was able to provide us with a fully working platform in a relatively short time.
FAQ
In our co-creation model, our developers work directly alongside your in-house team to design and develop solutions together, with continuous mutual learning and knowledge transfer throughout the project. The goal is not just to deliver software — it is to ensure your team understands and can independently maintain and extend the system after delivery.
Historically it works best with Oracle APEX and other low-code technologies, where the declarative development model makes knowledge transfer particularly effective and includes non-technical stakeholders more naturally. However, co-creation can be adapted to any technology context where your organisation wants to build internal capability alongside the project deliverable.
It depends on the nature of the project and your aims. We are always flexible and can provide more or fewer people as circumstances change. Co-creation is an option, not a requirement — the choice of engagement model is entirely yours.
The most significant benefit is the internal independence you gain through continuous knowledge transfer. When the project ends, your team can maintain and extend the solution without depending on external support. This is particularly valuable for UK organisations concerned about vendor lock-in, key person risk, or IR35 contractor dependency.
Yes — entirely. Because every Pretius specialist is a full-time, salaried employee of Pretius Ltd (our registered UK entity), the engagement is a clean B2B contract with no off-payroll working arrangements. There is no IR35 liability for your organisation, no status determination requirement, and no PAYE or National Insurance obligation on your side.
Absolutely. Co-creation's value is greatest when business users and domain experts participate alongside technical teams. Your compliance officers, operations managers, and subject matter experts bring knowledge of what the system needs to do; our developers bring knowledge of what the technology can do. The collaboration between these perspectives produces better outcomes than either side working alone.
Yes. If you want ongoing support after the project, we can maintain and extend the solution. Many of our co-creation clients choose to continue working with us for additional projects or feature development. Some of our client partnerships have lasted over 18 years.
Yes. We teach Oracle APEX development at technical universities, including WIT Academy and the Military University of Technology. Our team members have co-authored books, published tutorials, and delivered conference presentations at events including APEX World, ODTUG Kscope, and UKOUG. Adam Kierzkowski's free Oracle APEX course on YouTube is one of the most recognised APEX learning resources available. Knowledge transfer is not something we do as an afterthought — it is a core part of how we work.
For UK-regulated organisations subject to FCA operational resilience requirements or DORA, co-creation supports your ICT risk management in two important ways. First, it ensures your internal team genuinely understands the systems they operate, providing a stronger foundation for business continuity planning, DR testing, and regulatory documentation. Second, the collaborative model means compliance and risk teams participate in design decisions from the start — building audit trails, access controls, and regulatory reporting capabilities into the system rather than retrofitting them later.
