5 products, each grown from client work.
Licensed, hosted and supported by the team that wrote them.
Working out who touches a record, in what order, and what decision each person makes — before anything is drawn. This is where a build gets cheap or expensive.
The screens themselves, designed with the real field names and the real worst-case row, because that is what breaks a layout.
A component set and the rules behind it, so the product stays consistent when somebody adds a feature in eight months without asking.
Where software already exists and already has users. The constraint is not taste, it is not retraining three hundred people.
Indicative figures while we settle the final rate card — tell us the brief and we will send a real number rather than a bracket.
Every number is a starting range, not a quote. What it actually costs comes back in writing after one call — with the scope it is attached to.
Yes, and you get the file. Your next designer should not have to start again because the last one left.
Yes. We hand over a specified design and a component set, and we will answer your developers' questions during the build. It is a common arrangement and it works.
Then the first job is finding out whether the problem is the design or the process it is describing. Quite often it is the second one, and more screens will not fix it.
One reply from the person who would do the work.
Hello. Tell us what you are trying to build, or what is going wrong with what you have. A person reads these — not a bot.
