Engagements
Four ways to work with the implementation team.
The engagement is chosen by where your business is now, not by which product you buy.
4
Engagement models, chosen by where you are now
8
Delivery phases with a stated responsibility split
6+
Platforms taken to production this way
Engagements start in a solution workshop: product scope, user journeys, provider list, and the boundary between platform and integration work, mapped before anything is built.
01
Launch
Businesses moving from concept, licence, or prototype to production.
You have a licence or a regulatory partner and a launch date.
Included
- Product and architecture review
- Web, Android, and iOS applications
- Selected provider integrations
- Production-ready foundation with your branding and core customization
- Standard deployment in your environment
- QA, documentation, training, and launch support
02
Growth
Live businesses adding integrations, products, markets, or capacity.
The product works and the constraint is now capacity or scope.
Included
- Architecture review against current load and roadmap
- New modules and advanced customization
- Additional provider and corridor integrations
- Performance and security work
- Analytics and operational reporting
- Managed maintenance
03
Platform Modernization
Companies outgrowing scripts, technical debt, or a rigid platform.
You are paying recurring fees for a platform you cannot change.
Included
- Current-state assessment and migration roadmap
- Architecture redesign
- Data migration
- Interface modernization
- Integration rebuild
- Controlled cutover with rollback planning
04
Enterprise
Regulated or higher-volume operators with institutional requirements.
Procurement, audit, and security review are part of the buying process.
Included
- Enterprise architecture and high availability design
- Dedicated product team
- Advanced security work and disaster recovery
- SLA with defined response and resolution targets
- Audit logs, roles, and permissions
- Long-term roadmap execution
Dedicated FinTech engineering
Available across all four engagements once a product is live. A product, integration, maintenance, mobile, or modernization squad working to your priorities with predictable capacity.
How pricing works
Platform licence, implementation, customization, integrations, infrastructure, security, and ongoing support are priced separately so you can see what each part costs. You receive an itemized proposal after the scoping call, so every line can be questioned before any commitment is made.
Implementation
How a launch actually runs.
Eight phases. The responsibility split is stated at each one, because unclear ownership is what delays regulated launches.
01
Qualification
Assess fit, scope, and whether the foundation suits your business model. Decline early if it does not.
Share the business model, regulatory position, and launch constraints.
02
Solution workshop
Map product scope, user journeys, provider list, and the boundary between platform and integration work.
Bring the product decisions and the commercial constraints. Paid discovery is used where scope is complex.
03
Architecture
Produce target architecture, deployment model, data model, and integration design. Document it.
Approve the architecture. Confirm the cloud or data-centre environment.
04
Implementation
Customize the foundation to the agreed scope. Build the workflows and product logic your business requires.
Review builds against scope. Keep decisions moving.
05
Integration
Connect your selected providers and handle the technical integration, testing, and error handling.
Hold the provider contracts, credentials, and commercial terms. Provider approval timelines are yours.
06
Testing
Functional QA, integration testing, security hardening, and load testing against agreed targets.
User acceptance testing. Any external audit or penetration test you require.
07
Launch
Production deployment, cutover support, monitoring setup, and a defined hypercare period.
Regulatory approvals, operational readiness, support staffing, and the go-live decision.
08
Ongoing development
Managed maintenance, SLA support, or a dedicated squad continuing the roadmap.
Set the roadmap priorities. The product is yours to direct.
Licensing, legal compliance, banking relationships, provider contracts, business operations, internal approvals, and regulatory reporting remain the client's responsibility unless separately agreed in writing.
Implementation duration depends on scope, integrations, regulatory readiness, and customization. AppDevs does not publish a universal launch timeline, because a number that ignores your provider approvals would not be a real commitment.