The Fessburn Evidence Loop
How we run a project, from the first interview to the release.
Every project goes through the same six stages, whoever on the team is running it. We don’t start a stage until the one before it has evidence behind it, so you only pay to build what real users have already tested.
- 01
Understand
We interview your users and your team, look at the data you already have, and work out which regulations apply to your product, like IEC 62366-1, the European Accessibility Act, or AI Act Article 50.
You getA short brief with the problem, the users, and the rules we have to design to
- 02
Prototype
We build a working version of the riskiest part of the product first, in days. A working version can settle the question faster than going through round after round of reviews.
You getA clickable or coded prototype on a live URL
- 03
Test
Real users try real tasks on the prototype. We watch where they hesitate, where they make use errors, and where they give up, and we write it all down.
You getA written test report with what worked and what didn't
- 04
Decide
You get a go or no-go, and a fixed price for the build. If the test shows the idea doesn't work, we tell you, and you can stop here.
You getA decision, and a fixed price for the next step
- 05
Build
The same team designs and codes the product, so the reasons behind each decision make it into the code. You get a release to a staging URL every week.
You getWeekly releases and a written update
- 06
Verify
Before launch, we check the release against what we found in testing. Anything that doesn't hold up gets fixed before it reaches your users.
You getA release checked against the test findings
Working together
What we commit to, and what we need from you.
We commit to
- We reply within one business day
- Every project has a named lead
- You get a written update every week
- The price is fixed for the scope we agree on
- You own everything we make once it's paid for
- We'll sign an NDA before the first call if you want one
We need from you
- One decision-maker on your side
- One to two hours a week for reviews
- Feedback within 48 hours, so the schedule holds
- Access to the files, data, and people we need
Day to day
We work in your files, and you don’t need a call every week.
We work asynchronously in the Figma files and the repository you already use, with review points we agree on at the start. You get a written update every week, and a recorded walkthrough when we hand something over. If you want a call, you can always book one.
We use AI tools to prototype and build faster. A person on our team reviews everything before it reaches you, and we only put your data into tools you’ve approved.
Where to start