






A website or digital system still needs attention after the project is complete. Content changes, links need correcting, and small usability issues collect between larger priorities. Without a defined support arrangement, routine upkeep keeps returning to people whose attention is needed elsewhere.
Truesight provides scheduled maintenance and support for approved existing work. We handle agreed updates, carry out routine checks, and help distinguish a manageable fix from a change that needs its own scope.

Maintenance and support protect the usefulness of systems that are already built. The work covers an agreed property or system and a defined range of routine changes, checks, and assistance. That may include CMS updates, minor content or design adjustments, platform and integration monitoring, basic performance review, and small usability improvements within the existing structure.
This is a fit when the foundation is sound and the organization needs someone to look after recurring care. It is different from an ongoing design partnership, where the priority is actively developing an experience, brand, or product. A request to correct existing information may belong in maintenance; a request for a new page, feature, or campaign requires a different level of work.
Maintain sits outside the subscription ladder and is available after a qualifying Truesight project or an approved onboarding audit. We agree the covered property, access, responsibilities, and support process before accepting the work. Coverage is for scheduled maintenance rather than emergency or after-hours response. Unfamiliar systems or significant existing issues may require separately scoped assessment or remediation before ongoing support can begin.
A team member spots outdated information and asks who can change it. A form needs checking, but the person responsible for publishing is unsure which settings affect the follow-up. An old integration sends an error nobody recognizes. Each issue moves between email, internal messages, and whoever last touched the system before someone can even decide what kind of help is needed.
The interruptions fall unevenly. Marketing delays a simple update because it does not want to disturb the layout. A founder becomes the contact for a website they do not maintain. Developers are pulled away from planned work to investigate a request that arrives without context. Customers may continue seeing inaccurate information while the organization works out who should be responsible for correcting it.
An undefined support relationship creates problems in the other direction too. A small change becomes a new section, a minor adjustment turns into custom development, and neither side has agreed how the extra work will be handled. The business needs dependable boundaries as much as a contact name: what is covered, how requests are reviewed, and when an issue belongs with a platform provider or a separately scoped project.
We begin by reviewing the agreed property, its current condition, available documentation, and the access needed to support it. We identify the supported components, recurring checks, and types of updates included. Known issues and responsibilities are documented before the arrangement begins, so the maintenance plan reflects the actual system rather than a general promise to handle anything that comes up.
During the engagement, requests enter an agreed process for review and scheduling. We carry out covered changes, check the affected areas, and record what was done. When a request falls outside maintenance, we explain the next step and scope additional work before proceeding. New pages, product features, custom development, major redesigns, campaigns, and ongoing content production are excluded; emergency and after-hours response are not part of the service.
Publish supplied content and make minor corrections within existing CMS structures and approved layouts. Review affected pages after changes; new pages, major sections, and original content production require separate scope.
Address agreed presentation issues and small usability problems within the established system. Keep larger experience changes, new components requiring custom development, and redesign work outside the maintenance allowance.
Review agreed pages, forms, platform connections, and basic performance or accessibility concerns at the established cadence. Flag issues requiring deeper investigation; routine checks do not guarantee uninterrupted operation or exhaustive defect detection.
Review incoming requests, clarify their scope, and direct issues to the appropriate next step. Keep a record of completed changes, unresolved concerns, and recommendations for separately approved improvements.
“I had the opportunity to work alongside Garrhet, and his work ethic was something I noticed right away. He was always looking for ways to improve, willing to take on new challenges, and consistently brought a positive attitude to the team. He's dependable, professional, and genuinely cares about doing good work. Those are qualities that make a difference, especially when you're working with someone every day.”

The team has a defined place to send ordinary updates and support questions. Requests arrive with the context needed for review, and covered changes can be scheduled without turning each one into a new procurement exercise. People know what the arrangement includes and what it does not. That clarity helps internal teams concentrate on their work while keeping ownership of the existing system visible.
Customers benefit from more consistent attention to the information and interactions already in place. A corrected link, an updated contact detail, or a resolved display issue may be a modest change, but it can remove an unnecessary obstacle. Scheduled checks provide opportunities to notice problems within the agreed coverage. They cannot prevent every issue or control a third-party platform, and the support arrangement should not imply otherwise.
Leadership gains a clearer distinction between maintaining the current investment and deciding to improve it. Routine changes have a place, while requests that require design, development, or broader investigation can be considered with an appropriate scope and budget. Maintenance records also preserve useful context for future work. The result is a more orderly way to care for what exists without allowing a modest support arrangement to become an undefined development commitment.
Tell us which website or system needs ongoing care and the requests that keep interrupting your team. We will review whether it is a fit for maintenance, identify any onboarding requirements, and define the coverage before the support arrangement begins.







Single Projects
Ongoing Sprints