Stop scrambling: five numbers that keep work coming.
Read the skill at https://ai-skills-vault.pages.dev/skills/freelance-client-pipeline.md and install it as a skill in your agent. Follow it exactly, including its checklists. Then ask me the questions it requires and do the work.
Freelancers do not fail at the work. They fail at the gap between projects: no pipeline, so they take the first bad client who calls, who then eats the month that should have been spent finding good ones.
This skill builds the pipeline before you need it - a niche, proof, a price with a floor, a proposal that closes - and the five numbers that tell you whether next month is safe.
Do NOT use for: salaried job hunting (that is a different pipeline with a different funnel), or agency sales with a sales team - this is one person selling their own hours and outcomes.
1.1 Choose a niche by outcome and industry, not by tool: "billing automation for dental clinics", not "Python developer".
1.2 Write the sentence a past client could say to a friend: "she set up our invoicing so we stopped chasing payments". Referrals only travel in sentences like that.
1.3 Test the niche against three questions: can you name 20 buyers, have you solved their problem at least twice, and can you charge above ₹1,500 an hour for it?
| Niche test | Pass | Fail |
|---|---|---|
| 20 named buyers | a list exists | "everyone needs this" |
| Solved it twice | 2 case studies | learning on their money |
| Rate above ₹1,500/hour | yes | commodity work |
| Recurring need | monthly or quarterly | one-time project |
| Referral path | clients know each other | isolated buyers |
1.4 Keep a second niche as a bench, and never market both at once. Two niches read as "no niche".
1.5 Write down who you will turn down. A niche with no exclusions is not a niche, and bad-fit clients cost 3x a good one in time.
Gate: one niche sentence, 20 named potential buyers, two exclusion rules.
2.1 Three case studies beat twenty screenshots. Each is problem, what you did, result with a number, in that order.
2.2 If you have no client work, build the proof: a spec project for a real company, a teardown of their current flow, a measured before-and-after on a demo account.
2.3 Get one sentence of permission to use the client's name and logo. If they refuse, use the industry and the number without the name.
2.4 Put the numbers in the first line of each case study. "Cut invoice disputes from 14 a month to 2" is the whole story; the process is supporting detail.
2.5 Publish them as three pages on your own domain, plus a one-page PDF you can send in a chat.
| Case study field | Bad | Good |
|---|---|---|
| Result | "improved efficiency" | "disputes 14 to 2 per month" |
| Scope | "worked on billing" | "rebuilt invoice generation, 3 weeks" |
| Proof | "client happy" | quote with name and role |
| Duration | not stated | "3 weeks, ₹90,000" |
2.6 Update one case study per quarter. Proof decays: a 2023 result reads as history by 2026.
Gate: three published case studies, each with a number in the first line.
3.1 Price the outcome, not the hour, once you can predict your own speed. Hourly billing punishes you for getting better.
3.2 Set three numbers: an hourly floor for small work, a project price for defined scope, and a monthly retainer for ongoing work.
| Engagement | Structure | India anchor | When it fits |
|---|---|---|---|
| Audit or teardown | fixed | ₹15,000-40,000 | entry point, low risk |
| Defined project | fixed, 50/50 | ₹60,000-3,00,000 | clear scope, 2-6 weeks |
| Monthly retainer | monthly, in advance | ₹40,000-1,50,000 | ongoing maintenance or growth |
| Day rate | per day | ₹12,000-25,000 | consulting, workshops |
| Hourly floor | hourly | ₹1,500+ | small changes, undefined work |
3.3 Never quote before the discovery call. A number without context is a guess that becomes an anchor against you.
3.4 Quote one price, not three, on the first conversation. Options come later in the written proposal, where they belong.
3.5 Add 20% for scope you cannot see. Undefined integrations and stakeholder reviews are where projects lose money.
3.6 Charge in advance: 50% to start, 50% on delivery, or 100% for retainers. Waiting 45 days for a first payment is how freelancers finance their clients.
Gate: three numbers written down, with the scope each one covers.
4.1 Twenty-five minutes, six questions, no pitch. The call qualifies the client, and most of the selling happens by listening.
4.2 Ask: what happens today, what breaks, what it costs them, who decides, what timeline, and what they have already tried.
4.3 Quantify the pain: "how many hours a week does this take, and who does it?" A number turns a wish into a budget.
4.4 Identify the decision maker. A call with someone who cannot approve a ₹1,00,000 payment is a free consultation.
4.5 Say what you would do in one sentence, then stop talking. The silence after is where they say "yes" or "how much".
4.6 End with the next step and a date: "I'll send a one-page proposal by Thursday, and if it looks right we start Monday the 24th."
4.7 Take notes in the call and read them back in the last two minutes: "so the problem is X, the cost is Y hours a week, and the decision is yours". Misunderstanding caught here costs nothing; caught in week two it costs the project.
4.8 Disqualify out loud when it is wrong: budget under your floor, no decision maker, or a timeline of "someday". A polite no now leaves the door open later.
Gate: six questions asked, decision maker identified, next step dated.
5.1 One page. Anything longer is read after the decision, not before it.
5.2 Sections: the outcome in one line, what you will do (5 bullets), what they get (deliverables), timeline, price and payment terms, what you need from them.
5.3 Put the price on the page. A proposal without a price invites a call about price.
5.4 Include three options when the buyer needs a choice: essentials, standard, and with-support. Most pick the middle, which is why the middle is the one you want to sell.
Outcome: invoice disputes under 3 a month within 6 weeks.
Scope: audit current flow, rebuild invoice generation, 2 review calls, handover doc.
Timeline: 3 weeks from kickoff, kickoff within 5 days of signature.
Price: Option A ₹90,000 (scope only) / B ₹1,20,000 (+ payment reminders) / C ₹1,60,000 (+ 3 months support).
Payment: 50% on signature, 50% on handover. GST 18% extra.
From you: read access to the billing system, 2 hours of review time per week, one decision maker.
Not included: data migration beyond 5,000 rows, third-party licence fees.5.5 State what is not included. The exclusions section prevents 80% of scope arguments.
5.6 Send it as a PDF and paste the key terms in the email body, so it is readable on a phone without opening anything.
5.7 Follow up once after 4 working days, then stop. A third follow-up costs you the referral.
Gate: proposal sent within 48 hours of the call, with price and exclusions.
6.1 A one-page agreement is enough for most freelance work: scope, price, payment terms, timeline, IP, confidentiality, termination.
6.2 Scope by reference: attach the proposal as Annexure A and say the proposal is the scope.
6.3 Payment terms: 50% advance, balance on delivery, 18% GST extra if registered, late payment interest at 1.5% a month.
6.4 IP transfers on final payment, not on delivery. Before that, you own the work.
6.5 Termination: either side with 14 days' notice, and work done to date is payable. Without this clause, a cancelled project leaves you unpaid for three weeks.
6.6 Keep client data handling explicit: what you will store, where, and for how long. Under India's DPDP Act you are a data processor for their data, and that has obligations.
6.7 Have a lawyer review the template once. A ₹8,000 review of a ₹1,00,000 contract template pays for itself the first time a client stalls.
6.8 Send the agreement as a PDF with a signature field, and keep the countersigned copy in the project folder - not in an inbox.
Gate: a signed agreement before the first line of work, with scope annexed.
7.1 Register for GST once turnover crosses ₹20 lakh for services (₹10 lakh in special category states). Below that, you may still register voluntarily if clients want input credit.
7.2 Charge GST only if registered, and show it separately on the invoice: CGST plus SGST for a client in your state, IGST for another state.
7.3 Invoice fields that matter: your GSTIN, invoice number and date, client name and GSTIN, SAC code, description, taxable value, tax rate and amount, place of supply.
7.4 Number invoices in one continuous series per financial year, and never reuse a number.
7.5 Set payment terms at 7-15 days for small clients and 30 for larger ones, and put the due date on the invoice itself.
7.6 Track receivables weekly. One client above 45 days overdue is a cash-flow problem, not an admin detail.
7.7 File returns on time even in a month with no revenue; a nil return is a filing, and late filing carries a fee per day.
7.8 Keep invoice data as structured records, not only as PDFs, so a year-end reconciliation is a query and not an afternoon of reading:
{"invoice_no":"INV/2026-27/0007","issued_on":"2026-11-15","client":"Acme Clinics",
"client_gstin":"29ABCDE1234F1Z5","place_of_supply":"29","sac":"998313",
"taxable":90000,"cgst":8100,"sgst":8100,"igst":0,
"terms":"50% advance, balance on handover","due_on":"2026-11-30","paid_on":null}Gate: an invoice template with every required field, and a receivables sheet.
8.1 Send a Friday update: done this week, next week, blockers. Four lines, every week, without being asked.
8.2 Work in visible milestones with a demo at each one. Clients who cannot see progress invent doubts.
8.3 Keep a single shared document per project: scope, decisions, open questions, dates. Decisions made in a call are lost in a week.
8.4 Log change requests in writing with a price and a date effect. "Sure, I can add that" without a number is how a 3-week project becomes 9.
8.5 Raise problems early and with options. A client told about a delay with two options stays a client; one surprised at the deadline does not.
8.6 Send a handover document at the end: what was built, how to run it, who to call. It is the cheapest way to get the next project.
Gate: weekly update sent every week of the project, handover delivered.
9.1 Offer a retainer at handover, when the value is fresh: "₹40,000 a month for maintenance, monitoring and 8 hours of changes."
9.2 Price the retainer on the client's cost of the thing breaking, not on your hours. Hours invite a comparison with the cheapest hourly rate they know.
9.3 Cap the hours in the retainer and state the overage rate. Uncapped retainers become a second job with one client.
9.4 Ask for a referral in the same message, naming the type of client you want. Vague referral asks produce nothing.
9.5 Ask for one sentence of testimonial with a number in it, and permission to publish.
9.6 Keep in touch every quarter with something useful: a benchmark, a warning about a change, a small teardown. Not "checking in".
9.7 Put the retainer offer in the handover document itself, so the client reads it while the value is visible rather than in a separate sales email a week later.
Gate: a retainer offered at every handover, referrals asked by name.
10.1 Pipeline value: total quoted work not yet closed. Below one month of expenses, you are not running a business.
10.2 Conversations per week: new qualified conversations started. Five a week is the number that keeps a solo pipeline alive.
10.3 Close rate: proposals accepted over proposals sent. Below 25% means the qualification or the price is wrong.
10.4 Days to payment: average from invoice to money in the bank. Above 30, tighten terms.
10.5 Revenue concentration: the share of income from your largest client. Above 50% is a job with extra steps.
| Metric | Danger | Healthy |
|---|---|---|
| Pipeline value | under 0.5 month of costs | 1.5-3 months |
| New conversations per week | under 2 | 5 |
| Close rate | under 20% | 30-50% |
| Days to payment | over 30 | 7-15 |
| Largest client share | over 50% | under 30% |
10.6 Review the five numbers on the first Monday of the month, in 15 minutes, in writing. The review is what makes the pipeline a system.
10.7 Keep one page per client: start date, scope, rate, renewal date, referral given or owed. It is the file you read before a renewal call.
10.8 Raise your rate once a year, on new clients first, by 10-20%. Existing clients keep the old rate for one renewal cycle and are told the new one with 30 days' notice.
Gate: all five numbers recorded for the last three months.
A freelance developer in Pune, 14 months in, moving from scrambling to a pipeline.
| Month | Conversations | Proposals | Closed | Revenue | Largest client share |
|---|---|---|---|---|---|
| 1 | 3 | 2 | 1 | ₹70,000 | 100% |
| 3 | 9 | 4 | 2 | ₹1,40,000 | 64% |
| 6 | 18 | 7 | 3 | ₹2,30,000 | 43% |
| 12 | 21 | 9 | 4 | ₹3,60,000 | 28% |
The change that mattered was not a higher rate; it was the niche sentence and three case studies, which made referrals specific enough to arrive without asking.
| Symptom | Real cause | Fix |
|---|---|---|
| Client went quiet after the quote | Price sent without a call, so there was no context | Run discovery first, then propose with a range of options |
| Project ran 3x the estimate | Scope never written down, changes accepted verbally | Annex the proposal and price every change request |
| Paid 60 days late | No advance and no due date on the invoice | 50% upfront, due date on the invoice, 1.5% monthly interest |
| Every client negotiates | Niche too broad, so price is the only difference | Narrow the niche, publish case studies with numbers |
| Feast and famine | Pipeline built only when work runs out | Five new conversations a week, every week |
| One client is 70% of income | Retainers sold to whoever was already there | Cap concentration at 30%, keep the bench niche warm |
| Referrals never arrive | Asked vaguely, at the wrong moment | Ask by name at handover, with the client type stated |
| GST notice for a missed month | Nil months not filed | Calendar reminder on the 11th and 20th of every month |
| Rate stuck for three years | No annual review of pricing | Raise 10-20% on new clients each year, tell existing ones in advance |
Read the skill at the URL above and help me build a freelance pipeline. Ask me: what I do, who I have worked for, my current rate, whether I am GST registered and how many months of expenses I have. Then write the niche sentence and 20 named buyers, three case studies in problem-result-number form, and my three prices with the scope each covers. Then the six-question discovery call script, the one-page proposal with three options and exclusions, the contract checklist, and the invoice fields I need. Finish with the five pipeline numbers and a monthly review template. Do not invent clients, results or rates I have not given you.