Tell me what you need.

Yes, and that's the usual starting point. Describe what's going wrong and who it affects, in your own words. Working out the technical side is my job; I'll explain any choices in plain language.

It depends on what you need. A small website moves quickly; a larger system takes longer and has more checkpoints. Once we've gone through your requirements, I'll give you a realistic estimate of both before any work starts, so there are no surprises.

You get it running, with documentation, backups and admin screens your staff can use day to day. On the college website, office staff update every page themselves. If you'd like me to stay on for fixes and changes, we can agree on that up front.

Yes. On the college website I handled everything myself: the design, frontend, backend and deployment. If you already have designs, I'll build from those.

Yes. I start by understanding what's already there before suggesting changes, so you don't pay to rebuild what works. On the college website, I moved a running application to its own server and to a new storage service.

You'll see it. The work arrives in small pieces you can try as it's built, and I keep in touch by email, or by phone and WhatsApp if you prefer; both are on the contact page.

Yes. I'm looking for an entry-level software developer role working with Java, Spring Boot and React. My resume has the details.

Send a message through the contact form or by email. I reply by email, usually within two working days. A rough idea is a fine place to start.