A free, text-first technical reference for freelancers and small service businesses that want to build a simple client acquisition system without paid ads.
This project treats client acquisition as an operational system rather than a collection of disconnected marketing tactics.
No videos. No motivational content. No email signup required. No complicated funnel architecture.
The manual focuses on components, decision rules, implementation steps, and common failure modes.
flowchart LR
A[Traffic Sources] --> B[Service Landing Page]
B --> C[Contact or Opt-In Trigger]
C --> D[Follow-Up Sequence]
D --> E[Automation]
- Create a simple service landing page
- What to put on a service landing page
- Service landing page vs homepage
- Write a short follow-up sequence
- How many follow-up emails should you send?
- Simple follow-up sequence
- Automate the client acquisition system
- How to automate client acquisition
- Basic lead follow-up automation
- Use one clear landing page instead of sending prospects through multiple disconnected paths.
- Give every visitor one obvious next action.
- Choose the contact trigger based on the prospect's level of intent.
- Use a short, consistent follow-up sequence.
- Automate repetitive steps only after the manual process is clear.
- Keep the system simple enough to maintain without a dedicated marketing team.
This manual is designed for:
- freelancers
- consultants
- agencies
- independent service providers
- small service businesses
It is not intended to document paid advertising, large sales teams, complex enterprise CRM systems, or content-heavy personal brands.
Version: 1.0 Status: Work in progress Last reviewed: June 2026
The current version documents the basic system architecture and its core components. Additional decision guides, implementation notes, and failure modes may be added over time.
This manual is free to read and does not require an email signup.
Some implementation examples may contain affiliate links. These links do not change the price for the reader.
The underlying architecture and decision rules are intended to remain tool-agnostic. Specific tools are presented only as implementation examples.
Errors, unclear explanations, and suggestions can be submitted through GitHub Issues.