Product engineering: from a defined workflow to an operated application
Custom software is justified when an important business workflow cannot be served adequately by the existing tools or a suitable product. The first task is to make that difference explicit so engineering effort is spent on a real operating need.
FI Digital works from the user journey and business rules through architecture, build and release. The scope defines what the first version must do, how it connects to current systems and who will own its operation.
Choose the relevant service
Custom software development
Scope web, mobile and API work around a useful first release.
Selected custom applications
Review geographically labelled group delivery experience.
AI product development
Evaluate where AI belongs in the application and what requires review.
FI Digital UK / Workflow
Product engineering
Illustrative workflow, not a product screenshot or a claim about a client’s production architecture.
Step 5 of 5Resolve with the owner (Needs correction)
Keep scrolling to follow the flow
- Discovery and fitCompare configuration, integration and custom development against the required workflow.
- Product designDefine users, permissions, records and acceptance criteria before expanding the feature list.
- Review and authoriseDecision point
- Release and ownershipPlan deployment, training, documentation and maintenance. Agree source-code and third-party licensing terms in the contract.
- Resolve with the ownerOutcome: Needs correction
What the engagement covers
Discovery and fit
Compare configuration, integration and custom development against the required workflow.
Product design
Define users, permissions, records and acceptance criteria before expanding the feature list.
Build and test
Develop the agreed application and integrations, including exceptional paths and operational controls.
Release and ownership
Plan deployment, training, documentation and maintenance. Agree source-code and third-party licensing terms in the contract.
A practical example
An illustrative business needs a partner application that accepts a request, routes it for approval and shows its current status. A useful first release proves that complete journey rather than launching many disconnected features.
Relevant delivery experience
Australian group delivery example: an anonymous automotive OEM connector was deployed across 232 dealerships in two months using Zoho Catalyst and custom development. Leads transferred in seconds. The client confirmed approximately three hours saved per week at OEM level in total, and approximately one hour per week at each dealership. These are figures for that engagement, not forecasts for another project.
Questions that shape the scope
Use these questions to identify the first decision and the information needed to make it.
- What problem requires custom behaviour?
- What is the smallest useful release?
- How will users accept the work?
- Who owns the code and operation?
Make the UK operating requirements explicit
Separate the UK organisation’s requirements from any wider group template. Identify the legal entity, business owner, connected accounts and the people authorised to accept the result. If the workflow relies on financial or employment rules, your qualified advisers should confirm the applicable settings and obligations; software configuration alone does not establish compliance.
From assessment to an accepted result
Define a useful first release
Agree the user, workflow, expected outcome and acceptance owner. Identify the important unknowns early.
Design the system boundaries
Set out records, interfaces, permissions and dependencies. Make failure recovery part of the design.
Build and review working increments
Review usable work against representative scenarios. Keep decisions and scope changes visible.
Release with an operating plan
Confirm acceptance, rollback, account ownership, documentation and the support arrangement.
Scope and responsibilities
The scope, acceptance criteria, third-party dependencies and operating responsibilities are agreed for the engagement. No partner tier, certification, guaranteed saving or fixed delivery period is implied.
Frequently asked questions
001Should we build custom software or buy a product?
Compare the required workflow, available products, integration effort, control needs and total operating cost. Buying may be sensible where a product fits well. Custom development is more useful when the difference creates material business value. Discovery should make the trade-off explicit rather than assuming a build is always the right answer.
002What do we receive at handover?
The agreement should define the application, source-code arrangements, deployment configuration, documentation, tests and administration access included in the handover. Third-party licences and ongoing services should be listed separately. The team responsible for operation should be able to understand the system’s dependencies and the process for making and releasing a change.
003Can the project start with a smaller first release?
Yes, if the first release covers a useful end-to-end workflow rather than disconnected screens. Agree the user, outcome, acceptance checks and operational owner. Keep later features visible without placing them all in the initial scope. The first release should test the important assumptions and leave a maintainable foundation for the next decision.
004How are cost and delivery time estimated?
The estimate follows the agreed workflow, interfaces, data, permissions and operating requirements. Discovery should expose uncertain dependencies before they become hidden commitments. Break the work into reviewable milestones and state assumptions, exclusions and third-party costs. A fixed number of weeks or a low starting price is not a reliable substitute for a defined delivery scope.
005Can you integrate with our existing systems?
Integration depends on the systems’ available interfaces, access rights, limits and commercial terms. Review the actual records and actions required before choosing a connector or custom interface. Define identifiers, retry behaviour, duplicate prevention and reconciliation. The proposal should distinguish supported actions from capabilities that still require discovery or permission from another system owner.
006Who owns the software and accounts?
Ownership, licensing and access should be explicit in the agreement. Distinguish custom code from existing product components, third-party services and open-source dependencies. Agree where repositories, cloud accounts, credentials and documentation will be controlled, and what is handed over. Do not assume that commissioning a project automatically transfers every underlying software right or provider account.
007How do you test before launch?
Test the business workflow, user permissions, ordinary failures and recovery, using representative scenarios agreed with the people who will operate the result. Include data quality and integration behaviour where relevant. Record acceptance and unresolved issues before release, with a rollback or fallback appropriate to the change. A demonstration of the happy path is only one part of readiness.
008Is ongoing maintenance included?
The proposal should distinguish delivery, warranty or defect correction, and ongoing operational support. Dependencies, usage and business requirements can change after launch, so assign ownership for updates and monitoring. Support hours, response targets and service levels require a specific agreement. They should not be assumed from a general description of development or platform operations services.
Discuss your project
Discuss your project→Tell us about your project
We use the information you provide to respond to this enquiry. Read our Privacy Policy.