Annual raises, pricing, branding, and hiring for small startups

Executive overview

Growing bootstrapped SaaS teams face recurring operational questions: how to set fair pay, when to announce pricing changes, whether branded free plans are worth it, and how to find people who thrive in small teams. Rob Walling and Josh Pigford work through listener questions covering all four.

The common thread: small-team founders over-complicate these decisions — most answers come from testing, not policy.

Annual pay raises

• Standardise compensation using salary surveys (Buffer's formula or Radford surveys) rather than ad hoc negotiation.
• Base raises on performance and skill progression, not tenure — someone who improves gets more; someone who hasn't gets feedback.
• Market-rate anchoring matters: salaries drift below market over time and employees notice before you do.
• A structured range (e.g. 3–5%) beats arbitrary amounts — top performers get the ceiling, underperformers get a conversation first.
• Annual reviews shouldn't deliver surprises; feedback should be ongoing throughout the year.
• Contractors-only is a legitimate alternative if managing W-2 employees feels like too much overhead.

Announcing price increases

• No blog post needed for a standard price increase — almost no one is watching your pricing page closely enough to care.
• Exception: use a price rise as a limited-time promotion (email list only) to drive a rush of sign-ups before the deadline.
• Test pricing changes silently first; only make them public once you're confident you'll keep them.
• Founders should be adjusting pricing regularly — most early-stage products are underpriced.

Branded free or discounted tiers

• Don't offer a lower-priced plan where the only difference is showing your branding — price-sensitive customers rarely generate useful traffic.
• Better model: include branding on all sub-premium plans by default; charge significantly more to remove it as part of a higher tier with other benefits.
• Test virality before changing pricing: add the branded link to your existing plan and measure click-throughs with UTM parameters for a few months.
• Branding links work better as an awareness play than a conversion engine — think advertising, not referral loop.

Finding good startup people

• Prioritise candidates who have been self-employed or freelanced — they already wear many hats and self-manage by necessity.
• Look for people at large companies who are unhappy there; they understand the trade-offs and want out.
• Remote-first experience is a strong proxy for self-management ability.
• Useful job boards: We Work Remotely, Authentic Jobs, Dynamite Jobs, Remote OK.
• Communities like MicroConf Connect have a jobs channel used by founders and aspiring founders.
• Avoid candidates who are optimised for a single narrow specialty — early-stage teams need generalists.

Full-time vs. contract developers

• Contract-first for 3–6 months is a useful trial: validates there's enough work before asking someone to quit a stable job.
• Full-time is preferable for core development roles once work volume is confirmed — loyalty, focus, and team cohesion follow.
• Contractors suit marketing, sales, and ops roles where scope is more variable.
• Long onboarding time (3+ months to productivity) makes contract engagements harder for complex back-end roles.

Using recruiters

• In-house recruiters at larger companies are highly effective — they post jobs, filter resumes, run initial screens, and handle negotiation.
• For small teams: find a recruiter willing to do a flat-fee engagement ($3,000–$5,000) rather than a percentage-of-salary deal.
• Dynamite Jobs offers a recruiter-style service at a published flat rate.
• Founders should not be filtering 100 resumes down to 10 — that work can and should be delegated.