Every project starts with your business requirements. We then assess the solution, cost and delivery approach.
Share your project briefTell us about the problem, the users and the intended outcome. We discuss the workflow and constraints before choosing technology.
Current systems / Users / Goals / Indicative budget and timeline
OUTPUTA brief and a list of questions to investigateReview data readiness, integrations and the operating environment. Compare suitable approaches. Any discovery work or proof of concept is scoped before it starts.
Feasibility / Data and access / Integrations / Risks
OUTPUTA proposed solution direction and initial scopePrepare a proposal covering deliverables, schedule, pricing and terms. Identify related costs such as licences, cloud usage and support based on the assessment.
Included and excluded scope / Milestones / Acceptance criteria / Support scope
OUTPUTA solution proposal and quotation for reviewDeliver the agreed scope in reviewable stages and test integrations. Changes are assessed for their effect on cost and schedule before implementation.
Project contacts / Reviews / Test environment / Change control
OUTPUTWorking increments and test resultsRun user acceptance testing, plan data migration and proportionate rollback, then provide the documentation and training included in scope.
UAT / Access / Backup / Launch plan / Handover documentation
OUTPUTA launch-ready system and handover recordAgree on support channels, service hours, ownership and response levels. Review improvements as usage and business needs change.
Service hours / Response levels / Maintenance / Backup and monitoring
OUTPUTAn agreed support arrangement and improvement planBring your goals, examples and any information about existing systems. A TOR or RFP can be shared with the team by email.
Start the conversationWe discuss your brief, assess requirements, prepare a solution proposal and quotation, build and integrate, test and go live, then provide the agreed support. Responsibilities and acceptance criteria are defined together.
Share your goals and context with the team. You can attach a TOR or project brief to an email so we can discuss requirements, constraints and the systems involved.
Service hours, contact channels and support scope are defined in the project proposal or agreement. Confirm those details before work begins.
