Custom Work
Bespoke development: how a quote works, timelines, and what you end up owning.
Web applications, e-commerce builds, SaaS dashboards, landing pages, custom WordPress work, integrations, and adapting one of our own products beyond what configuration allows.
Tell us what you are trying to build and we will tell you honestly whether we are the right fit. Sometimes the answer is no, and it is cheaper for both of us if we say so early.
No. It is an estimate for guidance only — not an offer, not a quotation, and not binding on either of us.
It exists so you can gauge whether a project is in the right order of magnitude before spending time on a conversation. A real price comes after we understand the scope, and it becomes binding only when we put it in writing.
Tell us about the project — what it needs to do, who it is for, any deadline, and roughly what budget you have in mind.
The budget question is not us sizing you up. It tells us whether to propose the thorough version or the lean one, and it stops us both wasting time on a proposal that was never going to fit.
A written statement of work: the scope, the deliverables, the fee, the payment schedule, an indicative timeline, how many revisions are included, what we are assuming, and who owns what at the end.
That document governs the engagement. If it is not in there, it is not in scope — which protects you as much as us.
Usually a deposit up front and the balance on delivery, as the statement of work sets out. Larger projects may be split across milestones.
A deposit is consideration for work commenced, so it is not refundable once we have started — and it is refundable if we have not. Clause 11 of the Refund Policy is the authority.
The 72-hour product window does not apply. Bespoke work is built to your specification and cannot be returned or un-built.
Where we fail to deliver what was agreed, you have real remedies under the statement of work and at law — that is not a formality. What is not a ground for refund is a change of mind after delivery.
The statement of work gives an indicative timeline. It assumes you supply content, access, credentials and approvals when they are needed — and it extends by any delay there.
That is not a disclaimer in advance. It is genuinely the most common cause of a project running long, and saying so up front is how we both avoid it.
The statement of work says, explicitly, and we write it so there is nothing to argue about later.
Where the engagement includes one of our existing products, that product stays licensed under the Licence Agreement and the statement of work names the tier included.
Within the revision allowance in the statement of work, yes. Beyond that it is a change, needing a written variation to the fee or timeline.
We will tell you when a request falls outside scope rather than absorbing it quietly and producing a surprise invoice.
We may describe the nature of the work and show it, unless the statement of work says otherwise or you ask us in writing not to.
If confidentiality matters, say so at the proposal stage and we will put it in the document.