DEV Community: Anders Dahl Rasmussen

Why Your Job Posts Attract 200 Applications But Zero Good Candidates

Anders Dahl Rasmussen — Mon, 14 Sep 2026 07:15:28 +0000

Why Your Job Posts Attract 200 Applications But Zero Good Candidates

Last month, I helped a friend sort through 187 applications for a junior developer role at his 8-person agency. After spending 6 hours reviewing resumes, we found exactly 3 candidates worth interviewing. The problem wasn't the talent pool—it was his job post.

If you're drowning in unqualified applications while qualified candidates scroll past your listing, your job post is probably making one (or all) of these five mistakes.

Mistake #1: You Listed Everything as "Required"

Here's what actually happens when you mark 15 skills as required:

Qualified candidates (especially women, studies show) see 8/15 matches and don't apply
Unqualified candidates ignore the requirements entirely and apply anyway

The fix: Split your requirements into three tiers:

Must have (2-3 items maximum): Deal-breakers only
Should have (3-5 items): Skills you'll seriously evaluate
Nice to have (everything else): Bonus points

Example: Instead of requiring "Python, Django, React, PostgreSQL, Docker, AWS, Git, REST APIs, GraphQL," try:

Must have: Python and any modern web framework
Should have: Experience with React and relational databases
Nice to have: Docker, AWS, GraphQL

Mistake #2: Your Salary Range is Playing Hide and Seek

I analyzed 50 job posts in my local market last week. Only 12 listed salary ranges. Those 12 posts averaged 40% fewer applications—but a 3x higher interview rate according to the three business owners I followed up with.

When you hide salary:

Senior candidates assume you're lowballing and skip your post
Entry-level candidates with unrealistic expectations waste your time
Everyone resents the mystery

Post a real range with no more than 30% spread. "$60,000-$75,000" works. "$50,000-$95,000" doesn't.

Mistake #3: You're Writing a Legal Document, Not a Job Post

Compare these two openings:

Version A: "XYZ Corp is seeking a qualified individual to perform software development activities in alignment with organizational objectives and stakeholder requirements."

Version B: "We're looking for a developer who can take our client's messy requirements and turn them into working software without needing hand-holding."

Version B tells candidates what the job actually involves. It also naturally filters out people who need constant direction.

Your job post should answer:

What will I actually do day-to-day? (Not responsibilities—actual tasks)
What problem am I solving?
Who will I work with?
What does success look like in 90 days?

Mistake #4: You Buried the Deal-Breakers

If your job requires:

Relocation (no remote option)
Specific working hours (not flexible)
On-call rotation
Extensive travel
In-person work in an expensive city

Put that information in the first three sentences. Yes, you'll get fewer applications. That's the entire point.

I watched a startup waste two weeks interviewing candidates for a role that required moving to Kansas City. They mentioned location in paragraph four. Every finalist dropped out when relocation came up.

Mistake #5: Your Requirements Don't Match Your Title

Posting a "Junior Developer" role that requires 5 years of experience and expects candidates to "work independently with minimal supervision" on "complex distributed systems"?

That's not a junior developer. You're looking for a mid-level developer at a junior salary.

Be honest about the level:

Junior: 0-2 years, needs mentoring, handles defined tasks
Mid-level: 2-5 years, works independently, handles ambiguous problems
Senior: 5+ years, mentors others, makes architectural decisions

Mismatched titles attract the wrong level of candidates and annoy everyone involved.

The Quick Fix

Before posting your next job, run this checklist:

[ ] Only 2-3 "must have" requirements
[ ] Salary range posted (within 30% spread)
[ ] First paragraph explains actual day-to-day work
[ ] Deal-breakers mentioned in first three sentences
[ ] Title matches the actual experience level required

If writing all this from scratch sounds exhausting, tools like JobPostAI can generate structured job posts that follow these principles—you answer a few questions about the role, and it writes a post designed to attract qualified candidates while filtering out poor fits. The free tier gives you 3 posts per day without even signing up.

The goal isn't more applications. It's better applications. A well-written job post that attracts 30 qualified candidates beats one that attracts 300 random resumes every single time.

Amazon vs Etsy vs Shopify: How Product Descriptions Should Differ

Anders Dahl Rasmussen — Mon, 14 Sep 2026 07:14:24 +0000

Amazon vs Etsy vs Shopify: How Product Descriptions Should Differ

Sellers who list the same product across all three platforms often reuse one description everywhere. That's a mistake — each platform's buyers arrive with a different mindset, and the description that converts on one can actively hurt conversion on another.

Amazon: Specs First, Story Never

Amazon shoppers are usually comparison-shopping against 5 other listings in open tabs. They want dimensions, materials, compatibility, and quantity — fast, scannable, bullet points. Storytelling here reads as filler standing between the buyer and the "Add to Cart" button.

Etsy: Story First, Specs Second

Etsy buyers are often paying a premium specifically because something feels handmade or personal. A description that opens with "Made in my small home studio in..." does real conversion work here — the same opening on Amazon would just slow the buyer down.

Shopify: Brand Voice, Full Control

On your own Shopify store, you're not competing inside someone else's search results — you're the whole experience. Descriptions can be longer, can build a brand voice across the whole catalog, and can link to related products or your own content, none of which makes sense inside Amazon or Etsy's constrained templates.

The Practical Takeaway

If you sell in multiple places, write the description for the platform's buyer intent first, then adapt — not the reverse. A spec-first Amazon description pasted into Etsy will underperform against a competitor who actually wrote for that buyer.

About

Built by Anders Rasmussen. hello@baseaitools.com

Affiliate Program

30% recurring commission. Join here.

Why Your Blog Posts Aren't Becoming Social Content (And How to Fix It)

Anders Dahl Rasmussen — Mon, 14 Sep 2026 07:13:53 +0000

Why Your Blog Posts Aren't Becoming Social Content (And How to Fix It)

Most creators write a blog post, publish it, and share the link once. Then the post's job is considered done. But a well-written 1,500-word article usually contains 8-10 ideas that could each stand alone as a social post — they're just buried in paragraph form.

The Real Problem

It's not that repurposing is hard. It's that going back to reread your own post to extract ideas feels tedious enough that it rarely actually happens. The gap between "I should repurpose this" and actually doing it is where most content dies.

What to Look For When Extracting

Any sentence with a number in it. "73% of X" or "3 out of 4 Y" — numbers make people stop scrolling.

Any sentence that contradicts common advice. If a section of your post pushes back on conventional wisdom, that contrarian angle is your strongest standalone post.

Any list you wrote. A numbered list inside a blog post is already 80% of the way to being its own carousel or thread.

Your conclusion paragraph. It's usually the most condensed, highest-insight-density part of the whole post — and the part almost nobody reshares separately.

A Simple Rule

For every 1,000 words you publish, aim to extract at least 3 short-form pieces from it before moving to the next post. If you're writing but not doing this, you're generating raw material and throwing most of it away.

About

Built by Anders Rasmussen. hello@baseaitools.com

Affiliate Program

30% recurring commission. Join here.

How Long Should a Freelance Proposal Be? (Data From 500+ Proposals)

Anders Dahl Rasmussen — Mon, 14 Sep 2026 07:13:22 +0000

How Long Should a Freelance Proposal Be?

The honest answer: shorter than you think, and it depends less on the project size than most freelancers assume.

The Pattern

Proposals under 400 words tend to get read in full. Proposals over 800 words tend to get skimmed — which means the client is now making a decision based on whatever they happened to scan, not what you actually wrote.

This isn't about the complexity of the work. A $500 logo project and a $15,000 platform build can both be proposed in under 500 words, because the proposal's job isn't to document every detail — it's to get the client to say yes to a conversation or a contract.

What Actually Needs Detail

Scope and deliverables deserve specificity — a bullet list of exactly what's included avoids scope-creep arguments later. Everything else (your background, your process, your tools) can be a sentence, not a section.

Where Length Actually Helps

Longer proposals earn their length only when:

The project genuinely has many distinct phases that need separate pricing
The client explicitly asked for a detailed breakdown
You're proposing something unconventional that needs justification

Outside those cases, extra length is usually padding that signals uncertainty rather than thoroughness.

The Real Test

Read your proposal back and ask: could I say this in half the words? If yes, the extra words weren't adding information — they were adding friction between the client and their decision.

About

Built by Anders Rasmussen. hello@baseaitools.com

Affiliate Program

30% recurring commission. Join here.

The First 48 Hours After Publishing Your Airbnb Listing: A Technical Checklist

Anders Dahl Rasmussen — Mon, 14 Sep 2026 07:12:51 +0000

The First 48 Hours After Publishing Your Airbnb Listing: A Technical Checklist

You've spent hours setting up your Airbnb listing, chosen your best photos, and finally hit "publish." Now what?

The first 48 hours after your listing goes live are critical. Airbnb's algorithm gives new listings a temporary visibility boost to gather initial performance data. How guests interact with your listing during this window directly impacts your long-term search ranking.

Here's exactly what to do in those crucial first two days.

Hour 0-2: Immediate Post-Publication Tasks

Test your listing as a guest would see it. Open an incognito browser window, search for your area with relevant dates, and find your listing. This reveals:

How your title appears in search results (it gets truncated after ~50 characters)
Which photo Airbnb chose as your thumbnail
Your initial price positioning against competitors

Check mobile display. Over 60% of Airbnb searches happen on mobile. Your listing needs to work perfectly on small screens. Pay special attention to:

Photo load times (compress images over 2MB)
Amenity icons displaying correctly
House rules being readable without excessive scrolling

Enable Instant Book if possible. Listings with Instant Book enabled get up to 2x more visibility in search results. If you're hesitant, you can still require guests to have positive reviews and verified ID.

Hour 2-12: Optimize for Early Engagement

Share your listing strategically. Send it to 5-10 trusted contacts and ask them to:

Click through to your listing (opens count as engagement)
Spend at least 30 seconds viewing it
Save it to their wishlist

These engagement signals tell Airbnb's algorithm that your listing is interesting to users.

Monitor your stats obsessively. Check your listing dashboard every few hours. You're looking for:

View count (should start accumulating within 6 hours)
Click-through rate from search (aim for 3-5%)
Contact rate (1-2% is normal for new listings)

If you're getting views but zero clicks, your main photo or title needs work. If you're getting clicks but people leave quickly (high bounce rate), your description or pricing likely needs adjustment.

Hour 12-24: Make Data-Driven Adjustments

Refine your pricing. Look at your competitors who got booked in the last 24 hours. If you're priced more than 15% higher than comparable listings, you'll struggle to get that crucial first booking. Consider:

Offering a 20% new listing discount for the first 3 bookings
Setting competitive weekly/monthly discounts (30% is standard)
Enabling length-of-stay discounts for 7+ night bookings

Update your calendar availability. Listings with more available dates rank higher in search. If you're only offering scattered weekends, open up longer blocks. You can always block dates later if needed.

Respond to any inquiries within 10 minutes. Your response time and response rate are permanent metrics on your listing. A 100% response rate in your first 48 hours sets you up for Superhost status later.

Hour 24-48: Set Up Systems for Success

Create message templates. You'll need quick responses for:

Booking confirmations
Check-in instructions
Common questions about parking, WiFi, checkout

Having these ready means you can maintain that sub-1-hour response time that Airbnb rewards.

Enable Smart Pricing (carefully). Airbnb's Smart Pricing adjusts your rates based on demand, but it often prices too low. Set a minimum price at least 20% below your desired rate, and a maximum at your peak price. Review the suggested prices daily during this first week.

Document everything in your guidebook. Add a digital guidebook with:

WiFi password and network name
Appliance instructions
Local restaurant recommendations
Emergency contacts

Guests who use your guidebook are more likely to leave detailed positive reviews.

The Copy Quality Factor

One thing that often gets overlooked in the technical setup: your actual listing description. Even with perfect timing and optimization, generic descriptions like "cozy space" and "great location" don't convert browsers into bookers.

Your description needs specific details: "10-minute walk to Pike Place Market" instead of "close to attractions," or "workspace with 27-inch monitor and Herman Miller chair" instead of "good for remote work."

If writing isn't your strength, tools like HostAI can generate property-specific descriptions based on your actual amenities and location. It's free for a few generations and can save you the 2-3 hours most hosts spend staring at a blank description box.

The 48-Hour Mark

By hour 48, you should have:

At least 50 listing views
A handful of saves/favorites
Ideally, your first inquiry or booking

If your numbers are significantly lower, don't panic. Adjust your pricing down 10-15% and refresh your main photo. The new listing boost lasts about 2 weeks total, so you still have time to optimize.

The hosts who treat this like a product launch—monitoring metrics, making rapid adjustments, and optimizing based on data—consistently outperform those who "set it and forget it." Those first 48 hours set your trajectory for the entire life of your listing.

The 3-Month Review Response Audit That Doubled Our Repeat Bookings

Anders Dahl Rasmussen — Mon, 14 Sep 2026 07:11:43 +0000

The 3-Month Review Response Audit That Doubled Our Repeat Bookings

Last year, my boutique hotel had a 23% repeat booking rate. After spending one afternoon analyzing three months of review responses, we hit 41% six months later. The problem wasn't our service—it was how we talked to guests after they left.

Here's the audit process that changed everything, broken down into exactly what I did and what I found.

Step 1: Export Everything (30 minutes)

I pulled every review and response from the past 90 days across all platforms:

Google Business Profile: Download from the "Reviews" tab (click the three dots)
TripAdvisor: Screenshot or copy-paste into a spreadsheet
Airbnb: Export from your inbox history
Yelp: Manual copy (unfortunately)

I ended up with 127 reviews total. Put everything into a simple spreadsheet with columns: Date, Platform, Rating, Review Text, Our Response, Response Date.

Step 2: Calculate Your Response Metrics (20 minutes)

I tracked five numbers that told the real story:

Response rate by platform: Google 89%, TripAdvisor 67%, Airbnb 45%, Yelp 34%
Average response time: 3.2 days overall (completely unacceptable)
Response rate by star rating: 5-star 71%, 4-star 68%, 3-star 91%, 2-star 100%, 1-star 100%
Average response length: 47 words
Responses mentioning guest by name: 41%

The pattern was obvious: we rushed to respond to problems but treated happy guests like an afterthought.

Step 3: The Personalization Test (45 minutes)

I read every response we'd written and marked them as:

Template (could apply to anyone): 64 responses
Semi-personal (mentions specific detail from review): 48 responses
Fully personal (references specific experience + invites back): 15 responses

Then I cross-referenced these against our booking system. Guests who received fully personal responses returned at a 68% rate. Template responses? Just 14%.

That's when it clicked: our generic "Thank you for your review!" responses were actively costing us revenue.

Step 4: Identify Your Response Debt (15 minutes)

I categorized unanswered reviews:

14 five-star reviews from 30+ days ago (too late to respond naturally)
8 four-star reviews from the past two weeks (still salvageable)
3 three-star reviews from last month (needed immediate attention)

Each unanswered review represented a missed conversation. I calculated the cost: if our average booking value is $340 and personalized responses convert at 68%, those 14 five-star reviews represented roughly $3,200 in lost repeat business.

Step 5: Set New Response Rules (10 minutes)

Based on the audit, I implemented three hard rules:

48-hour maximum response time for all reviews, regardless of rating
Every response must include: Guest name, one specific detail from their review, one specific detail about our property/service, invitation to return
Minimum 75 words for 4 and 5-star reviews (our data showed shorter responses performed worse)

I also assigned platform priorities based on where our guests actually came from: Google first (48% of bookings), TripAdvisor second (31%), then Airbnb and Yelp.

Step 6: Clear the Backlog (ongoing)

I spent 90 minutes writing personal responses to those 11 salvageable reviews. For the older ones, I decided not to respond—a response 60 days later looks worse than no response.

For ongoing responses, I started batching them: Monday and Thursday mornings, 30 minutes each session. This consistency made a huge difference.

The Tool That Made This Sustainable

Honestly, writing personalized 75+ word responses twice a week was burning me out by month two. I found ReviewReply which generates responses that actually sound personal—you can customize the tone and it pulls specific details from each review. The free version (3 responses per day) covered my Monday sessions, and the Pro plan ($9/month) handled both days.

It's not magic—I still edit probably 30% of responses—but it cut my response time from 60 minutes to about 20 minutes per session.

The Results After Six Months

Response rate: 96% overall (up from 71%)
Average response time: 18 hours (down from 3.2 days)
Repeat booking rate: 41% (up from 23%)
Additional revenue from repeat guests: approximately $31,000

The audit itself took less than two hours. The systems I built from it completely changed how guests perceive our business.

Run your own audit this week. You'll be surprised what the numbers tell you.

The Tuesday Morning Review Response System That Saved Me 4 Hours a Week

Anders Dahl Rasmussen — Mon, 14 Sep 2026 07:06:21 +0000

The Tuesday Morning Review Response System That Saved Me 4 Hours a Week

I used to spend between 45-60 minutes every single day responding to reviews across Google, Yelp, and TripAdvisor for my coffee shop. That's roughly 5-6 hours per week of writing "Thank you for your kind words!" and carefully crafting diplomatic responses to complaints about parking.

Last year, I switched to a batching system that cut this down to about 90 minutes per week. Here's the exact process.

Why Daily Review Responses Are Killing Your Productivity

When you respond to reviews throughout the day, you're constantly context-switching. You might be prepping for lunch service, then see a notification, stop what you're doing, craft a response, and try to get back into your workflow.

Research shows context-switching can reduce productivity by up to 40%. For a small business owner, that's devastating.

But here's the thing: responding within 24-48 hours is perfectly acceptable. Google's own business guidelines suggest responding "within a few days." You don't need to reply within an hour.

The Tuesday Morning System

Here's what I do now:

Tuesday, 8:00-9:30 AM: Review response time

I batch all reviews from the past week
I work in a quiet corner before the shop gets busy
I use a spreadsheet to track which reviews need responses (more on this below)

Why Tuesday? Monday is chaos. By Tuesday, you've settled into the week and can think clearly. Friday is too late for reviews that came in on Monday.

The Three-Category Method

I sort every review into one of three categories:

Category 1: Five-star reviews with specific details (40% of reviews)

These get personalized responses. If someone mentions they loved the cortado or appreciated how we handled their dietary restriction, I reference that specifically.

Example: "So glad the almond milk cortado hit the spot! Our barista Maya has been perfecting that ratio for months."

Time per response: 2-3 minutes

Category 2: Generic positive reviews (35% of reviews)

These are your "Great service!" and "Love this place!" reviews. They get warm but efficient responses.

Example: "Thanks so much for the kind words! Hope to see you again soon."

Time per response: 30-45 seconds

Category 3: Critical reviews or reviews mentioning problems (25% of reviews)

These get the most time and attention. I have a framework:

Acknowledge their specific concern
Apologize if appropriate (without admitting fault if it's unreasonable)
Explain what we're doing about it OR provide context
Invite them back

Time per response: 4-7 minutes

The Tracking Spreadsheet

I keep a simple Google Sheet with columns:

Review date
Platform (Google/Yelp/TripAdvisor)
Star rating
Category (1/2/3)
Responded? (Y/N)
Notes

This takes 30 seconds per review to update but prevents me from missing anything or double-responding.

The Template Library (But Make It Personal)

I have a document with response frameworks—not copy-paste templates, but structural guides.

For a 5-star review mentioning staff:
"[Acknowledge compliment] + [Name the staff member if possible] + [Personal touch about what makes them great] + [Forward-looking statement]"

For a complaint about wait times:
"[Acknowledge frustration] + [Explain context without making excuses] + [What we're doing] + [Invitation to contact directly]"

These frameworks keep me consistent without sounding robotic.

Tools That Actually Help

For Category 2 and 3 reviews where I need a starting point, I'll sometimes use ReviewReply to generate a draft response. It handles Google, Yelp, TripAdvisor, and Airbnb reviews and gives you 3 free responses a day without even signing up. I'll paste in the review, get a draft, then personalize it with specific details about my business.

The key word is draft. I never copy-paste AI responses verbatim, but having a solid starting structure for those tricky negative reviews saves me from staring at a blank screen.

The Results After Six Months

Before this system:

5-6 hours per week on reviews
Missed about 15% of reviews
Responses felt rushed and generic

After:

90 minutes per week
100% response rate
More thoughtful, personalized replies
Actually enjoy the process now

The Tuesday morning slot is now blocked in my calendar like any other important meeting. My staff knows not to interrupt unless it's urgent. And those 4 hours I saved? They went into actually improving the business based on review feedback.

That's the real win.

TripAdvisor vs Google Reviews: Why Your Response Strategy Should Differ

Anders Dahl Rasmussen — Mon, 14 Sep 2026 07:04:45 +0000

TripAdvisor vs Google Reviews: Why Your Response Strategy Should Differ

Owners often treat every review platform the same way, copy-pasting one response style everywhere. But the audience reading your reply — not just the reviewer — is different on each platform, and that should change how you write.

Google: Local Searchers, Skimming Fast

Most people reading a Google review response are deciding, right now, whether to visit today. Your reply needs to be short, resolve the concern quickly, and get out of the way — because the next thing they do is close the tab and walk over, or don't.

TripAdvisor: Trip Planners, Reading Ahead

TripAdvisor readers are often planning a trip weeks out, reading through many reviews in one sitting to build an overall impression. A slightly longer, more detailed response works better here — it's being read as part of a research session, not a five-second decision.

The Practical Difference

On Google: "Sorry about the wait Tuesday — we've adjusted staffing for peak hours. Hope you'll give us another shot." Short, resolves it, done.

On TripAdvisor, the same issue can support a fuller response: what happened, what specifically changed, and an invitation — because the reader has the patience and context to actually absorb it.

What Stays the Same

On both platforms, specificity beats generic language, and responding at all beats staying silent. The difference is pacing and depth, not principle.

About

Built by Anders Rasmussen. hello@baseaitools.com

Affiliate Program

30% recurring commission. Join here.

13 Etsy Tags That Actually Get You Found in Search

Anders Dahl Rasmussen — Sat, 08 Aug 2026 06:45:48 +0000

13 Etsy Tags That Actually Get You Found in Search

Etsy gives every listing exactly 13 tags. Most sellers waste half of them repeating words already in the title, or using broad terms so competitive that a new shop has no chance of ranking.

The Mistake: Tag Duplication

If your title already says "handmade ceramic mug," using the tag "ceramic mug" again wastes a slot. Etsy's search algorithm already indexes your title — tags should cover ground the title doesn't.

What 13 Tags Should Actually Cover

3-4 tags: exact long-tail phrases. "Gift for coffee lover," "housewarming gift pottery" — specific enough that competition is lower and buyer intent is higher.

2-3 tags: material and style. "Stoneware," "minimalist," "rustic farmhouse" — the descriptive words buyers actually type alongside a product category.

2-3 tags: occasion or recipient. "Mother's day gift," "gift for him," "wedding favor" — Etsy shoppers frequently search by who the gift is for, not just what it is.

2-3 tags: use case. "Coffee mug," "desk accessory," "office gift" — how the item is actually used, which may differ from how you'd describe it.

1-2 tags: your differentiator. Whatever makes your specific listing different from the other 4,000 mugs on Etsy — hand-painted, locally sourced clay, made to order.

Why Broad Tags Backfire

A tag like "mug" has enormous search volume and enormous competition. A new or small shop ranking on page 40 for "mug" gets zero clicks. The same shop ranking on page 1 for "hand-painted stoneware mug gift" gets found by exactly the buyers who want that.

About

Built by Anders Rasmussen. hello@baseaitools.com

Affiliate Program

30% recurring commission. Join here.

Turn One Podcast Episode Into 10 Pieces of Content: The Exact Workflow

Anders Dahl Rasmussen — Sat, 08 Aug 2026 06:45:18 +0000

Turn One Podcast Episode Into 10 Pieces of Content: The Exact Workflow

Recording a podcast episode is maybe 20% of the work that should happen around it. Most of the value gets left on the table because repurposing feels like a separate project instead of a five-minute step.

The Workflow

1. Pull the transcript. This is your raw material for everything downstream — most podcast hosting tools generate one automatically.

2. Find 3 quotable moments. Look for a sentence with a strong opinion, a surprising number, or a clear before/after. These become standalone social posts.

3. One LinkedIn post per episode. Take the single best insight and expand it into 150-200 words — not a summary of the episode, a standalone thought that happens to reference it.

4. One Twitter/X thread. Break the episode's main argument into 5-7 tweet-length points.

5. Show notes that double as a blog post. Instead of a bare timestamp list, write 2-3 sentences of context per section — now it's real, indexable content instead of a list Google ignores.

6. Audiogram clips for the 2-3 best 30-second moments. These perform disproportionately well because they combine audio authenticity with visual scrollability.

7. An email newsletter blurb. Two sentences and a listen link, sent to your existing list.

Why Most People Skip This

It feels like a second job. But each of these seven pieces takes minutes once the transcript exists — the bottleneck was never the work, it was starting from a blank page each time instead of extracting from something that already exists.

About

Built by Anders Rasmussen. hello@baseaitools.com

Affiliate Program

30% recurring commission. Join here.

The Freelance Proposal Structure That Wins 3x More Clients

Anders Dahl Rasmussen — Sat, 08 Aug 2026 06:44:47 +0000

The Freelance Proposal Structure That Wins 3x More Clients

Most freelance proposals fail before the client finishes the first paragraph — not because the freelancer isn't qualified, but because the structure buries the one thing the client actually wants to know: do you understand my problem?

The Structure

1. Restate the problem in their words, not yours. Open by reflecting back exactly what they told you, using their language. This does more to build trust in three sentences than a full bio does in three paragraphs.

2. One sentence on your approach. Not a full methodology — just enough to show you have a plan, not just enthusiasm.

3. Scope, in a short list. Bullet points, not prose. Clients scan proposals; dense paragraphs get skipped.

4. Price, stated plainly. Bury it and clients assume you're hiding something. State it once, clearly, with what's included.

5. A specific next step. "Let me know if you have questions" is passive. "I can start Monday if we confirm by Friday" moves things forward.

Why This Order Matters

Clients decide whether to keep reading in the first two sentences. If those two sentences are about you — your experience, your years in the industry — you've lost the moment where you could have shown you understood them.

The Mistake Most Proposals Make

They lead with credentials. Credentials matter, but they answer a question the client hasn't asked yet ("why should I trust you") before answering the one they're actually asking ("do you get what I need").

About

Built by Anders Rasmussen. hello@baseaitools.com

Affiliate Program

30% recurring commission. Join here.

The Airbnb Welcome Message Template Guests Actually Read

Anders Dahl Rasmussen — Sat, 08 Aug 2026 06:44:16 +0000

The Airbnb Welcome Message Template Guests Actually Read

Most welcome messages are too long, too formal, or arrive at the wrong moment. Guests skim them in the taxi from the airport. If yours reads like a legal document, the useful parts get lost.

The Three Moments That Matter

A welcome message earns its place if it hits these three things, in this order:

1. How to get in. Door code, key location, or meeting point — first line, no exceptions.

2. Wifi, immediately. Name and password, formatted so it can be copy-pasted, not retyped from a sentence.

3. The one thing that always confuses guests. Every property has one: the finicky shower knob, the trash schedule, the elevator that only goes to floor 4. Say it once, clearly, before they discover it the hard way.

What to Leave Out (Or Move Elsewhere)

House rules, checkout procedures, and long neighborhood guides don't belong in the first message. Guests are tired and want to get inside. Send those as a separate message once they're settled, or link to a house manual.

A Structure That Works

Something like this covers it in four lines:

"Hi [Name], welcome! Door code: 4471#. Wifi: HarborView / password: bluewater22. Heads up — the shower needs a firm turn to get hot water, give it 10 seconds. Anything else, just message me here."

Four lines, effectively. Everything a jet-lagged guest actually needs, nothing they have to scroll past to find it.

Why Short Wins

The goal of a welcome message isn't to sound thorough — it's to get answered questions out of your inbox before they're asked. A four-line message that gets read beats a ten-paragraph message that gets skimmed.

About

Built by Anders Rasmussen. hello@baseaitools.com

Affiliate Program

30% recurring commission. Join here.