Skip to content
AspirecoStart
All answers

Working with us

What should a free software audit include?

The short answer

A written assessment of what your current systems actually do, where money or time leaks between them, what is safe to keep, and what fixing it would involve — ranked, specific, and with a scope and cost range. It should be useful even if you hire someone else to do the work.

Updated

What it should assess

  • A technical and commercial review of the current system: whether it works, and whether it pays.
  • Ranked findings with estimated revenue impact, so the worst leak is named first.
  • An integration, data-quality and security assessment.
  • A scope and cost range for the work worth doing.

What you should get

A written dossier, yours to keep whether or not you hire the studio that wrote it. Ours follows inside a week, and it says so plainly when the answer is that you are too early — if the whole thing is a brochure site, you do not need a studio.

Who should write it

The people who scope the work should be the people who build it; otherwise the scope is a guess relayed to someone else. There is no account manager between you and the builders here.

Red flags

An audit that is really a sales call, one that arrives without findings, or one that cannot be used without hiring its author. A free audit should stand on its own. Start one here.

Asked next

How quickly should audit findings arrive?

Within a week is a reasonable standard. Ours: a reply within one business day, and the written dossier inside a week.

Is a free software audit just a sales pitch?

It should not be. The test is whether the document is useful without hiring its author. Ours is written to be specific enough to act on elsewhere; we would rather lose a badly scoped project than win it.