This is not a story about a website that makes decisions on its own without Jesse. It is the opposite: Jesse uses Angel to bring the technical execution closer to his own ideas. He decides what should change, provides examples or screenshots, and reviews the result before anything goes live.
Before: knowing what you want, then still having to build it yourself.
Jesse managed his website himself in WordPress. When he wanted to change something, he first had to find where on the page to work, then deal with containers and visual styling, and sometimes use additional tools. He became familiar with that environment, but it remained execution work he had to do himself.
The creative request and the technical implementation were separate pieces of work that Jesse had to connect himself.
Angel translates the requested change into concrete website work while Jesse remains the owner of the decisions.
“For me, the biggest value is the combination of speed and control.”
Jesse Wildenbeest · WeAreTellers · translated from Dutch
How Jesse uses Angel in practice.
Jesse works from ChatGPT. A request does not need to start with technical specifications. He can take a screenshot of his website, add a reference and describe in everyday language what he wants to change. Angel then takes on the technical execution.
- Jesse sets the direction.
He describes what he wants to change and can add a screenshot, visual example or other reference.
- Angel turns that into website work.
The Hand takes on the technical implementation instead of Jesse first having to work out how to build the change himself.
- Jesse reviews the result.
He can check whether the change matches what he intended and adjust the direction when needed.
- Publishing remains a deliberate step.
For Jesse, it matters that he keeps control before publication and decides whether a change may go live.
Jesse describes himself as the creative brain and the person who gets the engine moving. Angel does not need to decide what WeAreTellers should communicate; its role is to help execute Jesse’s creative choice technically.
The Hand takes on execution, not Jesse’s creative responsibility.
That division is central to the value Jesse sees. He does not want an agent deciding independently what should change on the website. He wants to move faster from his own idea to a working result. He therefore provides direction and references while Angel can take on the technical and repetitive part.
Jesse did not have to complete the technical setup entirely by himself. Tijmen van Mook from Hands fully guided him through setting up and configuring Angel. This case therefore describes how Jesse uses the Hand after that setup was completed together — not that the entire setup was already self-service for him.
Angel has since expanded: from changing the website to helping improve it deliberately over time.
Since the interview, Angel has been expanded with four relevant connectors. This means the same Website Hand can involve not only the technical side of the site in its work, but also available data about search visibility and website usage when Jesse asks questions about them.
The place where website code and changes can be managed.
For the technical layer around publishing and website infrastructure Angel needs for the work.
So search-performance and visibility data can be included in questions about the website.
So available usage data can inform follow-up questions and possible improvements.
That makes Angel more future-oriented than an executor for isolated changes. Jesse can ask the same Hand to change the site and to use available data to better understand where there may be opportunities or points that deserve attention.
Jesse has not measured a reliable number of hours saved, and no measured SEO improvement has been attributed to this newer setup. The concrete change he does describe today is a shorter route from idea to execution, fewer intermediate steps and continued control.
What has already changed for Jesse.
The clearest difference for Jesse is the shorter path from an idea to a working website change. Previously, he had to work out both the visual or technical solution and then process it himself in WordPress. Now he can work more directly from a request or reference and let Angel take on the execution.
He also says he needs fewer separate tools. At the same time, the site remains his: Jesse decides what should happen and wants to review the result before it goes live.
“I can have an idea or reference translated much more directly into something that is actually on the website.”
Jesse on the step from idea to execution · translated from Dutch
An honest early-adopter experience: the possibilities are larger than the starting point.
Jesse sees substantial potential in Hands, but also names a clear learning curve. In WordPress, he eventually knew exactly where to go. Working through prompts feels to him like a larger and less familiar playing field. Especially at the beginning, he would value more visual examples, concrete use cases and suggestions based on how he uses the Hand.
A capable Hand is not enough on its own. New users also need to quickly see what is possible and which next step makes sense. Jesse’s feedback reinforces why examples, guidance and contextual suggestions matter in onboarding.
For Jesse, the potential of agents is ultimately not just about automation. He expects well-configured Hands to take on repetitive work more structurally, as long as the context is right and it remains clear who makes the important decisions.