Some technology questions need an answer before they need a build. We assess the systems you have, review their architecture and security, and set out what to build, buy or retire. You should be able to act on the advice with us or with someone else.
What we cover
The output is advice and a plan that your organisation can act on.
- 01
Digital strategy
A plan for which parts of the organisation move to software, and in what order.
- 02
Technology assessment
A review of the code, architecture and security of a system, including one built by another vendor.
- 03
Process optimisation
A look at how the work is done today, and which steps software should take over.
- 04
IT architecture
A recommended structure for your systems: what runs where, and how the parts exchange data.
- 05
Security consulting
A review of where a system is exposed, with the findings reported in plain language.
- 06
Project management
Keeping a technology project to its scope and to its order of work.
How the work runs
This is the short version. The full one is on the page about how we scope and quote a project.
- Step 01
Agree the question
We agree what has to be decided and what you will receive. The deliverables are settled before the work starts.
- Step 02
Assess
We review the systems you have: their code, their architecture and their security.
- Step 03
Report
You receive written documents, such as an assessment of the current systems, a recommended architecture, or a plan with the steps in order.
After the report
A consulting engagement ends with documents, not with a launch. The plan is yours to use with any team. If you want us to build it, our development services are available, and that is a separate decision.
- 01
Build with us
The plan becomes the starting point for a scope, and the quote follows the scope.
- 02
Build with another team
The documents are written in plain language, so that another team can act on them.
Tools
These are the tools we build with ourselves, so they are the ones we know best. A recommendation can also be to buy a product, or to retire one.
- 01
Interfaces
What a person sees and uses in the browser.
- React
- Next.js
- TypeScript
- Tailwind CSS
- 02
Server side
The data, the rules and the APIs behind the interface.
- Laravel
- Node.js
- Python
- GraphQL
- 03
Mobile apps
One codebase that serves both iOS and Android.
- React Native
- 04
Hosting and infrastructure
Where the software runs once it is live.
- AWS
- Docker
- Firebase
Questions
What does IT consulting from Durrani Lab cover?
It covers digital strategy, technology assessment, process optimisation, IT architecture, security consulting and project management. The output is advice and a plan that your organisation can act on.
When should we hire a consultant instead of starting development?
Hire a consultant when the right approach is not yet clear, for example when choosing between building and buying, or when an existing system keeps failing. An assessment first can prevent a build that solves the wrong problem.
What do we receive at the end of a consulting engagement?
The deliverables are agreed before the work starts. They are usually written documents, such as an assessment of the current systems, a recommended architecture, or a plan with the steps in order.
Can you review software built by another vendor?
Yes. A technology assessment can cover code, architecture and security of a system built by someone else. We report what we find in plain language.
If we take your advice, do we have to build with you?
No. The plan is yours to use with any team. If you want us to build it, our development services are available, and that is a separate decision.
Related services
CRM, ERP and internal systems for organisations that have outgrown their spreadsheets.
More on custom softwareCloud architecture, migration and release pipelines for teams whose software has to stay up.
More on cloud and DevOps
Start here
Describe the systems you have and the decision in front of you. A few lines are enough to begin.