I'm a software engineer, and an acquaintance asked me to build a website for his construction business. It will probably be a small static site with four or five pages and no back end. I'm trying to figure out the best way to handle the repository, hosting, domain registration, and ownership. Should the client create and own the accounts while giving me access, or should I keep everything under my personal accounts and transfer it later? I'm especially concerned about the client losing access to the code or domain if we stop working together. I'd also appreciate guidance on pricing a project like this and whether a short contract is worthwhile even though the scope is small.
3 Answers
There are two reasonable models: you can own and manage everything in exchange for an ongoing maintenance fee, or the client can own the accounts and you hand over the finished site. The second approach is usually cleaner for a one-off project because you aren’t permanently responsible for hosting, renewals, or unexpected support. Even a one-page contract is worthwhile—small projects can still turn into open-ended requests if the number of revisions and the definition of “finished” aren’t documented.
I’d put the domain, hosting, and source repository under accounts owned by the client. Create the accounts using their email, then add yourself with the access you need. That way they retain control if they switch developers, while you can still build and deploy the site. For a small static site, a free static host and a reasonably priced registrar should be enough. Also use a short written agreement that defines the pages, revisions, launch requirements, payment schedule, ownership, and what future maintenance will cost.
For a four- or five-page static site, price it based on the actual work rather than just the page count. Include discovery, design or adapting a template, writing or organizing content, development, testing, deployment, and a limited number of revision rounds. Set a fixed project price with a deposit, then quote ongoing updates separately. The exact amount depends on your market and experience, but clearly defining the deliverables matters more than finding one universal price.
That makes sense. I’m comfortable building the initial version, but I don’t want unlimited revisions or indefinite maintenance to be assumed as part of the original price.