A client-acquisition stack under $50 that does not become a second job

A client-acquisition stack has four jobs: capture an inquiry, decide whether it fits, book the next conversation, and preserve context until the deal is won or closed. If a tool does not improve one of those handoffs today, it probably does not belong in the starting stack.

The default below uses HubSpot Free as the system of record because its published tools can keep forms, contact records, and a basic sales path together. Calendly and Tally are optional substitutions—not extra apps you must install. The result is not universally “best”; it is deliberately small and reversible.

Start with one system of entry

HubSpot can display limited-time offers. This guide does not use a promotional number as a permanent baseline.

Build the path in five steps

1. Define the acceptance fields

Ask only for information you will use before the next contact: name, work email, company or project URL, project type, budget band, desired start window, and a short problem statement. If you collect marketing consent, make the choice explicit and separate it from the project inquiry. Never collect passwords, payment data, health information, or other sensitive data in a general lead form.

2. Create a small pipeline

Use stages representing a real change in commitment: New inquiry → Qualified → Discovery booked → Proposal sent → Won / Closed. “Follow up someday” is not a stage; it is a task with a date.

3. Publish one discovery-call link

Offer one duration and say what the call is for. Example: “A 25-minute fit call to clarify the problem, timing, decision process, and next step. This is not a free consulting session.” Connect only the calendar that accurately reflects your availability.

4. Write two messages, not a funnel

Create an immediate receipt stating when a human response will arrive, and a qualified-lead follow-up that points to the booking link. Do not simulate personal attention with “I just reviewed this” if nobody did.

5. Run a Friday pipeline review

For every open record, choose one next action and one date. Close records that do not fit. Simple weekly discipline prevents more leakage than another dashboard.

Swap a component only when its boundary fits better

Do not upgrade on a feeling. Log the constraint.

Keep this one-line ledger for 30 days:

Constraint: [what failed]
Frequency: [times per month]
Cost now: [minutes × internal hourly value + lost opportunities]
Paid fix: [plan and exact feature]
New monthly cost: [subscription + seats + contacts + admin]
Decision date: [after enough observations]

Upgrade when the recurring cost of the constraint is credibly higher than the full cost of the fix—not when a countdown banner creates urgency.

What this stack does not solve

• Traffic: software does not create qualified demand by itself.
• Positioning: a form cannot rescue a vague offer.
• Consent: a project inquiry is not automatically newsletter permission.
• Deliverability: no platform can guarantee inbox placement.
• Sales judgment: a score cannot replace a clear fit rule at low volume.