Clear requirements, sound architecture and a plan that can be delivered.
Before money is committed to a system, we help you define what it must do, how it should be built and how it will be delivered.
- What we deliver
- Requirements documentation
- Solution architecture
- Implementation planning
Most failed technology projects fail before a line of code is written: in vague requirements, unexamined architecture or plans nobody believes. We work on those first.
Grounded in delivery
Our recommendations come from teams that build, secure and run systems.
Written to be used
Documents your procurement, technical and leadership teams can all work from.
Usable by any delivery team
Specifications and plans stand on their own, whoever builds the system.
Where we help most
A mandate without a specification
Leadership has set a goal; nobody has defined what the system must do.
Vendor proposals that cannot be compared
Each bid answers a different question, because the question was never written down.
An architecture that grew by accident
Systems were added one at a time, and now nobody can change one safely.
A plan nobody believes
Timelines were set before scope, so the plan slips from the first week.
What we deliver
Requirements documentation
What the system must do, for whom and under which constraints, agreed with the people who will use it.
- Requirements specification
- User stories
- Acceptance criteria
Solution architecture
How the system should be built and integrated, with the reasoning behind each decision.
- Architecture diagrams
- Decision records
- Integration map
Implementation planning
Scope, milestones, dependencies and risks, in a plan that can be procured and delivered.
- Milestone plan
- Risk register
- Procurement-ready scope
How a consulting engagement runs
Short, defined engagements that end in documents you can act on.
Step 1: Understand
Goals, users, constraints and existing systems.
Step 2: Define
Requirements written and agreed.
Step 3: Design
Architecture options and a recommendation.
Step 4: Plan
Milestones, dependencies and risks.
Step 5: Hand over
Documents walked through with your teams.
What you receive
- Requirements specification
- Agreed with users and owners
- Architecture and decision records
- Options, trade-offs and the recommendation
- Implementation plan
- Milestones, dependencies and risks
- Procurement-ready scope
- Comparable bids from any supplier
Government & public institutions
Revenue administration, public-sector systems, data protection
Education & scholarship administration
Identity verification, Microsoft 365 licensing and training
Financial services
ISO/IEC 27001 and PCI DSS certification support
Starting something new?
Tell us the goal and the constraints; we will help you define the rest.