Where each part of the work is explained
Everything Moksy publishes about scoping, specifying and reviewing a build, indexed by the question it answers.
Start with the question, not the document
Most of what people want from a resources page is one specific answer: what goes in a brief, what a review actually changes, what any of it costs, what happens to the data. Each of those is written down somewhere on this site already.
This page is the index. Nothing here is a summary of the page it points at — go and read the page.
Before you spend money on software
Neutral guides to what software costs, how to brief it, and how to hire for it — written by people who are not trying to sell you the build.
What does software cost in the UK?
The published ranges, what moves a project between them, and the costs quotes leave out.
What does an app cost to build?
Simple, mid-range and complex — and how to tell which one you really have.
What does a booking system cost?
When a £20-a-month tool is right, and the signs you have outgrown it.
What does an online shop cost?
Shopify, custom, and the point where the answer changes.
What goes in a software brief?
A requirements template for people who are not developers.
How do I compare quotes?
Why three quotes for one idea differ tenfold, and how to read them.
Fixed price or time and materials?
Which contract fits which project, and who carries the risk.
What should I ask an agency?
The questions that separate a partner from a sales process.
The questions, and where each is answered
How does an idea become a plan?
The four stages, from the paragraph you type to the reviewed document you take away.
What is actually in the plan?
The sections, the analysis areas that get scored, and what the document deliberately is not.
What does a review change?
The lifecycle of one review, and what makes a correction acceptable rather than an opinion.
What does it cost to run?
What a membership covers, and what MOX credit is for when work falls outside it.
What happens to what I type?
Where data is held, who can reach it, which sub-processors are involved, and what happens in an incident.
How do I get a useful result?
How to answer the Briefing, and what to do with the plan once it exists.
Not here yet
Said plainly, because an index that hides its gaps is not an index.
- Downloadable templates. There are none, and a page headed "templates" with nothing behind it is worse than one that says so.
- Case studies. They need a customer’s written permission and real numbers, and we will publish the first real one rather than an anonymised composite.
- A blog. Two posts and a gap reads worse than no blog at all.