Practical answers about building, changing, owning and operating enterprise applications with Genesis.

Frequently asked questions

Getting started

What is Dalfin Genesis?

Genesis is Dalfin AI's AI-assisted enterprise application engineering platform. It helps turn business requirements and supporting evidence into applications through a scoped, reviewed and validated process.

Do we need a detailed specification before talking to Dalfin AI?

No. A business problem, existing process documents, spreadsheets, screens or a catalogue blueprint can be a useful starting point. Important rules, responsibilities, data and exceptions must still be confirmed before they are treated as implementation requirements.

Can we start from an existing application or a design?

You can discuss existing systems, documents, screenshots and design references as inputs. The feasibility of reusing or migrating particular software, code or data must be assessed; it is not assumed from the ability to upload a file.

What does a solution blueprint mean?

It is a starting application concept describing a possible business solution. It is not, by itself, a production-tested or customer-specific application. The catalogue provides 5,000 searchable solution blueprints across 35 industries. All are available to explore; each selected concept needs scoping, engineering, testing and acceptance.

Can we select a blueprint and add instructions for Genesis?

Yes. Select Use this blueprint in Genesis and add your organisation's instructions. The selected blueprint and instructions pass into Genesis as an initial application request for review in your authorised organisation workspace. Requirements and scope must be confirmed before engineering begins. Contact Dalfin AI to discuss enterprise access.

Can Genesis produce an application without a Figma file?

Yes, the starting material can be a written business requirement or other evidence. The interface still needs to be designed and validated against the intended users and workflow.

What is built?

Does Genesis generate more than screens?

The intended enterprise build can include interfaces, data structures, backend services, business workflows, roles, rules, reports and integrations. Actual components depend on the agreed requirements, supported capabilities and testing.

Can Genesis create a complete ERP system?

Enterprise programmes can include multiple applications, modules, integrations and complex workflows. An entire ERP should not be assumed to fit inside a small initial scope. The breadth of the system, delivery stages, AEU allocation and Connected scope need to be assessed and agreed.

How are approval rules and exceptions handled?

They should be captured explicitly in the requirements, reviewed by authorised business owners and tested. Sensitive transactions or approval processes should not be accepted merely because a form or database table exists.

Are mobile applications supported?

Mobile experience and device needs can be included in the solution scope. Device functions, offline behaviour, scanners and other hardware integrations require compatibility and acceptance testing for the chosen deployment.

Can Genesis integrate with our current systems?

Integrations are assessed according to the systems, interfaces, data permissions, operating constraints and reliability requirements involved. No specific third-party integration is promised without scoping.

Are catalogue screenshots or demonstrations evidence of a live product?

Not necessarily. Illustrative interfaces and solution concepts should be labelled as such. A verified demonstration is separately identified and should state what was actually tested or deployed.

Delivery and changes

Who provides the business requirements?

Your organisation is responsible for the business decisions and for approving the requirements and acceptance criteria. Dalfin AI's preparation and engineering role depends on the engagement model.

Can our developers work directly with Genesis?

Yes, under a Customer led or Assisted engagement with suitable authorised access and the agreed working practices. The available tools and permissions depend on the current product release.

What happens if we need changes after the first release?

Changes can be proposed, assessed and implemented through the agreed process. Context Memory helps preserve relevant business and engineering decisions. Genesis-assisted customisation consumes AEU according to the scope and complexity of the change.

Can a small application grow into a much larger one?

It can be extended if technically feasible and agreed. Additional workflows, modules and integrations are evaluated as additional scope; they are not an unlimited inclusion of the original generation or Connected service.

Can we use our own developers or other AI tools for changes?

Depending on your agreement, you may perform authorised customer-led changes. Review, testing, supportability, Context Memory updates and any reintegration to Genesis are governed by the agreed technical and commercial arrangements.

AEU and Connected

What is AEU used for?

AI Engineering Units (AEU) account for Genesis-assisted application generation and Genesis-assisted customisation. Usage depends on the work performed and its complexity, not merely on the number of pages in an application.

Are all later changes included in the original AEU allocation?

No. Later Genesis-assisted changes also use AEU. Whether an allocation is sufficient for a particular set of changes depends on the agreed capacity and the complexity of the work.

How will administrators see AEU consumption?

Only your organisation's authorised administrators can view AEU consumption and available balances in the Genesis admin panel.

Can remaining AEU be used on another app?

Where permitted by the organisation's agreed allocation and programme, remaining capacity can be used for additional applications in that organisation.

Does Connected include unlimited customisation?

No. Connected is the ongoing context and Genesis service relationship for the agreed application scope. It does not provide unlimited application engineering or development services.

Are AEU prices and service charges published here?

No. Commercial terms are tailored to the agreed programme and are included in your proposal or agreement.

Ownership and security

Do we own the generated source code?

Customers own the agreed customer-specific application source and deliverables under their engagement terms. Genesis, Context Memory, reusable shared platform components and certain third-party technologies remain subject to separate ownership or licensing rights.

Can the application operate without Genesis?

Do not assume it can operate fully disconnected. Applications retain the agreed dependencies and connections to Genesis services for shared platform capabilities and other contracted functions. Any isolation requirements should be reviewed during design.

Is everything hosted in our cloud?

Not necessarily. Where the application runs and where the Genesis platform and Context Memory operate are separate architectural questions. The approved deployment arrangement is defined for each engagement.

Is Genesis certified for our industry's security standards?

Any required certification, contractual control, hosting region or regulatory requirement must be checked against current evidence and agreed in scope. This guide does not make blanket compliance certifications.

Speaking with Dalfin AI

How do we begin?

Send a short description of your business need or the relevant catalogue concept through Dalfin AI's contact page (opens in a new tab). Include the outcome you want and the type of delivery support your team needs. Do not send credentials or sensitive production data in a general enquiry.