Most IT project failures are not technology failures. They are process failures — unclear requirements, miscommunication between client and provider, scope creep that nobody managed, and handovers that leave the client more confused than when they started. We have seen it happen, and we built our delivery process specifically to prevent it.
Stage 1: Discovery (Week 1)
Every Mandleva engagement begins with a discovery session — not a sales call. We are not trying to sell you anything in this session. We are trying to understand your operation: what systems you currently run, where the pain points are, what you have tried before, and what success actually looks like for your organisation. Most clients tell us this session alone gives them more clarity than months of internal discussion.
We document everything from the discovery session into a brief that both parties sign off on before any work begins. This document is the contract between us on what the project is actually for.
Stage 2: Architecture & Proposal (Week 1–2)
Based on the discovery, we design a technical architecture and produce a detailed proposal. This is not a generic template with your logo on it — it is a document that reflects your specific environment, your constraints, and our recommended approach. We explain why we are recommending each component, what alternatives we considered, and what the risks are. You should be able to read this document and understand exactly what you are approving.
Stage 3: Build & Communication (Ongoing)
During the build phase, we operate on a weekly update cycle. Every Friday, you receive a written update covering what was completed, what is in progress, and whether the project is on track against the agreed timeline. If something changes — scope, timeline, cost — we tell you immediately in writing, not at the end of the project.
Stage 4: Testing & Acceptance
Before we declare any project complete, it goes through a structured testing phase. For software, this means functional testing, user acceptance testing with your team, and a security review. For infrastructure, it means a documented commissioning process. Nothing goes live until both parties have signed an acceptance document confirming the deliverables match what was agreed.
Stage 5: Handover & Support
Handover is where many IT providers disappear. We do the opposite. Every project includes a handover pack — documentation, credentials, architecture diagrams, and a training session for whoever will be managing the system day to day. We offer post-handover support packages for clients who want ongoing managed services, and we remain available for questions even for clients who do not.
This is how we work. If it sounds like the kind of IT partner you have been looking for, we would like to hear from you.
