A portfolio does not stop changing when it launches. Projects are replaced, contact details change and paid services renew. Before commissioning the site, decide who can make those changes and who receives the bills.
You may not need a maintenance subscription for every small portfolio. You do need a workable plan for the things that can change or fail.
Make a responsibility table
Use roles rather than assuming “the website person” handles everything:
One person may hold several roles. The important part is making that explicit. Do not assume a one-time build includes an indefinite obligation to make changes.
Rehearse one ordinary edit
Ask how you would replace an image, update a project description or change a link. Where possible, try the agreed editing workflow before handoff is complete. If edits require code, identify who can build and publish the change.
Keep a recoverable copy before changing the live site. Test the result on mobile and confirm that a longer title does not damage the layout. A tiny text change can still reveal that nobody knows the publishing process.
If the editing workflow was part of the purchase, verify it during website handoff and acceptance, while open questions can still be resolved.
Track renewals separately from support
Owning the site and paying for its operation are related but distinct. For example, Wix's ownership-transfer guidance explains that transferred paid services can require billing details for future renewals. Check the exact transfer and billing rules of your chosen platform.
A support agreement may cover corrections, while a hosting plan keeps the site available. Neither necessarily includes new project pages, copywriting or redesign. List exclusions and renewal responsibilities in plain language before accepting an ongoing package.
Check what changed, not just the homepage
After an update, inspect the edited project, its links, the mobile layout and the main contact action. Keep the previous version or another supported recovery route until the change is confirmed.
You can use a lightweight review schedule, with an extra check whenever a project or account changes. The right frequency depends on how often the portfolio changes and what it relies on. Do not buy daily maintenance simply because a generic checklist recommends it.
Choose support that matches your ability
If you can safely make content edits, you may only need a clear route for occasional technical help. If you cannot edit or publish, price that assistance before choosing the initial service. The companion cost and handoff guides help define the boundary.
The goal is simple: you can add your next piece of work, remain reachable and keep the site operating without guessing who is responsible.
To check what Agent.Space currently offers, visit its service marketplace. Confirm that a suitable service is listed and read its delivery scope before ordering.
