Fixed quote after a free call

Website feedback and change requests in one list, sorted

Staging review brings feedback from several stakeholders through feedback widgets, email, chat and calls. We build a workflow that collects it into one list in your project tool, classifies each item as a bug, content edit, design change or possible new scope, groups duplicates and contradictions, and drafts a change request for anything outside the agreed scope. A typical build costs $1,000 to $2,500 per workflow and takes about three to four weeks.

The problem

Why staging feedback turns into unpaid scope

The client reviews staging and feedback arrives everywhere: pins in a feedback widget, a long email from the marketing lead, a chat message from the CEO and a note from a call. Developers fix the same issue twice, miss others, and argue over what was actually agreed.

The hardest items are the ones that look small but are new scope: a new page, an extra integration, a redesigned section. Without a classification step they slip into the build unpriced, and the project margin disappears quietly.

What we build

What our website feedback and change request automation includes

All feedback in one list

Marker.io or BugHerd reports, emails and chat messages collected into one list per review round.

Classification

Each item sorted as bug, content edit, design change or possible new scope, with the page and device.

Duplicates and conflicts

Repeated items grouped and contradictions between stakeholders highlighted.

Tasks with context

Bugs created as tasks with screenshots, browser and URL in your project tool.

Change request drafts

Possible new scope turned into a draft change request with an estimate placeholder for the project manager.

Round summary for the client

A summary of what will be fixed, what needs a decision and what is a change request.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Feedback arrives

    Widget reports, emails and chat messages reach the workflow.

  2. 02 Automated

    Sorted and grouped

    Items are classified, duplicates grouped and conflicts flagged.

  3. 03 Automated

    Tasks and drafts

    Bugs become tasks; possible new scope becomes a draft change request.

  4. 04 Project manager review

    Project manager confirms

    The project manager checks every classification and agrees the list with the client.

  5. 05 Project lead or agency owner decides

    Scope decisions

    Whether new requests are absorbed, priced or deferred is decided by the project lead with the client.

How it behaves

How the feedback workflow behaves

What each person sees and what runs in the background, including what happens when something goes wrong.

What the client sees

  • They can give feedback however they prefer
  • A clear summary of each round
  • Change requests to approve before new work starts

What the agency sees

  • One sorted list per round
  • Bugs as tasks with full context
  • Drafted change requests for new scope

What the automation does

  • Collects feedback from every channel
  • Classifies and groups items
  • Creates tasks and drafts change requests

Edge cases and fallbacks

Stakeholders contradict each other
Both comments shown side by side for the project manager to resolve with the client.
Feedback refers to an old staging build
Marked as possibly fixed for a developer to check.
Classifier unsure
Left as unsorted for the project manager.
Feedback tool or API outage
Items are collected when it returns; nothing is lost.

Architecture

Staging feedback and change requests at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Feedback widget Marker.io, BugHerd Email and chat Stakeholders n8n workflow Collect by round Classifier Bug, edit, scope Project tool Tasks with context Change request Draft for PM Project manager Agrees with client
  • Input
  • Logic and services
  • AI step
  • Data
  • Output
  • People

How it flows

  1. 1 Feedback widget reports, emails and chat messages are collected per review round.
  2. 2 Each item is classified as bug, content edit, design change or possible new scope.
  3. 3 Bugs become tasks with context, and possible new scope becomes a draft change request.
  4. 4 The project manager confirms the list and agrees scope decisions with the client.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Staging feedback & change request workflow project plan

Typical time to launch: about 3 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Feedback tools, review rounds, scope documents and how change requests are handled today.

  2. 02

    Design

    2 to 3 days

    Classification rules, task format, change request template and client summary.

  3. 03

    Build

    About 1 week

    Collection, classifier, task creation, change request drafts and summary.

  4. 04

    Shadow run

    About 1 week

    Run on a live review round with the project manager checking every item.

  5. 05

    Launch

    1 to 2 days

    Switch on for all staging reviews.

  6. 06

    Support

    Ongoing

    Rule tuning and new feedback channels.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n Marker.io webhooks or integrations BugHerd API, confirmed per project Gmail or Microsoft 365 API Asana, ClickUp, Jira, Trello or Linear API Claude or OpenAI for classification

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Channels, classification rules and templates.

    $200 – $450

  • Build

    Collection, classifier, tasks and change request drafts.

    $500 – $1,250

  • Integrations

    Feedback tool, email, chat and project tool.

    $150 – $400

  • Testing and shadow run

    Live review round.

    $100 – $250

  • Launch and training

    Switch-on and team walkthrough.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Feedback tool, AI usage and n8n are billed to you directly.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • Feedback tool: Your Marker.io or BugHerd plan, if used.
  • n8n: Self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).
  • AI model usage: Billed by the provider per use; small at typical review volumes.

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

Feedback can contain personal data

Screenshots and comments may include client customer data; feedback tools and AI vendors need Article 28 processor terms.

Source: gdpr-info.eu

Accessibility feedback is a requirement

Feedback about keyboard use, contrast or screen readers is classified as a bug against WCAG 2.2, not a nice-to-have.

Source: www.w3.org

Scope changes agreed in writing

Change requests are drafted for the project manager and only become work once the client approves them.

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Staging feedback & change request workflow questions, answered.

Marker.io and BugHerd are popular website feedback tools that pin comments to the page with browser details. We connect to whichever you use and add the email and chat feedback those tools miss.

Yes. Emails and chat messages go into the same list as widget reports, so clients do not have to change how they work.

It compares requests with the agreed scope and flags items that look like new pages, features or integrations. The project manager decides; the workflow only drafts the change request.

Yes. We add a simple change request form for clients after launch, feeding the same workflow, so post-launch edits are tracked the same way.

Bugs become tasks with the page URL, browser, device and screenshot attached, grouped so the same issue is not fixed twice.

Feedback rounds per project, duplicates grouped, change requests raised and approved, and time from round close to fixes deployed.

Free 20-minute call

Want this for your web developer?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call