For software owners, operators and technical sponsors
Software built around the way your business works.
Review the tools you use, the work your team actually does and the functions you are missing. Compare keeping, extending or replacing the current system, then scope a maintainable solution and a realistic migration path. Add AI only where it has a clear purpose and can be tested.
Start with a scoped review. Development, migration and ongoing support are estimated after requirements and access rights are understood.
What we review
- Real workflows Who does what, where information moves and where work is repeated.
- Current software and costs Licences, integrations, administration and support, not only a monthly subscription.
- Gaps and constraints Required functions, user roles, data quality, reporting and switching risk.
- Access and rights Permitted inputs, APIs, source code where authorized, data ownership and third-party terms.
What an agreed review can produce
A review can set out alternatives, a prioritized scope and a way to test the most important workflow. Where development is justified, a proposal can cover acceptance criteria, migration checks, documentation and support responsibilities. Keeping or configuring the current product may be the right recommendation.
- Options review
- Scoped pilot
- Migration plan
- Handover and support plan
Workflows to discuss
Examples include job tracking, approvals, operational reporting, equipment availability, and customer or partner portals. The aim is to fit an agreed workflow, not reproduce every screen and feature of another product. Diagrams and prototypes can illustrate a proposed workflow.
From review to operation
- Review Establish the sponsor, objective, permitted materials and current workflow.
- Compare Assess keep, configure, integrate, extend and replace options, including no-build.
- Pilot Test a narrow end-to-end workflow against agreed criteria before a broader commitment.
- Migrate If needed, agree data checks, permissions, reconciliation and rollback in advance.
- Operate Document handover, access, maintenance and incident responsibilities.
Compare the full cost, not only the subscription
A useful comparison includes discovery, development, migration, hosting, licences, maintenance, support and the effort of changing how a team works. Custom software is not automatically cheaper. The review should make trade-offs visible before a build decision. Code, licences, hosting, data export and support responsibilities are agreed in writing; no blanket ownership or perpetual support is implied.
Work within authorized access
Work begins with a clear purpose and authorized access. Requirements, documented interfaces and permitted observation are preferred starting points. Source-code or deeper technical analysis requires appropriate rights and a defined scope. Licence bypass, unauthorized copying and access-control circumvention are outside this service. Security testing is not included by default.
Questions about software reengineering
Can you replace every feature of our current software?
No feature parity is assumed. We agree required workflows and acceptance criteria first.
Will custom software be cheaper?
Not necessarily. The comparison includes implementation, migration and ongoing ownership costs. Keeping the existing tool may be better.
Do you need the vendor's source code?
Often no. Work can begin from requirements and permitted workflows. Any source review needs appropriate rights.
What happens to our data?
Access, migration checks, hosting and retention are agreed before handling production data. The first enquiry needs only a short non-sensitive description.
Will we own the code?
Rights to new work and third-party components depend on the agreed contract and licences. These are defined before development.
Who maintains the result?
The proposal identifies the operating owner, documentation, included support and separately scoped maintenance. No unstated service level is promised.
Start with one workflow that is not working well
Tell me which software you use, who uses it and what you would like to improve. Approximate costs are useful but optional. Do not send source code, credentials or confidential files in the first message.
Initial discussion only · access, rights and scope are agreed before work begins.