Define before developing.
The proposed approach provides a working structure. Deliverables and commitments are agreed for each project.
Scope
Describe processes, users, constraints and acceptance criteria.
Proposed deliverable: scope and requirements brief.
Design
Define data, permissions, integrations and hosting conditions.
Proposed deliverable: architecture and specifications.
Develop and integrate
Develop in stages, connect existing systems and migrate data.
Proposed deliverable: successive releases and technical documentation.
Verify
Test workflows, migration, access rights and agreed recovery scenarios.
Proposed deliverable: acceptance test plan and results.
Deploy
Prepare documentation, onboarding and operational responsibilities.
Proposed deliverable: operational handover package.
Maintain
Fix, enhance and support users on the agreed terms.
Proposed deliverable: maintenance agreement and support procedure.
Control is defined in the architecture and the contract.
Hosting location, administrator access, key management, backups, data export and exit arrangements: these choices need to be explicit. The word "sovereign" is not a substitute for them.
Before getting started
Where will the software be hosted?
The choice depends on project constraints. No hosting location or service level is assumed before scoping.
Is there a ready-to-deploy product?
We develop software suited to each organisation. Scope, components and commitments are defined during scoping.
Can you show past work?
Applications and projects delivered for our clients are not presented publicly without their permission. In a conversation, we can describe our approach without disclosing confidential information.
Can I send a confidential file?
Not through the website, social media or an introductory email. Appropriate sharing rules and a channel must be agreed first.
Discuss your project.
An initial conversation to understand the context, users and constraints.
Discuss your project