Building an Autonomous Client Pipeline for a Freelance Studio
A serverless system that takes a project enquiry from first contact through quoting, payment, onboarding, and follow-up with almost no manual work.
This is my own studio platform, built and run in production. I am including it because it demonstrates the kind of system I build for clients, end to end.
The problem
Freelance work has a hidden cost that has nothing to do with writing code: chasing enquiries, writing quotes, sending invoices, following up on unpaid work, and remembering to check in on quiet leads. For a solo developer, that admin quietly eats the hours that should be billable.
I wanted a system where a stranger could find the site, describe their project, receive a quote, pay, and be onboarded without me touching anything until real work needed doing.
What I built
The public site is static and dependency-free, which keeps it fast and cheap to run. Behind it sits a set of serverless edge functions handling enquiries, quoting, payments, email, and scheduled automation.
Enquiries arrive through either a contact form or a branching application wizard that asks one question at a time. Both feed a single pipeline. An admin panel gives a live board of every lead with search, filtering, scoring, notes, and an activity timeline.
Quoting is AI-assisted: the system reads the answers a client gave and drafts a scoped quote with a price and timeline, which I can edit before sending. Sending a quote automatically creates a Stripe payment link, and when the client pays, a webhook marks the project won and triggers the onboarding email. No invoice chasing, no manual status updates.
Making it autonomous
A scheduled job runs daily and handles the work I would otherwise forget. It scores and tags new leads, flags spam, sends follow-up nudges to enquiries that have gone quiet, reminds clients about unpaid quotes, closes stale ones, requests reviews from finished projects, and re-engages old leads after a set period.
Every action is written to an activity log, which is also what makes the automation safe to run repeatedly: the system checks what it has already done before acting, so nobody receives the same nudge twice.
Clients get a magic-link status portal showing progress without needing an account, and a weekly digest email summarises the pipeline so nothing needs checking manually.
The template shop and personalisation agent
The second half of the system turns a low-cost product into a hands-off one. The site sells ready-made website templates, and buying one does not simply deliver a zip file.
After purchase, the buyer receives a setup link. They answer a handful of questions about their business, and an agent generates their copy from those answers, applies their branding to a tokenised version of the template, publishes the finished site, and emails them the live URL. The entire path from payment to live website runs without me.
Every step also routes people back toward custom work, so a small template sale doubles as a lead source for larger projects.
Engineering decisions worth noting
The whole backend is dependency-free and built on web standards rather than npm packages, which keeps cold starts fast and removes a class of maintenance and supply-chain risk.
Automated outreach was deliberately built as a supervised system rather than a fully automatic one. Anti-spam law in Canada and the United States carries serious penalties, and the responsible design was to draft messages automatically but require approval before sending, with unsubscribe handling and a separate sending domain to protect the main domain's reputation.
Stack
- Static HTML, CSS and vanilla JavaScript front end
- Serverless edge functions, dependency-free
- PostgreSQL via a hosted REST layer
- Stripe for payments, subscriptions and webhooks
- Transactional email with domain authentication
- LLM API for quote drafting and copy generation
- Scheduled cron jobs for the automation engine
Outcome
The pipeline runs end to end in production. Enquiries arrive, get scored and quoted, payments reconcile themselves, follow-ups send on schedule, and template buyers receive a personalised hosted site without manual involvement. The same architecture, minus the studio-specific parts, is what I build for clients who need bookings, payments, client portals, or automated workflows.