DEV Community: Alfred P

5 Questions to Ask Before Taking Any Freelance Project

Alfred P — Mon, 25 May 2026 16:34:48 +0000

Not every project is worth taking.

This is a hard lesson because when you are building a freelance business, every project feels like one you cannot afford to say no to. But the wrong projects cost more than their invoice value: they consume time you could spend on better clients, create stress that damages your other work, and sometimes leave you with less money than you started with.

Five questions that help you decide before you commit.

1. Is the scope actually clear?

Not "can I build something for this client" but "can I describe the finished product in a single paragraph with enough specificity to build to?"

If you cannot describe the deliverable precisely, you cannot estimate it accurately. Vague scope leads to underquoting, scope creep, and a fixed-price project that bleeds money.

Ask yourself: if the client and I disagreed at the end, would the contract protect me? If the answer is no, the scope needs more definition before you start.

2. Can I talk to the actual decision-maker?

Projects run by committee or filtered through a middleman who then interprets to someone else are high-risk.

Find out early: who has final say on design decisions, on delivery acceptance, and on payment approval? If you cannot get in front of that person at least once before the project starts, you are going to spend a lot of time getting conflicting feedback from people who do not have authority to actually approve anything.

3. Does the timeline make any sense?

"We need this in two weeks" for a six-month project is a red flag, not a challenge.

Unrealistic timelines create one of two bad outcomes: you rush and deliver something below your standard, or you work unsustainable hours and resent the project by the end. Neither is good for your reputation or your wellbeing.

If the timeline does not work, say so and propose a realistic one. Clients who accept that are clients you can work with. Clients who insist on the impossible timeline are showing you how the rest of the project will go.

4. Do I actually want to work with this person?

This sounds unserious. It is not.

You will spend hours communicating with this person. Their communication style, their responsiveness, their tendency toward reasonable or unreasonable feedback will affect your daily experience for weeks or months.

The first interaction you have with a client is the best version of the working relationship. If it is already uncomfortable or frustrating in the sales stage, factor that in.

5. Is the rate actually right?

Not "is this a rate I would accept" but "is this a rate at which this project is profitable?"

Calculate: estimated hours times your target rate, plus a buffer for revision cycles and client communication. Compare that to the quoted price. If the math does not work at your target rate, you are either underquoting or taking a below-rate project.

Both are okay sometimes. They should be conscious decisions, not accidents.

Saying no to the wrong project creates space for the right one. The discipline to ask these questions consistently is one of the things that separates sustainable freelance businesses from ones that feel like they are always barely holding on.

The Solopreneur AI Toolkit includes prompts for evaluating projects and writing airtight proposals. EUR 12.

How to Write a Freelance Invoice That Gets Paid on Time

Alfred P — Sun, 24 May 2026 15:53:24 +0000

Late payments are one of the most common complaints in freelancing.

Most of the time the invoice itself is part of the problem.

A vague invoice with no due date, no payment instructions, and no consequences for late payment is an invoice designed to be ignored. Here is how to write one that gets paid.

Include a specific due date, not "net 30"

"Net 30" is accounting language. Most clients think it means "sometime in the next month."

Write: "Payment due by [specific date]."

Specific dates get actioned. Vague terms get filed and forgotten.

Put the payment method front and center

Do not make clients figure out how to pay you. Tell them exactly how:

Bank transfer: [account details]
PayPal: [link]
Stripe: [link]

One click to pay is better than three steps to figure it out. Every extra step is friction that delays payment.

Include a late payment clause

"Invoices unpaid after [due date] are subject to a [X]% monthly late fee."

Most clients will never trigger this. Its presence signals that you track payment timing and you will follow up. That signal alone improves payment rates.

Reference the project clearly

"Invoice for [specific project name], [phase/deliverable], as per contract dated [date]."

Clients who process multiple invoices need to know immediately what this is for. Vague invoices get held for clarification. Specific invoices get approved.

Send immediately on delivery

Do not wait until the end of the month. Invoice on the day you deliver.

The client's satisfaction is highest the moment they receive good work. That is the moment to invoice. Waiting a week creates distance between the good feeling and the payment request.

Follow up before the due date

Three days before the due date, send a short reminder: "Just a heads up that invoice [number] for [project] is due on [date]. Let me know if you need anything from my end to process it."

This is not chasing. It is professional communication that removes the "I forgot" excuse.

What to do when payment is late

Day 1 after due date: friendly reminder. "Invoice [number] was due yesterday. Sending a reminder in case it slipped through."

Day 7: firmer follow-up. "Invoice [number] is now [X] days overdue. Please confirm when we can expect payment."

Day 14: phone call or escalation to whoever handles accounts payable.

Most late payments resolve at the first reminder. A small percentage need the escalation. Almost none need legal action if you follow up consistently.

Invoicing is not just admin. It is the last step of the project and it deserves as much care as the work itself.

The Freelance Command Center includes an invoice tracker and follow-up system so nothing slips. EUR 17.

The Client Onboarding Checklist That Prevents 90% of Project Problems

Alfred P — Sat, 23 May 2026 11:46:30 +0000

Most freelance project problems are visible before the project starts.

The wrong clients, unclear scope, missing access credentials, the stakeholder who was not in the initial conversation - all of these create problems later. Most could be caught in the first week with a proper onboarding process.

Before work starts

Signed contract. No exceptions. Nothing starts without one.

Deposit paid. If your terms include a deposit, payment clears before work begins.

Kickoff call scheduled. Not to start work - to confirm alignment.

The kickoff call agenda

Five things to cover:

Who is the final decision-maker? Not who you have been talking to - who has final authority on design decisions, feature priorities, and delivery acceptance. Get this confirmed explicitly.

What does success look like? Ask them to describe the project when it is done and they are happy. Their answer tells you if expectations match scope.

What are the non-negotiables? Specific deadlines? Technologies they cannot use? Things previous developers did that they definitely do not want repeated?

How do they prefer to communicate? Async email, Slack, scheduled calls? Settle this early.

What could make this project harder than expected? Ask directly. Clients often know about complications - internal approvals, data issues, unreliable third-party dependencies - that they forgot to mention.

Post-kickoff: the onboarding document

Send a one-page summary: what we agreed the project is, key milestones, what I need from you and when, my communication schedule, how to reach me.

This confirms alignment and gives both sides a reference if memory differs later.

The access checklist

Before starting technical work, confirm you have:

All logins and credentials needed
Codebase access if working on existing code
Staging/development environment access
Design files, brand guidelines, or content if in scope

Discovering on day three that you lack critical access delays projects and frustrates clients.

The one thing that prevents most problems

Most freelance project problems come from mismatched expectations that existed from the beginning and were never surfaced.

The onboarding process surfaces them early, when they are easy to address, rather than late, when they create conflict.

Two hours at the start saves ten hours of conflict management later.

The Freelance Command Center includes a complete client onboarding template and checklist. EUR 17.

How I Turned One Good Client Into Five Without Cold Outreach

Alfred P — Fri, 22 May 2026 16:39:28 +0000

My first real freelance client came from a former colleague.

My next four came from that client.

Not referrals in the formal sense. The natural result of doing good work and asking simple questions at the right moment.

What actually happened

The project was a dashboard for internal reporting. Delivered on time, within scope.

At delivery I asked one question I had not asked before: "Now that we are wrapping up, are there other teams at your company that deal with similar reporting problems?"

The client introduced me to two other teams within the same company. Both became clients within 60 days.

One question. Two clients. Zero cold outreach.

Why it works

Your happy client has already done the trust-building work for you.

When they introduce you to a colleague, that colleague's default is trust rather than skepticism. You are not a stranger with a cold pitch. You are someone their colleague vouched for.

Conversion rate on warm introductions: roughly 70-80% become at least a conversation, 50-60% become paid projects. The math makes the 30 seconds it takes to ask obviously worthwhile.

Expanding into the same company

Doing good work for one team often opens doors to others. Especially in larger organizations where teams have separate budgets and limited visibility into what other teams are doing.

After every successful project: "Is there anyone else at your company you think might benefit from this kind of work?"

Not aggressive. A professional question clients are happy to answer when they liked working with you.

Vertical expansion with the same client

A client who hired you for Project A and was happy is already open to Project B. No trust rebuilding needed.

After every delivery, discuss what comes next: "Now that this is done, what is the next thing on your list I might be able to help with?"

Some have nothing. Others have a backlog. Either is useful information.

Staying in touch without selling

Between projects, maintain contact with clients you want to work with again. Quarterly check-ins. A relevant article when something specifically matches their situation.

None of this is a sales pitch. All of it keeps you present when they have a new project.

This requires two things that are not systems: do genuinely good work, and ask simple questions.

The good work builds trust. The questions open doors.

The Freelance Command Center includes a client tracker that keeps the full history of every project and relationship. EUR 17.

Why Freelancers Who Specialize Earn More (The Logic Behind It)

Alfred P — Thu, 21 May 2026 17:32:53 +0000

"I specialize in everything" is a sentence that costs freelancers money.

I know because I spent two years saying it. Not in those exact words, but that was the practical effect of marketing myself as someone who could build anything for anyone.

The generalist problem

When you offer everything to everyone, you compete with everyone on price.

A client looking for "a developer" finds hundreds of options. The primary filter becomes price. You win projects by being cheap enough, not by being the right fit.

When you offer something specific to a specific type of client, the comparison set shrinks dramatically. A client looking for "a developer who builds internal tools for logistics companies" finds very few options. Price becomes less important because the alternatives are not clearly equivalent.

What specialization actually means

There are three types that work well for freelancers.

By problem type. Dashboard and reporting systems. E-commerce performance optimization. API integrations. Clients who have this problem seek you out.

By industry. Legal tech. Healthcare data. Supply chain software. You understand the domain problems deeply, which makes your solutions better and your sales conversations faster.

By client type. Early-stage SaaS. Established professional services. Non-profits. You understand how they think, what they worry about, and how to work with them.

You can combine these. "I build client portals for legal and professional services firms" is defensible in a way that most generalists cannot compete with.

Why specialists charge more

Reduced perceived risk. Hiring a specialist feels safer. Clients feel like they are hiring someone who has solved their problem before.

Faster time to value. Specialists produce results faster in their area. Clients understand they are paying for efficiency.

No direct comparison. When you are the developer for legal client portals, the client cannot compare you to "a developer who builds websites." You are in a different category.

The transition

Moving from generalist to specialist does not require turning down all existing work immediately.

Start by marketing yourself as a specialist while continuing to take generalist work. Gradually shift your portfolio, content, and outreach. Raise rates for specialized work.

Within six to twelve months, the type of work you attract changes.

The Freelance Command Center includes a proposal system to present your specialization consistently. EUR 17.

The Async Communication System That Eliminated My Client Check-in Calls

Alfred P — Wed, 20 May 2026 18:03:17 +0000

I used to spend four to six hours a week on status calls.

Not discovery calls. Not scope calls. Status calls. "Where are we, what is done, what is next."

This time is not zero value. But six hours of calls to convey information that could be a five-minute read is an expensive way to deliver it.

The weekly update template

Every Friday, every active client gets a short email with the same structure:

Done this week: [Completed items, specific]

In progress: [What is actively being worked on, expected completion]

Needs from you: [Specific decisions, content, or approvals needed]

Next week: [What I plan to work on]

Current status: On track / At risk / Blocked

Under 200 words. Takes five minutes per client.

Why it works

Clients book check-in calls because they are anxious about progress. They do not know where things stand, so they ask.

The weekly update removes the uncertainty before it becomes anxiety. When clients receive consistent updates every Friday, they stop needing to ask.

The "needs from you" section is the most important part. When I am waiting on content or a decision, it is documented. This protects me when timelines slip and it motivates clients to act on their items.

The project dashboard

For projects over six weeks, I set up a simple shared Notion page with milestones, status, and links to deliverables.

The client can check it anytime without messaging me. Most check it once a week. Fewer interruptions mid-session.

Handling clients who still want calls

Structure those calls to be short and decision-focused. "We have 30 minutes. Let me cover the three things that need your input."

A client who received your Friday update before the call has already read the status. The call becomes decisions and relationship, not status reporting.

Setting expectations at project start

Tell clients in the onboarding email: "I send weekly updates every Friday covering what was done, what is in progress, and what I need from you. If something comes up that needs your input before Friday, I will message you directly."

When clients know the system exists from day one, they adopt it naturally.

Async communication is not about being unavailable. It is about making sure the communication you do have is high quality and decision-driven.

The Freelance Command Center includes client communication templates including the weekly update format. EUR 17.

How to Price a Discovery Call (And Why You Should Charge for It)

Alfred P — Tue, 19 May 2026 17:41:27 +0000

Free discovery calls are one of the most expensive things freelancers offer.

Not because calls take time. Because free calls attract people who are not serious buyers.

When you charge for a discovery call, the quality of people who book changes immediately.

What a paid discovery call actually is

A paid discovery call is not a sales pitch. It is a short consulting engagement with a specific deliverable.

You spend 60-90 minutes understanding the client's problem, their constraints, and what they have already tried. At the end, they get a written document: a clear problem statement, your initial thinking on approach, and enough information for you to provide an accurate estimate.

The client gets real value from the session even if they do not hire you for the full project.

Why free calls filter wrong

When discovery calls are free, you attract serious buyers AND people using your time for free consulting with no intention to hire.

Both look identical in the calendar. You cannot tell them apart until the call ends and they disappear.

A paid discovery call eliminates the ones not committed enough to invest in understanding their own problem.

How to price it

Two to four hours of your standard rate. If you charge $100/hour, a discovery call is $200-$400.

You are genuinely spending time preparing, running the session, and producing a written output. Price it like the professional service it is.

How to position it

"I offer paid discovery sessions for new projects. In 90 minutes, we get clear on what you need and what a solution would actually look like. You get a written brief at the end. If we move forward together, the session fee applies to the project."

That last sentence matters. It reduces friction and signals confidence in your ability to convert.

What to cover in the session

What problem are you trying to solve? (Ask why multiple times.)
What does success look like in 90 days?
What have you already tried?
What are the constraints? (Budget range, timeline, technical requirements)
Who else is involved in the decision?

The written output

After the call, send a 1-2 page document: problem statement in their language, your observations and initial thinking, key open questions, next steps.

This demonstrates value immediately and becomes the foundation for your project proposal.

The Solopreneur AI Toolkit includes prompts for structuring discovery sessions and writing project briefs. EUR 12.

Building a Referral System That Brings Work Without You Asking

Alfred P — Mon, 18 May 2026 17:35:26 +0000

Referrals are the best source of freelance clients.

Higher close rate. Less time selling. Clients who already have some trust in you. But most freelancers treat referrals as luck. They are not.

Why referrals do not just happen

Good work alone does not generate referrals. Referrals require three things: your client had a great experience, they know who specifically benefits from your work, and they have a reason to bring you up in conversation.

Satisfying all three requires active effort.

Step 1: Make it easy to describe what you do

If clients cannot easily describe what you do, they cannot refer you accurately.

"They build websites" is not a referral. "They build internal tools for operations teams - the kind of thing that replaces three spreadsheets with one dashboard" is a referral.

After every project, tell the client how to describe your work to others. It sounds awkward. It is actually useful for both of you.

Step 2: Tell clients you take referrals

Most clients want to help if they liked working with you. They just do not think to refer you because nobody asked.

After a successful delivery: "If you know anyone who might need similar work, I always appreciate introductions. It is mostly how I find new clients."

Simple. Direct. Not desperate.

Step 3: Stay top of mind without being annoying

Referrals happen when someone's need meets your name in someone's memory at the same moment. You cannot control the need timing. You can influence the memory part.

A quarterly check-in with past clients - not selling anything, just genuine contact - keeps you present.

Step 4: Refer other people

The easiest way to get referrals is to give them. When you meet designers, copywriters, or other service providers you respect, refer them when appropriate.

People who receive referrals from you are far more likely to send referrals back.

Step 5: Close the loop

When someone refers a new client, tell the referrer how it went. Thank them specifically. If it becomes a paid project, acknowledge it meaningfully.

Reinforce the behavior you want to see again.

A referral system produces a compounding return over twelve to twenty-four months. The freelancers who always seem to have work have been building this systematically for years.

The Freelance Command Center includes a client relationship tracker so no contact falls through the cracks. EUR 17.

How to Handle a Client Who Wants Changes After Final Payment

Alfred P — Mon, 18 May 2026 13:49:05 +0000

It happens more than it should.

Project done. Client approved everything. Final payment received. You archived the files and moved on.

Then two weeks later: "Hey, we have a few things we want to change."

How you handle this moment matters for your reputation and your sanity.

First: determine what they are actually asking for

Is it a bug in the delivered work? Most freelancers include bug fixes for a defined period post-delivery (30-90 days). If it is a real bug in delivered functionality, fix it.

Is it a new feature or changed requirement? Billable. Full stop.

Is it something they forgot to ask for during the project? Also billable.

Is it a scope ambiguity - something neither clearly in nor out of scope? This is the hard one.

The judgment call on scope ambiguity

If your contract was specific enough, this should be clear. If it was vague, you may share responsibility for the ambiguity.

For small items in gray area: fix them and document clearly you are doing so as a goodwill gesture outside original scope. Then tighten your scoping for the next project.

For larger items in gray area: acknowledge the ambiguity, propose a fair split - absorb part, they pay part. Maintains the relationship and establishes that you take scoping seriously.

The change request conversation

When it is clearly new work:

"Thanks for reaching out. The items you have described are outside the scope of the original project, so they would be handled as a new engagement. I can put together a quick estimate - want me to go ahead?"

Not defensive. Not apologetic. Just clear.

Building the ongoing relationship

Clients who want changes after delivery are often clients who want to keep working with you. Handle the transition professionally and they come back for the next project.

If they regularly come back with updates and small changes, a monthly retainer often works better for both sides. They get predictable access to you. You get predictable recurring income.

Post-delivery requests are not problems. They are opportunities, if you handle them well.

The Freelance Command Center includes a client tracker with full project history. EUR 17.

The Cold Email Template That Gets Freelancers Actual Responses

Alfred P — Sun, 17 May 2026 11:43:53 +0000

Most freelance cold emails fail in the first sentence.

"Hi, my name is X and I am a freelance developer with Y years of experience specializing in Z."

The client does not care yet. You have led with your resume instead of their problem.

Here is a framework that actually works.

The problem with most cold outreach

Cold emails fail because they are self-centered. They start with who you are, what you do, and what you want. The reader is thinking about their own problems, not yours.

Effective cold outreach starts with them.

The four-part structure that works

1. Prove you did your homework (one sentence)

Reference something specific about their business, product, or content. Not generic ("I love your company") but specific ("I noticed your checkout flow requires account creation before purchase - that typically drops conversion by 20-30%.").

This sentence says: I actually looked at your business.

2. Name the problem you noticed (one to two sentences)

State a specific problem or opportunity directly and confidently. You are making a professional observation, not guessing.

3. Connect it to what you do (one sentence)

How your specific skill set addresses this specific problem. Not "I build websites." "I build checkout flows that reduce abandonment for e-commerce brands."

4. A low-friction call to action

Do not ask for a project. Ask for a conversation. "Would a 20-minute call make sense to explore this?" is a much easier yes than "I would love to work with you."

The template

Subject: [Specific observation about their product/site]

Hi [Name],

I was looking at [specific thing] on [their product/site] and noticed [specific problem or opportunity]. For [type of business], this usually means [consequence they care about].

I help [type of company] fix exactly this. [One specific example of related work, with a number if possible].

Worth a 20-minute call to see if it makes sense?

[Your name]

Under 100 words. Specific. About them, not you.

Volume vs personalization

Ten personalized cold emails per week beats 100 generic ones every time. You do not need volume. You need specificity.

The Solopreneur AI Toolkit includes prompts for writing cold outreach, proposals, and follow-ups. 75 prompts, EUR 12.

What to Do When a Client Ghosts You After Seeing the Proposal

Alfred P — Sat, 16 May 2026 16:10:48 +0000

You spent four hours on a proposal. You sent it. Nothing.

Three days pass. A week. You send a follow-up. Silence.

Every freelancer knows this feeling. Here is how to handle it without looking desperate or burning a relationship that might not be dead yet.

First: understand why proposals go quiet

Clients ghost proposals for three main reasons.

Budget shock. Your number was higher than they expected and they do not know how to respond. This is not a no. It is discomfort. Many clients who ghost over price come back weeks later.

Internal chaos. Something happened on their end - a competing priority, a budget freeze, a key decision-maker who went on holiday. Nothing to do with you.

They chose someone else but feel awkward saying so. This is the least common reason, despite being the one freelancers assume first.

The right follow-up sequence

Day 3-4: Short check-in. Add something useful, do not just nudge.

"One thing I forgot to mention in the proposal: [relevant detail]. Also happy to jump on a 15-minute call if any questions came up. What does your timeline look like?"

Day 10: Close the loop professionally.

"Checking in one last time on the proposal I sent on [date]. If the timing is not right or you have gone another direction, just let me know and I will close this out. Happy to revisit if things change."

This email does something important: it gives them permission to say no. Surprisingly often, that permission unlocks a response.

After day 10: Move on. Mark it as closed in your pipeline.

What not to do

Do not send more than two follow-ups. After the second one, you have done your job.

Do not apologize for following up. "Sorry to bother you again" signals that you are not sure you deserve a response. You do.

Do not reopen the negotiation in a follow-up. "I could also do this for less" devalues your work before they have even said price is the problem.

One thing that reduces ghosting

Put a deadline on your proposals.

"This proposal is valid for 21 days. After that, availability and pricing may change."

This creates a reason for the client to respond, even if just to ask for an extension.

Ghosting is part of freelancing. The freelancers who handle it well are the ones who have a system: follow up twice, let it go, keep the pipeline full.

The Freelance Command Center has a proposal pipeline tracker so nothing falls through the cracks. EUR 17.

How to Write a Freelance Contract That Clients Actually Read

Alfred P — Sat, 16 May 2026 15:30:26 +0000

Most freelance contracts are written to protect you if everything goes wrong.

That is the right instinct. But there is a second problem nobody talks about: clients do not read them.

They click "sign" without reading a word. Then three months later they are surprised by something that was clearly in section 4.

A contract that clients actually read does two things: it protects you legally AND it sets expectations in plain language before the project starts. Here is how to write one.

Keep the language simple

Legal language signals "this is something to skim and sign." Plain language signals "this is a document we are both going to work from."

Compare:

"The client shall remit payment within fourteen (14) calendar days of invoice issuance."

vs.

"Payment is due within 14 days of invoice. Late payments are subject to a 2% monthly fee."

Same protection. One of them gets read.

Put the important stuff at the top

Most freelance contracts bury the critical terms in the middle. Clients lose attention by paragraph three.

Move your payment terms, revision policy, and kill fee to page one. Not buried in appendices. Right at the top under "How This Works."

When clients see payment terms immediately, they engage. When it is on page seven, they skip it.

Use a "plain English summary" section

Before the legal body of the contract, add a short section called something like "What We Are Agreeing To." Three to five bullet points summarizing:

What you are building
What is explicitly not included
When payment is due
How revisions work
What happens if the project is cancelled

Clients read this section. They reference it during the project. It prevents 80% of scope disputes before they start.

Include the change order trigger explicitly

Do not just say "changes may affect price and timeline." Say exactly what triggers a change order.

"Any request that adds features, changes the agreed scope, or requires rework of completed deliverables will be handled via a written change order with updated cost and timeline before work begins."

When a client reads that sentence before the project starts, the change order conversation later is not a surprise. It is a reminder.

Address the "just one more thing" problem directly

Add a section called something like "Scope and Revisions." State clearly how many rounds of revision are included, what counts as a revision versus a new request, and what happens when you exceed included revisions.

"Two rounds of revision are included per deliverable. A revision is a change to an existing design or feature. A new feature request is a change order."

Clients who read this once will self-police their own requests.

Send it with a short explanation email

When you send the contract, include three sentences:

"Please review the attached contract before signing. The 'What We Are Agreeing To' section at the top covers the key points. Let me know if anything needs clarification before you sign."

This frames the contract as a document to read, not a form to process.

Contracts are not just legal protection. They are the first real communication about how you work. Clients who read your contract before signing are clients who understand your process. That is the project you want.

The Freelance Command Center includes contract templates, client onboarding checklists, and a project scoping system. Built in Notion. EUR 17.