From first message to ongoing support.
The nine stages of a typical project. The detail changes by service; the order does not.
- 01
Initial inquiry
You describe the problem and the outcome you want.
- What happens
- A short note or the project form is enough. We read it and reply with questions.
- You get
- A shared first understanding.
- 02
Discovery
We gather requirements and understand how the work happens today.
- What happens
- Interviews, process walk-throughs, and a look at the tools involved.
- You get
- A written problem statement and requirements.
- 03
Assessment
Feasibility, risks, integrations, and possible approaches are evaluated.
- What happens
- We check APIs, data quality, permissions, and volumes before promising anything.
- You get
- Findings and viable options.
- 04
Proposal
Scope, deliverables, assumptions, and commercial terms are defined.
- What happens
- Tailored to your project. No templated price lists.
- You get
- A proposal you can accept, change, or decline.
- 05
Architecture
The solution design and implementation plan are established.
- What happens
- Components, data flow, permissions, and a test plan.
- You get
- A design you sign off before building.
- 06
Development
The agreed system is built and integrated.
- What happens
- Regular updates and a working system in a test environment as early as possible.
- You get
- Working components.
- 07
Testing
Functionality, reliability, and relevant safety requirements are evaluated.
- What happens
- Normal cases, edge cases, failure scenarios, and your own real examples.
- You get
- Test results against agreed criteria.
- 08
Deployment
The solution is deployed in the agreed environment.
- What happens
- Release, handover, and documentation. Rollback plan in place.
- You get
- A live, documented system.
- 09
Support
Maintenance and support are provided under the agreed arrangement.
- What happens
- Fixes, monitoring, and upstream changes as agreed. New features are scoped separately.
- You get
- Ongoing reliability.
The delivery framework
The same eight phases show up across every service page.
- 01
Discover
Understand the business, processes, current technology, and desired outcomes.
- 02
Assess
Evaluate feasibility, risks, constraints, data availability, integrations, and approaches.
- 03
Design
Define the architecture, workflow, components, permissions, and implementation plan.
- 04
Build
Implement the agreed solution using suitable technologies.
- 05
Integrate
Connect the solution to existing systems where technically feasible.
- 06
Validate
Test functionality, integration behavior, failure scenarios, and agreed performance criteria.
- 07
Deploy
Deploy to the agreed environment: client-managed, cloud, or another supported arrangement.
- 08
Support
Provide the agreed maintenance, troubleshooting, monitoring, and improvements.
Deployment, customization, and support
Three things worth knowing before you start.
In an agreed environment, subject to feasibility, infrastructure, security, and access: AUROZEN-managed, client-managed cloud, client-owned servers, or hybrid, where we can support it.
We separate configuration, integration, and substantial new development in each proposal so the scope is never vague.
Monthly support is available as an engagement where appropriate. It is not an automatic promise of unlimited maintenance.
Have a business problem worth solving?
Explain your requirements and we will discuss a suitable approach.