Learn how to start from requirements, documents, designs or an enterprise solution blueprint and prepare a useful Genesis request.
Starting an application
Begin with what your organisation already knows
You can start with a business problem, existing operational material or an application concept. You do not need to produce a complete technical design before discussing a Genesis build.
The better the starting information, the easier it is to identify gaps, make decisions and scope the application responsibly.
Four common starting points
A description of the business need
Explain what the organisation is trying to achieve, who will use the application and what problem it should solve. Include the most important actions, decisions and outcomes.
Example: "We need to control equipment movements across our sites, including approvals, custody history and reconciliation."
Existing documents and spreadsheets
Documents may describe operating procedures, approval conditions, forms, policies, data fields, reports and integration requirements. Spreadsheets may provide useful examples of records, calculations and decision points.
A spreadsheet column or current practice is not automatically the right rule for the new application. These details are interpreted and confirmed as part of scoping.
Screenshots, sketches and design references
Existing screens, sketches, wireframes and Figma designs can help communicate the intended layout and user experience. If no interface has been supplied, interface requirements can be developed from the business workflows and user needs.
Design evidence helps explain presentation. It does not replace workflow, security, integration or acceptance requirements.
A Genesis solution blueprint
The Dalfin catalogue (opens in a new tab) contains 5,000 searchable enterprise solution blueprints across 35 industries. All are available to explore as starting application concepts. Each selected blueprint still requires customer-specific requirements, engineering, testing and acceptance.
Choose the nearest concept and describe how your organisation differs. Examples of useful additional instructions include:
- "Require approval from two delegated roles before a high-value transfer."
- "Include our existing item master and warehouse interface."
- "Provide a mobile task for authorised receiving staff."
- "Add a reporting view for unresolved exceptions."
Select Use this blueprint in Genesis to pass the selected blueprint and your additional instructions into Genesis as an initial application request. Continue through your authorised organisation workspace to review the requirements and scope before engineering begins.
For enterprise access or a scoping discussion, talk to Dalfin AI (opens in a new tab).
What to include in a useful request
| Question | Helpful information |
|---|---|
| What outcome is needed? | The problem, goals and measures of success |
| Who does the work? | User groups, roles and approval responsibilities |
| How does work move? | Main steps, handoffs, exceptions and completion conditions |
| Which rules matter? | Mandatory checks, limits, restrictions and audit requirements |
| What information is used? | Forms, fields, reference data, reports and record history |
| What must connect? | Existing applications, APIs, imports and exports |
| Where will people work? | Desktop, mobile, field or other operational environments |
| How will it be accepted? | Realistic test scenarios and accountable reviewers |
If something is unknown, say so. A clearly identified question is more useful than an assumed answer presented as a fact.
What happens next?
The initial material is reviewed to identify scope, gaps and decisions. The customer confirms the important business rules, roles and outcomes. An agreed engineering and acceptance process follows.
A blueprint or document is therefore a starting point, not a shortcut around verification.
How Genesis works ยท Application generation
Confidentiality and sensitive information
Do not place passwords, access tokens, live credentials or unnecessary personal or commercially sensitive records into a public enquiry form. Where sensitive documents are needed, agree the approved exchange and processing arrangements with Dalfin AI before sharing them.