From scattered notes
to working tools.

The website, the research, the instructions, the follow-up. Useful work is usually spread across a few places. We used agents to connect the pieces and check the handoffs.

Real examples from our own working sessions, presented as an anonymized client-style brief. This is internal project work, not a customer testimonial.

The brief.

Make the business easier to run and the work easier to pick up again. Keep the knowledge organized, turn repeated procedures into reusable instructions and give people a clear way to get in touch.

We worked in small steps. Agents researched, drafted, edited files, ran checks and helped operate the browser. People supplied the direction, corrected the work and kept control of sensitive decisions.

01 / Give the knowledge one home.

Research and operating notes had outgrown their original project folder. We moved them into a dedicated knowledge base and connected it to a searchable local reading view.

What we checked: all 48 original files were preserved and hash-checked. A migration map recorded where each went. Older reading-view URLs continued to reach the right notes, and hidden agent records and archives stayed outside the reading export.

The handoff: an index, linked source notes and a record of completed work and open questions. The next session had somewhere concrete to start.

02 / Write the procedure once.

Repeated jobs need more than a good prompt remembered by one person. We built project-specific instructions for site checks, profile work and booking setup, then consolidated overlapping shared instructions.

Short entry instructions pointed to detailed references and helpers when needed. The cleanup preserved all 73 original helper and policy files in active or archived locations; resource links and local fixtures were checked.

The handoff: reusable procedures with inputs, checks and stopping points. Less duplicated instruction to maintain. We did not measure token-cost savings from that cleanup.

03 / Ship the change we checked.

Agents helped turn source material into a voice guide, service copy, a preparation guide and an About page. The website kept its core content and links usable without JavaScript.

What we checked: generated pages, local links, metadata and sitemap, followed by desktop, mobile and keyboard inspection. The packaged source was published, and the same commit was mirrored to the private source repository.

The handoff: a working site and a record of exactly what was released. Publication was verified; search gains and customer demand were not inferred from it.

04 / Follow the inquiry all the way through.

The first form route showed a success response. That was encouraging. It still didn’t tell us whether anyone could find the inquiry.

We replaced the unverified delivery path with a form in an existing business account. A synthetic inquiry appeared in the private response record. Its notification landed in Spam; we corrected the routing and confirmed the Inbox move. A live embedded-form test also saved its response.

The handoff: the owner reviews recorded inquiries and replies personally. The form includes a standalone fallback. These were internal tests, not customer leads or evidence of improved conversion.

05 / Make “done” mean something.

Earlier task-runner work addressed a familiar problem: an agent can announce completion before the work deserves it.

A regression fixture specified that a failed check must leave the task open, even if the agent emitted its completion marker. Progress and run durations were recorded, and branch-preservation behavior was built into the runner.

The lesson: agree what a good result looks like before starting. The agent’s answer is part of the work; checking it is part of the work too.

What carries over to your business?

The tools will differ. The pattern travels: choose a task, gather the right inputs, let the agent do the repeatable part, check the result and leave clear controls for the person using it.

A working knowledge base, a published page and a recorded test inquiry are concrete outputs. Hours saved, revenue gained and dependable day-to-day operation need their own evidence.