DEV Community: Alfred P

The Scope Document Template That Prevents Project Arguments

Alfred P — Sun, 26 Jul 2026 10:03:02 +0000

Most freelance project arguments are not about the work. They are about what was agreed at the start.

A scope document that prevents these arguments is not a complex legal instrument. It is a clear, specific description of what is in and what is out, written in plain language that both sides can reference when memory diverges.

The five sections of an effective scope document

Project overview. One paragraph describing the project in plain language. What problem it solves, for whom, and what the high-level approach is. This paragraph should be readable by the client's non-technical stakeholders.

Deliverables. A numbered list of everything you are delivering. Not categories. Specific items.

Not: "User authentication system."
Yes: "1. Email and password registration. 2. Email verification flow. 3. Login with session management (30-day session expiry). 4. Password reset flow with email link. 5. Account lockout after five failed login attempts."

Every deliverable specific enough that both sides can agree when it is done.

What is not included. The most important section most freelancers skip.

List the things a client might reasonably assume are included but are not. "Social login (Google, Apple, Facebook) is not included in this scope." "Mobile application versions are not included." "Content migration from the existing system is not included."

This section prevents more disputes than any other single element.

Assumptions. Everything you assumed when building the estimate. "This estimate assumes: client provides all copy and images before development begins. Existing API documentation is accurate. Hosting environment is [platform]. One round of revision per deliverable."

When an assumption proves wrong, the scope conversation is simple: "This assumption turned out to be incorrect, which affects [timeline/cost]. Here is how I propose we handle it."

Change order policy. One paragraph: any work outside this document requires a written change order agreed by both parties before work begins.

Sending and confirming the scope

Send the scope document before work begins and ask for explicit confirmation.

"Please review the attached scope document. This defines what is included in this project. If anything looks different from your understanding, let me know before we start."

Explicit confirmation before starting. Not assumed.

The Freelance Command Center includes scope document templates and a project tracking system. EUR 17.

How to Win Freelance Projects Against Cheaper Competition

Alfred P — Sat, 25 Jul 2026 09:52:10 +0000

You will lose projects to cheaper competitors. Some of those losses are correct.

When a client chooses someone else based on price and the project is simple and well-scoped, the other developer may be the right fit. Accepting this is not defeatism. It is accurate market reading.

The projects worth winning are the ones where quality, expertise, and professional process matter to the client's outcome. Those projects can be won without being the cheapest option.

Why clients choose cheaper when they should not have to

The most common reason clients make price the deciding factor is that they cannot differentiate between options on other dimensions.

When two developers both have portfolios of reasonable work, both seem competent, and both respond professionally to the brief - price becomes the rational tiebreaker.

Your job is to create visible differentiation before price enters the conversation.

The differentiation levers

Specificity. A developer who specializes in the type of project the client needs feels like less of a risk than a generalist who can do anything. "I have built four of these for companies in your sector" is more reassuring than "I can build this."

Process transparency. Showing a client exactly how you will approach their project, before they sign anything, demonstrates both competence and professionalism. Most developers send a price. Some send a proposal. Few send a structured walkthrough of their thinking.

Quality of questions. The questions you ask during the sales process reveal whether you understand the problem. Smart, specific questions differentiate you from the developer who quoted without engaging with the brief.

Evidence of outcomes. Testimonials that describe results, not just satisfaction. "They saved us six hours a week on manual reporting" is more persuasive than "great to work with."

When to compete on price (and when not to)

Competing on price is appropriate when: you are earlier in your career and building a portfolio, the project is simple and price-sensitive buyers are your market, or you want a specific client for strategic reasons that justify the below-market rate.

It is not appropriate when: you are trying to attract the kinds of clients who value professional quality. Discounting to win price-sensitive clients produces more price-sensitive clients.

The Solopreneur AI Toolkit includes prompts for writing proposals that differentiate on dimensions other than price. EUR 12.

How to Handle Clients Who Treat Every Request as Urgent

Alfred P — Fri, 24 Jul 2026 10:22:38 +0000

Some clients have no concept of priority gradation. Everything is urgent. Every message expects an immediate response. Every request appears with an implicit pressure to drop everything.

Working with this type of client in an unmanaged way is exhausting and produces poor work, because constant urgent interruptions are incompatible with the focused attention that good development requires.

The good news: most clients who behave this way are not doing it maliciously. They are doing it because nobody has established a different expectation.

Setting the expectation at the start

The best time to establish communication norms is at the start of the engagement, before the pattern develops.

"I work best with batched communication. I check and respond to messages twice a day, at [time] and [time]. For genuine emergencies, here is how to reach me: [method]. Everything else I will address in the next communication window."

This statement in the onboarding message or kickoff call establishes your working style as a professional norm, not a personal preference.

Most clients accept this. A few push back. The ones who push back significantly are signaling how they will operate throughout the project - useful early information.

Resetting the expectation mid-project

If the pattern has already developed without this conversation, you can reset it.

"I want to make a small process adjustment. I have noticed that our communication is quite reactive, which makes it hard to maintain focus on the project work. Going forward, I will batch responses to twice a day. For anything that cannot wait, [method]. This will let me give the project work the attention it deserves."

Not a complaint. A process improvement framed as serving the project.

The response to the "just quickly" message

"Just quickly" is the signal that a client is about to add something outside the expected communication pattern.

You do not need to respond immediately to a message that begins "just quickly." You can respond in your next communication window.

If you respond to every "just quickly" immediately, you establish that "just quickly" gets immediate responses. The pattern compounds.

What genuinely requires immediate response

Production is down. A security incident. A decision that is blocking client operations and cannot wait.

Everything else is not actually urgent. It feels urgent to the client because they thought of it. It is not urgent in any objective sense.

The Solopreneur AI Toolkit includes prompts for writing professional boundary-setting messages and resetting communication patterns. EUR 12.

The Follow-Up System That Keeps Your Freelance Pipeline Full

Alfred P — Thu, 23 Jul 2026 10:26:13 +0000

A pipeline that fills itself is a myth. A pipeline that fills with less effort than you currently spend is not.

The difference is a follow-up system that runs on a calendar rather than on memory.

Memory is unreliable for follow-ups. You send a proposal, the client goes quiet, and within two weeks the proposal is mentally filed under "lost" and you have moved on. But the proposal was not lost. The client got busy. The decision got delayed. The timing shifted.

The clients who hire you are often not the ones who responded immediately. They are the ones you followed up with at the right moment.

The four categories of follow-up

Open proposals. Any proposal you have sent that has not received a response. Follow-up sequence: day four (add something useful), day ten (close the loop professionally). Calendar reminder set when proposal is sent.

Past clients. Anyone you have completed a project with in the past eighteen months. Quarterly check-in: "How are things going? Anything I can help with?" Calendar reminder, recurring, quarterly.

Not-right-now contacts. People who expressed interest but said the timing was not right. Follow-up in six to eight weeks. Calendar reminder set at the time of the conversation.

Warm network. People who could refer you but you have not been in active contact with. Monthly or bimonthly check-in. Not asking for work. Staying present.

The system mechanics

Every contact goes into one of these four categories when it first appears.

Every category has a predefined follow-up schedule.

Every follow-up gets a calendar reminder set when the contact is logged.

When the reminder fires, the message takes three to five minutes to write and send.

The whole system operates on the calendar, not on memory or motivation.

The message content

Follow-ups fail when they feel like nudges. They work when they add value.

For open proposals: one new observation, one relevant resource, or one clarifying question.

For past clients and warm network: genuine interest in what they are working on, a relevant piece of information, an introduction if you have one.

For not-right-now contacts: a check-in on whether the timing has shifted, framed as a genuine question rather than a sales push.

The Freelance Command Center includes a pipeline tracker with follow-up date fields so nothing expires without action. EUR 17.

How to Transition Between Freelance Projects Without Income Gaps

Alfred P — Wed, 22 Jul 2026 10:28:52 +0000

The income gap between projects is one of the most predictable problems in freelancing and one of the most preventable.

It happens because most freelancers start looking for the next project when the current one ends, rather than when it begins.

Why the gap exists

A project ends on a Friday. You start looking for the next one on Monday. The earliest a project can realistically start is two to four weeks later: initial conversations, proposal, contract negotiation, client preparation.

During those two to four weeks, you have no income from that workstream.

If your entire income was tied to the ending project, those weeks are a gap. If you were already in the sales process for the next project, those weeks are a transition.

The difference is entirely in when you started the sales activity, not how much you do it.

The pipeline maintenance rule

Start the sales process for your next project when you are halfway through your current one.

Not when it ends. When you are at the midpoint.

At the midpoint, you have enough delivered to feel like the current project is under control. You have two to four weeks before the project ends to get conversations started. Those conversations can produce a signed project that starts the week your current one ends.

This is not always possible. Some projects overlap in ways that prevent it. But as a default rhythm, halfway is when you start looking.

What "starting the sales process" looks like at the midpoint

Not a frantic search. A deliberate set of activities:

One or two warm network messages to people who might have work or know someone who does. A follow-up on any open proposals from the past month. A piece of content published that signals you will have availability soon. A check-in with a past client you have not spoken to in a while.

An hour of activity. Not a week of stress.

The retainer as a permanent gap-filler

If you can keep even one small retainer client running continuously, it provides an income floor that makes project transitions dramatically less stressful.

The between-project weeks are not gaps when you have $500-1000 in recurring monthly income. They are quieter weeks.

The Freelance Command Center includes a pipeline tracker that makes it visible when you need to start filling it. EUR 17.

The Minimum Viable Freelance System (What You Actually Need)

Alfred P — Tue, 21 Jul 2026 10:27:36 +0000

There is a version of freelance infrastructure advice that sends new freelancers down a rabbit hole of CRMs, project management tools, accounting software, and productivity systems before they have a single client.

None of that matters until you have clients.

Here is the actual minimum you need to start and run a professional freelance business.

What you need before the first client

A way to receive a signed contract. A PDF, a simple e-signature tool, or even a scanned signature. One contract template, not a bespoke document for every client.

A way to send and receive money. A bank account, PayPal, or a payment processor. Something the client can pay to.

An email address that looks professional. yourname@yourdomain.com costs a few dollars a month and is worth it from day one.

That is it for before the first client.

What you need after the first client

A way to track what you owe and what you have been paid. A spreadsheet with three columns (client, amount invoiced, amount received) is sufficient. More sophisticated later.

A folder structure for client files. One folder per client, one sub-folder per project. Documents, deliverables, contracts, correspondence. Simple and consistent.

A calendar for follow-ups and deadlines. Any calendar app. The specific follow-up dates and project milestones for your current clients.

What you need after five clients

A client database. Which clients are active, which are past, what they paid, what you delivered, how to reach them.

A proposal template. A structure you can customize rather than rebuild for every new project.

An invoicing process. Not software necessarily. A consistent template, a consistent numbering system, a follow-up schedule.

A weekly review habit. Fifteen to twenty minutes on Friday: what was done, what is due next week, what follow-ups are outstanding.

What you probably do not need right away

A project management platform. You are one person. You do not have dependencies to track across a team.

A full CRM. A spreadsheet works until you have enough clients to justify the overhead.

An accounting software subscription. Your first tax year you can hand a well-organized spreadsheet to an accountant.

A personal productivity system more complex than a weekly priority list.

Start simple. Add tools as you have problems that require them.

The Freelance Command Center is the step after the spreadsheet: all of these functions in one connected Notion workspace. EUR 17.

How to Structure Your Freelance Week for Maximum Billable Hours

Alfred P — Mon, 20 Jul 2026 10:55:53 +0000

The freelancer who works 45 hours a week and bills 20 of them has a different problem than one who works 35 hours and bills 25.

The first problem is not lack of work. It is lack of structure.

The second freelancer has figured out something the first has not: protected time for client work, batched time for everything else.

Why unstructured days produce low billable ratios

When your day has no structure, everything competes with everything else.

A client message arrives and interrupts focused development work. You switch to answer it, lose the context of what you were working on, and spend fifteen minutes getting back. This happens four or five times per day. You lose an hour of productive work to context switching you never tracked as a cost.

Business development, admin, invoicing, and marketing happen "whenever there is time," which means they compete with client work for the same unprotected hours and frequently win because they feel urgent.

By the end of the week, you have been busy the entire time and billed eighteen hours.

The structure that changes this

Morning block: deep client work. The first three to four hours of the working day, before email or messages. This is your highest-cognitive-capacity time. Protect it entirely for billable client work.

No email in this block. No messages. A phone on silent. The only thing in the morning block is the most important billable task on your list.

Midday check: communication batch. One window, thirty to forty-five minutes, for responses to all client messages and business development items.

Afternoon block: flexible client work or business tasks. Less cognitively demanding client work, or business development if the morning block covered your delivery commitments.

End-of-day ritual: next day prep. Ten minutes to set your one or two priorities for the following morning. This preparation means the morning block starts immediately, not after fifteen minutes of deciding what to work on.

What this produces

Protected morning blocks consistently produce more billable output than unstructured days, because the interruption cost is eliminated and the cognitive state needed for complex work is maintained longer.

The communication batch means messages are answered, just not immediately. Almost nothing a client sends requires a response within minutes. Almost everything can wait until the midday window.

The Freelance Command Center includes a weekly review template that makes this structure visible and maintainable. EUR 17.

The Second Client Meeting That Decides Whether You Win the Project

Alfred P — Sun, 19 Jul 2026 09:54:38 +0000

Most freelancers focus their energy on the first meeting: the discovery call, the initial impression, the questions they ask.

The second meeting is often more decisive.

By the second meeting, the client has heard from multiple developers. They have had time to reflect on who understood them best. They are making the decision, consciously or not.

What you do between the first and second meeting determines which side of that decision you end up on.

What the gap between meetings is for

The gap is not idle time. It is when you demonstrate, through action, that you are different from every other developer who had the first meeting.

Send something useful within 24 hours. Not a proposal. A brief follow-up message with one observation, one clarification, or one piece of relevant information.

"After our call I was thinking about the integration issue you mentioned. One approach that has worked well in similar setups is [approach]. Happy to discuss whether it fits your situation."

This message does multiple things: it shows you were listening, it shows you have been thinking about their problem, and it distinguishes you from the developers who sent nothing between calls.

Prepare specifically, not generally. Before the second meeting, review everything you know about this client. Look at their product, their team, their industry. Find one or two things that are specific to them that you can reference in the second meeting.

Generic preparation produces generic conversations. Specific preparation produces conversations that feel like you were paying attention.

What to cover in the second meeting

The second meeting should not re-explain what you do. It should advance from where the first meeting ended.

"Based on our last call, here is how I would approach your project." Walk them through your thinking specifically, not a generic proposal structure.

Ask the questions you could not ask in the first meeting: "After our first call, did anything come up that changed your thinking about scope or timeline?"

And close: "Does this approach make sense? Is there anything that would prevent you from moving forward?"

The question at the end

Most freelancers leave second meetings without asking if there are barriers to moving forward.

This is a missed opportunity. The client who is almost certain but has one concern will not always volunteer it. A direct question surfaces it.

"Is there anything I have not addressed that would prevent you from moving forward with this?"

The answer is either yes (and you can address it) or no (and you have a clear path to the project).

The Solopreneur AI Toolkit includes prompts for preparing sales conversations, second meetings, and closing sequences. EUR 12.

How to Pitch Yourself for Freelance Work Without Feeling Salesy

Alfred P — Sat, 18 Jul 2026 09:36:57 +0000

The discomfort most freelancers feel about pitching themselves comes from confusing pitching with selling.

Selling is persuading someone to buy something they might not otherwise want. Pitching, done well, is presenting relevant information to someone who has a problem that you can solve.

The second version does not require a sales personality. It requires specificity, relevance, and the ability to describe what you do clearly.

The non-salesy pitch

The pitch that does not feel salesy has one quality: it starts with a genuine observation about the other person's situation, not with information about you.

"I noticed [specific thing about their business/work]. That usually means [specific consequence]. I have solved this for [type of company] before and got [specific result]. Worth a conversation?"

Four sentences. Specific. About them, not you.

Compare to the version that feels salesy: "I am a developer with eight years of experience specializing in X and Y, and I would love to work with a company like yours."

That version is about you. You are asking them to care about your credentials before they know whether you are relevant to them.

The permission to be direct

Professional directness is not salesy. Vagueness is.

"I think I could help you with [specific problem]. Can I show you how?" is direct, clear, and professional.

"I was just reaching out because I thought it might be interesting to connect and see if there are any synergies..." is vague and sounds like every other cold message.

Be specific about what you do. Be specific about what you have observed about their situation. Be specific about what happens next.

Where to use this

Before a networking conversation. "I work with operations teams at mid-sized logistics companies to build internal tools that replace manual processes. Is that relevant to what you are working on?"

In a cold email. "I noticed your team is hiring for a data analyst role. That often signals that the reporting infrastructure is not keeping up. I have helped three companies in your situation build something more sustainable."

In a proposal introduction. "The reason I think I am specifically suited to this project is [one specific, relevant reason], not general experience."

The internal shift that makes it work

When you genuinely believe that the person you are talking to has a problem you can solve, the pitch is not persuasion. It is information sharing.

That belief - that you are providing value by being specific and relevant - removes most of the discomfort.

The Freelance Command Center includes a proposal system that helps you present your work specifically and professionally. EUR 17.

The Networking Strategy That Works for Freelancers Who Hate Networking

Alfred P — Fri, 17 Jul 2026 10:01:48 +0000

Most networking advice is written for extroverts who are comfortable in rooms full of strangers.

Most freelancers are not those people.

The good news is that the networking strategy that produces the most freelance clients is not the one involving rooms full of strangers. It is a quieter, more specific approach that works particularly well for people who find large-scale networking uncomfortable.

Why most networking produces little

Traditional networking events are inefficient for freelancers. You meet many people, most of whom cannot use your service and do not know anyone who can. The time investment is high and the conversion to actual work is low.

The freelancers who get the most referrals are not the ones who attend the most events. They are the ones who have deep relationships with a small number of people who understand their work and move in circles where that work is relevant.

The deep network approach

Instead of meeting many people superficially, invest in a small number of relationships deeply.

Identify ten to fifteen people in your professional network who are well-connected in the world of your ideal clients. Former colleagues, adjacent service providers, people you have worked with in any capacity.

Maintain genuine contact with this small group. Not to sell to them. To stay present and add value where you can. Share something relevant. Make an introduction when you can. Ask what they are working on.

When someone in this group encounters a potential client for you, you are the first person who comes to mind.

Content as passive networking

Writing consistently about your work is networking that scales without requiring your presence.

When someone reads your content, understands what you do, and refers you to someone who needs it, that is a referral from someone you may have never met.

This is the approach that works for people who find active networking uncomfortable. The content does the visibility work. The relationships do the trust work.

Where to show up

Two communities where your ideal clients spend time. Not twenty. Two.

One community for peer learning (other developers or freelancers). One community where your clients spend time.

Show up consistently. Be useful. Ask good questions. Over six months, you become a familiar face without ever having to introduce yourself to a stranger in a conference room.

The Solopreneur AI Toolkit includes prompts for content creation and community participation that build your network without mass networking. EUR 12.

How to Track Freelance Metrics That Actually Matter

Alfred P — Thu, 16 Jul 2026 10:12:18 +0000

Most freelancers either track nothing or track the wrong things.

Revenue is not a useful metric on its own. Total hours worked tells you how busy you are, not how well the business is doing. Number of clients is a vanity metric without context.

The metrics that actually tell you something useful are the ones that connect behavior to outcomes.

The four metrics worth tracking

Effective hourly rate. Total revenue divided by total hours worked (including unbillable time). Not what you charge. What you earn per hour of your life spent on the business.

This metric makes the cost of scope creep, unbillable admin, and long proposals visible. A freelancer who bills $100/hr but spends half their time on unbillable work has an effective rate of $50/hr. That gap is actionable.

Pipeline velocity. How long does a prospect typically take to move from first contact to signed contract? How many prospects convert to projects?

This metric tells you whether your sales process is working and where prospects drop off. A high contact rate with a low conversion rate is a proposal problem. A low contact rate is a visibility problem.

Client acquisition source. Where do new clients come from? Referrals, content, direct outreach, platforms, other?

Knowing which sources produce clients allows you to invest in them deliberately. If 80% of your clients come from referrals and you have been spending time on cold outreach, you are optimizing the wrong thing.

Revenue by client. What percentage of revenue comes from each client?

Any client above 35-40% of total revenue is a concentration risk. That number does not mean end the relationship. It means actively diversify while the relationship is healthy.

The tracking system that is actually maintainable

A monthly spreadsheet with four columns: revenue, hours (billable and total), new contacts, new clients, and their source.

Review it on the first Monday of every month. Takes fifteen minutes. Produces enough data over six months to see patterns.

No software required. No elaborate dashboards. Four numbers, tracked monthly.

The Freelance Command Center includes a financial dashboard and client tracker that makes these metrics visible. EUR 17.

When to Say No to a Well-Paying Client

Alfred P — Wed, 15 Jul 2026 10:05:59 +0000

There is a specific kind of freelance decision that does not get talked about enough.

Not whether to say no to difficult clients. Most freelancers can make that calculation, even if they do not always act on it.

The harder decision: whether to say no to a client who pays well, respects your rate, and is not obviously difficult but is pulling you in a direction you do not want to go.

I have said no to three clients in this category. All three were correct decisions in retrospect. None of them felt comfortable at the time.

The direction problem

The most common version of this situation: a client whose work is not in the niche you are building toward.

They are good payers. The projects are manageable. But the work is in a domain that does not contribute to the case studies, skills, or referral network you are trying to build.

Every month you spend with this client is a month you are not developing depth in the area you want to be known for.

The financial calculation says: take the money. The strategic calculation says: your time has an opportunity cost that is not captured in the current invoice.

The capacity problem

The second version: a client who would be fine in isolation but whose project, combined with your existing commitments, would make everything worse.

Not just the new project. The existing work would get less attention. The quality of everything would drop. The stress would compound.

The financially correct choice (take the well-paying project) produces the professionally incorrect outcome (deliver everything at a mediocre level).

The values problem

The third version: work that is legal, professional, and well-compensated but that you do not feel right about. Not a dramatic ethical issue. Just a mismatch with what you want to be building.

This one is hardest to justify to anyone else. It often does not need to be.

How to say no professionally

You do not owe a full explanation.

"After reviewing this, I do not think I am the right fit for this project at this time. I would be happy to suggest someone who might be a better match."

Professional. Complete. No elaboration required.

The Freelance Command Center keeps your pipeline visible so you can make these decisions with a clear view of your options. EUR 17.