Website content collection that chases clients so you do not have to
The build is ready and the content is not. We build a content collection workflow that turns the approved sitemap into a request per page, collects copy, images, bios and product data in one place, sends scheduled reminders in a tone your project manager approves and shows which missing items are blocking launch. Logins go through a password manager, never email. A typical build costs $1,000 to $2,500 per workflow and takes about three to four weeks.
The problem
Why website content collection delays launches
Content is the most common reason website projects run late. The client means to send the copy, then the team photo, then the product list, and every week the project manager writes another polite email while developers wait or build around placeholders.
Collecting through email and shared drives also loses things: the latest version of the About page, the images in the right size, the login for the domain registrar. Nobody can say exactly what is still missing.
What we build
What our website content collection automation includes
Requests from the sitemap
Each page in the approved sitemap becomes a content request with the fields it needs.
One place to upload
A form or portal for copy, images and documents, with guidance on sizes and formats, or a connection to Content Snare if you use it.
Scheduled reminders
Friendly nudges at intervals the project manager sets, escalating to a call after a set number.
Blocking view
Which missing items block which pages, and the launch date at risk.
Secure credentials route
Logins requested through your password manager share link, never typed into email.
Files to the right place
Uploads renamed and saved into the project folder in Google Drive, Dropbox or your storage.
Who does what
Automation does the chasing, people make the calls.
-
01
Automated
Sitemap approved
Approval of the sitemap creates content requests per page.
-
02
Automated
Requests sent
The client gets one link with everything needed and guidance per item.
-
03
Automated
Reminders
Scheduled reminders go out for missing items; uploads update the status.
-
04
Project manager review
Project manager checks
The project manager reviews uploads and asks for changes where needed.
-
05
Project lead or agency owner decides
Deadlines
Conversations about delays or moving the launch date are handled by the project lead.
How it behaves
How content collection behaves
What the client sees
- One link listing everything needed per page
- Guidance on what to send and in what format
- Friendly reminders, then a call
What the agency sees
- Uploads saved in the project folder
- A blocking view against the launch date
- Fewer chasing emails to write
What the automation does
- Creates requests from the sitemap
- Sends reminders on schedule
- Updates status as items arrive
Edge cases and fallbacks
- Client sends content by email anyway
- The project manager forwards it and the item is marked received.
- Sitemap changes mid-project
- New requests are added and removed pages are closed.
- Upload in the wrong format
- Flagged for the project manager to request again.
- Storage or form outage
- Requests resume when the service returns; reminders pause meanwhile.
Architecture
Website content collection for a web agency at a glance.
- Input
- Logic and services
- Output
- Data
- People
How it flows
- 1 Approving the sitemap creates a content request for every page and its fields.
- 2 The client gets one link to upload copy, images and documents, with guidance per item.
- 3 Files land in the project folder and reminders go out for anything still missing.
- 4 The project manager reviews uploads and sees which missing items block the launch.
Project planner
How the project runs, phase by phase.
Website content collection & client chasing project plan
Typical time to launch: about 3 weeks, then support
-
01
Discovery
2 to 3 days
How content is collected today, sitemap format, storage and reminder tone.
-
02
Design
2 to 3 days
Request fields per page type, upload guidance, reminder schedule and blocking rules.
-
03
Build
About 1 week
Request generation, form or Content Snare link, reminders, file routing and blocking view.
-
04
Shadow run
About 1 week
Run on a live project with the project manager reviewing every reminder.
-
05
Launch
1 to 2 days
Switch on for new projects.
-
06
Support
Ongoing
New page types and request templates.
What it runs on
Real products only, connected through the access each vendor provides. See all integrations
Cost estimate
What it costs, line by line.
-
Discovery and design
Request templates, guidance and reminder tone.
$200 – $400
-
Build
Request generation, reminders, file routing and blocking view.
$500 – $1,300
-
Integrations
Form, storage and project tool.
$150 – $400
-
Testing and shadow run
Live project run.
$100 – $250
-
Launch and training
Switch-on and 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. Form tool, storage 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.
- Form or collection tool: Your vendor's own plan.
- n8n: Self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).
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
Privacy and consent
Rules we design for, with the sources.
Client data in uploads
Team bios and customer lists are personal data; storage and form vendors need Article 28 processor terms.
Source: gdpr-info.euAccessible content from the start
Requests ask for image descriptions and plain headings so the finished site can meet WCAG 2.2.
Source: www.w3.orgCredentials never by email
Logins are requested through a password manager share, and access is logged for handover.
Free tools
Try these first, free.
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.
FAQ
Website content collection & client chasing questions, answered.
Ask per page, with clear guidance on what each field needs, in one place, with reminders on a schedule. That is what this workflow does, using a form, a portal or Content Snare.
We build the template from your sitemap and page types, so a services page asks for different things than a team page. You keep the template for future projects.
Yes. It starts when the sitemap is approved, which usually follows onboarding, and can include onboarding items such as domain and hosting access.
You set the tone and the interval. After a set number of reminders the workflow stops and asks the project manager to call instead.
Yes, through cloud storage links or direct upload, with guidance on formats. Our free image tools help clients resize before uploading.
Days from sitemap approval to content complete, reminders per project and launch dates moved because of content.
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.
More for web developers
All servicesCRM 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
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