Case Study
Case Study: Web Agency Delivery & Care Plan Automation
We built a connected set of automations for a web design and WordPress agency: enquiry-to-brief CRM, content collection with scheduled reminders, staging feedback sorted into one list, automated launch QA and care-plan monitoring across client sites. Project managers stopped chasing and copying, developers got better tasks, and launches follow the same checks every time.
- Agency type
- Web design and WordPress development agency with care plans
- Team involved
- Owner, project managers, developers, designers
- Systems connected
- CRM, proposal tool, project tool, feedback widget, CI, site management, monitoring, n8n
- Delivery
- Scrum, 1-week sprints, about 8 weeks to full launch
The challenge
Where the practice started
Enquiries were researched by hand before every call, and proposals went quiet without follow-up.
Content collection ran through email and shared drives, and projects regularly waited weeks for copy and images.
Staging feedback came through a feedback widget, email and chat, with duplicates and unpriced new requests slipping into builds.
Launch checks were a manual checklist, and care-plan alerts came from several tools in different formats, so expiring domains and failed renewals were easy to miss.
Goals
What the project had to change
- Every enquiry has a brief draft and a current-site snapshot before the call.
- Content is requested per page with reminders and a clear blocking view.
- Staging feedback lives in one sorted list, and new scope becomes a change request.
- Every launch runs the same automated checks with developer sign-off.
- Care-plan sites are watched from one alert stream with monthly client reports.
What we built
What we built, as one connected system.
Enquiry-to-brief CRM
We captured enquiries into the CRM, drafted briefs, attached a technical snapshot of the current site, tracked proposal events and created signed projects with kickoff tasks.
Service detailsContent collection
Approved sitemaps now create content requests per page, with one upload link, scheduled reminders, files routed to the project folder and a blocking view.
Service detailsStaging feedback
Widget reports, emails and chat messages are collected per round, classified, grouped and turned into tasks or draft change requests.
Service detailsLaunch QA
Redirect checks against the old sitemap, meta and indexing checks, Lighthouse CI, axe-core, form and SSL tests run before every launch with a sign-off report.
Service detailsCare-plan monitoring
Uptime, SSL, domain, backup and update signals feed one alert stream, open tickets with context and produce a monthly care report per client.
Service detailsArchitecture
How the web agency workflows connect
- Input
- Logic and services
- AI step
- Data
- People
- Output
How it flows
- 1 Enquiries, project events and client-site monitoring signals feed one n8n instance.
- 2 Workflows draft briefs, sort feedback, run launch QA and create tasks in the project tool.
- 3 Project managers confirm briefs and scope; developers fix issues and sign off launches.
- 4 Launch QA reports and monthly care reports are produced for each client.
How it behaves
How the system behaves day to day
What clients see
- A prepared discovery call
- One clear content request with friendly reminders
- A summary of each feedback round
- Launches that keep old links working and a monthly care report
What the agency sees
- Briefs, blocking views and sorted feedback lists
- Launch reports with pass, fail and manual items
- One alert stream for all care-plan sites
What the automation does
- Drafts, requests, sorts, checks and monitors
- Applies opt-outs and reminder limits
- Logs every step and alerts the owner if a run fails
Edge cases and fallbacks
- A prospect has no current site
- The snapshot is skipped and the brief asks about domain and hosting.
- Stakeholders contradict each other on staging
- Both comments are shown for the project manager to resolve.
- Old site already offline before launch
- Old URLs come from Search Console exports for the redirect check.
- A backup fails on a care-plan site
- Updates on that site are held until a good backup exists.
- n8n or a monitoring tool is down
- A heartbeat check alerts the team that monitoring itself is down.
Integrations
What we connected
HubSpot
CRMEnquiries, deals, briefs and proposal stages.
HubSpot CRM REST API and webhooks.
PandaDoc
ProposalsProposal views and signatures moving deals.
PandaDoc API.
Asana
Project managementKickoff tasks, content requests and feedback tasks.
Asana API.
Marker.io
Website feedbackStaging bug reports and feedback with browser details.
Marker.io integrations and custom webhooks.
GitHub
Code and CIRepositories, Actions for Lighthouse CI and launch checks.
GitHub REST API and Actions.
MainWP
WordPress managementUpdates, uptime and site status across client sites.
MainWP REST API.
UptimeRobot
MonitoringUptime, SSL and domain-expiry monitors and alert contacts.
UptimeRobot API.
Cloudflare
DNS and securityDNS records, certificates and security settings.
Cloudflare API.
n8n
Automation platformRuns the workflows, self-hosted or on n8n Cloud.
Your own n8n instance; we hand over every workflow.
How we delivered it
Week by week, one workflow at a time.
Delivery timeline
Typical time to launch: about 8 weeks, then support
-
01
Discovery
Week 1
We followed two projects from enquiry to launch, reviewed care-plan alerts and agreed data flows and processor terms.
-
02
Design and access
Week 2
Brief template, content request templates, feedback rules, launch checks and alert rules; API and CI access.
-
03
Sprint 1: CRM and briefs
Week 3
Built capture, brief drafts, site snapshot and proposal tracking; shadow-ran on live enquiries.
-
04
Sprint 2: content collection
Week 4
The CRM went live. Built content requests, reminders and the blocking view.
-
05
Sprint 3: staging feedback
Week 5
Content collection went live. Built feedback collection, classification and change request drafts.
-
06
Sprint 4: launch QA
Week 6
Feedback went live. Built redirect mapping, Lighthouse CI, axe runs and the sign-off report; piloted on a real launch.
-
07
Sprint 5: care-plan monitoring
Week 7
Launch QA became part of every go-live. Built the alert stream, tickets, expiry watch and care reports.
-
08
UAT and handover
Week 8
The team ran acceptance tests, we switched everything on, handed over run books and trained the team.
-
09
Support
Ongoing
Weekly check-ins during stabilisation, then monthly care.
Who does what
What the team does, and what automation does.
Automation does
- Captures enquiries and drafts briefs with a site snapshot
- Creates content requests and sends reminders
- Collects and classifies staging feedback
- Runs launch checks and builds the sign-off report
- Normalises care-plan alerts and builds monthly reports
The team does
- Project managers confirm briefs and agree scope
- Project managers review content and resolve feedback
- Developers fix issues and complete manual accessibility checks
- Developers handle incidents and run updates
Project lead or agency owner decides
- Decides prices, payment terms and commitments
- Approves change requests with the client
- Signs off every launch
- Decides rollbacks and renewals involving payment or ownership
Compliance handled
Privacy, consent and safety, built in.
Processor duties
Every vendor touching client data was covered by Article 28 GDPR terms before go-live.
Source: gdpr-info.euAccessibility checks
Launch QA maps to WCAG 2.2 and always includes manual checks, since automated tools find only part of the issues.
Source: github.comCertificate lifetimes
Expiry monitoring was built for shorter certificate lifetimes set by the CA/Browser Forum baseline requirements.
Source: cabforum.orgB2B email rules
Proposal follow-ups and reminders honour opt-outs within CAN-SPAM's 10-business-day limit.
Source: www.ftc.govCredentials never by email
Client logins are requested through a password manager and access is logged.
Outcomes
What changed for the practice
- Project managers walk into discovery calls with a brief draft and a snapshot of the current site.
- Content arrives per page through one link, and the team can see what blocks the launch.
- Staging feedback lives in one sorted list, and new requests become change requests instead of free work.
- Every launch runs the same automated checks, and developers sign off from one report.
- Care-plan sites are watched from one alert stream, and every client gets a monthly care report.
What we track
The measures the practice watches.
Enquiry handling
Time to first reply and briefs ready before the call.
Content readiness
Days from sitemap approval to content complete.
Feedback rounds
Rounds per project and change requests raised and approved.
Launch quality
Issues caught before launch and post-launch hotfixes.
Care-plan reliability
Incidents caught before the client noticed, and renewals completed before expiry.
Cost estimate
What a project like this costs
-
Discovery and design
Process mapping, data flows and backlog for all five workflows.
$1,000 – $2,000
-
CRM and brief module
Capture, brief drafts, site snapshot and proposal tracking.
$600 – $1,500
-
Content collection module
Requests, reminders, file routing and blocking view.
$700 – $1,700
-
Feedback module
Collection, classification and change request drafts.
$700 – $1,700
-
Launch QA module
Redirects, meta, Lighthouse CI, axe and sign-off report.
$800 – $2,000
-
Care-plan monitoring module
Alert stream, tickets, expiry watch and care reports.
$800 – $2,000
-
Integrations
CRM, project, feedback, CI, site management and monitoring connections.
$100 – $400
-
Testing, UAT and launch
Pilots, acceptance tests, launch and training.
$300 – $1,200
-
Total project estimate
$5,000 – $12,500
Optional monthly care after launch is quoted with your proposal. Typical range for this scope: five workflows at our per-workflow range. Every agency gets its own fixed quote after a free call.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- n8n: Self-hosted Community edition, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.
- AI model usage: Billed by the provider per use; briefs and feedback sorting stay small at agency volumes.
- Vendor plans: CRM, proposal, feedback, monitoring and site management tools on their own plans.
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
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 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 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 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 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
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
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
Tools we built
Free tools we built and use every day.
The Make It Flow platform
Website audits, monitoring and reports
- Bulk Website Audit Audit up to 100 URLs at once by pasting a list or uploading CSV
- Site Crawl Crawl up to 500 pages for links, clusters and cannibalisation
- Accessibility Check FreeAutomated Lighthouse checks for contrast, alt text, labels and ARIA
- Website Monitoring Scheduled re-scans, score emails and 5-minute uptime alerts
- White-Label Reports PDF reports with your logo, name and color, and shareable links
- Website Audit API Queue scans and read results via REST API with signed webhooks
Free website tools for practices
Services in this case study
CRM automation for web design agencies: enquiry to proposal
Capture every website enquiry in one CRM pipeline, turn vague requests into a structured brief with a quick audit of the current site, track proposals and hand signed projects straight to delivery.
From $1,000 · About 4 weeks Details
Website content collection & client chasing
Collect copy, images, bios, product data and logins against the approved sitemap, with scheduled, friendly reminders and a clear view of what is blocking the build.
From $1,000 · About 3 to 4 weeks Details
Staging feedback & change request workflow
Gather staging feedback from Marker.io, BugHerd, email and chat into one list, sort bugs from content edits and new requests, and draft change requests for anything outside scope.
From $1,000 · About 3 to 4 weeks Details
Pre-launch QA, accessibility & migration checks
Run broken links, redirects from the old site, Lighthouse, accessibility, meta tags, forms and SSL checks automatically before every launch, with a report the developer signs off.
From $1,000 · About 4 weeks Details
Care-plan monitoring: uptime, SSL, domains & updates
Watch every care-plan site for downtime, SSL expiry, domain renewal, failed backups and pending updates, open tickets with context and send each client a monthly care report.
From $1,000 · About 4 weeks Details
Project lead or agency owner decides
-
Website Launch QA Process: A Repeatable Workflow for Web AgenciesAutomation · 9 min read
-
Website Launch Checklist: Technical, SEO, Email and SecurityGuides · 8 min read
-
Website Audits for Agencies: Win, Onboard and Keep ClientsGuides · 8 min read
-
Automate Website Monitoring for Free: Uptime, Audits and AlertsAutomation · 10 min read
-
Automate SSL Certificate Renewal: Certbot, acme.sh and AutoSSLAutomation · 11 min read
-
How to Make a Website Accessible: WCAG 2.2 Basics ExplainedGuides · 7 min read
-
WordPress Security Checklist: 20 Steps to Harden Your SiteWebsite Security · 1 min read
-
How to Audit a WordPress Website: A Step-by-Step ChecklistGuides · 7 min read
Free 20-minute call
Want this built 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.
Sources we checked
Rules and product facts on this page come from these pages, checked in November 2026. This is general information, not legal advice; confirm the rules that apply to your practice with your own adviser.
- W3C: WCAG 2.2
- ADA.gov: Fact sheet on the web content and mobile apps rule
- European Commission: European Accessibility Act
- axe-core README
- Lighthouse CI
- CA/Browser Forum: Baseline Requirements
- Let's Encrypt: From 90 to 45 days
- GDPR Article 28 (processor)
- EU AI Act, Article 50
- FTC: CAN-SPAM Act compliance guide for business
- UK PECR regulation 22
- WordPress REST API handbook
- MainWP (REST API, uptime monitoring, reports)
- ManageWP
- UptimeRobot API
- Cloudflare API
- Kinsta API
- Marker.io integrations
- BugHerd API v2
- Content Snare
- HubSpot API reference
- Pipedrive API reference
- PandaDoc API
- Asana developers
- ClickUp API
- Jira Cloud platform REST API
- GitHub REST API
- Help Scout developers
- Harvest API v2
- FreeAgent API
- Xero Accounting API
- QuickBooks Online API
- n8n pricing
- Google autocomplete phrasing checked for keywords (web design crm, website content collection, website feedback tool, website qa automation, wordpress care plans, ai helpdesk, white label web development)