CRM automation for web design agencies, from enquiry to signed proposal
Website enquiries often arrive as one line and a link to an old site. We build a CRM workflow in HubSpot, Pipedrive or the CRM you use that captures every enquiry, drafts a structured brief with a quick technical snapshot of the current site, lists the questions to ask, tracks proposals and creates the project in your delivery tool when the client signs. A typical build costs $1,000 to $2,500 per workflow and takes about four weeks.
The problem
Why web design enquiries take so long to price
A prospect writes that they need a new website, maybe with a link and a rough deadline. Before anyone can price it, someone has to look at the current site, guess at page count, integrations and content, and work out what to ask on the call. That research is repeated for every enquiry, including the ones that never become projects.
Proposals then disappear into the inbox. Without a pipeline that knows a proposal was viewed but not signed, follow-up depends on memory, and good projects go to whichever studio replied twice.
What we build
What our web design CRM automation includes
Every enquiry captured
Website forms, email, chat and referral introductions logged as deals with a source and budget band.
Structured brief draft
Goals, audience, required features, integrations and deadline pulled from the enquiry into your brief template for the project manager to edit.
Current-site snapshot
Page count estimate, CMS and technology, speed, SSL and obvious accessibility issues on the existing site, using our own audit tools.
Questions to ask
A list of open questions for the discovery call, so assumptions are confirmed before pricing.
Proposal tracking
PandaDoc or your proposal tool updates the deal when proposals are viewed or signed; quiet proposals get a drafted follow-up.
Signed project handover
Signing creates the project, folders and kickoff tasks, and starts content collection.
Who does what
Automation does the chasing, people make the calls.
-
01
Automated
Enquiry arrives
A form or email creates a deal with its source in the CRM.
-
02
Automated
Brief and snapshot
A brief draft and a technical snapshot of the current site are attached to the deal.
-
03
Automated
Proposal tracked
Proposal events move the deal; quiet proposals get a drafted follow-up.
-
04
Project manager review
Project manager edits
The project manager edits the brief and confirms every assumption with the client.
-
05
Project lead or agency owner decides
Price and scope
Pricing, payment terms and what the agency commits to are decided by the owner.
How it behaves
How the web agency CRM behaves
What the prospect sees
- A quick, specific reply to their enquiry
- A discovery call with someone who has looked at their current site
- A follow-up on the proposal, not silence
What the agency sees
- Every enquiry in one pipeline with a brief draft
- A technical snapshot of the current site
- Signed projects created in the delivery tool
What the automation does
- Captures enquiries and drafts briefs
- Runs quick checks on the existing site
- Tracks proposals and hands off on signing
Edge cases and fallbacks
- No current website
- The snapshot is skipped and the brief asks about domain and hosting instead.
- Enquiry is clearly out of scope
- Tagged for the owner to decline politely or refer on.
- Prospect opts out of emails
- Every follow-up stops and the opt-out is recorded.
- CRM or proposal API down
- Events are queued and retried; the project manager gets an alert.
Architecture
Enquiry to proposal for a web agency at a glance.
- Input
- Logic and services
- AI step
- Data
- People
- Output
How it flows
- 1 A website enquiry reaches the n8n workflow from a form or email.
- 2 The current site is checked for technology, speed and SSL, and a brief is drafted from the enquiry.
- 3 Both are attached to a CRM deal, and proposal events move the deal through stages.
- 4 The project manager confirms scope with the client, and signing creates the project with kickoff tasks.
Project planner
How the project runs, phase by phase.
CRM automation for web design agencies: enquiry to proposal project plan
Typical time to launch: about 4 weeks, then support
-
01
Discovery
2 to 3 days
Enquiry sources, brief template, proposal tool, stages and handover to delivery.
-
02
Design
2 to 3 days
Stage definitions, brief fields, snapshot checks, follow-up timing and project template.
-
03
Build
1 to 2 weeks
Capture, brief draft, site snapshot, proposal events and project creation.
-
04
Shadow run
About 1 week
Briefs are drafted for live enquiries while the team works as usual, and we compare.
-
05
Launch
1 to 2 days
Switch over and walk the team through the pipeline.
-
06
Support
Ongoing
New services, templates and stages as the agency changes.
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
Sources, brief template, stages and handover.
$250 – $450
-
Build
Capture, brief draft, site snapshot and follow-ups.
$450 – $1,200
-
Integrations
CRM, proposal tool and project tool.
$150 – $450
-
Testing and shadow run
Live enquiries compared with manual briefs.
$100 – $250
-
Launch and training
Switch-over 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. CRM seats, proposal software 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.
- CRM subscription: Your CRM vendor's own plan.
- 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; one brief per enquiry is a small amount.
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.
US: CAN-SPAM for follow-ups
The FTC guide states CAN-SPAM makes no exception for business-to-business email and opt-outs must be honoured within 10 business days.
Source: www.ftc.govUK: PECR marketing emails
Regulation 22 of PECR sets consent and soft opt-in rules for marketing emails to individual subscribers.
Source: www.legislation.gov.ukEnquiry data under GDPR
Enquiries contain personal data; vendors storing them on your behalf, such as the CRM and AI provider, need Article 28 processor terms.
Source: gdpr-info.euFree 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
CRM automation for web design agencies: enquiry to proposal questions, answered.
One your team will keep updated. HubSpot suits agencies that run inbound marketing, Pipedrive suits owner-led sales, and a web development CRM inside your project tool can work for small studios. We automate the one you choose.
It drafts the brief and the questions, and can prefill a proposal template with scope and timeline. Pricing, payment terms and commitments are decided by the owner; the draft is a starting point, not a quote.
It runs quick checks on the prospect's existing site: technology and CMS, speed, SSL and obvious issues, using tools we built. It gives the project manager talking points, not a full audit.
PandaDoc has a documented API with document events, and most proposal tools offer webhooks. We confirm your tool on the free call.
Yes. The brief template can branch by project type, such as marketing site, ecommerce or custom application, with different questions for each.
Enquiries by source, time to first reply, briefs completed before the call, proposals followed up and win rate by project type.
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 servicesWebsite 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