Choose the level of engineering and delivery support your organisation needs with Dalfin Genesis.
Choose how your organisation works with Genesis
Different organisations have different technical capacity, implementation experience and governance needs. Dalfin Genesis supports three ways of working. The platform, engineering scope and acceptance principles remain consistent; what changes is who performs which parts of the work.
Customer led
For organisations with an established technical team.
Your organisation leads requirements refinement, engineering decisions, testing and deployment coordination using Genesis under the agreed access and delivery arrangements. Dalfin AI provides the Genesis platform and the level of support included in your engagement.
Your team should be ready to: own the business specification, make design and approval decisions, manage users and dependencies, validate the result, and run the release process.
Assisted
For organisations that want to retain control while adding specialist support.
Your team and Dalfin AI divide responsibilities for engineering, integration, review, testing and release. Responsibilities and decision rights are agreed before work begins, so there is a clear owner for each critical outcome.
Typical arrangement: the customer provides business owners and internal system access; Dalfin helps with agreed engineering and delivery activities. Actual task ownership depends on the statement of work.
Dalfin delivered
For organisations seeking an accountable delivery team.
Dalfin AI leads the defined application delivery programme, including the agreed engineering and quality activities. Your organisation still supplies subject-matter expertise, approves business requirements, provides access to relevant systems and accepts the outcome.
Dalfin-delivered does not mean requirements, integrations, infrastructure decisions or acceptance can be assumed without customer input.
Responsibilities at a glance
| Activity | Customer led | Assisted | Dalfin delivered |
|---|---|---|---|
| Business objectives and process ownership | Customer | Customer | Customer |
| Requirements, business rules and acceptance decisions | Customer | Shared preparation; customer approval | Dalfin prepares as agreed; customer approval |
| Application engineering | Customer leads | Shared | Dalfin leads |
| Integration arrangements and third-party permissions | Customer coordinates | Shared | Shared under agreed scope |
| Functional and business validation | Customer leads | Shared | Dalfin coordinates; customer participates |
| Release and operational handover | Customer leads | Agreed split | Dalfin coordinates agreed handover |
| Ongoing changes | Per agreement | Per agreement | Per agreement |
This table explains typical responsibility boundaries; the signed engagement documents govern the actual delivery model.
What is the same in every model?
- An approved scope, defined roles and a route for resolving unknown requirements.
- Business rules, permissions, dependencies and acceptance criteria that are explicitly reviewed.
- AEU accounting for Genesis application generation and Genesis-assisted customisation.
- The applicable Connected service and ongoing platform dependencies.
- Customer ownership of agreed generated application deliverables, subject to the contractual intellectual-property provisions.
- A defined testing, deployment and acceptance approach.
How should we choose?
Choose Customer led if your team wants to direct engineering day to day. Choose Assisted if you need specialist capacity while retaining hands-on control. Choose Dalfin delivered if you want Dalfin AI to coordinate the agreed delivery work.
Your choice is confirmed during discovery and may evolve through a separately approved change in scope.
Request a discussion (opens in a new tab) ยท Understand the engineering journey