A solo architect wants a website where clients can log in to view documents and drawings instead of using shared folders. He also wants an app, but a mobile-friendly site might be enough.
Would you use a hosted site builder, WordPress, or a custom portal? What should we consider for security, ongoing maintenance, and cost?
Start with what the shared folders aren't doing well. Is the problem finding the latest drawing, managing access, or just making the client experience look nicer? Those point to different solutions.
You could keep the public website separate from the document portal and use an established file-sharing service for the private side. Check whether it supports separate client access, removing access when a project ends, and the kind of document organization he needs. A nice website doesn't have to become the system that stores every drawing.
For the portal, client isolation is the big thing. A client must not be able to get another client's files by changing a link or guessing an identifier. Files need access checks on the server, not just hidden links or buttons.
Whatever route you choose, look at account recovery, multifactor authentication, backups, updates, and how access gets revoked. Drawings and project documents can be sensitive. AI-generated code can help with the build, but it still needs review and security testing by someone who understands it.
WordPress can work if he wants to edit the public site himself, but don't assume a portal plugin makes the private side safe by default. Check the permissions, file storage, update history, and support before choosing one. Someone still needs to keep the site and plugins updated and deal with problems later.
A hosted site builder may mean less maintenance for the public pages. Check its actual client portal features before signing up, though. A password-protected page isn't necessarily a separate, private workspace for each client.
A custom portal is an option if the workflow is specific enough to justify it. You get more control over the interface and how projects and documents are organized, but you're also paying for design, development, testing, hosting, and ongoing fixes. It needs an owner after launch, especially if the architect doesn't code.
For pricing, separate the public site from the portal in the quote. Define how many user roles there are, what clients can do, who uploads files, and who handles support. A flat number without that scope could be wildly misleading.
I'd start with a mobile-friendly website, not a downloadable app. Clients can open it from a link without installing anything, and you can revisit an app later if there's a specific need the browser can't meet.
Same goes for a chatbot. A clear document area, contact details, and a useful FAQ might be more helpful to start with.
Answers are reviewed before publication.
9r!busphase_724:
Also check how clients will find updated versions. A clean folder structure and clear filenames may solve part of the problem without building new software.