NaturalSoftware Consultants

Software system reviews · Architecture consultancy · Sale, Greater Manchester

See the shape of your software before you decide what to do with it.

Natural Software Consultants reviews existing systems and advises on architecture for organisations that depend on software they did not always design. We read the code, the infrastructure and the way your team works, then tell you plainly what is sound, what is fragile and what is worth changing first.

Describe your systemHow a review unfolds

Illustrative image: a quiet garden courtyard seen through tall glazing, with an ochre lounge chair beside the window
Our working stanceUnhurried attention, precise notes, and recommendations you can actually act on.

The kind of question we are usually asked

Most people contact us at a fork in the path. The system works, mostly, but every change feels heavier than it should. A new product line, a merger, a growth plan or a departing lead engineer has made the question urgent: can this software carry us through the next three years, and if not, what exactly needs to change?

That question deserves a better answer than a gut feeling or a supplier's sales pitch. We give it a structured, evidence-based review: what the system is made of, how its parts depend on each other, where effort and risk are concentrated, and which changes would return the most for the least disruption. You keep ownership of every decision; we make sure you make it with clear sight.

Illustrative image: courtyard planting framed by tall glazed panels

Practice one

System reviews

A system review is a fixed-scope look at software that already exists. We examine the codebase, its dependencies, deployment arrangements, data model, test coverage and the operational record, and we talk to the people who build and run it. The output is a written findings report ranked by consequence, not a list of everything that could theoretically be better.

  • Code structure and the cost of change
  • Dependencies, versions and end-of-life exposure
  • Data model integrity and integration points
  • Deployment, environments and recovery arrangements
  • Observability: can you tell when something is wrong?
Read about system reviews

Practice two

Architecture counsel

Sometimes the system has not been written yet, or a significant part of it is about to be rewritten. Architecture counsel is a short engagement where we work alongside your team or supplier on the structural decisions: boundaries between services, how data moves, what should be bought rather than built, and which choices are hard to reverse.

We write decision records with you, challenge assumptions respectfully and leave behind a design your own engineers understand and can defend. We do not take over delivery, and we have no product or hosting to sell you, which keeps our advice independent.

Read about architecture counsel
Illustrative image: an ochre chair and low table beside a window onto planting

Where would a review begin for you?

A short orientation, not a diagnosis. It reflects how we would usually open the conversation.

Which of these sounds most like your week?

Choose the statement closest to your situation and we will suggest where a review would usually start, what we would look at first and what you would receive.

What you actually receive

Every review ends in a findings report written for two audiences at once: the people who fund decisions and the people who will carry them out. It opens with a two-page summary in plain English and then sets out each finding with its evidence, its consequence if ignored, a recommended response and a rough sense of effort.

Alongside the report you receive an annotated map of the system as it really is, which is often the first accurate picture anyone has had, and a short read-out meeting where your team can question every conclusion.

See how a report is structured

Finding, as it would appear

Observation
Order processing and invoicing share one database table with no ownership rules.
Evidence
Schema, write paths in two services, three incidents in the operational log.
Consequence
Either change can silently break the other; testing cannot catch it reliably.
Response
Assign ownership, introduce a narrow interface, migrate in two steps.
Effort
Moderate. Weeks, not months, for a team that knows the code.

Illustrative example of format, not a client finding.

How a review unfolds

  1. Conversation

    A free initial call to understand the decision you face and whether a review is the right tool. Sometimes it is not, and we will say so.

  2. Scope and access

    We agree in writing what is in and out, who we will speak to and how access is granted. Read-only access is almost always enough.

  3. Reading the system

    Quiet, careful work: code, configuration, history, documentation and interviews. We share early concerns as they arise rather than saving surprises.

  4. Findings and read-out

    The written report, the system map and a session to talk it through. Questions afterwards are part of the service.

The full approach, with timings

What we need from you

A review goes faster and lands better when a few things are ready. None of them need to be perfect; part of our job is working with what exists.

Honest limits

We are not auditors. A review is professional technical opinion, not a certification, penetration test or compliance sign-off. Where we see security or regulatory concerns we will flag them and suggest the right specialist.

We do not build your product. We do not manufacture software products or sell licences, and we do not take on long implementation contracts, so there is no incentive to inflate the problem.

Time-boxed means time-boxed. A review looks deeply at what matters most. If something important falls outside the agreed scope, we tell you and you decide whether to extend.

What good work looks like to us

Every finding traceable to evidence. Every recommendation sized and sequenced. Every sentence readable by someone who did not write the code.

We judge our own work on whether your team can act on it the following Monday. That means naming specific files, services and decisions rather than general principles, and being clear about confidence: what we verified, what we inferred and what we could not see.

Questions people ask first

How long does a review take?

A focused review of a single product typically runs two to four weeks of elapsed time, depending on size and how quickly access is arranged. We agree the timeline before starting.

Do you need write access to our systems?

No. We ask for read-only access and never change your code or infrastructure during a review.

Can you review work done by our supplier?

Yes, and we do so fairly. We aim to give the supplier a chance to respond to findings, because a review that produces a stand-off rarely helps you.

What happens after the report?

Questions about the report are answered as part of the engagement. If you want help sequencing the changes or checking progress later, we can agree a short follow-up.

Tell us about the system and the decision in front of you.

A few paragraphs are enough. We reply within two working days, Monday to Friday, 09:00 to 18:00 UK time.

Start the conversation Existing client support