About

How this studio works, and what it will tell you

An about page is normally built from client logos, years in business and photographs of a team. This one is not, and it says why rather than filling the space.

What this is

A software studio working across four disciplines
For small and mid-sized organisations

Nova Script Solutions builds web and mobile applications, tests software, designs interfaces and looks after systems that are already live. A job can need two of those at once.

The work it suits best is the kind where somebody does something repetitive by hand every week: enough process that manual effort is expensive, small enough an organisation that one team can still change how things are done.

The purpose is unglamorous and worth stating plainly — taking tedious work off people so their time goes somewhere that needs a person.

How we work

Scope first, in writing, before anyone commits

Nothing is built before it is written down. Scoping produces a document describing the work — screens, open questions, what we would not build, and a cost range rather than a number — and it stays true whoever ends up doing the job.

That means you can take it to another supplier. This is deliberate: a scope you can only use with us is a sales document, and we would rather lose the work at that stage than three months in.

A range comes before a number, always. Anyone quoting a figure on a first call is either guessing or pricing a job other than yours.

Scope

Where the answer is somebody else

Work turning on medical, legal or financial regulation in a jurisdiction we would have to learn. Requests to rescue a failing build against a fixed public date. Jobs where the honest answer is that a spreadsheet already does it.

Each of those is better said in the first exchange than after a proposal. It costs a sale and saves a bad engagement, and it is the part of this you should test first.

Before you commit

What you will be told, whether or not it helps us

  • What is still uncertain

    The parts of the scope we are least sure about, and what would resolve them. Uncertainty that is named can be planned around; uncertainty that is smoothed over in a proposal becomes a change request.

  • What depends on you

    The decisions, the access and the test data that have to come from your side, and what stalls without them. It is the part of a timeline a supplier does not control, and it is the part a proposal usually leaves out.

  • What we would not build

    The parts we think are not worth their cost, with the reasoning. You are free to overrule it — it is your money and sometimes your judgement is better — but you will know our view.

  • When the answer is not software

    Some processes should be changed rather than automated, and some should be left alone. If that is what scoping shows, that is what you get told.

  • What you own at the end

    What the scope says about who holds the code, the accounts and the credentials. Settled in writing at the start, because that is what makes leaving possible.

What is not on this site

The absences here are deliberate

You will have noticed what a page like this normally contains and this one does not. Rather than leave you guessing, here is the list.

  • No client names or case studies This site does not publish them. If relevant work matters to your decision, ask in the enquiry and it can be discussed directly.
  • No team photographs or biographies You will find out who you are dealing with in the first conversation, which is a better test than a headshot.
  • No counters or awards No projects-delivered figure, no satisfaction percentage, no badges. Numbers on a website cost nothing to type, so they prove nothing.
  • No prices Cost drivers are set out on each service page and in the questions. A price before scoping would be a guess with a currency symbol in front of it.
  • No technology logos The stack follows the job. A wall of framework logos tells you what a studio owns, not what your problem needs.
Cost and timing questions

Test it with something small

Send the most annoying repetitive task in your week. Whether it is worth building at all is the first thing worth establishing, and establishing it does not commit you to anything.

Start an enquirySee the four services