Case studies

What we were asked for, and what we delivered

Each study states the brief, the work carried out and the deliverables the client signed off.

Business analysis

Business challenge: Work ran across both automated systems and manual steps, with no single documented account of how a process actually happened or where the gaps sat.
Solution: Offsite stakeholder interviews, requirement-gathering workshops and As-Is analysis of the current system and workflows, modelled in BPMN. Findings are written up as Business Requirement Documents and Standard Operating Procedures, with To-Be requirements defined against the gaps.
Technologies used: BPMN
MS Visio
draw.io
Jira
MS Office
Business outcome: SOP and BRD sets are issued workflow by workflow, giving the organisation a single documented account of how each process runs.

Programme management

Business challenge: A national rollout needed both a defensible vendor selection process and operational sites genuinely ready to run the new systems when they arrived.
Solution: Phase one developed the business readiness approach, models, strategies and policies, contributed to the bidding documents and supported vendor selection. Phase two produced the rollout plan, readiness assessments across operational locations, training materials and delivery.
Technologies used: Business readiness assessment
Bid documentation
Train-the-Trainer
Programme reporting
Business outcome: Every major deliverable — readiness models, bidding documents, rollout plan, readiness reports, training manuals and the closure report — was approved by the Federal Transport Authority.

Programme management

Business challenge: A system integrator had been appointed to design, develop, implement and maintain the platform, but the council needed independent technical capacity to hold that contract to its stated requirements.
Solution: Programme management across stakeholders and the field team, vendor management against contract compliance, review of the SRS and SDD, and assessment of delivered modules against both the SRS and the RFP separately.
Technologies used: SRS and SDD review
UAT management
Vendor governance
Technical documentation
Business outcome: Each milestone was accepted against documented criteria — inception approach, SRS, SDD, implementation approach, module testing and gateway integration.

Solution design

Business challenge: The development team needed requirements, architecture and infrastructure sizing settled up front for a marketplace spanning admin, seller and buyer experiences.
Solution: Requirements and workflows across all three portals, a full security architecture, integration design for payments and ERP, and infrastructure sizing delivered as a build-ready specification.
Technologies used: Balsamiq
Figma
MS Visio
Jira
MS Teams
Business outcome: Delivered as a system architecture document, wireframes, workflow documentation, technical diagrams and a project scope document the team could build directly from.

Solution design

Business challenge: The platform carried three distinct user roles with overlapping workflows, and development could not start without one specification covering all of them.
Solution: Domain research, process flowcharts and a Software Design Document specifying every role-level workflow, from shipment creation through to electronic proof of delivery.
Technologies used: Software Design Document
Process flowcharts
Requirements analysis
Business outcome: The development team received complete system workflows and technical guidance covering all three roles.

Business analysis

Business challenge: The concept needed testing against its market and translating into requirements before any development commitment was made.
Solution: Detailed business analysis, SWOT analysis of the proposition, and a Business Requirements Document covering platform scope.
Technologies used: Business analysis
SWOT analysis
BRD
Business outcome: The client moved from concept to a signed-off requirements baseline ready for development.

Send us the brief, the RFP, or a paragraph describing the problem. A consultant reads it and replies within one business day — no sales sequence.