Software consulting for companies that build or buy software
Software consulting for the decisions that are expensive to get wrong: whether to build or buy, how a new system should be designed, whether the code you already paid for is sound, and what to do with a project that has stalled. We review, decide with you and write it down, and because we also build software, the advice is grounded in what delivery really takes.
- No minimum contract: book a few hours or a full project
- Scope agreed in writing before work starts
- Independent advice: no reseller commissions
This page covers decisions about one application: build, buy or rescue. For IT strategy across the company, such as cloud services, admin rights and the order of system purchases, see IT consulting.
What is software consulting?
Software consulting is expert advice on one application or one software project, rather than on your IT as a whole. A software consultant looks at the business problem, the options for solving it with software, the design and the code, and the supplier relationship, and turns that into a clear recommendation. It is the work that happens before a large build is signed, at a review point in the middle of one, or when something has gone wrong and you need an outside view you can trust.
It differs from IT consulting, which maps every system a company pays for and decides what to buy, keep or remove. Software consulting goes one level deeper, into a single system: its architecture, its data, its code quality and its roadmap.
When companies ask for software consulting
- Before a build. You have an idea or a requirement list and need to know whether to build, buy or adapt something, and what a sensible first version is.
- Before signing a supplier. Three quotes that differ by a factor of three, and nobody in-house who can tell why.
- In the middle of a project. Releases slip, every change breaks something else, and the supplier says the next phase will fix it.
- After a handover. You inherited an application from a supplier or a former employee and need to know what you own.
- Before an investment or acquisition. A buyer or investor asks what state the software is in, and you want the answer before they find it.
In each case the goal is the same: a decision you can defend, written down with the reasons, so the next person who asks why the software was built, bought or replaced finds the answer in the report rather than in a former colleague's memory.
What our software consulting covers
- Build or buy. The ready-made products that come closest, what they cost over three years, where they fall short, and what a custom build of only the missing part would take.
- Scope and first version. The smallest version that solves the real problem, written as a scope any supplier can quote on.
- Architecture review. How the system is split, where the data lives, how it connects to other systems and how it will grow.
- Code and security review. Structure, tests, dependencies, access control and deployment, with findings ranked by risk.
- Supplier review. Quotes, contracts and delivery plans read side by side, with the questions that expose the differences.
- Project rescue. A short, honest assessment of a stalled project and a plan to finish, fix or replace it.
Build or buy: how we decide
Most software problems are already solved by a product, and buying is usually faster and safer than building. We start there. Building pays off in narrower cases: when the software is how you compete, when your rules are too specific for any product to model without workarounds, when per-user fees grow faster than the business, or when the ready-made products cannot connect to the systems you depend on. Often the answer is a mix: a standard product for the common parts and a small custom piece for the part that is yours. We write the reasons down, so the decision can be revisited when circumstances change.
| Signal | Points towards |
|---|---|
| Your process is the same as most companies in your sector | Buy |
| Staff keep spreadsheets next to the product to work around it | Build the missing part, or adapt |
| The software is part of what customers pay you for | Build |
| Licence costs grow with every hire | Compare a build over three years |
| Nobody in-house will own the system after launch | Buy, or build only with a maintenance plan |
Code and security reviews
A code review answers a simple question: is this a foundation you can keep building on? We read the repository, run the tests if there are any, check how the application is built and deployed, and look at the third-party packages it depends on. Security is reviewed against the categories that matter in practice. The current OWASP Top 10:2025 (read 10 November 2026) ranks broken access control first and lists software supply chain failures third, ahead of injection. Both are common in business applications: users who can see data that is not theirs, and outdated or abandoned packages nobody is tracking.
The report ranks every finding by risk and effort, separates "fix this week" from "plan this quarter", and is written so your supplier can respond point by point. We do not need to be the ones who fix it.
Rescuing a stalled software project
Stalled projects share a pattern: the scope grew, the foundations were rushed, and every release now takes longer than the one before. The fix is rarely more people. We spend a short, fixed time with the code, the backlog, the contract and the team, and come back with one of three recommendations: continue with a smaller scope and a firm release plan, pause to repair the foundations that slow everything down, or stop and replace with a product or a rebuild. Each comes with an estimate of time and cost, and with the first steps for the next two weeks. Many stalled projects never had a written specification; our software requirements specification guide shows how to write one.
Ownership protects you
Many software problems turn out to be ownership problems. The code is in the supplier's account, the cloud subscription is on someone's personal card, and the domain belongs to a former employee. Part of every review is a check of what you actually own: the source code repository, the hosting accounts, the domains, the app store listings and the data. Where something is not in your company's name, we tell you how to move it, and we check that someone in the company knows how to renew each account, licence and domain before it lapses. That is the standard we hold our own builds to as well: the code sits in your repository and custom systems run on hosting in an EU data region.
How an engagement runs
- Brief. The decision you need to make and what you already know.
- A written hour estimate. What we review, what you receive and by when.
- Review. Documents, code, contracts and short conversations with the people involved.
- Recommendation. A written report with options, costs and the one we recommend, walked through with you.
- Next step, if you want it. We can build it, support your team, or step back while your supplier delivers.
If the question is how a team should organise the work, see our guide to software development methodologies; for the wider picture, see software development trends and challenges. Our hourly rate is public: see prices. For how to choose a technology stack, read software development technologies; for checking a supplier before you sign, read how to choose a software development partner.
Advice from a team that builds
We design, build and run software ourselves, from custom business software to mobile apps, and our own apps are live on the App Store: see our apps. That keeps the advice practical. A recommendation that sounds good in a meeting but cannot be built on time and budget is not a recommendation. Related: internal tools, AI consulting and digital transformation.
Questions we get
What is software consulting?
Expert advice on one piece of software: whether to build or buy it, how it should be designed, whether the code you have is sound, and what to do when a project stalls. The result is a decision and a plan, written so any team can act on it.
What is the difference between software consulting and IT consulting?
IT consulting looks at all the systems a company pays for and decides what to buy, keep and remove. Software consulting goes deep on one application: its design, its code, its supplier and its roadmap.
Can you review code another company wrote?
Yes. With read access to the repository we review structure, tests, dependencies, security and how the application is deployed. You get a written report with findings ranked by risk, and the supplier gets the same list so they can respond.
Our software project is late and over budget. Can you help?
Yes. We start with a short review of the code, the backlog and the contract, then recommend one of three paths: continue with a smaller scope, fix the foundations first, or stop and replace. Each path comes with a time and cost estimate.
Do you only advise, or can you build too?
Both. We build custom software, so our advice is tested against real delivery. You can use the recommendation with us, with your current supplier or with anyone else; the material is yours.
How is software consulting billed?
By the hour, with a written estimate before we start and any overrun agreed with you first. A focused review is usually a matter of days, not months.
Get a written quote
Tell us in a few lines what you need. We reply within one working day with a written quote: scope, timeline and a fixed price or an hour estimate. Asking is free and commits you to nothing.