01 · Repair
Restore what should already work.
Best when the foundation is sound and a defined technical problem is interrupting the experience.
Technical care + improvement · H-A-T
Your digital system should work.
Let’s fix what doesn’t.
Technical care for organizations with broken functionality, outdated content, unreliable forms, mobile layout problems, or a digital system their previous developer left behind.
Tell me what’s broken- Good starting point
- A URL and a plain-language description
- Approach
- Diagnose before expanding the scope
- Working model
- One lead, from inspection through handoff
What brings people here
You don’t need to know the technical name for the problem.
Start with what you can see, what changed, or what customers are experiencing.
- 01
Something stopped working
A form no longer sends, a button goes nowhere, a page throws an error, or an integration has quietly failed.
- 02
The mobile version fell apart
Layouts overlap, navigation is difficult to use, or important content disappears on smaller screens.
- 03
The information is out of date
Services, people, pricing, imagery, downloads, or business details no longer reflect what is true today.
- 04
Small edits feel risky
The site is difficult to update, the original developer is unavailable, or every change seems to create another problem.
- 05
The site feels painfully slow
Pages hesitate, images drag, or visitors leave before the experience has a chance to make its case.
- 06
It needs more than a patch
The website technically works, but its structure, design, or technology is holding the business back.
01 Observe02 Understand03 Resolve
The first useful decision
Repair, update,
or rebuild?
Technical stewardship
From visible glitches to the system underneath.
The scope can stay small when the problem is small—and widen only when the evidence supports it.
Functionality repairs
Broken links, buttons, menus, forms, interactive elements, integrations, and errors that interrupt the customer journey.
Content + design updates
New copy, images, services, team details, landing-page sections, and focused visual improvements without an automatic full redesign.
Responsive fixes
Layout, spacing, navigation, readability, and interaction problems across phones, tablets, and desktop screens.
Performance improvements
A practical review of heavy assets, front-end behavior, loading problems, and other issues affecting site speed and usability.
Search foundations
Metadata, redirects, crawlability, page structure, analytics implementation, and technical SEO issues discovered during the work.
Technical troubleshooting
Hosting, domains, SSL, deployments, CMS behavior, dependencies, and third-party tools when they are part of the underlying problem.
How the work moves
A clear path from “something’s wrong” to resolved.
- 01
Inspect
Share the website and describe what feels broken or outdated. I reproduce the issue and review the surrounding system.
- 02
Diagnose
I identify the likely cause, separate symptoms from root problems, and clarify the responsible scope before larger work begins.
- 03
Repair + update
I make the agreed changes while preserving the parts of the website that already serve the business well.
- 04
Test + hand off
The result is checked across relevant screens and workflows, then handed back with a clear account of what changed.
Why H-A-T
Repair is technical.
Choosing the right repair isn’t.
- 01
Human
Judgment before activity
The goal is not to create a longer task list. It is to understand what matters, what can stay, and which change will make the website more useful.
- 02
AI
Speed with supervision
AI can accelerate investigation, comparison, and repetitive production. The diagnosis, priorities, creative direction, and final decisions remain human-led.
- 03
Technology
A fix that holds up
Repairs are considered in the context of the surrounding system so today’s solution does not quietly become tomorrow’s new problem.
Local focus, remote workflow
Care for the systems your work depends on.
Technical care goes beyond applying a quick patch. I inspect the surrounding system, identify the real source of the problem, and make changes that respect the dependencies already carrying important work.
Through H-A-T, Nancy provides direct technical support for existing websites, products, and workflows wherever the system can be accessed, tested, and improved responsibly.
Before you reach out
Technical care questions, answered plainly.
Can you fix a website you did not build?
Yes, existing websites are welcome. The first step is reviewing how the site is built, what access is available, and whether a focused repair is the responsible path.
What access will you need?
That depends on the issue. Useful access may include the website platform or CMS, hosting, domain or DNS settings, analytics, and relevant third-party services. I will ask only for what the diagnosis requires.
Can you make updates without redesigning everything?
Often, yes. Copy, imagery, page sections, business details, and focused interface improvements can frequently be handled without replacing the entire site.
What if repairing the site is not the best investment?
I will say so. If the underlying system makes a repair fragile or disproportionately expensive, I will explain the tradeoff between repairing, improving, and rebuilding before recommending a direction.
Do you provide ongoing website updates?
Ongoing support can be discussed when the website would benefit from recurring improvements or technical care. The right arrangement depends on the site and the expected cadence of work.
Do you work remotely?
Yes. H-A-T works remotely when access, testing, and collaboration can be handled effectively.
Start with the symptom
Show me what’s
not working.
Send the website URL, describe what you notice, and share when it became a problem. A polished technical brief is not required.
Tell me what needs attention