Every website has a list of small jobs. The search misses product names with accents. The opening hours changed in March. Someone asked in spring for a newsletter signup in the footer. None of these is hard. Each one waits because it needs somebody to find half an hour, and somebody else to remember that it was asked.
Resolve is our answer to that list. It is an AI that does the work on your website requests, and it leaves the decision to you. This article explains what it does, how a job runs from request to approval, and what it needs.
What Resolve is
Resolve works on the requests you keep in Flow, our issue tracker. If you have not met Flow, One place for every request about your website describes it. You write a request the way you would ask a colleague. Resolve does the work. You approve the result.
It takes four kinds of job:
- Fixes. Bugs, broken pages, security updates. You describe what is wrong. Resolve finds the cause and repairs it.
- Small features. A new section on a page, or a different layout for the top of your home page.
- Content updates. A text that needs changing.
- Regular jobs. Work that comes back, such as a new article every week in every language of your site. You set what and how often.
How a job runs
- You write the request in Flow. Your own words are enough: "Search does not find Crème when I type creme."
- You start Resolve on it with one button.
- Resolve tells you how many tasks the job needs. It tells you before it starts, so you know the cost before any work is done.
- Resolve does the work.
- The result arrives as a card on the request. The card shows what was done and gives you the address of a test copy of your site. Resolve does its work on a branch of your code and starts an environment from it, or puts the change on your staging environment if you prefer. The card has two buttons: approve, or ask for changes.
Apart from writing the request, your part is buttons: one to start Resolve, and two on each card.
Take the example on the Resolve page. For the search fault, the card reads: cause found, search ignored accented letters. Repaired, searching for "creme" now finds "Crème". Waiting for your approval, estimated and agreed: 1 task. You open the test copy, try the search yourself and press approve.
If the result is not right, you press the other button and say what should be different. Resolve estimates the change and works on it when you agree.
What a task is
Resolve counts its work in tasks. A task is about the amount of work a person would do in half an hour.
| The job | Tasks it uses |
|---|---|
| A small change, such as a fix or a text update | One |
| A bigger job, such as a new section | Several. Resolve tells you how many before it starts |
| A regular job, such as an article every week | Tasks each time it runs |
In the example on the Resolve page, a newsletter signup in the footer is estimated at 3 tasks. The estimate comes first. Then the signup is built and checked on phone and desktop, and the test copy is put in front of you.
One rule sits above all of this: you buy tasks in advance, and every job is estimated in tasks before it starts. The tasks are counted when you agree and the work starts. If you ask for changes, Resolve estimates them the same way. If Resolve cannot finish a job, its tasks come back to you.
Keeping the last word
Nothing goes live until you say so. Every result is shown to you first, and you see the change before your visitors do.
This is the part that makes handing work to an AI reasonable. An AI can misread a request, just as a person can. The approval step is where a misreading gets caught.
It also means the approval is real work, and it is yours. A test copy deserves a proper look before you press the button. Three habits help:
- Write requests that can be checked. "Make the footer nicer" cannot be approved with confidence. "Add a newsletter signup above the footer links" can.
- Use a test plan. A request in Flow can carry the steps to try and what should happen at each. Go through them on the preview.
- Look on a phone as well. A layout that works on a wide screen can break on a narrow one.
The same applies to regular jobs. A weekly article arrives as a draft for you to read. It is published when you approve it.
Where its job ends
Resolve does what a request asks. It does not decide which products to show first, what your prices are, or whether a change is a good idea for your business. Those decisions stay with you, and a clear request is how you pass them on.
The size of a task tells you what Resolve is built around: one clear thing asked for, one result to approve. A fix. A text. A section. A bigger job is several of those, counted before work begins.
Requests do not all have to come from you. With Flow and Resolve, a fault found by a scan or by monitoring can become a request that Resolve prepares a fix for. Two other articles cover where those findings come from: what one scan of your website tells you and Your website is up. Is it healthy? The approval is the same in every case. A prepared fix waits for you.
What it needs
Resolve needs Flow, because Flow is where the requests live, and it needs the Flow Team plan. Flow itself is free for one project and up to 3 people, so you can keep your requests there first and add Team and Resolve when you want the work done for you.
The prices, all per project and excluding VAT:
- Flow Team: €9 a month.
- Resolve with 10 tasks a month: €69 a month.
- Resolve with 30 tasks a month: €199 a month.
- A pack of 5 more tasks: €39.
With the smallest Resolve plan, that is €78 a month together.
What Resolve does, and the two plans, are on the Resolve page.
