Development through prototypes, testing and acceptance
Turn requirements into a working prototype, then develop in stages against features and acceptance criteria, with business users involved throughout.
Requirements and working prototypes
Confirm users, workflows and data sources, try key screens, and define first-phase features and exclusions.
Stage deliverablesWorkflows, prototypes and acceptance criteriaDevelopment and scenario testing
Implement features and test roles, validation and error handling. Check interfaces and licensing for external services.
Stage deliverablesTestable releases, test records and issue logsLaunch and maintenance handover
Confirm deployment, backups, administrator accounts and operational checks, then provide usage instructions, version handover and support responsibilities.
Stage deliverablesApproved release, deployment and administration documents
Checks before handover
- Main workflows and permissions for different roles have been tested.
- Error notifications, backups and rollback are arranged.
- Source code, data, third-party costs and maintenance responsibilities are specified.
Features, timelines, source code and intellectual-property arrangements follow the project agreement. Third-party interfaces, platform approvals and AI output quality require separate verification.
Start with one clear, repetitive process
Begin with data collection, preparation, notifications, reporting or follow-up. Identify who performs each step, when it happens and who receives the result. Customer updates, form follow-up, inventory exchanges and task notifications can all be discussed. Automate the parts with clear rules first, keeping judgement and approval with designated people.
- When the process starts, the data it uses and the expected result.
- How data moves between websites, apps, forms and business systems.
- Which steps repeat consistently and which need a person's decision.
- The effect of errors, omissions or delays on colleagues and customers.
Assess APIs, data exchange and connection permissions
Integration options include APIs, data exchange, file imports and exports, and custom connections to existing systems. Review available interfaces, formats, third-party licences and access restrictions before choosing an approach and defining development work. Supplier terms vary, so data ownership and maintenance responsibilities also need to be clear.
- Use only authorised data and connection methods.
- Assign read, write and administration permissions, protecting service accounts and connection secrets.
- Define field mappings, validation and duplicate handling.
- Specify approvals for external sending, deletion, data changes and other consequential actions.
Test exceptions as well as the normal workflow
Start with a limited-data prototype, then test valid input, missing data, duplicate requests, connection failures and permission changes. Before retrying, consider duplicate notifications or writes, and make important results verifiable. Agree which exceptions should stop the process for a person to handle before a phased deployment.
- Define successful results, error notifications and the person responsible for follow-up.
- Test retries, reconciliation and necessary recovery or remedial steps.
- If AI is used to prepare content, arrange output checks and any required human approval.
Plan records, deactivation and future changes
Assign responsibility for accounts, connection settings, execution records and exception notifications. Log content, access and retention should match the purpose without storing passwords or excessive sensitive data. Plan checks, access removal and unfinished-work handover when a third-party system changes, fields are updated or a workflow is retired.
- Provide the workflow idea, existing systems, data formats and processing frequency.
- If no platform has been selected, start with a process diagram or sample data.
- Identify approvers, steps that must remain manual and common exceptions.
- Explain the first improvement you want, target dates and arrangements with existing suppliers.
- List ongoing monitoring, changes, support and third-party charges separately in the proposal.
Functions, integrations, acceptance and ongoing support are subject to the agreed proposal.
Information and references
Suitability and enquiry preparation
When is this service suitable?
Common needs
- Repeated data entry causes errors or missed follow-up.
- Forms, email, approvals and notifications pass manually between colleagues and need a clear workflow.
- Websites, CRM or management tools need data exchange and integration assessment.
Which service do I need?
- Custom websites, applications and internal systems
Plan front-end features and internal systems around work requirements.
- AI work assistants and knowledge search tools
Assess which enquiries and document tasks suit AI assistance.
- Business data backup and recovery planning
Plan recovery from workflow errors or accidental deletion.
Prepare for an enquiry
- Who performs each step, which tools they use and approximate volume.
- Steps to automate and actions that still require human approval.
- Current software/platform names, interface availability and target completion date.
For an initial enquiry, describe the issue and equipment only. Do not submit passwords or verification codes. The team will arrange a secure channel for sensitive documents and incident records.
EnquireWorkflow automation and system integrationCybersecurity and AI useExplore security planning, responsibilities and acceptance considerations
Cybersecurity · Safe AI use
Software development and integration: security planning priorities
「Workflow automation and system integration」 includes the following security priorities; measures, tests and deliverables are specified in the proposal.
- Data and sign-inArrange authentication, data access and approvals around users and workflows, with clear purposes for company, development and test data.
- Integration and recordsCheck external interfaces, accounts and licensing, protect credentials, and plan logs for important actions, errors and changes.
- Testing and recoveryTest normal operation, invalid input and permission boundaries. Confirm release, backup, shutdown and rollback arrangements before deployment and maintenance handover.
AI considerationsAI queries must follow authorised data and user permissions. Restrict tool read/write access and retain human approval for important operations. Test malicious instructions in external content, data leakage and incorrect results.
Planning and acceptance recordsRequirements and acceptance checklist, software version, function and permission tests, deployment documents, and administration and maintenance responsibilities.
You may also want to know
Can we start by improving just one repetitive data-entry step?
Yes. Identify the input, output and systems involved, then assess a prototype and test plan for one clear workflow. Confirm results and manual takeover before discussing further steps; you do not need to rebuild every system at the outset.
Can existing systems exchange data through new integrations?
Describe the systems and required data flow so APIs, licensing, formats and restrictions can be assessed. We can then discuss connector development, data exchange, imports and exports, or steps involving people. Development and third-party work are defined after assessment.
How can staff take over if an automated process fails or data is wrong?
Define stopping conditions, notifications, records and responsible staff so completed, incomplete and unverified work is clear. Test retries, corrections and necessary recovery to avoid continuing errors or duplicate processing.
