The rules I work by. Plain English, no fine print. If anything specific to your project differs, we agree it in writing before starting.
These terms apply to any work I do for you, whether it's a new build, a fix, ongoing support, or anything else. By starting a project with me, you're agreeing to these terms.
"I", "me", and "my" mean Romans, trading as RomansCode. "You" means the person or business hiring me.
I'm responsible for the code I write. That means it should work as agreed, be reasonably free of bugs, and follow standard practice for security and performance.
I'm not responsible for things outside my code: hosting speed, server downtime, third-party services going down (payment providers, email services, plugins), or problems caused by changes you or someone else makes after the project is handed over.
Before any project starts, we'll agree in writing on what's being built, the price, and the timeline. This is the "scope" of the project.
If you want to add or change something during the project, I'll tell you what it'll cost and how it'll affect the timeline. Small things may be free; bigger changes get quoted as additional work. You decide whether to go ahead.
Anything we didn't agree on at the start isn't part of the original price.
Payment depends on the size of the project:
Invoices are due within 14 days. Late payments may be charged interest at 8% above the Bank of England base rate, in line with the UK Late Payment of Commercial Debts Act 1998.
If a payment is more than 14 days overdue, I may pause work until it's settled. Any delays caused by paused work aren't my responsibility.
Each project includes a reasonable number of revisions during the build, agreed at the start. Once the project is complete and the final invoice is paid, further changes count as new work and are quoted separately.
Email is my official channel. Anything we agree should be in email so there's a clear record on both sides.
Messages on chat apps, social media, or text are fine for quick check-ins, but they don't count as binding agreements. If something matters, send it by email.
While the project is being built, all files, code, and login details stay on my hosting. You'll get a private staging URL where you can view and test the work as it progresses.
The project transfers to your hosting only after the final invoice has been paid in full. Until then, no source code, database, or admin access is handed over.
Once you've paid in full, the code is yours. You can use it, modify it, or hand it to another developer. I keep the right to use general techniques and patterns from the project in future work.
Every project comes with a 30-day post-launch warranty. If something I built breaks during that time, I'll fix it free of charge. This covers genuine bugs in my code, not changes you or someone else has made after handover.
After 30 days, ongoing support is paid work. I offer two ways to do this:
Pricing is given separately and can change with notice. I don't provide free open-ended support after the warranty ends.
If you cancel: you pay for all work completed up to the point of cancellation, plus any non-refundable third-party costs already spent (domains, licences, etc.). Deposits are non-refundable.
If I cancel: I refund any payments for work not yet started. I keep the right to cancel a project if you stop replying to messages for more than 30 days, refuse to communicate, or breach these terms in another serious way.
I don't provide hosting. You're responsible for your own hosting, domain registration, and any third-party services (email, payment processors, plugins, etc.).
I'm happy to recommend hosting and set things up on your behalf, but the contract for those services is between you and the provider, not me.
I do my best to deliver good work, but software is never perfect. I'm not liable for indirect losses, lost profits, or any damage caused by use of the code beyond the scope we agreed.
My total liability for any project is capped at the amount you've paid me for that project.
Anything you share with me in the course of a project is treated as private. I won't share, sell, or publish your data, business information, or project details without your permission.
If you want a formal NDA before we discuss anything sensitive, I'm happy to sign a standard one.
I may update these terms from time to time. The version that applies to your project is the one in place when we agree the work, not any later version.
These terms are governed by the laws of England and Wales. Any disputes will be handled by the courts of England and Wales.